Why One Website Design Quote Is £800 And Another Is £8,000

If you’ve ever asked a few web design companies for a quote and wondered why the prices came back wildly different, you’re definitely not alone.

One business might quote a few hundred pounds. Another might come back with several thousand. A third might ask questions you hadn’t even considered before giving you a price at all.

The confusing part is that all of them might genuinely believe they’re quoting correctly.

And in a strange way, they probably are.

The reality is that website design pricing is rarely just about “how many pages” a website has. Different agencies and freelancers quote in completely different ways, based on how they work, what they include, the type of clients they normally work with, and how much risk they’re taking on with the project.

That means two quotes for “the same website” can look completely different on paper while both still being technically valid.

But recently, we’ve also been seeing another issue appear more and more often. Not necessarily bad agencies. Not necessarily dishonest freelancers. Just assumptions — and different people making completely different ones.

Assumptions Cause More Website Project Problems Than Most People Realise

One of the biggest causes of disagreements, delays, and unexpected costs in website projects is assumptions.

Customers naturally assume certain things are included because, to them, they feel obvious.

Designers and agencies often assume certain things are not included because they haven’t been specifically requested.

Neither side is necessarily trying to mislead the other. They’re simply viewing the project through different lenses.

A business owner might assume a “Contact Us” page includes a contact form, Google Maps integration, spam protection, mobile optimisation, and a styled confirmation message. Meanwhile, the agency may have priced for a standard informational page containing text and an email address because those features weren’t specifically mentioned.

Technically, both sides can feel justified.

And that’s exactly where problems begin.

In some cases, agencies intentionally avoid making assumptions because every extra feature increases the amount of work and therefore the cost. In others, they may deliberately include broader assumptions within the quote to avoid surprises later, which naturally pushes the quoted price upwards.

That’s one of the reasons two quotes can differ so dramatically. One company may be pricing for the minimum interpretation of the brief, while another is pricing based on what they believe the customer is realistically expecting to receive.

The Difference Between A Quote And An Estimate

This is another area where misunderstandings happen constantly.

A quote and an estimate are not the same thing.

An estimate is effectively an educated guess. A quote is generally considered a fixed-price agreement for a defined scope of work.

Increasingly, businesses are being given very low estimates with very little detail around what’s actually included. The initial number looks attractive, but because the specification is vague, additional charges begin appearing during the build once assumptions start being challenged.

We’ve seen situations where customers believed SEO setup, image optimisation, contact forms, mobile responsiveness, or social media integration were all part of the project because they considered them standard website features. The agency, meanwhile, viewed them as additional work outside the original estimate.

Again, neither side may have intentionally done anything wrong. The problem is that assumptions filled the gaps where clear specifications should have existed.

Why Some Agencies Ask Far More Questions

Sometimes customers are surprised when one agency asks dozens of detailed questions while another provides a price after a five-minute phone call.

But often, the agency asking more questions is simply trying to reduce assumptions.

Questions about who will update the website later, whether content already exists, how enquiries should be handled, whether staff need training, if the site needs to integrate with existing systems, whether accessibility compliance is important, and what level of SEO work is expected all help shape the real scope of the project.

That extra planning takes time, and it can sometimes lead to higher quotes because the agency is identifying work others may not yet have considered.

Ironically, the more detailed quote is often the one designed to reduce the risk of unexpected costs later.

Hourly Quotes Can Create Problems Too

Another increasingly common approach is quoting projects in hours rather than as a fixed project cost. Again, there’s nothing inherently wrong with this approach. In some cases it’s absolutely the best way to manage a project, particularly where requirements are likely to evolve over time.

The problem usually appears when there’s no clear agreement around what assumptions those hours are based on.

A project may be estimated at twenty or thirty hours based on the assumption that all content is supplied ready to use, feedback is provided quickly, and no major revisions are required. But if those assumptions turn out to be incorrect, the hours can increase very quickly.

This is something we’ve seen affect charities and non-profits particularly hard. Fixed budgets can suddenly become difficult to manage once projects move beyond the original estimated hours.

In many cases, nobody intentionally caused the issue. The original assumptions simply didn’t match the reality of how the project unfolded.

Why Some Websites Become Difficult To Manage

Another issue we’re increasingly seeing is websites being developed in ways that make them heavily dependent on the original developer or agency.

Sometimes this is intentional because it allows projects to be delivered more quickly and cheaply. Other times it’s simply the result of rushed development processes or shortcuts being taken under pressure.

More recently, AI-generated code has started creating its own set of challenges.

AI tools can absolutely help experienced developers work more efficiently. Used properly, they can speed up repetitive tasks and reduce development time significantly. But problems appear when the person using the AI doesn’t fully understand the code being generated.

We’re now seeing websites where themes and functionality have effectively been assembled by AI tools, but without enough consideration for how the business will maintain the site long-term. Initially the website may look perfectly fine. The problems often appear later when the business wants to make changes, improve functionality, or hand the site over to another developer.

Sometimes the original developer assumed the client would continue relying on them for updates. Meanwhile, the client assumed they were receiving a standard WordPress website that anybody could edit easily later.

Again, assumptions on both sides can completely change how the project is priced and delivered.

Why Two Very Different Quotes Can Both Be Correct

This is the part that makes comparing website quotes so difficult.

One agency may be pricing purely for the visual design and launch of the website itself. Another may be pricing for long-term maintainability, accessibility, SEO foundations, future scalability, security hardening, ongoing support, staff training, content population, and performance optimisation.

One may be making optimistic assumptions to keep the price competitive. Another may be deliberately pricing more cautiously to reduce the likelihood of future disputes or additional invoices.

From the outside, both proposals may appear to describe “a business website”.

Behind the scenes, they may actually be solving completely different problems.

The Questions Worth Asking

When reviewing website proposals, it’s often more useful to focus on clarity than price alone.

It’s worth asking whether the document is a quote or an estimate. Whether there’s a written specification. What assumptions the price is based on. What happens if additional work is required. Whether the site can easily be managed by another developer in the future. Whether support, backups, SEO work, security updates, and training are included.

Those conversations usually reveal why prices vary so dramatically between providers.

At O’Brien Media, We Prefer Clarity Over Surprises

One thing we always try to avoid is ambiguity. Not because every project goes perfectly smoothly — web development is still both creative and technical — but because clear expectations make projects significantly less stressful for everyone involved.

Some businesses genuinely only need a straightforward brochure website delivered at an affordable price. Others need something far more robust with room for growth, integrations, ongoing support, accessibility considerations, and long-term scalability built in from the start.

Neither approach is automatically right or wrong.

The important thing is making sure everybody understands exactly what’s included, what assumptions have been made, what isn’t included, and what happens once the website goes live.

Because when website quotes vary wildly, it doesn’t necessarily mean one company is honest and the other isn’t.

Very often, they’re simply approaching the project from completely different angles.