What to prepare before building a website
Goals, audience, materials and integrations: from an initial idea to a clear brief.
For the first conversation, explain the business challenge, your audience and the action you want visitors to take. Materials, integrations and constraints help define the scope. You don’t need a complete specification.
01. Start with the goal, not the page count
“We need a modern website” describes a wish rather than an outcome. Define what should change: customers find a service faster, send an enquiry, order a product or get an answer without calling.
For a service business, the main journey might be choosing a service and requesting a consultation. Structure, copy and the form should support that journey.
Agree how the outcome will be checked. If the site should generate enquiries, define an enquiry: a delivered request with contact details, a booked meeting or a paid order. Clicking a button and receiving a request are different events. Existing analytics can provide a baseline for a later comparison. A brief defines the intended result; it does not promise a particular number of sales.
02. Describe the people the website serves
Age or country alone is not enough. Describe the context: what question brings someone to the site, what they compare and what prevents a decision. If customer groups differ, describe their needs separately.
Plan accessibility early: clear labels, readable text, keyboard navigation and labelled fields. W3C WAI’s accessibility planning resources can help.
Consider an equipment maintenance business. A new customer needs to find a service and establish whether the team handles their equipment. A returning customer wants to request another visit and find documents. The first needs clear categories and examples; the second needs a short enquiry path. These differences are more useful for planning a website than a demographic description such as “men aged 25–55”.
03. Gather what you already have
Don’t postpone the conversation because some content is missing. Make an inventory and mark what can be reused and what needs creating or updating.
Give each item an owner and a status: ready, needs updating or missing. For example, the logo is ready, a manager is writing three service descriptions, and equipment photos still need taking. Check image usage rights separately. This supports parallel work and makes content dependencies visible. Do not put passwords or private customer records in a shared brief; arrange access through a separate agreed channel.
- Logo, colours, fonts and brand guidelines.
- Service descriptions, catalogue, photos and work samples.
- Reference websites with notes on what you like.
- Existing website structure, content and access when needed.
04. Separate essentials from extras
Discuss features through user journeys. Instead of “an account area”, say “customers see order status and download documents”. This helps define scope and select a solution.
Separate launch essentials from later improvements. A service business may initially need service pages, work examples, contact details and an enquiry form with reliable delivery. An account area or complex calculator can be estimated separately if the main journey works without it. Define a simple acceptance check for each feature: after form submission, the manager receives every field and the customer sees confirmation.
05. Include integrations and data migration
CRM, payments, delivery, analytics, email and catalogue systems can affect structure and development. List the systems you use and explain what data should move between them.
When replacing an existing site, discuss important URLs, content migration and redirects separately. Google Search Central’s starter guide provides an introduction to search requirements.
Naming a system is only the beginning. Specify what moves, when and to whom: the name, contact and selected service go to the assigned CRM owner after a valid form submission. Check API availability, permissions and failure handling. For an existing website, list important pages and assets as well. This lets the team plan migration and preservation of useful URLs separately from the new interface.
06. Put together a short brief
A brief does not need to be long. Record the goal, audience, main journey, available materials and known constraints. Add your budget and target date if you have them; otherwise we can discuss them.
Include your preferred launch date, why it matters and a budget range if known. A fixed exhibition date and an internal wish to finish sooner require different planning. Record who approves the design and how feedback is consolidated. When several people decide, one shared feedback list helps avoid conflicting edits. Mark unknown answers openly: clarifying them is part of the first conversation.
Example brief for a service business
| Question | Example answer |
|---|---|
| Goal | Receive consultation enquiries. |
| Audience | Small business owners comparing services. |
| Main journey | Find a service → understand the offer → provide contact details. |
| Integration | Send enquiries to the existing CRM. |
