Let’s talk

Websites

How to compare website proposals without choosing on price alone

Use a like-for-like checklist for scope, content, ownership, launch, support and the real first-year cost.

Two website proposals can quote very different prices while describing different work. Before choosing, put them on the same page: what will be built, what you must supply, what happens after launch and what you own if you leave.

Do not treat a lower price as a warning in itself. A smaller scope may be exactly right. The problem is an unclear scope that makes the price impossible to interpret.

Compare the actual deliverables

Ask each provider to describe the pages, features and content work included. “Five-page website” does not tell you whether the provider writes the copy, edits material you supply, sources photographs, connects a form or sets up analytics. Note which of those you need and which you can do yourself.

QuestionProposal AProposal B
Which pages and features are included?
Who writes, supplies and approves the copy?
Who provides images and confirms usage rights?
Where do form enquiries go, and how is delivery tested?
How many design revisions and launch checks are included?
Who controls the domain, hosting and source files?
What support, backups and updates follow launch?
What costs extra or starts a new quote?

An empty answer is a question to ask, not necessarily a reason to reject a provider. The goal is to make the decision explicit before work starts.

Calculate the same time period

Compare total cost over the period you expect to use the site. Include setup, monthly fees, domain renewal, paid software, content creation and any applicable VAT. A £500 build with separate hosting and support can cost more over a year than a higher initial quote with those services included; the reverse can also be true. Use the figures in the actual proposals rather than assumptions.

Check when payments begin and whether there is a minimum term. Ask what happens if the work changes or you leave after that term. The written proposal should make ownership and handover clear enough that another provider could understand what exists.

Test the route from promise to launch

Ask what you will be shown before launch and how you will accept the result. A useful acceptance check is concrete: “The site explains each agreed service, works on a phone, sends a test enquiry to the agreed inbox and uses the approved words and images.” Add any business-specific requirements, such as service-area wording or a booking integration.

Choose the proposal that describes a suitable result, responsibilities and support at a price you can sustain. If one provider has understood the problem better but left a key item out, ask for a revised scope; do not compare unlike quotes as though they were the same product. The website pricing page shows one fully described offer you can use as a comparison point.

Put the thinking into practice

Make the next step clearer.

Explore how I can help with your business website, or tell me what you have in mind.

Explore websites