Do I need a website if I already get customers from referrals?

What happens between the recommendation and the enquiry?

A referral carries trust, but it rarely carries every practical detail. The person recommending you may know one service you performed, not your current availability, service area or booking process. The next person still has questions. A useful referral page closes that information gap rather than restarting the conversation with a broad sales pitch.

Follow one real handoff with permission. Ask a recent enquirer what they received: a name, a phone number, a social profile or a website link. Then ask what they had to find out before contacting you. Write down their words. Those missing answers are better requirements for the page than a list of fashionable website features.

Which information should the page carry?

Start with the boundary of the work. Name what you do, who you do it for and what you do not take on. Explain the next action and what happens after it. If an estimate requires a conversation, say which details help you prepare. Do not make visitors supply a long project brief just to discover that their location is outside your area.

Keep changeable facts current. An old opening time or a disconnected phone number creates a different problem from an unattractive design: it can make a good recommendation difficult to act on. Assign someone to check those facts whenever the business changes. A small maintained page is more useful for this job than an elaborate page nobody owns.

What would a referral handoff look like in practice?

Consider a hypothetical repair business. A past customer recommends it to a neighbour, who opens the link while commuting. The neighbour needs to know whether the business handles that repair, serves that address and accepts photos before quoting. A page answering those questions lets the enquiry begin with the problem itself. It does not prove that the neighbour will book.

Compare that with a page saying only “quality service you can trust.” The recommendation already supplied that idea. Repeating it adds little. The useful extra material is operational: what to send, how the enquiry is handled and whether an urgent request should use a different contact route. This example describes a design decision, not a measured client result.

Does the job change for shops and online stores?

For a local shop, a referred visitor may need directions, current hours, accessibility information or a way to check whether a product is stocked. A booking-led service business needs a clear request or scheduling path. An online store needs the recommendation to land on a relevant product or collection, with delivery and return information available before checkout.

Do not force all three into the same lead form. Someone deciding whether to visit a shop should not have to request a sales call to find its hours. Someone buying an item should not have to describe a project. The right next action follows the customer’s task, even when the recommendation began in exactly the same way.

When is a rebuild unnecessary?

A rebuild may be unnecessary when the existing page answers the recurring questions, works on a phone and sends enquiries to someone who responds. Fixing a broken link, updating a service description or making the contact route clearer can be enough. If you are at capacity, the priority may instead be filtering unsuitable enquiries and communicating availability accurately.

Before commissioning work, keep a short record of referral enquiries and the information each person needed. Separate confusion on the page from delays inside the business. The free audit can flag technical and content issues in homepage HTML, but it cannot tell you what every referred visitor thought. Pair that report with the actual questions you heard, then choose the smallest useful change.

Apply it to your business

See how the work differs for your business type:

• Service businesses
• Retail and local shops
• Online stores