Planning

A small business website checklist: from brief to first enquiry

Plan a business website around customer questions, useful service pages, mobile contact paths, launch checks and clear ownership after handover.

The useful starting point

A useful small business website explains the offer, supports it with accurate evidence and makes the next step easy. Plan those three jobs before choosing animation or page count.

Choose one primary visitor journey

Write a sentence describing the visitor you most want to help. For example: an office manager comparing local equipment-maintenance providers needs to understand service coverage, availability and how to request a quotation. That journey suggests different content from a restaurant menu or a software trial.

Choose one primary action for the first version. It may be a qualified enquiry, a booking through an existing system or a call during business hours. Supporting actions can exist, but equal emphasis on six buttons can make the decision harder. Define what information a useful enquiry contains.

Build a page plan from real questions

A service page should explain who it is for, what is included, what affects the price and how work starts. Use actual service boundaries and authentic examples. A generic paragraph repeated under different city names gives visitors little reason to choose the business.

Build a page plan from real questions — decision worksheet
PageQuestion it should answer
HomeWhat do you do, for whom and what should I do next?
Service detailDoes this solve my problem, and what is included?
Work or examplesWhat can I inspect that supports the offer?
AboutWho is responsible and how do they work?
ContactHow do I enquire, and what information should I send?

Prepare content before the layout becomes fixed

Assign an owner to every piece of copy and every image. Keep a simple status list: draft, checked, approved and published. If a testimonial is unavailable, use a clear process explanation or a genuine product demonstration instead of inventing a review.

Tell the developer which facts change regularly. Weekly announcements may need an editor; an occasional change to opening hours may not justify a complex publishing setup. Agree image sizes and how future content will fit on a narrow screen. Long service names and phone numbers are useful layout test cases.

Check the journey, then the details

Have someone unfamiliar with the business find a relevant service and reach the contact step on a phone. Watch where they hesitate. A technically working page can still fail to explain whether the business serves their needs.

Before releasing, check form validation, successful delivery, error feedback, visible keyboard focus and the actual destination of each button. Confirm that titles describe their pages and that important pages are linked from the site. Keep private previews protected and verify production settings separately.

  • Accurate business name, service area and contact details.
  • Legible text and tappable controls on narrow screens.
  • Approved copy, licensed images and honest examples.
  • A working contact route with clear success and failure messages.
  • Business access to the domain, source and hosting account.

Give the website an owner after launch

Choose who reviews enquiries, checks broken links and updates stale information. Record recurring subscription dates and the agreed support channel. Track whether enquiries match the service you want to sell, not just whether the visitor count rose.

Use real questions from customers to improve existing pages. If people repeatedly ask whether installation is included, answer it in the service scope. This creates useful content from actual gaps rather than a publishing schedule detached from the business.