A UK business website can require anything from a few thousand pounds for a focused brochure site to tens of thousands for a bespoke, content-rich or integrated platform. Those are planning estimates, not market prices or quotations. The reliable number comes from a scoped quote covering pages, content, design, functionality, integrations, migration, accessibility, testing and post-launch support.
Budget should follow the job the website must do. A five-page credibility site, a lead-generation site with a CMS and an account portal are different products even if all three are called “a website”.
What outcome are you buying?
Write a one-page brief before asking for prices. Name the audiences, their priority tasks and the business action you want them to take. Include current problems, required launch date, internal decision-makers and any immovable technical or regulatory constraints.
Useful success measures might include qualified enquiry completion, successful recruitment applications, reduced support requests or the proportion of important pages that meet agreed performance and accessibility checks. Traffic alone does not show that a site is useful.
Separate requirements into must-have for launch, should-have soon and later possibilities. This lets suppliers propose a credible first release without quietly removing essentials.
What planning ranges are reasonable?
For early budgeting only, a template-led brochure website might sit around £2,000–£7,000; a custom marketing website with research, tailored design, CMS, migration and careful testing might sit around £7,000–£25,000; and a complex site with accounts, substantial integrations, multilingual content or bespoke application behaviour may start around £25,000 and rise materially.
These are broad planning bands, exclude or include VAT depending on the supplier, and require a scoped quote. They are not a tariff. Geography alone does not determine cost, and a higher quote is not automatically better.
Ask every supplier to state:
- Deliverables and excluded work
- Number of templates or page types, not merely page count
- Content writing, entry and migration responsibilities
- Revision and approval process
- Third-party licence and usage charges
- Hosting, maintenance and support costs
- Assumptions about integrations and supplied data
- Acceptance criteria and warranty period
Which variables change the quote most?
Content is a frequent hidden cost. Rewriting service pages, sourcing evidence, obtaining photography, producing case studies and migrating years of articles can exceed the effort of coding the templates. Decide who writes, reviews and enters each item.
Custom interaction and integrations also increase discovery and testing. A CRM form that creates records, assigns consent and handles failures needs more work than an email form. Ecommerce adds products, tax, fulfilment, payment, refunds and transactional communications. Membership adds identity, permissions, account recovery and personal-data controls.
Other variables include stakeholder count, legacy quality, multilingual workflows, design originality, analytics, cookie controls, search, calculators and external approval requirements.
Should you choose a template or custom build?
A good template can suit a small organisation with standard content and a limited budget. Check whether it supports your content structure, brand, accessibility and performance without many plugins or overrides. “Customised” may mean colours applied to a standard theme, so ask what is actually unique.
A custom design is useful where differentiation, complex journeys or a scalable component system matters. Bespoke functionality is justified when standard products cannot support a valuable process. Custom should not mean undocumented or dependent on one developer.
Choose the least complex approach that meets the validated need and leaves a sensible route for change.
What quality standards belong in the brief?
Accessibility should be planned from research through content and testing, not added at the end. Use WCAG 2.2 as the technical reference and state the intended conformance level. Automated checks help but do not replace keyboard, screen-reader and human review. Public-sector organisations have specific UK accessibility duties; GOV.UK accessibility requirements explain that context.
Require secure development, supported dependencies, backups and a clear patching owner. The NCSC guidance for small organisations provides a practical security baseline.
For search, insist on crawlable content, meaningful page titles, redirects for changed URLs, a sitemap and measurement setup. Google’s SEO Starter Guide describes durable fundamentals without promising rankings.
What are the ongoing costs?
Launch is the start of ownership. Annual budgeting may include domain renewal, hosting, CDN, premium software, analytics or consent tools, security updates, backups, monitoring, content changes, accessibility reviews and support. Ecommerce and high-traffic services may add transaction or usage fees.
Ask for a three-year ownership view. Clarify whether support is a retainer, prepaid allowance or time and materials. Define response targets separately from resolution times. Ensure your organisation controls the domain and has administrative access to hosting, source code, analytics and third-party accounts.
Beware a low build price tied to an unclear proprietary subscription or no migration route. Equally, do not pay for enterprise infrastructure a small brochure site does not need.
How should quotes be compared?
Create a comparison against your brief, not a single price column. One proposal may include research, copy support and migration while another assumes finished content and an approved design. Resolve those differences before selection.
Quote review checklist
- Scope maps to priority user journeys
- Content ownership and migration are explicit
- Mobile, browser and device coverage is defined
- Accessibility target and testing method are stated
- Performance, analytics and SEO foundations are included
- Security, backups and update ownership are clear
- Source code and account ownership are documented
- Milestones depend on tangible deliverables
- Change requests have an agreed process
- Recurring fees and exit arrangements are visible
What should happen before work starts?
Confirm one accountable client lead and a realistic review timetable. Give the supplier access to analytics, brand assets, existing content and subject experts. Identify legal review needs early.
Agree how acceptance works. Rather than “modern and fast”, specify supported journeys, content types and measurable checks. Keep a written decision log. If discovery reveals major uncertainty, re-scope before committing the entire build budget.
Frequently asked questions
How long does a business website take?
A focused site can take several weeks; a substantial custom site can take months. Content readiness, feedback and integrations often control the timetable. Request a schedule based on your actual scope.
Is hosting included in website development?
Sometimes. Ask who contracts with the host, what environments and backups are included, and how charges can change with usage.
Do I need an ongoing maintenance plan?
Someone must own updates, monitoring and recovery. That may be your team, a supplier or both. The responsibility matters more than the label.
Can a supplier guarantee Google rankings?
No supplier controls organic rankings. Buy sound technical foundations, useful content and transparent measurement, not guaranteed positions.
