Pricing
Priced after we look.Never before.
There is no price list on this page, and that is not a negotiating tactic. A build is shaped around one operation, so a menu price would be wrong for almost everyone who read it. What we can do is show you exactly how the number gets set, before you spend thirty minutes with us.
The anchor
You already knowthe number.
A build is priced against whatever you were going to do about this instead, and that is different for everyone. Some arrive having just decided to hire. Some are paying a capable team to spend its week on work that repeats. Some have just renewed a stack of tools for another year, or pay an agency monthly for something that never compounds. Some have simply decided the current shape of the operation cannot carry another year of growth.
Whichever it is, it has a number attached, and you know yours better than we do. That is the anchor: not our rate card, but the thing this work is currently costing you.
Which is also why the audit is free. If the honest answer is that your alternative is cheaper, you should hear that from us in half an hour rather than find out after an invoice.
How it runs
Free, then fixed,then optional.
Three stages, and you can stop after any of them.
01
The audit
Free. Thirty minutes on your real numbers, ending in a verdict: build, wait, or not a fit. You keep the map either way.
02
The build
Scope and price fixed in writing before any work starts. One number, agreed up front, covering the whole build.
03
The retainer
Optional and monthly. Stop it whenever you like and the system keeps running, because it was yours from the first commit.
What moves it
Four thingsset the price.
When we quote, these are what we are actually weighing. None of them are mysterious, and you can make a decent guess at your own build before we ever speak.
01
How much operation
One agent taking one job off your desk is a different build from a layer running several departments.
02
How many systems
Every tool the system reaches has to be wired and tested. Well documented APIs are quick. Stubborn ones are not.
03
How strange the edges
The rules that live only in your head are the valuable part and the slow part. Mapping them properly is most of the work.
04
How much is new
Replacing something that already works is faster than designing a process that has never existed.
Against the alternative
Whatever you weregoing to do instead.
Five ways operators arrive at this decision. Find the row that sounds like yours, and price the build against that.
What it costs you now
What a build does instead
A new hire
What it costs you now: A salary every year, plus employer costs, and weeks of ramp before they help.
What a build does instead: Paid once, useful the day it ships, and it does not resign.
The team you have
What it costs you now: Capable people spending their best hours on work that repeats.
What a build does instead: The repeating part runs itself. They get back to the work you hired them for.
Another tool
What it costs you now: A subscription that renews forever and fits the average business in your category.
What a build does instead: One build shaped to yours, with no licence to keep paying for.
An agency or freelancer
What it costs you now: A monthly retainer where nothing compounds and the knowledge sits with them.
What a build does instead: A system that compounds, documented in a repo you own.
Leaving it as it is
What it costs you now: The work grows with the business, and someone absorbs it. Usually you.
What a build does instead: The queue clears overnight, with your sign-off on anything that matters.
One row is missing on purpose. A person weighs the genuinely new case and decides. A system cannot, which is why everything it prepares stops for you before it acts.
When not to buy
Four reasonsto walk away.
We would rather lose the deal on the call than lose it after the build. If one of these is you, say so and we will tell you straight.
You are pre-revenue or very early
There is no operation to systemise yet, so a build would be guesswork dressed up as software. Come back when the work repeats.
The work does not repeat
A build pays back on rhythm and volume. If the painful thing happens twice a year, a system is the wrong answer and we will say so.
You want the cheapest option
This is a build, not a subscription. Cheap builds get rebuilt, and the second one costs more than doing it properly first.
You want AI with nobody in the loop
Everything we make stops for a human before it acts. If you want a system that runs unattended on your customers and your money, we are not it.