Find your growth opportunity Book a Discovery →
Pricing

Two ways to work with us.

Two ways to start — and no wrong door. Companies that want the result owned end-to-end start with Strategy + Build. Companies with their own technology teams usually start with Build Only. Many of our deepest engagements began as a single fixed-scope build.

Strategy + Build → Build Only →
Two doors, one relationship

Most engagements begin one of two ways.

Companies that want the result owned end-to-end start with Strategy + Build — we find the bottleneck, invest the build ourselves, and get paid as it runs. Companies with their own technology teams usually start with Build Only — your team drives, we build to your specification, you own the code from day one, and nothing about how you work has to change.

There's no wrong door. A fixed-scope build is how many of our longest relationships began — some clients we've now been inside for twenty years started with a single project. As trust compounds, the engagement usually does too: teams that started with Build Only later hand us an outcome to run; teams that started with an outcome ask the Factory to build the next three systems. The model can change. The relationship is the constant.

For Strategy + Build, there is no upfront CAPEX. We carry the cost of Discovery and the build ourselves. You start paying only when the system is live and running — and every invoice shows the exact math that produced it.

Our core engagement

Strategy + Build — we stay in it with you.

This is Discovery, the build, and the ongoing work of watching whether it actually moves the number — all as one engagement. We don't ship the software and leave.

  • Discovery — half a day to find the bottleneck and set the target
  • The build — live in under three weeks
  • Ongoing monitoring and tuning — we keep watching the number, 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 →

How it's billed

One fee basis per engagement, agreed at Discovery — whichever honestly fits how your value is created:

A toll per transaction.

Where the system processes countable units of value — an application decisioned, a booking made, an order fulfilled — 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.

A share of the result.

Where the outcome is a movement in a number rather than a count — margin recovered, working capital freed, capacity unlocked — the fee is a share of the movement you actually gained, measured against the baseline set at Discovery. If the number doesn't move, the fee reflects it.

A fixed project price.

Where neither basis can be measured honestly, we say so — and price it as a fixed project instead. The accountability doesn't change, only how you pay for it.

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.

What the math looks like

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.

Also available

Build Only — just the build.

For teams that already know their direction and just need the software built. Your team sets the direction; we bring the build engine. No consulting layer, no monitoring overhead — we build what's been specified, deliver it, and the code is yours. If the relationship grows from there, that's earned, not assumed.

  • Custom software and AI agents — built to your specification
  • Working software every 21 days — steady, visible progress you can use
  • A dedicated delivery team — with you throughout the build
  • You own the code from Day 1 — deployed on your infrastructure, yours to keep
How it's billed

Turnkey — a fixed scope, quoted before we write a line of code. We spec the build with you, calculate the price from the specification, and you know the full cost upfront. Best for a defined system with a clear end state.

Subscription — a dedicated team with a fixed monthly output and a fixed monthly price, for teams building continuously rather than once — scaling with output as your build does.

Either way: the same methodology, the same AI-accelerated pipeline, and the code is yours from Day 1.

The fine print, in plain language

Questions a CFO would ask.

What does Discovery cost?
Nothing. Discovery is how we decide, together, whether there's an engagement worth doing — charging for it would put us on the wrong side of that question. You leave with the bottleneck named, the target metric set, and our proposed billing basis, whether or not you go further with us.
What counts as a transaction?
It's defined in the engagement agreement before go-live — a specific, countable event the system processes (an application decisioned, a booking confirmed, an order fulfilled), measured by the system's own telemetry. You can verify every count against your own records; the invoice shows it.
Is there a minimum, or a cap?
No monthly minimum — if the system doesn't run, you don't pay. Caps and volume tiers can be agreed at Discovery where volumes are large or seasonal, so the fee stays a small fraction of the value created at any scale.
Our volume is seasonal. Do we pay in the quiet months?
Only for what runs. The fee follows your transactions, so a quiet month means a small invoice and a dead month means none. That's not a concession — it's the point of the model.
How do we end the engagement, and what do we keep?
You keep everything. Full source code, with a perpetual right to run, brand, host and modify it as your own — the only limits being resale or offering it to others as a competing service. The engagement ends on notice terms agreed upfront; nothing about your live system depends on us staying.
Who hosts it, and who pays for infrastructure?
It runs on your infrastructure — your cloud accounts, your data, inside your walls. Infrastructure costs are yours and are sized transparently during the build; they're typically a small fraction of the transaction value flowing through the system.
What happens if the outcome doesn't land?
The fee reflects it — that's the design, not an exception. A toll produces no invoice without transactions; an outcome share produces no fee without movement in the number. And your live system never hard-locks over billing: entitlement fails open, by design.
Why don't you publish a rate card?
Because an honest rate depends on what a transaction is worth in your business — a decisioned loan and a confirmed booking don't carry the same value, and pretending one rate fits both would make the fee arbitrary. What we publish instead is the discipline: the fee is a small fraction of the value created, set at Discovery, and shown in full on every invoice.
Start with understanding, not assumptions

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. Start with a conversation, and we'll work out which shape fits.

Book a Discovery → Find your growth opportunity →