Choose fixed-price when the website and its acceptance conditions can be fully defined before signing. Choose a retainer for a continuing programme with no natural finish line. Choose capped time-and-materials when discovery must resolve unknowns before anyone can responsibly price the build. The billing label never protects you — scope, change control and exit terms do.
Prefer certainty? Get a fixed-price quote for your build — defined scope, milestone payments and written change control, agreed before we start.
Which contract model fits your web project?
Every web contract is a trade in risk. Fixed-price places estimation risk on the supplier inside an agreed boundary. A retainer fixes the charge per billing period but can leave total duration open. Time-and-materials lets priorities change freely while you pay for the effort those changes consume. The safest starting model follows the uncertainty and continuity of the work:
| Situation | Starting model | Control to require |
|---|---|---|
| Defined marketing website | Fixed-price | Attached scope, acceptance criteria, written change approval |
| Unknown workflow needing research | Capped T&M discovery | Effort cap, named outputs, a stop decision |
| Operating site with a continuing backlog | Retainer | Capacity, priorities, renewal, notice, handover terms |
| Known build with one uncertain feature | Hybrid | Bound discovery first, then price the approved build separately |
Compare what you own after each payment — and what remains usable if the engagement stops today. That reveals far more than comparing opening invoices. The web development RFP template helps turn verbal assumptions into comparable written deliverables, and our fixed-price web design service shows what a properly bounded offer looks like.
How do the three models compare on cost, scope, speed and exit?
Score each model against five buyer risks rather than treating a predictable monthly charge as a predictable project total:
| Buyer risk | Fixed-price | Retainer | Time-and-materials |
|---|---|---|---|
| Cost predictability | Strong inside a written scope | Period charge known; duration may stay open | Depends on an effort or sprint cap |
| Scope-creep exposure | Additions require approved changes | New requests compete for recurring capacity | Every accepted addition consumes billable effort |
| Speed and finish pressure | Milestones create a defined finish line | Suited when no finish is intended | Depends on bounded outputs and review points |
| Priority control | Changes require visible trade-offs | Priorities can reset each cycle | Priorities can change while billing continues |
| Exit or lock-in | Clear when transfer duties are explicit | Depends on term, notice and asset transfer | Billing can stop while the product stays incomplete |
Estimation risk changes hands across the models. Under a properly bounded fixed price, the supplier absorbs the extra effort needed to deliver the agreed result. Under time-and-materials, you pay directly for extra effort. A retainer sits between them: the period charge is known, but unresolved work can extend the number of periods indefinitely. This is commercial project-planning guidance, not legal advice — have qualified counsel review material contract terms and remedies.
Project risk is not theoretical. The Standish Group's CHAOS research found only 16.2% of software projects completed on time and on budget, with challenged projects averaging 189% cost overruns and 222% time overruns — and 31.1% were cancelled outright. Separately, PMI research has found that poor project performance wastes roughly 9.9% of every dollar invested. The contract model you choose is one of your few levers on that exposure. See how to choose a web development company for supplier vetting, and how much a website costs in 2026 for realistic budget ranges.
How do you choose? A scope-certainty decision tree
- Can you list the required routes, features, integrations, responsibilities and acceptance conditions? If yes, request a fixed-price proposal with milestone payments and written change control.
- Must research or prototyping determine what should be built? If yes, commission capped time-and-materials discovery with named outputs: a route map, prototype, technical options, risk register and build estimate.
- Does an operating site have a continuing queue with no natural completion date? If yes, consider a retainer with stated capacity, priority rules, reporting, renewal, notice and handover terms.
- Does the project contain both known and unknown work? Split it. Bound the investigation, approve its outputs, then price the defined build separately.
For example, a ten-route professional-services site with approved copy and one established contact integration can be accepted route by route — that supports fixed-price. An untested customer portal connected to an undocumented internal workflow cannot be responsibly defined that way — it needs bounded discovery before a separate build decision. Documenting your process also matters; our website development process shows the phases a proposal should name, and web development consulting can run the discovery stage as a fixed, capped engagement.
"Adding manpower to a late software project makes it later." — Frederick P. Brooks Jr., The Mythical Man-Month. Scope discipline beats resource escalation every time.
What red flags can break a fixed-price contract?
A proposal labelled "fixed-price" can still leave the amount, finish or approval path unclear. Watch for:
- No attached scope — deliverables and exclusions exist only in sales messages, not in the agreement.
- No observable acceptance conditions — a milestone payment falls due without a reviewable definition of "done".
- No distinction between defects and changes — corrections, included revisions, preferences and added scope are treated as the same thing.
- No prior change approval — extra work can begin before both parties approve its cost and schedule effect.
- Calendar-only payment triggers — money becomes due because a date passed, not because a named stage was delivered.
- No handover inventory — the repository, source files, CMS, hosting, credentials, licences and documentation are not named.
A usable scope identifies routes, reusable components, integrations, content responsibilities, responsive states, migration duties, testing, handover assets and exclusions. Before signing, run the supplier through our agency vetting guide and confirm ownership terms in the website handover checklist.
How do you keep scope changes from becoming surprise charges?
Require a written change request that describes the requested difference, its price effect, its schedule effect and its acceptance effect — before any added work begins. If a request replaces an existing item, record what leaves the scope as well as what enters it. A simple approval record should state the request, why it is needed, the affected deliverables, added or removed cost, the timing consequence and the authorised approver.
This protects both sides: you see the commitment before it is made, and the supplier does not have to absorb work that was never included. The discipline matters most under fixed-price, where ambiguity about what "included" means is the number-one source of disputes. Our RFP template includes change-control language you can reuse, and transparent pricing shows how defined-scope offers are structured.
What does each model cost on the same project? A worked example
Assume a ten-page professional-services website with approved copy, one contact integration, analytics, a CMS and no custom application features. All figures below are hypothetical teaching figures, not WebStackRank prices or market benchmarks.
| Model | Hypothetical structure | Calculation | Main exposure |
|---|---|---|---|
| Fixed-price | $6,000 approved scope | $6,000 — or $6,800 after one separately approved $800 feature | Weak scoping can cause an inclusion dispute |
| Retainer | $2,500 / month | $7,500 for three months; $15,000 for six | The engagement continues after the finite build should have finished |
| Time-and-materials | $90 / hour | 70 hours = $6,300; 100 hours = $9,000 | Revisions and undecided details increase the total directly |
The formulas are: fixed total plus approved changes; monthly fee × active months; hourly rate × recorded hours. Comparing $6,000, $2,500 and $90 directly is misleading because the figures use different units — convert every option into a realistic total range, then list the usable outputs you hold at the same stopping point. For a real number on your scope, use the quote calculator or read how much a website costs in 2026.
How do you avoid a retainer that is difficult to exit?
Record the initial term, renewal event, notice deadline, final payment, work during notice and transfer duties before signing. If your approval team cannot calculate the exit date and remaining commitment from the agreement, the retainer is not commercially clear enough. Check:
- Renewal: does the agreement end, continue monthly, or renew for another fixed term?
- Notice: what action, through which channel, before which date?
- Exit amount: which approved charges remain payable?
- Unused allocation: does unused capacity expire, roll over or convert into outputs?
- Notice-period work: does delivery continue or switch to transition tasks?
- Transfer: when are paid-for files, accounts, decisions and unfinished work handed over?
Enter the review date in your contract register at signing, and assign someone to inspect usage, unfinished priorities and transition needs before that date. Our website handover ownership checklist covers the transfer side, and contact us if you want a second pair of eyes on a proposal.
What should you own if delivery stops tomorrow?
You should retain current requirements, decisions, design files, repository access, staging access, issue records and setup notes — enough for an authorised replacement team to assess completed and unfinished work without reconstructing the project from email.
| Stage | Buyer-accessible materials | Stopping-point use |
|---|---|---|
| Discovery | Brief, route map, requirements, integration list, decisions, risks | Another supplier can identify open questions and estimate the build |
| Design | Current design file, component states, responsive variants, approvals | You can distinguish approved work from unfinished exploration |
| Build | Repository, issue tracker, staging environment, setup notes, deployment status | A replacement team can retrieve the code and inspect incomplete work |
| Handover | Production access, CMS, source files, credentials, licences, documentation | You can operate the site and remove former-supplier access |
Access does not guarantee an unfinished artefact is reusable without further work — but it lets you see what exists, what was decided and what remains unresolved. Keep everything in organisation-controlled accounts, not shared personal logins. Full detail: the website handover ownership checklist and how much does a website cost service page.
Signing checklist: the controls that matter most
- Write the outcome, included work, responsibilities and exclusions.
- Connect milestone payments to reviewable outputs — or define recurring capacity precisely.
- Separate acceptance, defect correction, included revisions and new scope.
- Require written approval before any cost or schedule change begins.
- Record renewal and notice dates with a named internal owner.
- Keep current project materials in organisation-controlled systems.
- List every account, file, credential, licence and repository required at handover.
- Obtain qualified legal review for material terms and remedies.
Frequently asked questions
Is fixed-price always cheaper than time-and-materials?
No. Either model can produce the lower total depending on the project. Choose by uncertainty, change control and who should carry estimation risk — not by assuming one billing label is always cheaper. A well-scoped fixed-price build is usually cheapest for defined work; open-ended discovery belongs on capped time-and-materials.
When is a web design retainer appropriate?
A retainer fits a continuing, prioritised queue with no natural finish line — an operating site that needs steady improvement. It is a weak substitute for a finite website build when capacity, outputs, renewal and exit terms are unclear, because billing continues after the build should have finished.
Can one project combine contract models?
Yes, and this is often the smartest structure. Run uncertain discovery on capped time-and-materials, then approve a fixed-price build based on the discovery outputs. Treat continuing post-launch work as a separate decision with its own terms.
What should happen if the agency stops responding?
Your agreement should define notice, termination, payment and transition steps, and your delivery process should keep current work accessible through organisation-controlled systems from day one. Get jurisdiction-specific advice before relying on any contractual remedy.
Who owns the website if we part ways mid-project?
You should — provided the contract says so and handover assets are named: repository, source files, CMS, hosting, credentials, licences and documentation. Confirm this before signing, not when the relationship is already strained.
Conclusion
The billing label is the least important part of your contract. What protects your budget is a written scope, observable acceptance conditions, written change control, named ownership and a clear exit. Get those controls in place and any of the three models can work; skip them and even a "fixed price" becomes a negotiation.
Get a fixed-price quote for your project — defined scope, milestone payments and full asset ownership, agreed in writing before we start.
