Website pricing becomes confusing because radically different jobs are sold under the same label. A simple credibility site, a conversion-focused enquiry system and an ecommerce rebuild can all be described as “a website” while carrying completely different responsibilities. A universal price table creates false precision unless those responsibilities are fixed first.
Three different jobs can all be called a website
A credibility site primarily needs to explain who the business is, what it does and why it is legitimate. A lead-generation site must also attract or orient the right buyer, build confidence, capture useful context and connect that enquiry to a commercial next action. An ecommerce or connected site adds product, transaction and operating responsibilities.
These are not quality tiers. They are different jobs. The sensible budget follows the job being bought.
Price follows responsibility
A low-risk information site and a site responsible for generating, qualifying or transacting meaningful revenue should not be scoped the same way. Commercial responsibility changes the research, UX, content, proof, QA and integration work required.
Ask what the business would lose if this part of the journey failed. The answer often explains why two superficially similar proposals carry different levels of work.
Content and proof are part of the build
Projects are regularly under-scoped because copy, photography, product information, case evidence, reviews, policies and other decision material are treated as things that will “be added later”. They are part of the customer experience.
A cheaper build can become an expensive stalled project when nobody owns the content and proof required to make the pages commercially credible.
Integrations create operating scope
Forms, CRM, ecommerce, payments, booking, analytics, automation and reporting connect the website to the business. Those connections often matter more than page count.
Define what should happen after a form, booking or order. A website that hands work into the business carries more responsibility than one that ends at a contact detail.
Migration and technical debt can change the job
A clean new site and a rebuild that must preserve URLs, products, content, analytics, integrations or legacy behaviour are different projects even when the finished page count is identical.
The proposal should make migration assumptions explicit instead of discovering them after design is approved.
Compare proposals by responsibility, not page count
Check who owns strategy, information architecture, copy, proof gathering, design, implementation, mobile QA, forms, analytics, redirects, integrations, launch and post-launch fixes. A low quote may be completely appropriate when the responsibility is genuinely narrow.
The comparison becomes misleading when one proposal includes the commercial thinking and operating connections while another prices only page assembly.
A cheaper website can be the right answer
If the business needs a small credibility layer, has finished content and proof, requires no material integrations and does not expect the site to carry a complex conversion job, a lean build can be the sensible choice.
Do not add strategy theatre to a simple job. Scope should expand only when the commercial responsibility justifies it.
Ask what will be different after launch
A useful proposal should make the intended change explicit: clearer positioning, stronger buyer confidence, a better enquiry path, improved ecommerce journey or easier operations. If the only required difference is appearance, scope the project accordingly.
Where the desired outcome is commercial but the current constraint is still uncertain, diagnose that constraint before committing to the larger build.
Choose scope from the commercial job, the evidence and operating responsibility — not from an arbitrary page count or a generic market price table.