How to compare website quotes without missing the real costs

Two website quotes can look similar on the first page and describe very different projects underneath. One may include content planning, mobile testing and a usable handover. Another may cover the build alone, with those jobs left to your team.

The useful question is not simply “Which costs less?” It is “What will we have when this is finished, what will we still need to do, and what will it cost to keep running?”

If you are commissioning a website for a business in Southend-on-Sea, Essex or elsewhere in the UK, compare the scope before comparing the total. This guide gives you a practical way to do that, without pretending there is one correct price for every website.

Give every supplier the same brief

Quotes become difficult to compare when each supplier is solving a different problem. Before asking for prices, describe the customers you want to reach, the services you need to explain and the action you want visitors to take.

Include your existing website, any fixed deadline, the content you already have and the systems the new site must connect to. Explain who will maintain it. A site updated by a busy office manager needs an editing experience that works for that person.

For an Essex service business, meaningful local requirements might include an accurate service area, work photographs and a clear route to requesting a visit. A collection of nearly identical town pages is not a substitute for useful information.

Illustrative example: a property maintenance business wants separate pages for three services, a project archive and an enquiry form that sends requests to its CRM. That is a clearer starting point than “a modern ten-page website”. It describes both the content and the operational handover.

Compare deliverables rather than page counts

“Ten pages” leaves important questions unanswered. Are all ten individually designed? Do they use two reusable templates? Are project entries included? Who enters the content?

Ask for a page list, a template list and a functionality list. Then use a comparison table like this.

Mark every item as included, optional, excluded or unclear. Ask suppliers to resolve the unclear items before choosing. At BuzzBoost, our web design service brings strategy, design and development together; your proposal should still make the specific deliverables explicit.

Make content responsibility explicit

Design cannot resolve an unfinished proposition. A polished layout still needs accurate service descriptions, credible evidence and a useful explanation of what happens after an enquiry.

Find out whether the supplier will write new copy, edit what you supply or paste it in unchanged. Ask how many pages or words that covers, how approval works and whether uploading existing articles and projects is included.

Do the same for images. Stock photography, an AI illustration and a photograph of your team serve different purposes. Agree who supplies assets and checks their usage rights. A generated scene should not be presented as a photograph of your actual premises or work.

A useful proposal also names dependencies. If you must approve copy before design begins, that belongs in the schedule. It helps everyone distinguish a missed delivery date from a project waiting for information.

Ask what mobile and accessibility testing means

“Mobile-friendly” should cover more than shrinking a desktop layout. Ask which pages and journeys will be tested on phones, and whether the checks include navigation, buttons, forms, error messages and overlays.

A practical acceptance check is to complete the main enquiry journey on a small screen, then repeat it with a keyboard. Can you see where focus is? Can you understand the form labels? Does an error explain what needs fixing?

W3C’s accessibility guidance recommends evaluation throughout development and makes clear that no tool alone can determine whether a site meets accessibility standards. An automated report is useful evidence, but it does not replace informed human testing.

If a proposal promises conformance to a particular WCAG version and level, ask which pages and processes are covered, how they will be evaluated and what report you will receive. Agree how identified failures will be handled. This is a procurement checklist, not a determination of your legal obligations.

Turn “fast” into a measurable requirement

A performance claim needs a testing method. Which templates will be checked? Under what conditions? Will the report include the actual images, fonts and integrations planned for launch?

Google’s Core Web Vitals guidance defines good thresholds of 2.5 seconds or less for Largest Contentful Paint, 200 milliseconds or less for Interaction to Next Paint, and 0.1 or less for Cumulative Layout Shift. These assess loading, responsiveness and visual stability at the 75th percentile of visits, segmented by mobile and desktop.

That does not make a single test score a performance guarantee. Google distinguishes lab testing from field data: controlled tests help diagnose problems, while field data reflects real visits. A page may not have enough field data available: Google requires sufficient representative samples before PageSpeed Insights can show real-user data.

Ask for pre-launch test evidence and an agreed approach to checking real-world performance when data is available. Also agree what happens if a later chat widget, video embed or marketing script introduces a problem.

Google explicitly says that good performance reports do not guarantee top rankings. Treat speed as part of the customer experience, rather than a promised route to first place.

Separate launch SEO from ongoing marketing

“SEO included” might mean page titles and a sitemap. It might mean keyword research, service-page copy and a migration plan. Those are different amounts of work.

Ask the supplier to list the launch deliverables: page titles, descriptions, internal links, canonical checks, sitemap checks and the handling of any changed URLs. Then ask what ongoing work is excluded.

For a replacement website, a URL migration deserves its own line in the scope. Google’s site-move guidance describes mapping old URLs to their new destinations and using permanent redirects where appropriate. Sending unrelated old pages to the homepage is not a sound substitute.

Our guide to rebuilding a website without losing existing search traffic covers that work in more detail. Here, the buying question is whether someone is explicitly responsible for it.

Define integrations and measurement as complete journeys

“CRM integration” needs more detail than a product name. Which fields transfer? Who receives the record? How are duplicates handled? What happens if the connection fails?

For bookings or payments, agree the steps that must work from start to finish, including confirmation messages and failure states. A button opening another system may be enough for your needs, but it is a different deliverable from a deeper integration. Our web development and integration work starts with that distinction.

Measurement needs the same clarity. Agree what counts as a completed enquiry and how the team will test it. A click on “Send” is not sufficient evidence that a request was accepted and delivered.

Specify who configures analytics, who owns the accounts and who checks tracking and cookie choices. Treat privacy wording and legal review as named responsibilities. For reporting beyond launch, our analytics and reporting service is a separate conversation about what the business needs to measure.

Know what you control after handover

Ask who controls the domain registration, hosting account and website administration. Agree what access your team receives and how it is protected.

Clarify the rights to supplied designs, code, copy and photography in the contract. Third-party assets and software can have separate licence conditions. Ask what can be transferred if you change supplier, and which licences you would need to replace.

Request a demonstration of the everyday editing tasks your team will perform: changing a service description, replacing an image and adding a project. If each task requires a developer, include that dependency in the cost comparison.

Backups also need an owner. WordPress’s own training recommends backing up before updates and migrations. Ask how frequently backups run, where they are kept and who performs a restore. A documented recovery process is more useful than an unexplained “backups included” line.

Compare the first year and the following year

List the build price, setup charges, recurring fees and expected optional work separately. Ask whether each figure includes VAT where applicable. Do not assume all suppliers present prices on the same basis.

Illustrative calculation, not a BuzzBoost price: a £3,000 build plus £60 per month totals £3,720 in year one. A £3,500 build plus £15 per month totals £3,680. Those figures exclude VAT, domain renewals, transaction fees and additional work. They show why the headline build price alone cannot settle the decision.

Lower running costs are not automatically better. A maintenance fee might include updates, monitoring and support that another quote excludes. Compare the service behind the charge, renewal terms and exit arrangements.

Agree what “finished” means before paying a deposit

Your final comparison should cover acceptance, payment stages and support. Ask when invoices become due, how changes outside scope are priced and who signs off each stage.

Use this short checklist before committing:

• We have an agreed sitemap, template list and functionality list.
• Content responsibilities, approvals and dependencies are named.
• Testing covers the main journeys, rather than a homepage screenshot alone.
• Launch SEO, migration and measurement deliverables are explicit.
• We understand access, asset rights, licences and editing responsibilities.
• First-year costs, renewals and out-of-scope rates are clear.
• Handover, defect handling and ongoing support have defined boundaries.

Choose the supplier whose proposal explains the work and makes the commitments understandable. The price matters. So does knowing exactly what you are buying.

Planning a new website?

BuzzBoost works with businesses in Southend-on-Sea, across Essex and throughout the UK. Tell us about your website project, including your current site, goals, required functionality and any fixed deadline. We can discuss the scope and practical next steps.

Featured image: AI-generated editorial artwork, not a photograph of a real BuzzBoost office, client or result.