Reading time:
7 min read
Last updated:
Fixed-Price Website Design: What It Covers
A fixed price buys a page count, a set number of review rounds, and a date. What sits outside it, how change requests work, and when a retainer is cheaper.
A fixed-price website quote buys three things: an agreed page count, an agreed number of review rounds, and a delivery date. It does not buy unlimited changes. That is the trade. You get a single number you can put in a budget, and in exchange the scope stops moving.
Fixed price works when both sides can describe the site before it starts. It goes wrong when they cannot, and the argument that follows is always about the same thing, which is what counts as a change. Below is what the number covers, how change requests get handled, and when hourly or a monthly retainer is the better buy.
What the number actually covers
Read any fixed-price quote and you should be able to find four boundaries. A page count. A revision count, usually one or two rounds per milestone. A platform, because building on a tool the studio already knows is most of what makes a price predictable. And a date, which quietly assumes your side reviews on time.
Anything not named inside those four is outside the price. That is not a trick, it is the only way a fixed number can exist at all. A studio promising both a fixed price and unlimited changes has either padded the figure heavily or is planning to have an uncomfortable conversation with you in week three.
The change request is where fixed price lives or dies
Every fixed-price project meets a request that was not in the plan. A pricing page nobody mentioned. A different hero after the positioning shifted. A section for a partner who signed last week.
What matters is not whether that happens, because it always happens. What matters is whether the agreement already says what happens next. A good one names a rate or a rule for out-of-scope work before anyone needs it. A bad one stays silent, so the conversation lands at the worst possible moment, three days from launch, when you have no leverage and the studio has all of it.
Ask for the change process in writing before you sign. If the answer is vague, the price is not really fixed.
When fixed price is the right buy
Fixed price suits a project whose shape you can draw today. A marketing site of five to eight pages. A migration from one platform to another where the content already exists. A launch page with a real date behind it, because a funding announcement or a conference does not move.
It also suits teams who need a number approved by someone who is not in the room. One figure is easy to take to a board or a finance lead. An hourly estimate with a range on it is not, and you will spend more time defending the range than you saved.
When it is the wrong shape
Skip fixed price when the scope is genuinely unknown. If you cannot yet say what the product does, or the positioning is still being argued about internally, a fixed price forces both sides to guess, and that guess becomes the thing you fight over later.
Skip it when the work is continuous. A team shipping new pages every month is buying a stream, not a project, and a monthly retainer covering new pages, campaigns, and product design fits that far better. Our guide to web development retainers covers what a monthly deal should include and what it should cost.
And skip it if you expect to change direction halfway. Fixed price is not built to absorb a new idea in week two. Resisting exactly that is the job it was hired to do.
Five questions that test a fixed number
Ask what happens if your content arrives late, because content is the most common delay and somebody has to absorb it. Ask how many review rounds are included and what one round means, since a single person leaving comments and four people disagreeing are very different amounts of work.
Ask which platform the price assumes and what changes if you pick a different one. Ask what happens if the project finishes early, because a fixed price cuts both ways and the honest answer tells you a lot about who you are dealing with. Then ask for the out-of-scope rate in writing.
A studio that answers all five quickly has done this before. One that needs to get back to you is pricing your project for the first time.
A fixed price is a scope contract, not a discount
Teams often read a fixed price as the cheaper option. Usually it is not. It carries a risk premium, because the studio is absorbing the chance the work runs long, and that risk has to be priced somewhere.
What you are actually buying is certainty. Certainty is worth paying for when a date matters. When no date matters, hourly can come out cheaper, as long as you trust the count and someone on your side is reading it.
Where to go next
If your question is really about the size of the number rather than its shape, what web design costs for a tech company breaks down what moves the price. If you are still choosing who to talk to, how to choose a web design agency covers what to ask on the first call, and how long a website project really takes explains which parts of the timeline are yours rather than theirs.
And if you want names rather than principles, we maintain a comparison of studios that quote to a fixed scope, including which of them publish a starting figure at all.
Studio Maydit sells websites two ways: a fixed scope that runs three to four weeks for teams with a launch date, and a monthly retainer for teams that keep shipping. If you want a straight answer on which one your project should be, book a free 30-minute call.
Frequently Asked Questions
Continue Reading

ChatGPT Is Introducing Ads. Here’s the UX Risk Nobody Is Talking About
As ChatGPT prepares to introduce ads, most conversations focus on revenue and scale. But the bigger question is how monetization reshapes user trust, cognitive flow, and product intent. This Studio Notes piece explores the hidden UX risks product teams should pay close attention to.

Siddarth Ponangi

Why designing for power users too early breaks SaaS products
Many SaaS products become difficult to use not because they lack features, but because they introduce complexity before users are ready for it. Designing for power users too early often feels like progress, but it quietly undermines adoption for everyone else.

Siddarth Ponangi

Why second-use experience matters more than first impressions in SaaS
Many SaaS products spend enormous effort optimizing first impressions. What often gets overlooked is what happens when users come back for the second time, which is usually where real adoption either starts or quietly falls apart.

Siddarth Ponangi

