We price the working system, not the hours it takes.
A day rate prices our time. You are buying a working system. AI-first delivery has cut the time a given piece of software takes, and billing by the hour would keep that saving for us. So we price the outcome instead, and show you the comparison.
The commitment
Every proposal states what conventional delivery would cost and take, beside our number. If we cannot beat it meaningfully, we tell you and decline the work.
Pick the one that matches the shape of the problem.
All three start the same way: a senior engineer replies within one business day, a 45-minute call about the problem, and a written approach within a week.
Fixed-price phases
A defined piece of work with a clear finish line
One price per phase, agreed before we start
The default for most engagements. Within a week of the first call you get a written approach with a cost and time range. When you are ready, a fixed proposal sets out scope, price and milestones, and we carry the risk of our own estimate.
Written scope with an explicit definition of done
Fixed price shown beside a like-for-like comparison with conventional delivery
Payment on milestones you can check, not on elapsed time
Change is a new priced increment, never a surprise on an invoice
Dedicated team
Continuous product work with shifting priorities
A monthly cost, set by team shape
A named team working your backlog. It suits product companies whose roadmap moves too often for a fixed scope to stay useful. The engineers who built the system are the ones who keep improving it.
Named engineers, not a rotating pool
No minimum term: thirty days’ notice, and we help you move
You set the priorities, we hold the engineering standard
A written note every week on what shipped and what did not
Programme delivery
A large initiative delivered in several phases
Fixed price for each phase, planned as one roadmap
For replacements, platform builds and modernisation work too large to scope honestly in one go. We plan the whole programme, fix the price of each phase as it comes up, and set the architecture once so that the phases fit together.
A delivery roadmap with risks and dependencies written down
Each phase proposed and priced before it starts
Red-team week and a rehearsed rollback before every handover
Code and IP transfer to you on final payment for each phase
Where the saving comes from
Five times faster at a fifth of the cost is indicative. Here is where it comes from.
It is not one saving but four, and the fourth has nothing to do with AI. The real comparison for your project is the one in your proposal, not a figure on a web page.
First drafts written by AIBoilerplate, migrations, tests and the first draft of most modules. A named engineer reviews and owns every line, which is still far faster than writing it from nothing.
Buildless typing
Reading a system nobody understandsLegacy discovery used to be weeks of archaeology. AI reads the old system and produces a map, and our engineers then check it against how the business actually uses it.
Discoveryless archaeology
Review before reviewOrdinary mistakes are caught before a person looks, so senior review time goes on design rather than typos and missing null checks.
Reviewbetter use of seniors
Not building the wrong thingUsually the largest saving, and it has nothing to do with AI. A written scope agreed before we start removes the rework that eats most projects.
Scopeand the hard part
What we will not do
Four things, stated so you do not have to ask.
Bill for a change we caused
If we underestimated, that is our problem. A change order is for a change you asked for, and the difference is written into the contract rather than argued about later.
Take work we cannot beat the market on
If a standard product fits, we will tell you to buy it, even though it costs us the engagement. If our proposal cannot meaningfully beat conventional delivery, we decline.
Hold your code hostage
You have repository access from day one, and the code and IP transfer to you on final payment. Nothing in the stack requires us specifically.
Put a junior on it and call it senior
You are told who is on your team and at what level. The people you meet during scoping are the people who build it.
Tell us what you are trying to build. Within a week you will have a written approach with a cost and time range, and a recommendation on how to structure the work.
Seven short questions. About 90 seconds. A senior engineer reads your answers before we reply. No sales sequence, no newsletter. Just a thoughtful response about what comes next.
