Why two quotes for the same website differ by five times

It happens on nearly every project. The same brief goes to four suppliers, and the quotes come back so far apart that they appear to be for different jobs. Often they are. The brief described a website; each supplier priced a different interpretation of one.

Here is what actually moves the number.

Template versus design

The largest single variable. A configured theme with your logo and photography is a genuinely different product from a designed interface, and both are legitimate purchases. A theme gets you online quickly and cheaply, and constrains you to what the theme does. A custom design costs several times more and does what your business needs.

Neither is wrong. What is wrong is paying custom prices for a theme, which is a common outcome when nobody asked the question directly.

Page count is a bad proxy and everyone uses it

Quotes get built around a page count because it is easy to count. But ten pages that share one layout is a fraction of the work of five pages that each need a distinct one. The real driver is the number of unique templates and components, not URLs.

Ask any supplier to quote in templates. The answer tells you a great deal about how they work.

Who writes the content

This is the assumption that most reliably blows up a timeline. Many quotes silently assume the client supplies final copy and images on day one. Most clients cannot, discover this in week six, and the project stalls with everyone blaming everyone.

Content is a real workstream with a real cost — research, copywriting, photography, editing. Either buy it or schedule it, but do not let it sit unowned in the gap between two contracts. Our content creation and photography and videography pages exist because this is the most common project-killer we see.

Integrations, which are never simple

"Connect it to our CRM" can mean an hour or a month. A documented API with a maintained client library is straightforward. A legacy system with no API, or a payment gateway requiring compliance review, or a booking system whose vendor is unresponsive, is not. Suppliers who have been burned price this defensively; suppliers who have not, do not, and then discover why.

What happens after launch

Some quotes end at go-live. Others include hosting, updates, security patching, backups, monitoring, and a named person who answers when something breaks at 9pm. That is an ongoing operational cost, and its absence from a quote does not mean it is free — it means you are paying for it later, in a hurry, at whatever rate is available.

The things that are invisible in a demo

Two sites can look identical and differ enormously in what was built underneath.

• Performance — whether anyone measured load time on a mid-range phone on a mobile connection, or only on the designer's laptop.
• Accessibility — keyboard navigation, contrast ratios, screen reader semantics. Increasingly a legal requirement, always a usability one.
• Technical SEO — crawlable structure, clean metadata, structured data, a real sitemap. Retrofitting this costs more than building it in.
• Security — form validation, spam handling, dependency hygiene, an actual backup you have tested restoring.
• Analytics — whether conversion tracking works on launch day or gets added in a panic three months later.

None of these show up in a screenshot. All of them show up in the invoice, one way or another.

Five questions that expose the difference

• How many unique templates are you quoting, and what happens when we need a sixth?
• Who writes the copy and sources the images, and when is that due?
• What are the hosting, maintenance and support arrangements after launch, and what do they cost annually?
• What is your process when something is discovered mid-build that neither of us scoped?
• Who owns the code, the design files and the domain at the end?

That last one catches people. If the answer is anything other than "you do", understand exactly what you are agreeing to.

The cheapest quote is frequently the one that read the brief least carefully. The expensive part is not the build — it is the second build.

How to compare fairly

Put the quotes side by side and normalise them: same template count, same content assumption, same integration list, same post-launch arrangement, same three-year total rather than the day-one number. The spread usually collapses, and what remains is a real difference in what is being delivered.

We scope in writing before work starts, for exactly this reason. If you want a quote you can actually compare against others, send the brief and we will come back with the assumptions written down.