The Sale You Lost Before Anyone Contacted You

The objection you never hear

Picture someone opening your website between appointments. They have a real need and a few minutes to see whether you can help. The page looks polished. But they cannot tell whether you serve a business of their size, what happens after an enquiry or where to find the product they saw earlier. They close the tab.

There is no rejection email to learn from. Your sales team never hears the concern. You cannot assume that every short visit was a missed sale, but you can examine how much effort a suitable customer needs to make before a useful conversation can begin.

A silent departure is especially easy to overlook when existing customers already know how the business works. They know the product names, recognise the people and are comfortable sending a message. A first-time visitor has none of that context. Designing only around the familiar customer can leave the stranger doing a surprising amount of guesswork.

Your customer arrives with a question, not a sitemap

The labels inside a business are not always the labels a customer uses. A visitor may be looking for a way to manage appointments, while the navigation asks them to choose between unfamiliar product names. Another may want to know whether an item is available, while the page talks mainly about the brand story.

Choose a few common reasons people arrive and trace each one through the site. Can they recognise the relevant option? Can they understand enough to compare it? Does the next action match what they are ready to do? A clear path does not require every visitor to read every page.

Three questions your page should help answer

A useful review starts with three questions: is this relevant to me, can I trust what I am being told, and what happens if I proceed? These are prompts for examining a journey, not a claim that every visitor follows the same sequence. Someone arriving from a recommendation may already trust you but still struggle to find the right option.

Relevance comes from specifics: the situation a product suits, the people a service helps and any important limits. Trust comes from evidence appropriate to the decision, such as clear specifications, identifiable company information or work you can accurately explain. The next step needs an understandable commitment: am I buying, reserving, requesting a price or starting a conversation?

Look for a page that answers one question well while leaving another open. It may establish credibility through a detailed story but never explain how to proceed. Or it may have a prominent booking button without enough information to help someone choose the right appointment.

Make uncertainty smaller

For a service, clarity might mean explaining who it is for, what the first conversation involves and which information to bring. For a product, it might mean showing the important specification, delivery expectations and a useful view of the item. These details answer different kinds of hesitation.

More copy is not necessarily the solution. Put the useful information beside the decision it supports. A clear image can explain a physical detail faster than a paragraph. A short description of the next step can do more than a button that says ‘Submit’ without explaining what follows.

Imagine a small fitness studio promoting a beginner class. A page headed ‘Transform Your Potential’ might express the brand but leave practical questions unanswered. A description that explains the class length, what beginners need to bring, how intensity is adapted and how to choose a session gives someone material for a decision. The promise can still be appealing; it becomes easier to evaluate.

The same principle applies to imagery. A beautiful room establishes atmosphere. An image showing where the activity takes place or how a product is used can answer a different question. Decide what a visual needs to explain before using it to fill a layout.

Keep the promise consistent from the first click

The journey begins before the website. Someone may arrive from a creator’s demonstration, a search result or a forwarded message. If the destination uses a different name, shows a different option or makes them search again, the visitor must work out whether they reached the right place.

Follow the exact links customers receive. If a post explains one service, send people to information about that service rather than expecting the homepage to complete the explanation. Keep any important qualification visible as well. A generous headline followed by surprising restrictions is a poor way to begin a relationship.

Test on a real phone under ordinary conditions. Pay attention to text that needs zooming, buttons that are difficult to distinguish and essential information that appears only after a large image loads. The aim is to discover practical obstacles, not to judge the site only from a designer’s large desktop screen.

Try the journey with unfamiliar eyes

Ask someone unfamiliar with the business to complete a specific task on their phone. For example: find a suitable option, establish whether it meets a stated need and work out how to proceed. Ask them to say what they expect to happen. Watch before explaining the page to them.

Hesitation, repeated backtracking and an unexpected interpretation are useful observations. A handful of sessions can reveal questions worth investigating, although it cannot tell you how every customer behaves. Review analytics alongside these observations; a click count alone rarely explains the reason behind a choice.

Use a task that describes the customer’s goal without naming the button they should click. ‘Find a suitable first class for someone who has never attended’ is more revealing than ‘open the beginners page’. Record where the person hesitates and what they believe a label means. If you explain the navigation during the exercise, you start testing your explanation rather than the page.

A form is a conversation with no one there to clarify

Look at each field and ask why it is needed at this stage. A first enquiry may not require a visitor to know their exact budget, final specification or project date. If an answer is necessary, explain why and allow uncertainty where the business can reasonably handle it. The form should help a person begin, rather than make them finish the planning alone.

W3C’s form guidance recommends making required and optional input, expected formats and relevant instructions clear. It also explains why placeholder text should not replace a label: it disappears as the person types and is not a dependable label for assistive technology. Keeping instructions visible is a practical part of making the conversation understandable.

Check the awkward path too. Submit an incomplete form, correct a field and use the keyboard to move through it. Does the page explain what needs attention without erasing the work already done? Once the message is sent, can the visitor tell that it arrived? A polished first screen should not hide a frustrating final step.

Reference: W3C: Form instructions

The enquiry is still part of the experience

A form should ask for enough information to move the conversation forward without demanding work that belongs later. After submission, confirm that the request arrived and explain the next step accurately. If the enquiry goes into a shared inbox or system, make sure someone owns the response.

Before planning a redesign, choose one customer journey and remove its most obvious unanswered question. Then check whether suitable visitors can complete the task more easily. A website becomes more useful when it behaves like a considerate first conversation, especially when nobody is there to explain it.

Keep a short record of the questions new enquiries ask repeatedly. Some belong in a personal conversation; others reveal information that could have helped earlier. Review those questions alongside observed usability problems, make a focused change and check the journey again. The best next improvement may be a clearer sentence or a better handover, not a complete visual rebuild.