An engineering firm,
not an agency.
The distinction matters. An agency optimises for the pitch. We optimise for the eighteenth month — when the team has changed, the requirements have moved, and the only thing holding the product up is the quality of the decisions made at the start.
Flowstate LLP builds operational software — the systems a business runs on rather than the ones it shows off. Fleet telematics that has to survive a vehicle leaving coverage. Procurement workflows that have to satisfy an auditor. Asset registers that have to reconcile to the ledger exactly. Ledgers that have to reconcile exactly.
That work has a particular character. It is less forgiving than consumer software, because the failure mode is not a bad review — it is a truck dispatched to the wrong depot, an invoice paid twice, or a line stopped. It rewards engineers who ask what happens when the network is gone, when the data is malformed, and when the person using this has been on shift for ten hours.
We also do the newer work — LLM applications, agentic automation, smart contracts — and we apply the same standard to it. An evaluation harness before a demo. An audit before value moves on-chain. The technology is new; the engineering discipline is not.
Six things we will not
trade away for a deadline.
- 01
We will talk you out of things
The most valuable sentence in a first meeting is often 'you do not need this'. We have recommended against Kubernetes, against blockchains, against rewrites and against AI features, and we would rather lose that work than deliver something you regret paying for.
- 02
Estimates come after understanding
A number produced before anyone has looked at the constraints is a guess wearing a suit. We run a paid shaping engagement first, and the fixed quote comes out of that. You keep the plan either way.
- 03
The boring layer goes in first
Data model, authentication, deploy pipeline, observability. These are unglamorous, invisible in a demo, and the exact things whose absence forces a rewrite eighteen months later.
- 04
Nothing is a black box
You own the code from the first commit. Documentation, architecture decision records and runbooks are deliverables, not favours. The measure of an engagement is whether your team can carry it without us.
- 05
Bad news travels fast
If something is late, wrong or harder than we thought, you hear it that week — not at the end of the milestone when it is too late to change course. Surprises are a process failure.
- 06
One standard across every practice
A fleet telematics pipeline and a marketing site get the same discipline: typed, tested where it counts, deployed by pipeline, documented. Breadth is only defensible if the floor does not move.
Three ways
this usually runs.
8–16 weeks
Fixed scope
A defined build with a fixed price and date, quoted after a paid shaping week. Best when the outcome is clear and the scope can genuinely be held still.
Monthly, rolling
Embedded squad
A named team working alongside yours on a monthly basis, in your rituals and your repository. Best for ongoing product work where priorities move.
1–4 weeks
Advisory
Architecture review, technology selection, due diligence or fractional CTO cover. Short, sharp, and ending in a document you can act on.
How an engagement
is resourced.
A small senior core scopes, architects and stays accountable for every engagement from the first call through to handover. Around that core we assemble a team matched to the work — engineers brought in per project rather than carried as overhead.
You will always know exactly who is on your project and who answers for it. You will not be handed to an account manager, and the person who scoped the work does not disappear once it is sold.
This is worth saying plainly because it is a better structure than the alternative, not a smaller version of it. At a sixty-person shop the person who sells and the person who builds frequently never meet, and the gap between what was promised and what was understood is where most software projects go wrong.
The trade-off is real and we will not hide it: we take on fewer engagements at once than a larger firm, and if we are full we will tell you rather than stretching a team across your project.
Worth a conversation?
Tell us the outcome you need and the constraints you are under. We will tell you whether we are the right firm, what it would take, and roughly what it would cost.