wo web development quotes can differ by thousands while appearing to describe the same website. Usually they do not describe the same result. One may include strategy, copy migration, accessibility testing, redirects and post-launch support; another may price design and coding only. A fair comparison rebuilds each proposal into the same set of outcomes, responsibilities and lifetime costs.
- Discovery, research and information architecture.
- Copywriting, content entry, migration, photography and asset preparation.
- Design system, page templates, responsive states and interaction.
- Features, integrations, data work and third-party setup.
- Accessibility, browser, device, performance, security and failure-path testing.
- Analytics, redirects, deployment, training, documentation and warranty.
Mark each item as included, excluded, assumed, optional or unclear. Then ask suppliers to resolve the unclear cells. The purpose is not to force identical methods; it is to expose whether the final live result and the client workload are comparable.
A lower quote may depend on the client delivering final copy, correctly sized images, data exports, account access and consolidated feedback on precise dates. Those are real project costs. Estimate internal time and the consequence if a dependency arrives late. A quote becomes more expensive when it quietly transfers work to a team that has no capacity to perform it.
Record who controls the domain, hosting, repository, CMS, analytics and third-party accounts. Add software subscriptions, platform plans, payment fees, support, hosting, maintenance and likely renewal costs. Ask what can be exported and what happens if the supplier relationship ends. A proprietary convenience may be worthwhile, but it should be a conscious lifetime decision.
Understand what the supplier considers out of scope, how additional work is estimated, who approves it and how milestones are accepted. A fixed quote can move dramatically if assumptions are loose. An hourly quote can still be controlled with priorities, forecasts and caps. Look for a mechanism that makes change visible before it becomes an invoice.
Verify relevant work, meet the people responsible, and ask how difficult decisions, quality issues and delays are handled. Consider clarity, candour, communication, technical fit and the team’s ability to operate the finished system. Do not invent a false numerical precision; use a scorecard to make tradeoffs discussable, then apply judgement.
Thecheapestquoteisthecheapestequivalentoutcome—notthesmallestnumberonpageone.
Put each quote against the same rows and mark included, excluded, assumed and unclear. Ask suppliers to resolve material gaps in writing. A £5,000 quote and a £12,000 quote may describe different content responsibility, integrations, quality work and post-launch ownership rather than different margins.
- Outcome and priority journeys.
- Page templates, content population and migration.
- Design originality and responsive states.
- CMS, identity, integrations and exceptional states.
- Accessibility, performance, security and technical SEO evidence.
- Testing, acceptance, launch and correction period.
- Source, accounts, licences, data and documentation ownership.
- Hosting, vendor, maintenance and change costs for year one.
Score uncertainty separately from price. A low total with many unpriced assumptions can carry more budget risk than a higher fixed scope. Also compare communication cadence, the actual delivery team and whether the project remains transferable.