The price is set on the bottleneck — never on the work.
This is outcome as a service: you buy the bottleneck gone, not the effort spent removing it. There are no man-hours on the invoice and no FTE contract behind it, because the principal who scoped the outcome is the one who delivers it — so the cost of getting it wrong is ours, not a change request. How the delivery model works →
Companies that want the result run for them go through Usage — we measure the bottleneck, carry the cost of fixing it, and get paid per transaction once it moves. Companies that must own and operate what they buy go through Licence — one number for the bottleneck, full source delivered, every scope change free.
There's no wrong door. Some of the businesses we've now been inside for twenty years started with a single Licence build. As trust compounds, the door sometimes changes: a team that started on Licence later hands us a bottleneck to run on Usage; a team on Usage asks us to build the next three systems outright. What doesn't change is the promise — three years, no questions, on either door.
And if it slips, we keep building. No questions. For three years after done, if the number falls, we re-engineer whatever it takes to bring it back — free, whatever the cause. Not bug versus change, not your data versus our code. Both Usage and Licence carry this promise — it's what makes this outcome-based, not just effort-based work with a different invoice.
Usage — it starts the day the number moves.
This is Discovery, the build and launch, and the work of holding the number where it should be — all as one engagement. We don't ship the software and leave.
- Discovery — a short diagnostic to name the bottleneck, measure the number and agree what solved means
- Build and launch — typically live within weeks, instrumented to the number from day one, at our cost
- Done — and held — done is when the number holds unattended for the agreed period; we keep watching it, every week, for as long as we're engaged
You get the full source code, with a perpetual right to run, brand, host and modify it as your own. The only real limits: you can't resell it or offer it to others as a competing service. Read the full licence terms →
One basis, agreed at Discovery: a small fee per transaction the system processes.
Usage, per transaction.
The system processes countable units of value — an application decisioned, a booking made, an order fulfilled — and you pay a small fee per transaction. The fee is designed as a small fraction of the value each transaction creates: think card processing, not consulting retainers. No transactions that month, nothing owed.
It starts at go-live.
The meter starts the day the operation runs through the system — nothing is billed before that. The outcome itself is judged over the following quarter, against the baseline measured at Discovery. If the system isn't running, you aren't paying.
The engagement runs on Outcome, our operating platform: it tracks the result on pace, manages adoption, and meters the billing — so every invoice ships with its basis of computation, the exact count × rate that produced the number. Nothing is invoiced on faith, including ours.
An illustration, not a quote: a lender processes 5,000 loan applications a month through a system we built and run. Each processed application carries a per-transaction fee agreed at Discovery — a small fraction of the margin each application creates. The monthly invoice is one line: 5,000 × the rate, with the count drawn from the system's own telemetry, verifiable against your records. A slow month means a smaller invoice. That's the design.
Licence — one number for the bottleneck.
For organisations that must own and operate what they buy. One number, agreed before we write a line of code. Every scope change on the way to done is free.
- Full source delivered — under a source-available licence, yours from day one
- Working software within weeks — steady, visible progress you can use
- Milestones tied to the number — moving, not to deliverables
- No change requests, no timesheets — the final payment is due only at done
One capital fee — quoted before we write a line of code. We name the bottleneck with you at Discovery, price it as a single number, and you know the full cost upfront. Source is included. What the solution turns out to be is our problem; you never see a change request.
Milestones tied to the number — not to deliverables. The final tranche falls due at done: when the operation runs end to end and the number holds. The outcome is then judged over the following quarter, and No Questions covers it for three years after.
No rate card, no timesheets, and the code is yours from Day 1. Turnkey is this door →
Questions a CFO would ask.
Not sure which fits? Let's find out together.
The shape is above; the exact numbers are set at Discovery — sized to your transaction value, with the math shown from the first invoice to the last. A short Discovery names the bottleneck, measures the number, and tells you which door it goes through.