Why Website Quotes Vary So Much

You send the same brief to three people and get back three numbers that look like they are for different jobs. It is unsettling, and the natural conclusion is that somebody is trying it on.

Usually nobody is. The three of them read the brief differently and priced what they read. Here is what actually sits behind the number.

What you are buying is hours, not pages

Almost every quote is hours multiplied by a rate, then rounded. Page count is a poor proxy because two pages can differ enormously in effort. A page of text is an afternoon. A page with a filterable product grid, a booking flow and payment is weeks.

So when quotes differ, either the estimated hours differ or the rate does. Both are worth asking about, and a proposal that will not break the number down is hiding one of them.

The biggest single variable is design

Three broad approaches, and the price gap between them is larger than anything else in the quote.

An off-the-shelf theme, lightly adjusted. Fastest and cheapest. You get something competent that looks like other sites using the same theme.

A theme customised heavily. Middle ground. The bones are bought, the surface is yours.

Designed from a blank page. Most expensive. Every screen is drawn for you before a line of code exists.

None is wrong. A local trade business with five pages does not need bespoke design. A brand whose whole pitch is that it is different cannot use a theme thirty competitors are already using.

If two quotes are far apart, this is usually why. Ask each one which of the three they are proposing.

Functionality is where the estimate really moves

A brochure site is a known quantity. Everything below adds real, unavoidable work.

• Payments and checkout
• Accounts, logins and permissions
• Booking or scheduling with availability
• Search and filtering over a large catalogue
• Integration with an existing system such as stock or accounting
• More than one language

The integration line is the one that surprises people most. Connecting to something you already run sounds small and frequently is not, because the other system was not built with this in mind and its quirks only surface once you are inside it.

Content is the hidden line item

Most quotes assume you will supply text and images. Most clients assume the agency will produce them. That gap is responsible for a large share of delayed projects.

Writing copy for a ten page site is genuine work. So is photography. If you want it done for you, it belongs in the quote as its own number. If you are doing it yourself, put a date on it, because a finished site with placeholder text cannot launch.

What is not in most quotes

The build price is not the running cost. Ongoing you will have hosting, a domain, possibly licences for anything commercial, and maintenance.

Maintenance is the one people skip. Software gets security updates. A site nobody has touched in two years is a site with known holes in it. Whether you buy a support arrangement or call someone when something breaks, it is a cost, and it is better decided now than during an outage.

Rates differ for reasons that are not arrogance

A studio with three people has overheads a freelancer does not. It also has cover when someone is ill, a second pair of eyes on the code, and a business that will still exist next year.

A freelancer is cheaper and often excellent. The risk is concentration. One person, one calendar, one point of failure.

Neither is the right answer for everyone. The relevant question is how much the site matters to your revenue. If it is a brochure, concentration risk is tolerable. If orders come through it, it is not.

What a rewrite of an existing site costs

Rebuilding is often quoted higher than building new, which surprises people. There is a reason.

A new site has no constraints. A rebuild has an existing address structure to preserve, existing content to migrate, existing rankings that must survive, and often an existing system feeding it.

The redirect map alone is real work on a site with a few hundred pages. Skipping it is the fastest way to lose traffic you spent years earning.

If a rebuild quote is dramatically lower than the others, check whether redirects and content migration are in it at all.

How to compare three proposals fairly

Put them side by side and answer these questions for each.

• Which design approach is being proposed?
• Who writes the copy and who supplies images?
• How many rounds of revision are included, and what happens after that?
• What is the delivery date and what happens if it slips?
• Who owns the domain, the hosting account and the code at the end?
• What support is included after launch, and for how long?
• Can you edit content yourself afterwards, or does every change go through them?

The last two separate cheap quotes from expensive ones more often than the design does. A site you cannot update without paying someone is a subscription you did not agree to.

How payment is usually staged

Paying everything up front is risky for you. Paying everything on delivery is risky for them. Splitting the project into stages is the normal answer.

A common structure is a deposit to start, a payment when design is approved, a payment when the build is complete, and the balance at launch. Each stage is tied to something delivered.

What matters is that the trigger for each stage is measurable. "When design is finished" invites argument. "When the home page and three inner page designs are approved" does not.

What should be in the contract

• The scope, including what is explicitly not included
• The delivery date and what happens if it is missed
• How many revisions are included and the rate beyond that
• Who supplies content and by when
• Ownership of domain, hosting and code
• Post-launch support period and what it covers
• What happens to your files and data if the relationship ends

The content deadline is the most commonly omitted and the most commonly needed. When copy arrives late the project slips, and without a date in writing it looks like the agency's fault.

The hidden cost of the cheapest quote

Taking the lowest number is not automatically wrong. But ask one question before you do. Will the person charging this still be reachable in six months?

Inheriting a half-finished site costs more than building one, because you first have to understand somebody else's code, then fix it, and often end up rewriting it anyway.

That is not an argument against the cheap quote. It is an argument for checking references properly.

Questions worth asking before you decide

Ask to see two sites they built that are still live, and open them on a phone. Plenty of portfolios contain work that was fine on a desktop in 2019.

Ask who does the work. In small studios the person selling is often the person building, which is good. In larger ones it may not be, which is fine as long as you know.

Ask what happens when you want a change in a year. The answer tells you whether you are buying a site or a dependency.

How we quote

We break the number into design, build, content and anything that needs integrating, so you can see which part is driving the total and cut the right thing if the budget does not stretch.

We would rather have an awkward conversation about scope at the start than a worse one halfway through. If your budget does not fit the brief, saying so early is more useful to you than a low number that grows later.