Skip to content

One number, agreed before we start

Fixed price software development, paid when it actually arrives.

Our fixed price software development runs on a written scope, one agreed price and five milestones that each end in something you can open. Drag through them below and watch the invoice follow the deliverable, never the other way round.

If we estimated it wrong, that is our problem, not a variation on your invoice.

  • 6–14 wks

    Typical fixed project

  • 5

    Milestones, each with a deliverable

  • 48h

    To a written quote

  • 0

    Surprise line items

Get your free estimate

Three quick questions: scope, approach and a price range back within 48 hours. No sales call required first.

What do you need built?
When do you want to start?
Where should we send the estimate?

Answer all three questions above, then send.

NDA-friendly · IP yours from day one
One number, agreed up front. Pay against deliverables. Five milestones with artefacts. Changes quoted in writing. Exclusions listed explicitly

When it fits


Four signs fixed scope is the right model.

If two or more of these are true, a fixed project will cost you less and worry you less than a monthly team. If none are, we will recommend a pod instead, and either way what a project costs with us is written down before you sign.

  • You have a defined outcome

    A first release, a migration, a rebuild with a clear finish line. Someone can already describe what "done" looks like.

    Clear finish line

  • The budget is approved once

    Board or investor money released against a number, not a monthly rate you have to defend again every quarter.

    One approved figure

  • You need certainty over speed

    A fixed date and a fixed number matter more than the ability to change direction mid-build.

    Date and number fixed

  • Nobody in-house can run it

    No product owner spare to manage a team day to day. We bring the lead and the process with us.

    We run it

What fixed actually means


Fixed means fixed. Here is both halves of that.

The second list is the one most agencies leave off their website. It is short, specific, and agreed before you sign anything.

  • What is fixed

    What is fixed

    • The scope, written out feature by feature
    • The price, with the exclusions listed explicitly
    • The delivery date, with milestone dates behind it
    • The team: the engineers named in the scope build it
    • Design, QA and delivery management, all included
  • What is not fixed

    What is not fixed

    • Anything not written in the scope document
    • Third-party licences and cloud bills: billed at cost
    • Changes you request after sign-off, quoted separately first
    • Delays caused by waiting on your content, data or approvals

Milestones & payment


Five milestones. Each one ends in something you can open.

You pay against delivery, not against time. No milestone is signed off on a status update: there is always an artefact behind it.

  1. You get a scope document before you get an invoice.

    Feature list, exclusions, architecture decision record and a sprint plan. If you walked away here, you would still have something worth the money.

    Milestone one

    20% · Week 1–2

  2. A clickable prototype of every screen in scope.

    Your stakeholders react to something real before a line of production code exists. Changes at this stage cost nothing but a conversation.

    Milestone two

    20% · Week 3–4

  3. Working software on staging, demoed live.

    The largest payment sits behind the largest chunk of working software, not behind a status report claiming sixty per cent complete.

    Milestone three

    25% · Week 5–8

  4. Every scoped feature built, QA pass complete.

    The written test summary and the bug list come with it. Nothing is signed off on somebody saying it looks fine.

    Milestone four

    20% · Week 9–11

  5. Production release, docs, repos and 30 days support.

    The final payment is the smallest on purpose. By the time it falls due you already have everything you paid for.

    Milestone five

    15% · Week 12

Change requests


Changing your mind is normal. Surprises are not.

Fixed scope does not mean rigid. It means every change has a written price and a written date impact before anyone starts on it.

  1. You raise it

    A message is enough. No forms, no change-control board, no waiting for a weekly meeting.

    Any time

  2. We quote it in writing

    Cost, impact on the delivery date, and what it displaces if the date must hold.

    Within 48 hours

  3. You approve or drop it

    Nothing starts until you say yes in writing. Nothing appears on an invoice you did not approve.

    Your call

  4. Scope document updated

    The written scope is amended so there is one current version, not a thread of decisions.

    Same day

Start here


Send the scope. Get the number.

Even a rough feature list is enough to start. You get a written scope, milestone plan and fixed price within 48 hours.

  • Start here

    Send the scope. Get the number.

    Even a rough feature list is enough to start. You get a written scope, milestone plan and fixed price within 48 hours.

    • A scope document with the exclusions listed
    • A fixed price, not a range that moves later
    • Five milestones, each with a deliverable
    • Free, and yours to take elsewhere

FAQs · fixed-scope projects


Fixed-scope projects: frequently asked questions

Underestimates, change requests, late approvals and what happens the day after launch.

Ask us directly →
If we got the estimate wrong, that is our problem, not yours: a fixed price stays fixed and the extra hours are ours. If the scope itself turns out bigger, because something nobody wrote down is now needed, that new work is quoted as a change request in writing, and nothing is built until you approve it. This is why milestone one produces a written scope with the exclusions listed: it is the document both sides check when the question comes up.
Detailed enough that both sides would give the same answer to "is this in scope?". In practice that means a feature list, a screen list, an integration list and a written set of exclusions. You do not have to produce all of that yourself: a rough feature list is enough to start, and we turn it into the scope. The written scope, milestone plan and fixed price come back within 48 hours, free, and yours to take elsewhere.
Yes, through the change process. Send a message and within 48 hours you get a written quote with the cost, the impact on the delivery date and what it displaces if the date must hold. Nothing starts until you approve in writing, and the scope document is updated the same day, so there is only ever one current version. What a fixed price cannot carry is repeated changes of direction with the original date and price held; at that point we will recommend a dedicated team instead.
We tell you immediately and in writing what it costs in delivery days. We do not absorb it silently and then miss the date.
Yes: the first milestone, typically 20% of the price, invoiced at kickoff. It pays for the written scope, the exclusions, an architecture decision record and the sprint plan, delivered in weeks one and two. Every payment after that follows something you can open: a clickable prototype, working software on staging, a QA-complete build and the production release. The percentages are set in the scope document before kickoff, each milestone invoice is net 15, and if you walked away after milestone one you would still hold a scope worth the money.
Thirty days of support is included, and milestone five hands over the production release, the documentation and the repositories. After that, most clients move to a support retainer or a dedicated pod, but nothing obliges you to: you are free to walk away with everything you paid for. The final payment, 15%, is the smallest of the five on purpose, and it falls due only once you already hold all of it.
You do, from the first commit. Repositories and IP in your name under NDA, with commit access from day one.
Four things sit outside a fixed price: anything not written in the scope document, third-party licences and cloud bills, which are billed at cost, changes you request after sign-off, which are quoted separately first, and delays caused by waiting on your content, data or approvals. All four are agreed before you sign. Design, QA and delivery management are inside the price, not extras, and the exclusions specific to your project are listed in the scope document itself.
Fixed price is right when the work has a finish line: a first release, a migration or a rebuild that someone can already describe as done, paid from a budget approved once. A dedicated team is right when the roadmap keeps going after launch and you would rather reset priorities every sprint than raise change requests. Check the four signs on this page: two or more true points to a fixed price, none to a pod. The choice is not final, since milestone five is where a fixed project can roll into a monthly team.

Next step


One number. One date. In writing.

Send a rough feature list and you get a scope document, a milestone plan and a fixed price within 48 hours, free, and yours either way.