How to Read a Web Design Quote (and Compare Fairly)

You ask three web designers for a quote and get three wildly different numbers. One’s a fraction of the others. Is it a bargain, or a warning? Usually neither — the quotes just describe different projects. The trick is learning to read past the price to what you’re actually getting.

Here’s how to read a web design quote, compare fairly, and spot what’s quietly been left out.

How do you compare web design quotes fairly?

Compare what’s included, not just the price. Line up each quote’s pages, whether content and SEO are included, revisions, ownership, hosting and support. Two quotes often differ hugely because one is a template with stock photos and the other is a custom, written, search-ready build. Match the scope first, and the fair comparison — and the real value — becomes obvious.

Why quotes differ so much

The word “website” hides enormous variety. A quote might be any of these, all honestly called a website:

• A five-page template with a stock theme and placeholder text you fill in yourself
• A custom-designed site with written content, SEO setup and a proper handover
• Something in between

None is a scam. They’re different products at different prices. The cheap one isn’t ripping you off, and the dear one isn’t gouging — until you compare them as if they’re the same thing. That’s the mistake to avoid, and it’s the same logic behind our website cost guide.

Hourly vs fixed price: which is better?

You’ll see both. Neither is inherently better — they suit different situations.

	Fixed price	Hourly rate
You know the total	Yes, up front	No, it depends on hours
Best for	A defined project with clear scope	Open-ended or ongoing work
Risk	Low, if the scope is clear	Cost can creep
What to insist on	A detailed scope	An estimate and a cap

For a defined website build, fixed price with a clear scope gives you the most certainty: you know the number before you commit. Hourly can be fine for ongoing tweaks or genuinely open-ended work, but for a set project it leaves the final cost fuzzy. Either way, the scope is what protects you.

The checklist: what a good quote spells out

Read every quote against this list. The gaps are where surprises live:

• Pages — how many, and which
• Design — custom, or a template dropped in?
• Content — who writes the words? (Big cost, often left to you)
• Images — real photos, or stock?
• SEO setup — is the site built to be found, or bare?
• Revisions — how many rounds are included?
• Timeline — a realistic schedule with milestones
• Hosting and domain — set up, and in your name?
• Ownership — do you own the finished site outright?
• Support — what happens after launch?

A quote that answers these is from someone who’s thought about your project. A one-line number with no detail is a guess you’ll pay to correct later.

Red flags in a quote

Some things in a quote (or missing from it) should give you pause:

• No scope — just a price, no detail of what’s included
• “Content by client” buried in the fine print — that’s a big job now sitting on you
• No mention of ownership — a hint you might not fully own the site; get this in your contract
• A price that’s too good to be true — it usually is, once you find what’s excluded
• Vague hourly with no estimate — an open cheque

Cheapest isn’t the goal — clearest is

The right quote isn’t the lowest number. It’s the one that’s clear about what you get, what you own, and what happens after launch — at a price that fits. Sometimes that’s a modest budget spent well. It’s rarely the cheapest line on the table, because the cheapest usually becomes the expensive rebuild a year on.

If a quote is more, ask what the extra buys. If it’s less, ask what’s missing. A professional will answer both plainly, and how they ask about your business before quoting tells you as much as the number — one of the signs of a good web company.

Want a quote you can actually read? Tell us about your project and we’ll give you a clear, itemised, fixed price — every inclusion spelled out, nothing hidden. That’s how we quote every build.