A project-based contract works when the deliverable can be described before the work starts. The price is only fixed if the scope, acceptance criteria and change process are fixed too. Otherwise you have bought an estimate with a fixed label.
Key takeaways
- Write the scope and acceptance test before you compare prices.
- Tie payments to verifiable deliverables.
- Agree the change-request rate in advance.
- Keep a final payment for acceptance and handover.
What fixed price really means
A supplier who accepts a fixed price without a fixed scope is pricing risk into the quote. You may see a higher number, a longer timeline or a contract with enough assumptions that most of the real work becomes a change request. The goal is not to transfer all risk to the supplier; it is to make the boundary explicit.
| Pricing model | You get | Best fit |
|---|---|---|
| Fixed price | A defined deliverable and a single price | Stable, well-understood scope |
| Fixed scope, time and materials | A capped scope with transparent effort | Scope is clear but effort is uncertain |
| Milestone-based | Payments tied to phases | A larger build with review points |
| Retainer | Reserved capacity | Ongoing changes after launch |
The scope document
- Outcome: what the user can do when the project is finished.
- Must-have workflows: the few paths that must work on day one.
- Integrations: every system, who owns access and what happens when it fails.
- Exclusions: content, copywriting, photography, migrations, training, support.
- Acceptance: the test that decides whether the deliverable is complete.
- Assumptions: browsers, devices, volumes, languages and third-party limits.
Payment and acceptance
A sensible structure is a deposit, two or three milestone payments and a final payment on acceptance. Each milestone should be demonstrable in a staging environment. The final payment should cover the handover: repository access, environment variables, deployment notes and a walkthrough.
Change control
Even a good scope changes. The contract should say how: a written request, an estimate of cost and schedule impact, and an approval before work starts. A supplier who starts every change “to keep things moving” without approval is creating a dispute later.
Warranty and exit
- Defect-fix period after acceptance, typically 30–90 days.
- Response times for critical issues.
- Source code, design files and documentation on final payment.
- A handover session and a defined period of post-launch support.
- Clear ownership of domains, cloud accounts and third-party subscriptions.
Market checks for the UK
The cheapest quote is not comparable until the currency, tax, expenses and payment terms are explicit.
| Area | What to confirm | Why it matters |
|---|---|---|
| Contracting entity | Which legal entity signs and who employs the developer | Enforcement and accountability |
| Tax and status | How VAT and IR35 / off-payroll working rules apply | A quote can change after tax |
| Data protection | How UK GDPR and the Data Protection Act 2018 affect customer and employee data | Cross-border transfers and notices |
| Currency and payment | The invoice currency (£), expenses and payment terms | Avoid a hidden exchange or cash-flow cost |
| Disputes | Governing law, jurisdiction and escalation path | A cheap contract is expensive if it cannot be enforced |
| Communication | Overlap hours, written updates and a named decision-maker | Time-zone drift is a delivery risk |
- Ask for the legal name and registration of the entity that will invoice you.
- Put the tax treatment and expenses in the contract, not only in the proposal.
- Confirm who owns the code, design files and third-party licences.
- Agree how access is removed when the engagement ends.
Frequently asked questions
Only when the scope is genuinely fixed. Otherwise you pay for the risk in a higher price, a longer timeline or a stream of change requests. Fixed price is a good fit for a well-understood deliverable, not for a product still searching for its requirements.
Tie each payment to a verifiable deliverable, not to a calendar date. Keep a meaningful final payment for acceptance and handover. Avoid paying the full build cost before you have production access and the source code.
A short, written test that proves the deliverable works in the real environment: the user can complete the workflow, the data is correct, the error states behave and the agreed browsers and devices pass. “Looks good” is not an acceptance test.
Ask for a defined defect-fix period after acceptance, typically 30–90 days, covering defects in the agreed scope. It should not cover new features or changes caused by your own team. Put the response time and remedy in writing.
Sources and further reading
- GOV.UK: understanding off-payroll working (IR35) (gov.uk)
- ICO: UK GDPR guidance (ico.org.uk)
- NIST Secure Software Development Framework (csrc.nist.gov)
Related reading
Want a scope reviewed before you sign?
Send the statement of work and the acceptance criteria. I will point out the gaps that usually become change requests.
How to cite this guide: Nur Hossain Repon, “Project-based Contract in the UK: a buyer's guide”, Nhrepon Portfolio, reviewed October 2026, https://nhrepon.com/posts/project-based-contract-in-the-uk-a-buyers-guide.





Comments
No comments yet.