Quote comparison · reviewed 26 Sep 2026
Price bands vary too much to be useful without deliverables. Compare how much is being researched, designed, built, populated, integrated, tested and handed over.
The same total can describe very different work; the written scope is the comparison unit.
Quick answer
Website quote levels differ in the amount of discovery, original design, page and content work, integrations, testing, accessibility, performance, training and post-launch support. A starter site may use a small set of proven components; a business site adds tailored structure and content; commerce adds catalogue, checkout and operations; an application adds roles, data and workflows.
Ask for deliverables rather than relying on a price-band label.
Suitable when the offer and next action are simple.
Expect a small page set, an adapted visual system, supplied or lightly edited content, one clear enquiry route, baseline mobile and accessibility checks, and a defined handover. Confirm whether analytics, Search Console and business listings are included rather than assumed.
Adds information architecture, tailored components and multiple customer journeys.
Expect discovery, a page plan, original layout decisions, service-level pages, stronger proof, form routing, metadata, reusable editing patterns and broader testing. Confirm the number of distinct templates and populated pages.
The cost shifts into research, writing, review and governance.
Expect topic and intent mapping, editorial templates, subject-matter review, internal linking, location-specific evidence, migration rules and a publishing workflow. Bulk near-duplicate pages are not a substitute for this work.
A transaction adds operational requirements beyond page design.
Define catalogue and variation count, tax, payment, shipping or slots, notifications, refunds, roles, reports, legal copy, test cases and staff training. Third-party provider terms and recurring costs should be separate.
When different users create, change or approve data, requirements drive the estimate.
Document user roles, permissions, data, integrations, edge cases, security, audit needs, environments, acceptance tests and ongoing ownership. A single “website development” line cannot responsibly cover this category.
Normalise the proposals before comparing totals.
Use columns for discovery, templates, populated pages, content, features, integrations, data migration, accessibility, performance, browsers/devices, security, analytics, ownership, training, defect support, recurring charges, exclusions and change control.
Questions
Next step
Send the brief and receive a written scope, assumptions, exclusions and third-party costs.