How to compare website quotes beyond the headline price
Compare website quotes using a practical checklist for scope, content, ownership, hosting, support and ongoing costs before choosing a developer.
Two website quotes arrive in your inbox. Both promise a smart new site that works on a phone. Both include the pages you asked for. The prices are some way apart.
Where do you start?
Before deciding which offers better value, find out what each supplier expects you to do. One may be writing the service pages and moving your old content. The other may be waiting for you to send everything over, ready to upload.
That difference matters to the price, your workload and whether the project gets finished. Here's how to get the proposals onto the same footing.
Start with the job you need the website to do
A shared brief gives suppliers the same problem to respond to. It doesn't need to read like a technical specification.
“We need to explain our three services, show recent work and receive useful quote requests” is a start. Add your current website, any tools the new site needs to work with, the content you've already got and any deadline that matters. If nobody in the business has time to write the pages, say that early.
The technology can follow the conversation. A supplier should be able to explain why their recommendation suits the job and what they've assumed in the quote.
At Lineup, we begin with the business problem: where you are now, what you've tried and what you'd like to change. Sometimes that leads to a different solution from the one first requested. Understanding the need behind it helps us put the right work in the proposal.
If the page list itself is still taking shape, our guide to what a small business website should include can help.
“Ten pages” leaves quite a few questions open
One designer might plan ten individual layouts. Another might use three reusable layouts to hold ten pages of content. Either can work well. You need to know what you're comparing.
The content deserves just as much attention. Who is writing it, choosing the photographs, getting approval and putting it all on the website? “Content support” could mean editing your draft or producing the copy from a conversation with your team. Those are different amounts of work.
Imagine a service business with approved photographs but no finished service copy. A proposal that includes help with writing might be a good fit. A proposal that assumes the owner will supply the text could leave the project waiting on a job they haven't got time to do.
Neither arrangement is wrong. It needs to suit the people who will carry it through.
For a projects section, establish how many examples will be uploaded at launch and whether you'll be able to add later ones yourself. That brings the editing system and any training into the comparison too. Content deadlines, approval and responsibility should all be written down before they become a surprise.
Follow a customer all the way through
Feature names can make two quotes sound more alike than they are. Take a contact form.
The visible part is a set of fields and a send button. Behind it, the enquiry needs to reach somebody who can deal with it. It may also need to be stored, attached to a customer record or passed into another system.
A requirement like this is easier to review:
A visitor sends a quote request from their phone, sees that it was sent successfully, and the agreed member of staff receives the details needed to reply.
That's an example of the outcome you'd ask for. It gives both sides something more useful to check than “contact form included”.
Booking has similar questions. Does choosing a time confirm the appointment, or send a request for staff to review? When is a deposit taken? What happens if the customer needs to change it? The booking system guide helps you work through those choices.
Where another product is involved, find out whether the quote covers a link, an embedded tool or a connection that exchanges information. Any separate account or subscription belongs in the costs as well.
Put the answers beside each other
Once you've talked through the work, a short comparison sheet helps you see what remains unclear. You can copy this into a document and add a column for each proposal.
| Area | What you need to know |
|---|---|
| Pages and layouts | Which pages and reusable layouts are included? |
| Copy and images | Who prepares, approves and uploads them? Are licences needed? |
| Design review | What will you review, and how many rounds of feedback are included? |
| Editing | What can your team change, and will someone show them how? |
| Forms and connections | What happens after a customer sends, books or pays? |
| Testing | Which devices, browsers and customer tasks will be checked? |
| Existing website | What moves across, and who handles old page addresses? |
| Search | Which launch tasks are included, and what continues afterwards? |
| Ownership | Which accounts, files, rights and instructions will you receive? |
| Ongoing care | What do hosting, maintenance and support each cover? |
| Payment and timing | What triggers a payment, and what could hold up launch? |
Mark an answer as included, excluded, optional or still unclear. An empty box gives you a question to take back to the supplier. Once it's resolved, have the important clarification added to the proposal so you aren't relying on a half-remembered conversation.
Look beyond the build price
The website still needs to run once it's finished. Depending on the setup, you'll have domain renewals, hosting, platform subscriptions, paid extensions and perhaps form, email or support services.
Compare those costs over the same period, such as the first two years. Include the build, required renewals, the support you intend to use and optional work you've actually chosen. Check whether the quoted figures include VAT and when any introductory price ends.
Your team's time belongs in the decision too. Uploading projects and writing pages still takes work when it doesn't appear on a supplier's invoice.
Our proposals separate the plan, scope and costs so you can see how they fit together. Where it helps, we'll also look roughly six months ahead and talk about likely next steps. That makes it easier to understand what's needed now and what you might choose to do later, without treating every possible improvement as a commitment.
A monthly charge needs a closer look than its label. Hosting the site, updating its software, changing a paragraph and restoring a backup are separate jobs. The proposal should make clear which are covered and who takes responsibility when something goes wrong.
Support needs that same precision. Someone responding to a problem is different from promising to fix it within a particular time. Working hours and priorities should be clear enough that you know what to expect.
Make “you own the website” mean something
It's a reassuring sentence. On its own, it leaves a lot unanswered.
The domain account, your content, design files, custom code and third-party licences may have different arrangements. You should know who controls each part, what access you receive and what can move if you change supplier.
That includes what happens when a subscription or support agreement ends. Does the site continue to work? Are there transfer charges or restrictions? Which instructions and accounts would another developer need to look after it?
Access to an editor is useful, but it doesn't settle all of that. Receiving the code is only part of the picture too. You're looking for a working handover that gives the business the continuity it needs.
Give the old website a proper handover
A replacement site has work to do before launch day. Some old pages may still bring in customers, have links pointing to them or contain information worth keeping.
Google's site move guidance recommends mapping old addresses to the right new destinations, setting up redirects and monitoring the move. It also warns that search positions can fluctuate while the changes are processed.
So “move the old site” should have a proper scope. Who reviews the existing content? Who agrees the new destinations? Who checks the redirects after launch? If changing the domain settings could affect business email, that needs an owner as well.
“SEO included” deserves a similar explanation. Page titles, crawlability, internal links, sitemaps and redirects are specific pieces of work. Later content and ongoing improvements may be a separate arrangement. Google's SEO Starter Guide is clear that there isn't an automatic route to first place; a proposal should describe what will be delivered.
Agree what you'll check before signing it off
It's easier to discuss a fault when you've already agreed what the finished website should do.
For a simple service website, you might review whether a visitor can find the right service on their phone, send an enquiry and receive an honest confirmation. Your nominated editor should be able to make the agreed changes using the access and instructions provided.
Then try the less convenient situations. A form is missing a required detail. A payment is declined. A booking needs approval. The customer needs a clear explanation, and the team needs to know what's happened.
Agree who carries out those checks and how an unresolved fault is handled before approval. The same conversation should cover new requests: adding a feature after sign-off is different from correcting work that doesn't meet the agreed scope.
Choose the people and the approach that suit the job
By now, the quotes should tell a much fuller story. You can see the work being offered, the part your team will play and the likely running costs. That gives you room to consider the supplier's relevant work, their explanations and how comfortable you feel working with them.
An existing template or hosted platform can be a good choice when it supports the service. Custom work earns its place when there's a requirement the standard approach can't meet properly.
For example, WordPress can give a business an attractive website that's straightforward to get started with. If more involved booking rules are likely to follow, we'd talk about the available tools, connections and future work before choosing the setup. The platform decision should make sense for where the business is going as well as where it is now.
Our website design and development service brings the structure, design and customer tasks into that discussion. If you've got a current site and a job you need the next one to do, send them over and let's talk. We can start there.
