Topic hub

Planning and Strategy

1 published guides0 subtopicsUpdated 21 July 2026

Start here

The main guide for this topic

How to Build a Website for a Small Business

A useful small-business website does not begin with colours, templates or software. It begins with a commercial purpose: who the site is for, what those people need to know and what you want them to d…

Open the complete guide →

Published guides

Articles in this section

Complete guide21 July 2026

How to Build a Website for a Small Business

A useful small-business website does not begin with colours, templates or software. It begins with a commercial purpose: who the s…

Read guide →

About this section

Website planning turns a broad intention such as “we need a better website” into a project that can be priced, built and evaluated. It connects business goals to pages, content, customer actions and measurements. Without this work, design choices tend to fill the gap and the finished site may look polished without solving the original problem.

This section provides a practical planning sequence for small UK businesses. It is useful before a first build, a redesign or a move to a different platform.

The five planning questions

Questions that define a website project
Question	Useful output	Weak substitute
What business problem should the website help solve?	A specific objective and priority action	“We need a modern website”
Who must understand and trust the site?	Priority audience groups and their questions	“Everyone”
What information and evidence are required?	A page list and content inventory	Copying a competitor's menu
What must the website do?	Testable functional requirements	A list of fashionable features
How will the result be judged?	Measures linked to enquiries, bookings, sales or service	Traffic or appearance alone

Start with the objective

Choose one primary objective for the first release. Examples include generating qualified enquiries in a defined service area, allowing customers to book a particular service, selling a known product range or reducing routine support questions.

A website may support several outcomes, but one priority helps resolve conflicts. For example, a site designed mainly to generate local service enquiries will organise content differently from one designed to complete online sales.

Website Objectives and Success Criteria explains how to turn the objective into a measurable result and identify the events worth tracking.

Define the audience with evidence

A useful audience description includes the customer's situation, location, urgency, concerns, decision criteria and level of prior knowledge. It should be based on real enquiries, sales conversations, support questions or research rather than invented personality details.

How to Define Your Website Audience provides a simple process for grouping customers and deciding which group the first version should serve most clearly.

Learn from competitors without copying them

Competitor research is useful for understanding market expectations, missing information and common customer journeys. It is not a design-copying exercise. Record:

which questions competitors answer well;
where pricing or process information is unclear;
what proof they provide;
which actions they ask visitors to take;
which pages appear to serve search demand;
where their experience is frustrating or incomplete.

Competitor Analysis for Website Planning turns those observations into requirements without reproducing another site's claims or layout.

Plan the work as a controlled project

A website project normally includes discovery, content, design, development, testing, launch and post-launch work. These activities overlap, but each needs a clear owner and acceptance point.

How to Plan a Website Project explains dependencies, milestones and approval gates. It is especially useful when several suppliers or internal stakeholders are involved.

Write requirements that can be tested

Replace vague requests with observable outcomes:

Turning vague ideas into testable requirements
Vague request	Testable requirement
“Make it mobile-friendly”	Core pages can be read and used at 320–430 CSS pixels without page-level horizontal scrolling
“Add a contact form”	The form validates required fields, sends to the agreed address, stores or transmits data securely and shows a clear success message
“Improve SEO”	Existing valuable URLs are mapped, indexability is checked, titles are editable and Search Console ownership is retained
“Make it fast”	Representative pages are tested on mobile and major slow elements are documented before acceptance

Separate launch scope from future ideas

Use three lists:

Required for launch: essential to operate safely and complete the primary customer journey.
Useful after evidence: improvements that should respond to actual usage.
Not currently justified: features with no clear owner, need or maintenance plan.

This prevents the first release from becoming too large while protecting essential quality.

Planning checks before procurement

Is the primary objective written in one sentence?
Is the priority audience specific enough to guide content?
Are the essential pages and functions listed?
Do you know which materials already exist?
Can each important requirement be tested?
Is the first-year and ongoing budget understood?
Are ownership and maintenance responsibilities defined?

The next practical step is to prepare a one-page planning summary and use it consistently when briefing platforms, freelancers or agencies.