Company
We build it.
We run it.
We stand behind it.
FlowZa builds and operates its own cloud applications, with the people behind the products staying close to the businesses that rely on them. From product design and engineering to infrastructure and support, we take ownership of the entire experience—so we can keep improving what we build and deliver lasting value to our customers.
How the team works
Six working agreements
we actually keep.
These are not values on a wall. Each one costs us something specific, which is the only reason they survive contact with a quarter that is going badly.
No bespoke forks
We do not build a bespoke version of an application for a large customer. If something is worth building it goes into that application for everyone, and if it is not, we say no. This loses deals. It is also the reason an upgrade has never split the customer base.
Engineers do implementation
The person mapping your chart of accounts also writes the code for the application it runs in. It makes implementation more expensive per hour and much cheaper overall, because the awkward parts get fixed in the application instead of worked around in a configuration.
Support can ship a fix
Everyone on support has commit access and a path to production. A ticket that turns out to be a bug does not become a backlog item in another team’s queue.
We publish what breaks
Every customer-affecting incident gets a written review, published, with the timeline and the contributing causes. Not a status badge — the actual account of what we got wrong.
No change without a migration path
A schema change ships with the migration that carries existing data across, and both are reviewed together. Anything that would require customers to do the work themselves does not ship.
The roadmap follows the constraint
We build what unblocks the most operators, not what wins the most feature comparisons. Sometimes that means spending a quarter on the close process while a competitor ships another dashboard.
WHERE THE TEAM SITS
Two thirds of the company works on the applications directly. A commercial team that is smaller than the support team is a deliberate choice, and it shows up in how we sell.
Coverage
Eleven hours staffed.
Thirteen on call.
Most vendors write 24×7 on the contract and route the small hours to a rota. So do we — the difference is that we will show you exactly which hours those are before you sign.
The rota is named, not anonymous
Enterprise agreements list the escalation contacts by name and the number that reaches them. You are not paging a queue.
Handover is written
An open incident moves between offices with a written state, so the next engineer does not start by asking you to repeat yourself.
Severity is defined in the contract
What counts as a P1 is written down and agreed before anything goes wrong, which is the only time that conversation is calm.
We answer for our own infrastructure
If a dependency fails, it is still our incident. We do not forward a cloud provider’s status page and call it an update.
Partners
A deliberately
small network.
We certify few partners and we publish what each one is certified for. A large partner directory is easy to build and tells a buyer nothing about who can actually deliver.
Firms certified to run a full deployment — modelling, migration, parallel run and cutover — on their own. Certification is per module family and expires annually. Every certified consultant has completed a real migration under supervision before they lead one, and we publish who is certified for what.
9 firms
4 regions
Products we maintain a first-party connection to — banks and payment rails, tax and e-invoicing regimes, carriers, identity providers and telematics. These are engineering relationships with a shared test environment, not logo swaps. If a connector breaks, the ticket comes to us.
31 connections
maintained in-house
Accountants, industry advisers and operators who send us work without implementing it themselves. Paid on a flat fee at go-live rather than a share of the subscription, so the incentive ends when the customer is live and the advice stays honest.
Open
apply below
We are not looking for volume. If you have delivered operational software in one of the sectors we serve and want to be certified, the conversation starts with a deployment you have already done.
Contact
Reach the right
person first time
A single contact form that routes everything to one inbox wastes a day of your time and ours. Pick the row that matches what you need.
Response times are the ones written into standard agreements. Enterprise agreements can tighten them, and P1 targets are contractual rather than aspirational.
| If you want to | Goes to | Typical response |
|---|---|---|
| Evaluate the platform | Solutions engineering | Same working day |
| Report something broken | Support, in-product or email | 1 hour P1 · 1 day P3 |
| Complete a security review | Trust team, via your account manager | 3 working days |
| Discuss a migration | Implementation engineering | 2 working days |
| Become a partner | Partnerships | 5 working days |
| Ask about anything else | General enquiries | Best effort |
Named contacts and direct numbers are issued with your account rather than published here, so you always have a person rather than an alias. The offices themselves are below.
OFFICES
Working here
We hire slowly and
write everything down.
Roles open irregularly because we only post one when the work genuinely exists. If you have operated the kind of business these applications run, that experience counts for more here than a framework on your CV.