What a business website should cost in the UK

If you are trying to budget for a business website in the UK, the honest answer is that the cost depends less on the label and more on the work included. Two websites can both be described as a "new site" while involving very different amounts of planning, writing, design, technical setup, approvals and post launch responsibility.

That is why discussions about web design cost in the UK often feel vague. The useful question is not just "what does a website cost?" but "what are we paying for, what is excluded, and what problem is the site meant to solve?" For most businesses in Ipswich and across the UK, the right answer sits somewhere between a basic brochure site and an overbuilt platform that creates more admin than value.

What you are actually paying for

A website quote usually combines several different types of work. If these are not separated, it is hard to compare one proposal with another.

First, there is discovery and planning. This is the work done before any design starts. It includes understanding your business, your services, your customers, your enquiry process, your competitors, and the actions you want people to take. If a supplier is asking sensible questions early, that is usually a good sign. If they jump straight to colours and layouts, important decisions may be getting skipped.

Then there is design. This covers page layouts, visual hierarchy, mobile behaviour, calls to action, navigation, forms and component styles. Good design is not decoration. It should help visitors understand what you do, who it is for, and what to do next.

After that comes the build. This is the development work that turns approved designs into a functioning website. It includes templates, content management setup, responsive behaviour, forms, tracking, performance work, testing and deployment. A custom build will usually involve more work than adapting a theme, but a theme based site still needs careful setup if it is going to be maintainable.

Content is often a separate cost, even when it is not shown separately. Someone has to write, edit, structure and enter the words on the page. The same applies to images, team photos, service illustrations, diagrams and case studies. In many projects, content is the part that slows everything down most.

There is also technical setup. That can include domain and DNS changes, hosting setup, SSL certificates, redirects from old URLs, form routing, analytics, cookie controls, Search Console and Bing Webmaster Tools setup, and local business details where relevant. If a business depends on local enquiries, accuracy and consistency matter, but no supplier can buy a better local position from Google. Google states that local ranking depends on relevance, distance and prominence, not payment to Google (Google local ranking guidance).

Revisions are another real cost. A project with one decision maker and clear approval points is usually more efficient than one with six stakeholders sending comments by email over three weeks. Unlimited revisions are rarely truly unlimited. They usually mean the cost is hidden elsewhere, or the scope is loose enough to drift.

Finally, there is ongoing responsibility. Launching a site is not the end of the work. Content updates, plugin updates, backups, hosting support, search visibility checks, form testing and small improvements all need ownership. If nobody is responsible after launch, even a good site can become stale or unreliable.

When we scope website design and improvement work, we separate these areas as clearly as possible so businesses can see what is included, what depends on them, and what happens after launch.

What usually makes the price go up or down

The biggest cost drivers are usually practical, not glamorous.

Page count matters, but not just because there are more pages. More pages usually mean more structure, more content decisions, more internal links, more approvals and more opportunities for inconsistency. A ten page site with clear source material can be simpler than a five page site where nothing has been written yet.

Copy is one of the biggest variables. If you already have clear, current service information, case studies and answers to common customer questions, the project is easier. If the supplier has to extract your offer from scattered notes, old PDFs and a few phone calls, that takes time. Many businesses underestimate this.

Photography can also change the cost quickly. If you need fresh team photos, premises shots, process photography or product images, that is a separate piece of work. Stock imagery may be enough in some cases, but for many local service businesses, real photography helps trust far more than generic visuals.

Integrations increase complexity. Examples include CRM forms, booking systems, payment tools, stock systems, membership areas, job feeds, event systems, postcode lookup, delivery calculators or internal dashboards. Each integration brings setup, testing, failure points and support questions. If the website also needs to connect to internal workflows, the work may move beyond a standard brochure build. In those cases we sometimes end up discussing workflow automation or a lighter internal tool rather than forcing everything through the website.

Approvals make a large difference. A business with one owner manager can often move quickly. A business with directors, operations, marketing and compliance sign off will need more structured checkpoints. Neither is wrong, but the second needs to be planned for.

Accessibility expectations also affect scope. In the UK, accessibility duties can arise under the Equality Act 2010, and public sector websites have their own specific regulations. Private sector businesses are not all under the same formal website rules as the public sector, but accessible design is still good commercial practice and helps users complete tasks. Clear navigation, readable contrast, understandable forms and usable controls are established good practice (W3C accessibility tips).

Performance expectations matter too. If you want a site that feels fast on mobile, handles media carefully and avoids layout jumps, that requires attention during design and build. Core Web Vitals are a useful technical reference for loading, responsiveness and visual stability, but they are not a guarantee of sales or rankings (web.dev on Core Web Vitals).

The same applies to search visibility. A supplier can build the basics properly, such as crawlable pages, descriptive links, sensible page titles, clear information architecture and indexation checks. Google’s own guidance is clear that useful content and good site structure support discovery, but rankings are not guaranteed (Google SEO Starter Guide). If someone bundles "guaranteed first page" into a website quote, treat that as a warning sign.

When a smaller change is enough

Not every business needs a full new website.

Sometimes the real problem is that the current site does not guide people to enquire. In that case, a homepage restructure, clearer service pages, better calls to action, stronger proof points and a simpler contact process may be enough.

Sometimes the site looks acceptable, but the content is weak. If visitors cannot quickly tell what you do, where you work, what kind of jobs you want, and how to take the next step, rewriting key pages may do more than a visual redesign.

Sometimes the issue is internal. We see businesses where enquiries arrive by email, get forwarded manually, sit in someone’s inbox, and then receive inconsistent follow up. Rebuilding the website will not fix that on its own. A better process for assigning, tracking and responding to enquiries may have more impact.

Sometimes there is a technical issue rather than a design issue. Slow pages, broken forms, duplicate locations, indexing confusion, or poor mobile behaviour can all reduce the value of an otherwise decent site. Google’s page indexing reporting can help identify why a URL is excluded, and Google is clear that not every excluded URL should be indexed (Page indexing report guidance).

And sometimes the answer is simply focus. If you have twenty services listed but only five are commercially important, the site may need clearer priorities, not more pages.

This is often the right starting point for smaller firms in Suffolk, Essex, Cambridgeshire and Norfolk. A targeted improvement can be more useful than a complete rebuild, especially if the existing domain, content and customer familiarity still have value. We cover this thinking in our piece on web design that helps a small business win better enquiries.

How to compare quotes without guessing

When you receive two or three website proposals, look past the headline total.

Start with scope. How many templates, page types and forms are included? Is copywriting included, partly included, or assumed to be supplied by you? Are images included? Is content entry included, or are you expected to upload everything yourself?

Check exclusions carefully. Common exclusions include logo work, photography, copywriting, integrations, accessibility remediation, migration of old blog posts, redirects, analytics setup, cookie controls, training and post launch support. None of these are unusual exclusions, but they should be visible.

Ask who owns what at the end. You should know who controls the domain, hosting account, CMS access, analytics property, Search Console, design files and licensed assets. If a relationship ends, the handover should be clear.

Hosting needs its own line of questioning. Is hosting managed? Are backups included? How are updates handled? Who monitors forms? What is the process if the site goes down? Cheap hosting can be perfectly adequate for some sites, but only if somebody is responsible for the basics.

Support after launch is another area where quotes differ sharply. Some include a short warranty period for fixes only. Others include ongoing support time. Others stop at launch and leave everything to you. None of those models is automatically wrong, but they are not equivalent.

Check whether analytics and search basics are included. At minimum, you want to know whether reporting tools are being set up properly, whether key actions are being tracked, and whether the site structure supports discovery. Google’s guidance on AI features also makes clear that the same search fundamentals still apply, and there is no special AI schema or text file required simply to appear in AI powered search experiences (Google AI features guidance).

Also ask what happens after launch. Is there a scheduled review after a few weeks? Who checks whether forms are working? Who reviews which pages attract visits and which pages are ignored? A site that launches and is never reviewed usually leaves value on the table.

If a proposal is hard to compare, ask for it to be rewritten in plain scope headings. A good supplier should be able to tell you, in straightforward terms, what they are doing, what they need from you, and what is not included.

How to brief a supplier so the quote is useful

A vague brief produces a vague quote. If you want realistic proposals, give practical information.

Start with goals. What should the website help you achieve over the next 12 months? More quote requests? Better quality enquiries? Fewer irrelevant calls? Easier recruitment? Less admin? Clearer local visibility? These are different jobs.

Describe your users. Who visits the site, and what do they need to know before contacting you? A homeowner comparing trades is different from a procurement manager looking for a supplier. A returning customer trying to find a phone number is different again.

List the core pages you think you need. Not a perfect sitemap, just a sensible first pass. Home, about, services, service areas, case studies, FAQs, contact, careers, resources, policies, and so on.

Be honest about content. Do you already have usable text? Who will approve it? Are there existing brochures, proposals, sales emails or internal notes that explain your services clearly? Good source material shortens the process.

Explain your systems. Do enquiries need to go into a CRM? Does the site need to connect with a booking tool, stock system, finance platform or internal workflow? If staff currently copy information from one place to another, mention it. Sometimes the useful answer is not a larger website, but a small connected system.

State who approves what. Name the decision maker, the reviewers and the final approver. This sounds administrative, but it can save weeks.

Mention constraints early. Brand rules, compliance wording, franchise limitations, sector specific requirements, existing hosting contracts, procurement rules, or a planned rebrand all affect scope.

Finally, say what success would look like three months after launch. That helps the supplier focus on outcomes that matter in practice, not on adding pages for the sake of it.

If your business is also thinking about internal tools, AI assisted workflows or visibility beyond standard search, it helps to say that upfront. At Suffolk Web, that is where our wider work through Fleeta Limited, including projects such as Logivo.AI, Fleetalyse and Seonis, can shape the brief sensibly. The point is not to force AI into the project. It is to understand whether there is a repetitive workflow that actually needs solving. Public project accounts such as Jagelo Haulage are useful examples of operational context, but they are not a reason to overcomplicate a straightforward website.

What good value looks like after launch

A good website is not good value because it looked polished on launch day. It is good value if it stays useful.

The first test is usability. Can a first time visitor understand what you do, where you work, who it is for, and how to contact you without hunting around? Can they do that on a phone just as easily as on a desktop?

The second test is maintainability. Can someone in your business update a page, add a case study, change a team member or publish a notice without breaking the layout? If every small change requires a developer, the true cost may be higher than the quote suggested.

The third test is visibility basics. Are important pages indexable where appropriate? Are titles, headings and internal links sensible? Is the content genuinely useful to the people you want to reach? Search fundamentals still matter in both standard search and AI assisted search experiences (Google SEO Starter Guide, Google AI features guidance).

The fourth test is enquiry handling. When a person submits a form, what happens next? Who receives it? How quickly is it reviewed? Is the information complete enough to act on? A site can generate interest and still underperform commercially if the follow up process is weak.

The fifth test is whether the site reduces friction internally. Does it answer common questions before people call? Does it guide visitors to the right service? Does it reduce repeated back and forth? Sometimes that is where the real value appears.

That is the standard we use at Suffolk Web. We are based in Ipswich and work with businesses across Suffolk, Essex, Cambridgeshire, Norfolk and the wider UK. Our job is not to sell a bigger website than you need. It is to help you work out what should change, what can stay, and what needs proper ownership after launch.

If you want a practical proposal rather than a guess, send us a brief through our quotation request page at /start-a-project or contact us at /contact. The more clearly you describe the business problem, the more useful the quote will be.