Plan a website that turns visitors into enquiries

1. Choose the enquiry you want to receive.

“More leads” is too broad to guide a website project. A request for an estimate, a product demonstration, and a conversation about a creative brief need different information. Start with the conversation your team is prepared to have.

Write down who the page is for, what they need, and the next step you can offer. If you serve several audiences, choose the priority for each page. A homepage can introduce the business; a service page should help someone assess a specific offer.

Keep the invitation honest. Use “Request an estimate” if the team needs to assess the work before quoting. Use “Book a consultation” only when the visitor can actually arrange one. The button should describe the step that follows.

2. Give each part of the page a job.

Plan the reading order before the visual treatment. Visitors may arrive through a recommendation, a search, or a campaign, with very different levels of familiarity. The page should stand on its own without requiring them to explore the whole website.

1. Orientation: name the service or offer, the audience it suits, and the next action.
2. Fit: explain what you do, what the work includes, and any constraints that affect the decision.
3. Proof: show relevant work and describe your contribution.
4. Process: explain how the project starts and what the customer needs to provide.
5. Action: make the enquiry step easy to find when the visitor is ready.

Use headings that answer real questions. “What we build” or “How the project starts” is more useful than an impressive phrase that leaves the reader guessing. Design can express your personality while the words carry the information.

If two services require different proof, process, or questions, they may deserve separate pages. If their content would be almost identical, a clear section on one page may be enough. Give each page a reason to exist.

3. Choose proof that answers the buyer’s concern.

A portfolio image shows the result. A short explanation helps the visitor understand why it matters. For each example, describe the starting situation, what you delivered, and how the work fits the customer’s business. Make your role clear when others contributed.

Match the proof to the question. A buyer commissioning a website may want to see how services and contact information are organised. Someone commissioning a campaign may need to understand the creative and the enquiry journey. A testimonial can add the client’s perspective when you have permission to use it.

Separate what you delivered from what you measured. If you have reliable evidence of a business result, explain its context. If you do not, show the work itself and the problem it was designed to address. Specific, accurate detail is enough to make a case study useful.

4. Ask for what the first conversation needs.

Review every form field with one question: will this change how we respond? Contact details and a service choice may be enough to begin. A property location, project date, or short description can be useful when it determines whether you can help. Questions that only matter after a consultation can wait.

• Label the fields clearly. Keep labels visible while people type and mark optional details as optional.
• Explain what follows. Say who will respond and through which channel. Only promise a response time your team can maintain.
• Make mistakes recoverable. Show a helpful error beside the relevant field and preserve the details the visitor has already entered.
• Confirm successful receipt. The success message should appear after the enquiry is accepted, with a clear next step.

Keep privacy information accessible next to the form. An enquiry should not quietly become an unrelated marketing subscription. Ask your delivery partner how form data is stored, who receives it, and how access is managed.

5. Test the whole journey before launch.

Review the site on a real phone as well as a larger screen. Open it as a first-time visitor, including any consent banner. Then complete the same task you expect a customer to complete. A polished page is only part of the check.

• The offer and primary action are readable without dismissing something that covers them.
• Menus, buttons, and form labels work with touch and keyboard navigation.
• Project images are legible, video controls work, and important information is available without sound.
• An incomplete form explains what needs fixing without losing the rest of the enquiry.
• A clearly marked test enquiry is saved and reaches the person responsible for follow-up.
• A delivery problem has a recovery path; the team knows where to find the saved enquiry.

Agree who owns each issue before launch. Include content corrections, delivery settings, access, and ongoing updates in the handoff. Keep the launch checklist with the project so it can be reused after substantial changes.

6. Bring a one-page brief to the first meeting.

You do not need a complete specification to start a productive conversation. A short brief helps a designer or developer identify what is clear, what needs exploration, and which decisions affect the scope.

Mark unknowns openly. An agency can help shape an offer or organise content, but that work needs to be part of the scope. Bring examples of websites you like and explain what is useful about them: the clarity, the photography, the navigation, or the way a service is explained.

7. Learn from visits and actual conversations.

A website needs a way for the right people to find it. Include a distribution plan: relevant search content, useful social posts, existing business relationships, or an agreed campaign. A redesign alone does not establish demand.

Keep a simple record of where visitors come from, which enquiries arrive, and whether those enquiries fit your services. Check that analytics respects the visitor’s choices, and use the saved enquiry record to confirm submissions. A button click is an expression of interest; a received enquiry is a different event.

When traffic is limited, avoid drawing strong conclusions from a few visits. Combine the available data with questions customers ask. Improve the explanation, proof, or follow-up step that those conversations reveal, then observe the effect before making another large change.