Choose the visitor’s next step
Start with a sentence: “This website should help [customer] understand [service] and [next action].” A local service business may want an enquiry. A consultant may want a project brief. An online shop needs a different buying journey.
Choose one primary action for the most important pages. Then decide who receives an enquiry, what information they need and how the business will respond. A button is only useful if someone owns the next step.
List pages by customer questions
A small site can be clear without being large. Map each proposed page to a question the visitor needs answered:
- Home: what do you do, who is it for and where should I start?
- Services: what is included, what happens next and what affects the scope?
- About: who is responsible for the work and what experience can you substantiate?
- Work or examples: what can you show with permission, and what exactly was your role?
- Contact: how can I enquire and what should I send?
A separate service page is useful when it answers a distinct need. Avoid creating several near-identical location pages simply to add place names.
Prepare a content folder
Collect the business name, a short description, service details, approved contact details and images you have permission to use. Label anything unfinished. The developer needs to know whether copy is ready, being drafted or part of the project scope.
- Write services in language a customer would use.
- Explain inclusions, exclusions and important dependencies.
- Use real project details and testimonials with permission.
- Describe the subject of useful images; decorative artwork does not need a marketing message as alt text.
- Confirm the factual information required for your privacy notice and other applicable policies.
Agree ownership and access
Record who controls the domain, hosting, business email and WordPress account. Keep credentials in an appropriate password manager, rather than placing them in a project brief. Identify who pays for licences and who can restore a backup.
Ask what the team will be able to edit after launch. Changing a paragraph, adding a service and redesigning a template are different tasks. See our custom ACF development approach for one way to organize editing.
Write a small acceptance checklist
Make “finished” observable. Your checklist could require that the menu works on a phone, the primary enquiry route reaches the right inbox, links go to the intended pages and service content is accurate. Check keyboard navigation, headings and readable text as part of the review.
For an existing website, list URLs that must remain available and any redirects required by changed addresses. For a new site, review titles, descriptions, crawl settings and the sitemap before requesting indexing. Google discovery is a separate process from publishing a website.
Worked example: a first service-business website
Illustrative example: imagine a furniture-restoration business whose main goal is to receive enquiries about suitable projects. This is a planning exercise, not a client case study.
- Home: explain which furniture the business restores and show an approved example of the work.
- Services: describe repair, refinishing and upholstery separately if each needs different preparation information.
- Project examples: explain the starting condition and the work completed, using photographs the business can publish.
- Contact: ask for the furniture type and a short description, and explain how the owner will follow up.
The first version could use an enquiry form without online booking. A restoration estimate may depend on the item’s condition, so a fixed-price checkout would be a separate business decision. One useful launch check is whether a visitor on a phone can find the relevant service and send a test enquiry that reaches the intended inbox.
Write the same kind of example for your business before adding features. It helps distinguish what a customer needs now from what could wait for a later release.
For a more detailed example, follow the service-business website build plan. It connects a service brief to page content, editing fields and observable launch checks, with the assumptions clearly marked.
Copy this starting brief
- Business and customer: …
- Primary visitor action: …
- Pages and services: …
- Copy, photographs and brand assets available: …
- Booking, payment or other integrations: …
- Domain, hosting and email owner: …
- Budget range, preferred launch date and fixed dependencies: …
- Reviewer and launch approver: …
If you are still exploring the visual direction, you can request a free homepage mockup. Selected requests receive one homepage concept and a private desktop/mobile preview; a complete WordPress build is scoped and quoted separately.
Send these details when you discuss a business website. Missing information is fine when it is identified early; it can become a decision in the scope instead of a surprise during development. Our business website service explains the next steps.