By Mehdi HassanFixed-price projects promise certainty, and they can deliver it. They can also produce arguments about what was included, when the scope was vague. This guide explains how fixed-price website projects work, what to look for in the scope, how revisions and change orders should be handled, and uses our own published pricing as the worked example. For the full picture of startup website projects, see our guide to website design and development for startups.
How does fixed price website design work?
Fixed price website design works by agreeing the scope first and the price second. Once both are signed, the agency delivers that scope for that price, however many hours it takes.
The scope is the heart of it. It lists the pages, what each deliverable includes, what the client provides, what's excluded and how changes are priced. Hourly projects let the scope stay fuzzy because the meter covers it. Fixed-price projects can't, so a good one forces clarity early. That's the main benefit: you know the cost before you start, and the agency has a reason to work efficiently, because extra hours come out of its margin, not your budget.
- Designify website, up to 6 pages
- $8,000
- Each extra page
- +$500
- Trial week before you commit
- $1,000
What does a fixed scope website project include?
A fixed scope website project should include a clear list of deliverables, the page count, what the client is responsible for, and what's out of scope. If any of those four is missing, the price isn't really fixed.
Scope element | What good looks like | Red flag |
|---|---|---|
Page list | Named pages, with templates such as blog post counted once | "Approximately 5–10 pages" |
Copy | Who writes it, and how many rounds of edits | Not mentioned |
Design | Desktop and mobile, components, interaction states | "Homepage design plus inner pages" |
Build | Platform, CMS collections, forms and integrations listed | "Development as required" |
Client inputs | What you supply, and by when | Missing, so delays become disputes |
Exclusions | Named: migration, photography, custom features | No exclusions section at all |
Change pricing | Price per extra page or a rate for changes | "Additional work billed as needed" |
Our own model uses the page as the unit because it's the easiest one for both sides to count. The website package covers copy, custom design, a Next.js build with a CMS and animation for up to six pages at $8,000, with each extra page at $500. Migration work, if needed, is scoped separately on the intro call.
What's the difference between a revision and a change order?
A revision refines work already in scope; a change order adds something that wasn't. Changing a headline, adjusting a layout or swapping an image is a revision. Adding a page, a new integration or a feature nobody discussed is a change order.
The grey area is direction changes. If you approve a homepage direction and then decide, after the build, to reposition the company, that's not a revision, even though it's the same page. Good fixed-price contracts say how many revision rounds each stage includes and at which point a direction is locked. Ask for that in writing. Our article on change orders and scope creep covers how to keep the grey area small.
What are the pros and cons of a flat fee website?
A flat fee website gives you price certainty and pushes the agency to work efficiently; the trade-off is that you need a clear scope upfront and less room to change course mid-project.
Pros
- You know the cost before work starts
- The agency carries the risk of work taking longer
- Forces clear decisions about pages and content early
- Easy to compare quotes on the same scope
- No hourly tracking or surprise invoices
Cons
- Vague scope leads to disputes about what's included
- Mid-project pivots cost extra
- Some agencies pad the price to cover unknowns
- Harder to fit exploratory or open-ended work
For open-ended work, where the scope keeps evolving, a retainer often fits better than a project price. Our comparison of website care plans vs design retainers covers when to switch.
How do you check a fixed-price website quote?
Check a fixed-price quote by reading the exclusions, confirming the page count, and asking how three specific changes would be priced. The answers show whether the price is genuinely fixed.
Match it to your brief
Every section of your website design brief should map to a line in the scope, or to an exclusion.
Count the pages yourself
List every unique page design. Check against how many pages a startup website needs if you're unsure.
Read the exclusions
Look for copy, migration, tracking, photography and post-launch support. Anything excluded is a cost you'll pay elsewhere.
Test the change process
Ask: what does an extra page cost, a new form integration, and a headline rewrite after build? Clear answers mean a clear contract.
Check the handover
Make sure accounts and files end up in your name. Our website handover checklist lists them.
Hypothetical example: a seven-page site with one change mid-project
For example, suppose a startup books our website package for seven pages: six in the base scope at $8,000 plus one extra page at $500, for $8,500. Halfway through, the team decides it wants a second audience page. That's a new page, so it's an extra $500, agreed in writing before the work starts, bringing the project to $9,000.
Later, the founder wants to rewrite two homepage headlines after reviewing the build. That's a refinement of an existing page, which a clear contract treats as feedback within the agreed revision rounds, not a new page. The key is that both sides knew in advance which bucket each request fell into.
Who is a fixed-price website project not right for?
A fixed-price project isn't right for teams who can't yet describe what the site needs to do, or for products whose website is really an application. In both cases, the scope can't be pinned down, so a fixed price becomes guesswork.
If your positioning isn't settled, start with a smaller fixed step, like a design sprint or a trial week, before committing to the full site. If your site needs logins, custom product data or ongoing feature work, a retainer or a phased build suits it better. Platform costs can also shift mid-year, so read our piece on platform pricing changes before you lock in a builder. And if you're bringing an existing brand along, settle how it translates to the web first; see from brand identity to website.
