How to plan a business website that earns useful enquiries

A useful business website helps a visitor understand what you offer, decide whether it fits their situation, and take a clear next step. Planning should begin with those three jobs. The design, technology and page count follow from them. This guide walks through a practical website brief for a small business, including content, mobile layout, enquiry handling, ownership and launch checks. It is intended to help you make decisions before paying for features you may not need.

The fastest starting point is a one-sentence description of the customer and their immediate problem. For example, a local maintenance company might serve property managers who need a dependable contractor for urgent repairs. That is more useful than a broad ambition to look professional. It tells you which evidence, service details and contact options belong near the top of the page. It also gives you a way to evaluate whether the finished design actually works.

Choose the main job of the website

Start by choosing one primary outcome. A visitor might request a quote, book a consultation, view a catalogue or message your team. You can support secondary actions, but they should not compete equally with the main one. If a visitor needs to describe a complex requirement, a short enquiry form may work better than a purchase button. If customers usually need a quick conversation, a clearly labelled WhatsApp link can be appropriate.

Write down what makes an enquiry useful. A contractor may need location, the type of work and the preferred date. A design studio may need the project category and the desired outcome. Avoid asking for every possible detail at once. Each additional field creates work for the visitor and for the team storing the information. Collect the minimum needed to respond meaningfully, then ask follow-up questions in the conversation.

Decide who receives enquiries and what happens after submission. A beautiful contact page is not helpful when messages disappear into an unmonitored inbox. Assign an owner, set an achievable response expectation and prepare a fallback contact method. Test the entire journey with a real device before launch, including the confirmation message and the destination inbox.

Build a page map around customer questions

A small website can be effective without having dozens of pages. The homepage introduces the offer, a service page explains the detail, a work or examples page provides evidence, and a contact page supports the next step. Separate pages are useful when visitors have genuinely different needs, such as different services, locations or product categories. They are less useful when they repeat the same paragraph with a different heading.

For each planned page, answer three questions: who is arriving, what do they need to learn, and what should they do next? A page about commercial cleaning should address a facilities manager's practical questions, while a page about one-off home cleaning needs different information. If two proposed pages answer exactly the same questions, consider combining them into one stronger resource.

• Homepage: explain the offer, audience and main next step.
• Services: show deliverables, boundaries and relevant examples.
• Work: demonstrate real projects without inventing results.
• About: explain who is responsible for the business and delivery.
• Contact: offer a working route to a named team or function.
• Helpful guides: answer substantial questions that customers actually ask.

Prepare content before polishing the layout

Gather accurate service names, photographs, contact details and examples early. Missing content often causes late redesign because a layout built for short headlines does not work with long explanations. Draft the most important messages in ordinary language. A visitor should not need to decode abstract phrases to learn what your business does. Specific descriptions are usually more useful than claims such as innovative solutions or unmatched excellence.

Choose photographs that help customers understand the work. A real product photo, workspace or completed project can communicate more than a generic stock image. Check that you have permission to use every image and testimonial. If you use concept imagery, avoid presenting it as evidence of an actual completed job. Label examples accurately when their status could otherwise be misunderstood.

Keep essential facts in page text rather than only inside images. Search engines, screen readers and visitors using translation tools need accessible words. A headline baked into a banner may look attractive, but it can become unreadable on a small phone and cannot adapt to the visitor's settings. Use imagery for atmosphere and evidence, and use HTML text for the actual offer and calls to action.

Design the first mobile screen deliberately

Review the website on a narrow screen before treating the desktop layout as finished. The first screen should establish the brand, the offer and a useful action without feeling crowded. You do not need every service bullet above the fold. You do need to avoid a decorative image that pushes all meaningful information far below it. Balance the visual introduction with the visitor's immediate task.

Video needs particular care. A portrait crop may look impressive while taking up most of a phone screen. Test whether the full composition works with the headline and buttons, rather than choosing a ratio only because a social platform uses it. Keep the visual focus away from edges that will be cropped. A lightweight poster image helps the page look complete before the video begins.

Make buttons large enough to use comfortably and separate links that lead to different actions. A floating contact button should not cover navigation, form fields or important text. Check the page with larger text settings and keyboard navigation as well as touch. These checks often reveal practical problems that are not obvious in a full-size desktop screenshot.

Decide what should be editable

List the content that will change regularly. Prices, opening hours, services, staff profiles and project examples may need an editing workflow. A static marketing site can be simple and fast when updates are infrequent, but a team publishing every week may need a content management interface. The right choice depends on the actual editing pattern, not on whether one technology sounds more advanced.

Agree who can publish and whether changes need review. A small business may only need one editor, while a larger team may need draft and approval roles. Define what happens when an editor leaves the business. Accounts and access should belong to the business rather than remaining tied to one contractor's personal login. Document the route for making urgent corrections after launch.

Also ask what happens to the content if you move providers. A useful handover includes the source repository or export where applicable, asset files, domain access responsibilities and basic deployment instructions. You do not need to become a developer, but you should understand which parts you own, which services you subscribe to and who can make changes.

Keep integrations proportionate

An integration should remove a real piece of manual work or improve a customer experience. Sending a qualified enquiry into your CRM may be valuable. Connecting several analytics products before you have meaningful traffic may add complexity without a clear benefit. Start with the smallest reliable workflow and expand when you know how the team uses it.

For each connection, define the source of truth. If a service description is edited in two places, inconsistent information can appear. If an enquiry is sent to both email and a CRM, decide which system records ownership and follow-up. Explain how failures become visible. A failed automation should leave a recoverable record rather than silently losing a potential customer.

Chatbots also need a practical boundary. They can answer approved questions and collect an initial requirement, but uncertain answers should lead to a person. Do not promise live stock, guaranteed delivery dates or prices unless the system has reliable current information. Test the questions customers actually ask, including questions that the bot should decline to answer confidently.

Plan launch as a customer journey test

Before launch, test more than the homepage appearance. Open every important link, submit each form, check phone and WhatsApp destinations, and confirm that the business receives the message. Review page titles, descriptions, social previews and the sitemap. Make sure important pages can be reached through normal links rather than only through a search box or an interaction that requires special knowledge.

Check performance on a mobile connection and treat measurements as evidence, not as a guarantee of business results. Large images, unnecessary scripts and blocking fonts can slow an otherwise simple site. Optimise the obvious sources of delay while preserving the content people came to see. Repeat the audit after a material change, such as adding a video or a third-party booking widget.

Record the launch state so future changes have a useful reference. A short checklist, screenshots and a list of working URLs are enough for many small projects. Keep account ownership and renewal responsibilities in a secure business system. Never place passwords or private access tokens in a public project repository or a customer-facing guide.

A practical website brief

• Describe the main audience and their immediate problem in one sentence.
• Choose the primary conversion and define a useful enquiry.
• List pages with a distinct purpose and avoid unnecessary duplication.
• Provide approved copy, photography and accurate contact details.
• Identify the content that staff need to edit themselves.
• Name each integration and the manual task it should replace.
• Agree acceptance checks, ownership, support and a launch date.

A good brief does not need to predict every implementation detail. It should make the important decisions visible and identify questions that could change the scope. If you do not yet know whether you need accounts, payments or a management dashboard, say so. Those requirements may turn a marketing website into a platform project and should be discussed before a fixed scope is approved.

Frequently asked questions

Is a one-page website enough for a small business?

It can be, when the offer is focused and customers need only a short explanation before contacting you. Separate pages become useful when services, audiences or questions differ substantially. Choose the structure that helps customers understand the business rather than aiming for a particular page count.

Should I write the copy before the design begins?

Prepare the important facts and a rough message structure first. The wording can improve during design, but the designer needs to know the offer, audience, service boundaries and calls to action. Working with placeholder paragraphs until the final week often creates avoidable layout changes.

Do I need a chatbot on a business website?

Only if it solves a useful customer problem and has reliable information to work from. A clear contact route can be better than a chatbot that guesses. If you add one, provide approved answers, an uncertainty response and a straightforward handover to a person.

What should I receive at handover?

Ask for the agreed source or export, final assets, editing instructions, ownership responsibilities and a list of connected services. Confirm how the site is deployed and maintained. Credentials should be managed through appropriate account access, not copied into public documents or chat messages.

How does TenWeb approach this kind of project?

TenWeb offers marketing websites alongside management systems, platforms and mobile apps. The portfolio and pricing page is the starting point for choosing a category. The final scope should describe the required pages, content, integrations and acceptance checks before implementation begins.