One number, agreed before we start
You pay when something actually arrives.
A written scope, a fixed 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.
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.
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
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
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
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
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.
You raise it
A message is enough. No forms, no change-control board, no waiting for a weekly meeting.
Any time
We quote it in writing
Cost, impact on the delivery date, and what it displaces if the date must hold.
Within 48 hours
You approve or drop it
Nothing starts until you say yes in writing. Nothing appears on an invoice you did not approve.
Your call
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 →Keep exploring
Services behind it
Case studies
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.