How long does it take to build a business website?

A small brochure site with content ready can go live in two to four weeks. A typical service business site with a proper content structure takes four to eight weeks. eCommerce or custom functionality pushes it to two or three months. The most common cause of delay is not development; it is waiting for copy, images and sign-off.

Do I need a custom-designed website or will a template do?

A well-chosen template is fine for many small businesses, especially at launch. Custom design earns its cost when your content does not fit a template's shape, when you need to stand apart in a crowded local market, or when the site has to do something specific such as quoting or booking.

Should my website be built with SEO in mind from the start?

Yes. URL structure, page hierarchy, headings, internal links and speed are all decided during the build, and changing them later costs more than getting them right first. That does not mean buying an SEO package at launch; it means the developer should know what a crawlable, well-structured site looks like.

Will I be able to update the website myself?

You should be, and it is worth asking exactly how before you sign. Ask to see the editing screen for a service page. If changing a price or adding a team member requires the developer, every small update becomes a bill and the site goes stale.

Who owns the website once it is built?

You should own the domain, the hosting account, the content and the code. Agree this in writing. The most painful situations I see are businesses whose domain is registered in a former developer's name, which turns a simple change of supplier into a negotiation.

Is a website still worth it if most of my customers find me on social media?

Usually, yes. Social platforms control your reach and can change the rules or suspend an account overnight. A website is the one channel you own, it is what Google shows when someone searches your name, and it is where people go to check you are real before they pay.

Web Development 14 min read Sajid Aslam5 October 2026

Business Website Development: The Complete UK Guide

Every decision in a business website project, in the order you actually have to make them, with the trade-offs spelled out.

Decision map for a UK business website project from brief to launch

Short answer

Business website development is planning, building and launching a site that does a defined commercial job: generating enquiries, taking bookings or selling. Decide the job first, then the pages, then the platform, then the budget and who builds it. Most projects that go wrong picked the platform or the designer before anyone wrote down what the site had to achieve.

Business website development is the work of planning, building and launching a website that has a specific commercial job: bringing in enquiries, taking bookings, selling products, or giving people enough confidence to pick up the phone. The design is part of it. So is the code. But the decisions that decide whether the site earns its cost are made before either starts.

I have built business websites for eight years, mostly as one person working directly with the owner. This guide is the order I would want a client to think in, with links to deeper articles on each decision.

What business website development actually covers

People tend to picture design and code. Those are two of about eight pieces, and the others are where projects fail.

Piece	What it is	What goes wrong when it is skipped
Goal	The one thing the site must achieve	A good-looking site that nobody acts on
Content and structure	Which pages exist and what each one says	Pages that compete with each other, or gaps where a page should be
Platform	WordPress, Next.js, a builder, Shopify	A platform that fights the business model
Design	Layout, typography, visual hierarchy	Pretty, but the next step is hard to find
Development	Templates, functionality, integrations	Fragile code nobody else can maintain
SEO foundations	URLs, headings, metadata, structured data	Invisible in search despite good content
Performance and accessibility	Speed on a phone, usability for everyone	Lost visitors and possible legal exposure
Launch and care	Redirects, analytics, backups, updates	Lost rankings, broken forms, silent decay

A developer who only talks about the middle three rows is quoting for part of a website.

Start with the job the site has to do

Before platform, before budget, write one sentence: what should a visitor do on this site, and how will I know they did it?

For most businesses the answer is one of these:

Generate enquiries. Trades, consultants, professional services, B2B suppliers. The site's job is a form submission or a phone call.
Take bookings. Clinics, salons, instructors, venues. The job is a confirmed appointment.
Sell online. Products, courses, gift vouchers. The job is a completed order.
Prove you are credible. Businesses that win work through referral and need the site mainly to reassure. The job is a returning visitor who already knew your name.
Run a process. Customer portals, quoting tools, marketplaces. This is often a web application rather than a website, which do you need a website or a web application helps you tell apart.

Write the answer down. It decides what pages you need, what the homepage leads with, what the platform must support, and what analytics should count. A site with no stated job gets judged on looks, which is the least useful measure there is.

Decide the pages before the design

Design follows content. The opposite order produces pages built around placeholder text that the real copy never fits.

A typical service business needs a homepage, one page per service, an about page, a contact page, the legal pages, and some form of proof. What pages does a business website need goes through each, including the ones people forget and the ones that are not worth building.

Two structural rules save a lot of trouble later:

One page per service, not one page for all services. A single services page cannot rank for six different searches and cannot speak to six different buyers.
One job per page. If two pages answer the same question, they compete with each other in search. How to create an SEO-friendly website structure covers how this maps to navigation and URLs.

Choose the platform for the business, not the developer

The platform should follow from the job and the pages, not from what your developer happens to prefer.

Platform type	Good fit	Poor fit
WordPress	Content-led service sites, blogs, owners who edit often, WooCommerce stores	Highly interactive apps, sites where nobody will maintain plugins
Next.js (or similar framework)	Performance-critical sites, custom functionality, integrations, sites that may grow into apps	Owners who expect a familiar plugin ecosystem and low-cost changes from any freelancer
Website builders (Wix, Squarespace)	Very small sites, tight budgets, owners who want to do everything themselves	Complex SEO needs, custom functionality, businesses that want to own and move their code
Shopify	Product sales where commerce is the whole point	Content-heavy service businesses

The detail behind each row:

Next.js vs WordPress for a business website compares the two most common custom options. This site runs on Next.js; most of my client builds are WordPress. Both are right in different situations.
Custom website vs website builder covers when Wix or Squarespace is genuinely the sensible purchase, and the point at which people outgrow them.
If you are selling online, WooCommerce vs Shopify for UK businesses settles the eCommerce platform question.
If WordPress is the answer, WordPress website development: what businesses actually need is the deeper guide, including theme and plugin choices.

Set a realistic budget

Website prices in the UK range from almost nothing to six figures, and the spread confuses people because the quotes are rarely for the same thing.

The short version for a small or medium business, using the bands on my own website development service:

Scope	Typical starting point	What drives it
Small brochure site, up to about 5 pages	From £499	Template-based, content supplied
Business site, up to about 15 pages, custom design	From £1,499	Design work, content structure, SEO setup
Larger or custom build, eCommerce, integrations	From £3,999	Functionality, integrations, migration

Those are build costs. Hosting, domain, licences, email and maintenance sit on top, every year. How much does a website cost in the UK breaks down build and running costs across all platforms, and how much a WordPress website costs in the UK goes deeper on WordPress specifically.

A useful budgeting habit: work out what one new customer is worth to you, and how many the site needs to bring in per year to pay for itself. That gives you a ceiling worth arguing about rather than a number pulled from the air.

Decide who builds it

There are four realistic options: do it yourself on a builder, hire a freelancer, hire an agency, or use an in-house person. Each suits a different size of project and a different appetite for managing it.

The honest summary of the middle two: a freelancer usually costs less and you talk to the person doing the work; an agency has more people, more process and more resilience if someone is ill, and charges for all of it. Freelance web developer vs agency lays out where each wins, and how to choose a WordPress developer has questions that apply whichever platform you pick.

Whoever you hire, three things are non-negotiable:

You own the domain, registered in your name, on your account.
You own the hosting account, or have a written agreement covering access and handover.
You get the code and the content, with the logins, at the end of the project.

Write a brief that gets comparable quotes

Three quotes for "a website" will come back at £600, £3,000 and £12,000, and none of them will be wrong. They are quoting for different things because nobody told them what the thing was.

A good brief removes most of that spread. It does not need to be technical. It needs to say what the business does, what the site must achieve, roughly which pages it needs, what it must do beyond showing content, who will write the copy, what you already have, and your budget range. How to write a website brief that gets accurate quotes includes a template.

Giving a budget range feels like showing your hand. In practice it is the fastest way to find out what is achievable, and a developer who inflates a quote to match your ceiling is one you have learned something useful about.

How the build process works

Most professional projects follow the same stages, whatever the platform:

Discovery. Goals, audience, pages, functionality, what exists already.
Content and structure. Sitemap, page outlines, who writes what.
Design. Usually the homepage and one inner page first, then the remaining templates.
Development. Templates built, content model set up, functionality added.
Content entry. Real copy and images in place.
Testing. Devices, browsers, forms, speed, accessibility, links.
Launch. Domain switch, redirects, analytics, search console.
Handover and aftercare. Training, documentation, fixes.

The website development process, stage by stage covers what happens at each stage, what you are expected to supply, and where projects stall. If you are on WordPress, the WordPress development checklist is the working list I use before launch.

The stage that most often blows a timeline is content. If the copy is not ready when development finishes, the site waits. Start writing during discovery.

How long a business website takes to build

Timelines depend far more on decisions and content than on code. These are realistic ranges for a project where the owner responds within a few days and the copy is ready on time:

Project type	Typical timeline	What usually extends it
Small brochure site, template-based	2 to 4 weeks	Waiting for copy and photos
Service business site, custom design	4 to 8 weeks	Design rounds, late content
Site with booking, quoting or integrations	6 to 10 weeks	Third-party accounts and API access
eCommerce store	8 to 12 weeks	Product data, shipping and tax rules
Rebuild with migration	Add 1 to 2 weeks	Redirect mapping, content audit

A worked example. Say a plumbing firm wants eight pages: home, four services, about, areas covered and contact. The design takes a week including one round of changes. Building the templates takes a week and a half. Entering content and testing take another week. If the owner has the copy ready, that is a four-week project. If the copy arrives three weeks after development finishes, it is a seven-week project, and nothing the developer does changes that.

Two things genuinely speed a project up: one person on your side who can make decisions, and feedback gathered into a single list rather than sent in fifteen separate emails.

Hosting, domains and email: decide these deliberately

These rarely feature in quotes and cause a surprising share of the problems I am asked to fix.

Domain. Register it yourself, in the business's name, with a registrar you can log into. Turn on auto-renew. A lapsed domain takes the website and the email down together.

Hosting. Match it to the platform. A WordPress brochure site runs well on decent managed WordPress hosting. A WooCommerce store needs more server resource than shared hosting usually gives. A Next.js site needs a Node-capable host or a platform built for it. The cheapest shared plan is often the reason a site feels slow, and no amount of optimisation fully compensates. Choosing web hosting for a UK small business goes into the options.

Email. Keep business email separate from website hosting, on a service such as Google Workspace or Microsoft 365. When email lives on the same cheap server as the website, a hosting problem becomes an email problem too, and moving hosts becomes far riskier.

Form delivery. Website forms should send through a proper transactional mail service with SPF and DKIM records on your domain, not the server's default mail function. Otherwise enquiries land in spam or vanish, and the success message on screen still says they were sent.

What to have ready before you contact a developer

You do not need everything. The more of this you have, the more accurate the first quote will be:

A one-sentence goal for the site
A rough list of pages, especially services
Two or three sites you like, and what specifically you like about each
Your logo and any brand colours or fonts
Existing copy, even if it needs rewriting
Access details for the current domain, hosting and website, if they exist
A budget range and any hard deadline, with the reason for it

The last point matters. A deadline tied to a trade show or a product launch is planned around differently from one that is simply a preference.

What has to be built in, not bolted on

Some things cost little when they are part of the build and a lot when they are retrofitted.

SEO foundations

Clean URLs, one H1 per page, sensible heading structure, unique titles and descriptions, an XML sitemap, correct canonicals, structured data where it fits, and internal links between related pages. None of this is advanced. All of it is easy to get wrong, and some page builders get it wrong by default. What makes a WordPress website SEO friendly is WordPress-specific but the principles transfer.

If you are rebuilding an existing site, the most valuable SEO task is mapping every old URL that has traffic or links to its new equivalent and redirecting it. Skipping that is how redesigns lose half their search traffic.

Speed on a real phone

Google measures real-user experience through Core Web Vitals, and visitors leave slow pages whether Google is watching or not. Speed is mostly decided by the build: image handling, how much JavaScript loads, the theme, the hosting. Core Web Vitals explained sets out what is measured and what the thresholds are.

Accessibility

A site that cannot be used with a keyboard, a screen reader or zoomed text excludes customers and, under the Equality Act 2010, can expose a business to a claim. Most of it is cheap when designed in: colour contrast, real headings, labelled form fields, visible focus states. Website accessibility for small businesses covers what the law asks, what WCAG is, and what to check.

Conversion basics

A clear next step on every page, a short form that actually delivers, contact details that are easy to find, and proof that is real. How to create a high-converting service page covers the page type where most enquiries are won or lost.

Legal and tracking

Privacy policy, cookie handling, company information where it is required, and analytics that counts the thing the site is for, not just visits. UK website legal requirements covers the first group and how to track website conversions in GA4 covers the second.

Launch day is not the end

A launched website starts decaying immediately. Plugins and frameworks need updates, certificates renew, forms break when a mail provider changes a setting, and content goes out of date.

Budget for one of two things: a maintenance arrangement, or a person in the business who owns the checks. Website maintenance: the complete guide explains what needs doing and why, and for WordPress sites the monthly WordPress maintenance checklist is the practical list.

The first three months after launch are also when you learn the most. Watch which pages get impressions in Search Console, which get enquiries, and where people drop off. If traffic arrives but enquiries do not, why website visitors are not turning into leads is the diagnostic order to work through.

The mistakes I see most often

Choosing a designer from a portfolio of good-looking sites without asking whether those sites generate anything for their owners.
No written scope. "A website" is not a scope. Ten templates, a booking integration and 40 redirects is.
Domain in someone else's name. Check yours today.
Writing copy last. It holds up the launch and gets rushed.
Rebuilding without redirects. Years of search history thrown away on launch day.
Buying for today only. A site that cannot add a service page without a developer will cost more over three years than one that costs a little more upfront.
Rebuilding when a fix would do. Sometimes the answer is targeted work on the existing site. WordPress website redesign: when should you rebuild covers how to tell.

Questions to ask before you sign

Whoever you choose, these questions separate a considered proposal from a template one. Ask them in writing and keep the answers.

What exactly is included? Pages, templates, functionality, number of design revisions, content entry, training.
What is not included? Copywriting, photography, stock images, licences, hosting, migration. The gaps cause more disputes than the price.
How will I edit the site? Ask for a demonstration on a similar site, not a description.
Who owns what at the end? Domain, hosting account, code, design files, content.
What happens after launch? How long fixes are covered, what support costs after that, and how quickly someone responds.
How will you protect what already ranks? If there is an existing site, the answer should mention a URL inventory and redirects.
What does the payment schedule look like? Staged payments tied to milestones are normal. Full payment before work starts is not.

A developer who answers all seven clearly, without being asked twice, is likely to run the project the same way.

Where to go next

Deciding what to build

Choosing a platform

Budget and hiring

Running the project

If you would like to talk through a specific project, the website development service page shows how I work and what each package includes. For a WordPress build specifically, see WordPress development. Either way, send the brief first; it makes the first conversation far more useful.