How We Scope and Price

Transparency

How we scope and price a project.

Here is a real estimate we produced for a client — anonymised, but otherwise exactly as it was delivered. Most agencies would never show you this. That’s rather the point.

Why we’re showing you this

The single biggest fear a client has when hiring a software team is not that the work will be bad. It’s that the number will move. That the quote was a hook, and the real cost arrives later, in pieces, once you’re too committed to walk away.

The only honest answer to that fear is to show you how the number is built. So here is a genuine estimate: the phases, the hours, the team, and — importantly — the assumptions it depends on. If those assumptions break, the number moves, and we tell you before it does.

The estimate

A web platform with user accounts, real-time state and third-party integrations

Client and product anonymised. Everything else is unchanged.

PhaseHoursWhat that covers
Database design25Schema design, plus review iterations
Wireframes48Every screen, agreed before a line of code
UI development110Front-end build against the wireframes
Backend development350The actual system — APIs, logic, integrations
Testing60Functional QA across every module
Deployment20Database and application install, live testing
Total613 hours

Notice the shape of it. Backend is 57% of the effort. Design and wireframes together are 12%. That ratio is normal and it is worth understanding: the expensive part of software is almost never the part you can see. Anyone quoting you mostly for screens is quoting you for the easy half.

Who does the work

2 × Backend developer
Full time
1 × Front-end developer
Full time
1 × QA
Part time
1 × Project manager
Part time

No account managers. No “engagement leads”. The people on your project are the people building it.

The assumptions — the part nobody shows you

An estimate is only true if its assumptions hold. These are the ones that were attached to the number above. Every quote has assumptions like these. Most agencies just don’t tell you what they are — which is precisely how a fixed price quietly stops being fixed.

  • Logo and email addresses are supplied by the client; we integrate them.
  • The client purchases any third-party extensions and provides access.
  • Email content for automated messages is supplied by the client.
  • Hosting is the client’s choice; we default to a standard provider if unspecified.
  • Questions from the team get an answer within two working days — silence stalls the build.
  • If the agreed scope changes, the price changes — and we tell you the cost before we do the work, not after.

That last one is the whole contract in a sentence. It is the difference between a fixed price and a hostage situation.

What’s different now

That estimate is from our pre-AI era, and we’re showing it because the structure of honest scoping hasn’t changed. What has changed is the hours.

AI agents now do a large share of the scaffolding, the test writing and the documentation — the repetitive volume that used to consume a great deal of that 350-hour backend figure. Our engineers still design the system, review every line and own the result. The judgment is unchanged. The typing is not.

That’s the entire reason our prices look the way they do. Not a discount, not a loss-leader — a genuinely lower cost of production, passed on rather than pocketed. See our published pricing →

Want an estimate like this for your project?

Fixed scope, fixed price, and the assumptions written down. Within one business day.

Start the conversation
Scroll to Top