Pricing
No price list. A straight answer about the invoice instead.
Every project is a different size, so a number on this page would be fiction. What we can publish is how the number is built, what moves it, and what will never appear as an extra line later.
How a quote gets built.
Not a day rate multiplied by a guess. The scope is broken into named pieces, each piece is estimated, and the total is fixed for that scope.
We take the process apart
A call, then a short written summary of what you do now and where it hurts. Free, and yours to keep whether or not you hire us.
We list the pieces
Screens, integrations, roles, reports. Each one named, so you can see what you are paying for and strike anything you do not want.
We estimate each piece
Against work we have done before. This is where a reusable component library matters: we are not pricing in a rebuild of the parts that already exist.
The total is fixed for that scope
Not an estimate that drifts. If the scope stays still, the number stays still. If the scope moves, the change process handles it.
What moves the number.
Useful to know before you ask, because several of these are within your control.
Pushes it up
Integrations with systems that have no documented API
Scraping a screen or reverse-engineering an undocumented endpoint costs several times what a documented API costs, and it breaks more often afterwards.
Migrating historical data that is not clean
Moving records is cheap. Deciding what to do with duplicates, missing fields and three spellings of the same customer name is not.
More than one approver
Every additional person who can send work back adds a review cycle. This is a real cost and we would rather name it than absorb it.
Regulated or audited environments
Documentation, access controls and evidence trails all expand when someone external will inspect the result.
Brings it down
A process you have already mapped
If you can describe every step and edge case on day one, we skip the discovery that usually takes the first week.
Accepting sensible defaults
Standard authentication, standard roles, standard admin layout. Customising these is possible and rarely worth what it costs.
A narrow first version
Shipping the one workflow that hurts most, then extending, is almost always cheaper than building everything before anything is used.
One decision maker
The single largest lever on both cost and calendar, and the one clients most often underestimate.
Never an extra line.
These are inside the quoted price on every project. If any of them ever appears as an addition, we have got something wrong.
- Fixing something that does not do what the scope said it would
- The scope document itself, and the estimate
- Project communication, calls and written updates
- Handover of code, domains, accounts and documentation
- The recorded walkthrough at the end
- Defect fixes inside the warranty period
- Passing on third-party costs, which go through at cost with no margin
Why there is no number on this page.
Publishing ranges would filter enquiries better, and plenty of studios should do it. We have chosen not to, because the range honest enough to be useful would be so wide it would tell you almost nothing, and a narrow range would end up shaping the work rather than describing it.
What you get instead: a written quote within one working day of a scoping call, with the exclusions named, and no obligation. If the number does not work for you, that is a useful outcome reached quickly and at no cost.
Want the number for your situation?
One call to understand the work, then a written quote within one working day. No charge, and no pressure attached to it.