What a business website really costs in the UK

A business website in the UK can cost anything from a modest four figure sum to a substantial five figure project, and sometimes more. The reason the range is so wide is simple. You are not buying a website in the abstract. You are buying a piece of business infrastructure with a particular job to do, a certain amount of content to organise, and a level of complexity behind it.

When people ask us how much it costs to design a website, the most useful answer is this. The price depends less on whether you want “a new website” and more on what has to change, who is providing what, and how much thinking, writing, integration and testing the job really needs. A five page brochure site, a lead generation site with careful messaging, and a site connected to internal systems are not the same purchase.

What you are actually paying for

A website quote usually covers far more than the visual design. If two suppliers appear to be offering “a website”, but one quote is much higher, the difference is often in the work wrapped around the pages.

The first part is planning. This includes understanding your business goals, the audiences you need to speak to, the actions you want visitors to take, and the problems with the current site. For some businesses this is a short discovery call and a clear brief. For others it means reviewing enquiries, checking where users drop off, mapping services, and deciding what the site should and should not do.

Then comes content structure. This is the sitemap, page hierarchy, navigation, and page purpose. If your current website has grown over time, this stage often saves money later because it stops the build being based on duplicated pages, unclear service descriptions, or a menu that makes sense only to the people inside the business.

Design is the next visible layer, but it is not just choosing colours and layouts. Proper design work covers page templates, mobile behaviour, calls to action, readability, and how information is prioritised. A homepage that looks polished but hides the main service or confuses the next step is not doing its job. Good design also needs to account for accessibility. Clear navigation, readable contrast and understandable controls are established good practice, and the W3C accessibility guidance is a sensible baseline for any business site W3C accessibility design tips.

Build is where the approved design becomes a working website. That can include a content management system, forms, templates, redirects, search functionality, filtering, gated resources, team profiles, location pages, or links into other systems. If the website needs to connect with a CRM, booking platform, stock system, or internal workflow, the build effort rises because those connections need to be specified, secured and tested properly.

Testing is another cost people often underestimate. A business website should be checked on different screen sizes, current browsers, form journeys, error states, page speed, and basic indexing readiness. Performance matters because slow or unstable pages frustrate users, even though a technical score is not a guarantee of rankings or enquiries. Core Web Vitals are a recognised way to assess loading, responsiveness and layout stability Core Web Vitals. If you want a plain English view of this side of the job, our guide to a website that works properly on every screen explains what usually gets missed.

Launch support is the final part. This can include domain and DNS checks, redirects from old URLs, analytics setup, form testing, indexation checks, and a short period of post launch fixes. If a supplier is moving content from an old site, handling email related DNS records, or preserving search visibility during a migration, that work needs allowing for. Google’s own guidance is clear that useful, accessible content and descriptive links help discovery, but rankings are not guaranteed Google SEO Starter Guide.

What makes one website quote higher than another

The biggest cost driver is scope. A ten page website is usually not just twice the work of a five page website. More pages usually mean more decisions, more content review, more internal approvals, and more chances for one unclear section to delay the rest.

Copy is another major factor. If you already have strong, current copy that only needs editing, the project is simpler. If the supplier needs to interview your team, shape your positioning, write service pages, and turn fragmented notes into clear sales copy, the quote will reflect that. The same applies to photography. Existing professional images reduce cost. A need for new photography, image selection, editing and usage planning increases it.

Integrations can move a project from straightforward to technical very quickly. A basic enquiry form is one thing. A form that routes leads by service type, creates records in a CRM, sends internal notifications, and starts an admin workflow is another. At Suffolk Web, we often see this boundary clearly. Some businesses need a clean marketing site. Others need the website to connect to business systems or remove repetitive admin. That can involve custom workflow logic, not just page design.

Revisions matter too. A quote based on one round of consolidated feedback will be lower than one built around multiple review cycles with several stakeholders. If four directors, a sales manager and an external consultant all need separate review rounds, that is project management time, not just “small tweaks”.

Technical complexity increases cost in less obvious ways. Common examples include:

• Membership areas or client portals
• Multi location or multi service page structures
• Event booking or course management
• Advanced filtering or search
• Bespoke calculators
• Migrations from an old CMS
• Accessibility remediation on inherited templates
• Structured redirects from a large existing site
• Compliance requirements for forms or data handling

There is also a difference between a site that simply needs to exist and one that needs to support search visibility from the start. Search work is not magic, and no supplier should promise rankings. But clear information architecture, descriptive page titles, internal linking, crawlable page structure and sensible technical setup all take time. Google’s guidance on AI features also confirms that the same search fundamentals still apply, and there is no special AI schema or text file required just to be considered for those surfaces Google AI features.

If you are comparing offers, watch for hidden assumptions. One quote may include content population, redirects, technical SEO checks and launch support. Another may assume you will provide all copy, upload all content and check all forms yourself. The second quote will look cheaper, but it may not be cheaper by the time the site is actually usable.

When a smaller change is enough

Not every business needs a full redesign. Sometimes the right answer is to fix the part that is losing work.

If your branding is still sound, your service offer is clear, and the site is technically stable, a targeted improvement can be better value than starting again. We often recommend a smaller intervention where the problem is concentrated in one of these areas:

• The homepage is vague and does not explain what you do quickly enough
• Service pages do not answer buying questions
• Forms generate poor quality enquiries
• Mobile layouts make key information hard to use
• The site looks acceptable, but updating it is awkward
• Admin staff are retyping website enquiries into other systems

In those cases, improving a handful of important pages, rebuilding the enquiry flow, or connecting the website to a back office process may solve the real problem. A full redesign would add cost without necessarily improving the outcome.

For example, if your team keeps chasing missing information after every web enquiry, the issue may be the form design rather than the whole site. Better field logic, clearer service options, and a structured handoff into your admin process can make the website more useful without changing every page.

Similarly, if your current site already has authority in search and the structure broadly works, rebuilding from scratch can create unnecessary migration risk. A careful improvement project may be the better commercial choice.

This is especially relevant for independent businesses around Ipswich and the surrounding counties, where owners often need the website to support day to day operations, not just look refreshed. We have seen this across service firms, logistics and operational businesses, including public project accounts connected with Jagelo Haulage, Fleetalyse, Seonis and Logivo.AI. The common thread is not that every business needs more technology. It is that the website should solve the right problem.

If you are unsure, start by asking a simple question. Are we failing because the whole site is wrong, or because one important part of the journey is weak?

How to compare quotes without guessing

A good website proposal should let you compare scope, responsibility and risk, not just the headline figure.

First, check exactly what is included. Ask for the number of page templates, the expected number of pages, whether copywriting is included, whether content upload is included, and what launch support covers. “Website design and development” on its own is too vague.

Then check the exclusions. Common exclusions are photography, copywriting, logo work, email setup, analytics configuration, redirects, SEO checks, accessibility improvements, plugin licences, and ongoing maintenance. There is nothing wrong with exclusions if they are clear. Problems start when they are not mentioned at all.

Content responsibility is a big one. Who is writing the copy, who is uploading it, and who is responsible for chasing missing inputs? A quote can look efficient because it assumes your team will do a lot of work that nobody has actually scheduled.

Accessibility should be addressed in plain terms. A supplier does not need to claim legal perfection to explain how they approach readable text, keyboard friendly navigation, form clarity and mobile usability. If accessibility is absent from the proposal, ask why.

Performance and indexing should also be covered sensibly. That does not mean promises about search position. It means asking whether the site will be built with clean structure, sensible page speed practices, and launch checks for crawlability and indexing. If a supplier talks confidently about “guaranteed page one results”, treat that as a warning sign. Google’s own guidance on local ranking makes clear that relevance, distance and prominence matter, and that a better local position cannot be bought from Google Google local ranking.

Ongoing support matters more than many businesses expect. Ask what happens after launch. Is there a support arrangement, a maintenance option, training, or just a handover? If your site is important to enquiries, you need to know who handles updates, plugin issues, form faults and future changes.

If you want a practical way to compare suppliers, our guide on how to choose a web design agency that fits your business is a useful next read.

How to brief a supplier so the price matches the job

Most poor website quotations begin with an incomplete brief. If the supplier has to guess what you mean, the quote will either be too high to cover uncertainty or too low to cover the real work.

A useful brief does not need technical language. It needs clear business information.

Start with goals. What should the website do over the next year or two? Generate better enquiries, support a sales process, reduce admin, clarify services, help recruitment, or replace an outdated CMS? Put those in order of importance.

Define the audience. Are you selling to consumers, procurement teams, operations managers, landlords, patients, or local trade customers? A website aimed at owner managed businesses will be structured differently from one aimed at public sector tenders.

List the required features. Be concrete. Do you need enquiry forms, booking, downloads, gated files, case studies, staff profiles, location pages, a client login, CRM integration, or links to internal systems? If you already know a process is painful, describe it step by step.

Explain the current problems. Useful examples include:

• We get enquiries, but many are poor fit
• Visitors do not understand the difference between our services
• Updating pages is slow and awkward
• Our mobile site is hard to use
• We rely on email chains for approvals
• Staff re-enter website data into spreadsheets or another system

Set out what already exists. This includes your current website, domain access, hosting details, brand assets, photography, copy documents, analytics access, and any existing integrations. Missing access is a common cause of delay.

Name the decision makers and approval process. If one person signs off, say so. If content must be approved by several people, say that too. It affects timing and revision planning.

State any important constraints. These might be compliance requirements, procurement rules, internal IT policies, or a hard dependency such as “the new forms must feed into our existing CRM”.

If you want a simple starting point, our website enquiry checklist will help you gather the information a supplier actually needs.

What to do next if you need a realistic quotation

If you need a quotation that reflects the real job, the next step is not to ask three suppliers for “a price for a website” and hope the numbers line up. The better approach is to write down your goals, list the pages or features you think you need, explain the current problems, and be clear about what you can provide internally.

That gives us something concrete to assess. We can then tell you whether you are looking at a full website project, a focused improvement to key pages, or a simpler operational fix that does not require a full redesign at all.

At Suffolk Web, we handle website design, search visibility, AI assisted workflows where they genuinely fit, and connected business systems through Fleeta Limited. That means we can look at the website as part of the wider process, not just the visual layer. If the answer is better page structure and clearer copy, we will say that. If the answer is a form and workflow fix rather than a rebuild, we will say that too.

When you are ready, send us the outline through our project enquiry form or contact us about your website and process requirements. A realistic brief produces a realistic quotation, and that is the quickest way to find out what your website project actually needs.