How much doesa business website cost?

There is no useful single price for every website

A website can be a small brochure, a content-heavy marketing platform, an online store or the public part of a larger application. Each requires different planning, design, content, development and testing. A credible estimate must be tied to a defined scope and assumptions.

Page count is only one cost factor

A five-page website with custom booking, payments and several integrations can require more work than a twenty-page informational site built from a small set of reusable templates. Count unique layouts, behaviours and content requirements—not only URLs.

• Discovery, information architecture and conversion planning.
• Custom visual design, responsive states and interaction work.
• Writing, editing, photography, illustration and content entry.
• Forms, calculators, search, booking, payments or external integrations.
• Content-management permissions and editorial workflows.
• Accessibility, performance, analytics and technical SEO requirements.

Content can change the entire estimate

A design cannot be completed properly without knowing what each page must communicate. If the business needs help interviewing stakeholders, writing service pages, preparing case studies, selecting images or migrating older content, that work should appear in the proposal. Client-supplied content reduces cost only when it is complete, approved and ready on time.

Good to know: Late content often creates layout rework and launch delays. Assign an owner and approval date for every important page before development is nearly finished.

Custom functionality needs deeper planning

Any feature that stores information, applies rules or connects with another service needs requirements, error handling, security and testing. A request described as “just a form” may involve conditional fields, file uploads, spam protection, notifications, CRM synchronisation and privacy consent.

Understand common pricing approaches

A fixed project price can work when deliverables and assumptions are clear. Time-based billing fits discovery, evolving requirements and ongoing improvements. A phased model can price discovery first and estimate implementation once important unknowns have been resolved.

• Fixed price transfers some estimation risk to the supplier but requires controlled scope.
• Time and materials provides flexibility but needs budget visibility and frequent review.
• A monthly retainer suits continuing optimisation and support, not an undefined initial build by itself.

Budget for costs beyond the initial build

The total cost of ownership includes services required to keep the site available, secure and effective after launch. Some are annual or monthly, while others occur only when content, integrations or business requirements change.

• Domain registration, hosting, email and certificate costs where applicable.
• Premium fonts, stock media, plugins, APIs and software subscriptions.
• Backups, monitoring, security updates and technical maintenance.
• Content updates, SEO work, analytics review and conversion improvements.
• Support for third-party changes, new browser behaviour or regulatory requirements.

Compare quotations on the same basis

A low quotation may be completely suitable for a simple need, or it may omit important work. Request a written breakdown so each proposal can be compared fairly.

• Exact pages, templates, features and integrations included.
• Responsibility for writing, images, data entry and migration.
• Revision limits, testing, deployment and training.
• Hosting, licence and third-party charges.
• Warranty, support response and post-launch maintenance.
• Ownership of source code, design assets and accounts.

Reduce cost without weakening the result

Prioritise the pages and functions needed for the first business outcome, then add validated improvements later. Reuse a strong design system, prepare content early and avoid integrations that do not remove meaningful work. Cutting accessibility, security, mobile quality or testing usually creates a more expensive problem after launch.

Get a realistic estimate

Prepare the business goal, audience, required pages, examples, content status, integrations, launch constraints and expected post-launch support. The development team should identify assumptions and unresolved questions before presenting a final estimate.

Good to know: Treat an immediate price given without requirements as a rough indication only. It should not be used as the final project commitment.