Why two quotes for “a website” differ by a factor of ten
A business asks three providers for a website and gets back three numbers that barely resemble each other. The natural conclusion is that someone is overcharging.
Usually something less dramatic is happening: the three providers heard three different projects. “A website” describes an outcome, not a scope, and the work behind that outcome varies enormously.
Understanding the variables makes proposals comparable. Without that, the only available comparison is price, which reliably selects for whoever understood the project least.
Scale
The most obvious variable, and the one most people underestimate.
A five-page site presenting a single service is a fundamentally different project from a forty-page site covering a dozen services across several locations. Not because pages are expensive individually, but because structure gets harder as it grows. Forty pages need a navigation scheme, a linking strategy, and decisions about what belongs where.
Worth noting: page count should follow what the business needs to explain, not the other way around. Pages created to inflate a site tend to be thin and to underperform.
Whether the content exists
This is the variable that most often surprises people, and it moves budgets more than design does.
If a business has accurate, complete copy ready, a build is straightforward. If the copy needs to be researched, structured, and written — service explanations, page structure, the wording that makes someone act — that is substantial work, and it is the work most likely to determine whether the site succeeds.
Photography sits in the same category. Real photographs of the business, the team, and the space consistently outperform stock imagery. Whether they exist changes both cost and outcome.
When a proposal seems low, the first question is usually whether content is included or assumed.
Design approach
Broadly three levels:
Template. An existing theme, adjusted. Fastest and cheapest. The constraint is that the structure was designed for a generic business, so the specific business gets fitted into it.
Customized template. A framework, significantly reworked. A middle ground.
Custom design. Structure and layout designed for this business, its services, and how its customers decide. More work, and appropriate when differentiation matters or the business does not fit a standard shape.
None is correct universally. A new business testing an idea is often best served by a template. An established practice competing on credibility usually is not.
Technical requirements
Everything beyond presenting information:
- Booking or scheduling systems.
- Payments or e-commerce.
- Customer accounts or logins.
- Integrations with existing software.
- Custom calculators, configurators, or interactive tools.
- Multiple languages.
Each turns a website into something closer to an application. This is usually the largest single driver of cost when it is present.
Whether something already exists
Building from nothing is often simpler than working with a site already in place.
An existing site brings existing search visibility, existing URLs, and existing content. Preserving that during a rebuild means mapping old addresses to new ones, migrating content carefully, and handling the technical details that determine whether traffic survives the transition.
That work is invisible when done well and very visible when skipped. A redesign that quietly discards years of accumulated search equity is expensive in a way that does not appear on the invoice.
Technical foundations
Some things are hard to add later and comparatively cheap to build in:
- A structure that reflects how people actually search.
- Metadata and structured data done properly.
- Performance built in rather than optimized afterward.
- Accessibility considered during design.
- Analytics and Search Console configured correctly.
A quote that excludes all of this is cheaper for real reasons. The savings often reappear later as a rebuild.
What happens after launch
A website is not finished at launch. Software needs updates, content goes stale, and search visibility responds to ongoing attention.
Some engagements end at launch and hand over the keys. Others include ongoing work. Neither is wrong, but they are different products, and comparing a launch-only quote against one including twelve months of support is not a comparison.
How to read a proposal
Given all of this, the useful questions are:
- What is the scope, in pages and functionality?
- Who writes the content, and is that included?
- Who provides photography?
- Is this a template, a customization, or a custom design?
- What happens to the existing site’s search visibility?
- What technical foundations are included?
- What happens after launch, and what does that cost?
- Who owns the site, the domain, and the content?
A provider who can answer these clearly has thought about the project. One who cannot has quoted a guess.
That is why Webbify does not publish fixed prices. Every project is scoped around the business, website, content, technical requirements, and long-term goals. After an initial conversation and review, we recommend an approach and provide a clear proposal. More on how that works.