Show References That Lead to the Right Enquiries

Before making an enquiry, visitors want to see whether you understand similar cases. A service page explains what you offer. A reference shows what that work looked like for a real customer.

Many prospective customers already have a clear picture of their situation. They are not looking for a long explanation of CRM, content or automation. Instead, they check whether their questions and processes appear in the project.

This builds trust before the first conversation.

References answer questions before getting in touch

A reference does not need to be a major success story. It should show what the project was about, what was missing beforehand and what work was involved. Clear information is therefore more helpful than a logo without any context.

For example, a visitor may want to know whether a team can handle a high volume of enquiries. Contacts may be spread across inboxes, spreadsheets and individual notes. In that case, a reference about a well-structured process is often more useful than an image of the new website.

The scale of the project should also be clear. Was it a single page, new content or a system for managing contacts? This helps readers assess whether the scope matches their own plans.

A logo alone rarely does this job.

Describe the situation before the project in concrete terms

Many companies show only the finished result. That makes it difficult to understand the value of the work. Start by describing what was not working well in day-to-day operations.

Perhaps enquiries came in through several channels. One employee entered data manually into a spreadsheet. Or important information was only available in old emails.

Readers often recognise these situations from their own business. That makes them more credible than general statements about growth or efficiency. They also show that the project addressed a real task.

Stick to the facts of the case.

State the scope of work openly

A reference should clearly state what was part of the project. For a website, this may include structure, copy, forms and technical implementation. For a CRM, it may include fields, statuses and handover rules.

The customer team should also be included in the description. It often provides content, reviews processes or continues maintaining data. Making these roles visible avoids a misleading impression of who was responsible for what.

A system does not make sales decisions. It can, however, show open contacts and remind people about tasks. The article “A CRM Needs a Clear Process for SMEs” explains which questions should be resolved before setup.

Clear boundaries make references credible.

Choose images and screenshots with purpose

A screenshot can explain a great deal. But it should show a specific function. An image of a homepage without any connection to the task usually does not help visitors.

Instead, show a form with relevant selection fields. Or show an overview where open cases are sorted by status. A short text should then explain why this view matters for the case.

Remove names, email addresses and other internal data beforehand. This also applies to figures from sales or accounting. If a screenshot cannot be safely anonymised, a recreated view is often the better option.

Images always need a connection to the case.

Document approvals in writing

You may only publish customer names, logos and identifiable project information with explicit permission. A good working relationship is not enough. An older project also needs clear approval.

Record in writing what may appear on the website. This can include the company name, logo, images or a customer statement. Also clarify who gave the approval on the customer side.

If no approval is available, you can present the case anonymously. For example, name the industry and the type of task. However, make sure that individual details do not make the customer identifiable after all.

Anonymous cases can be just as convincing.

Organise references by need

A long list of old projects rarely helps visitors. They mainly look for examples that match their own task. For this reason, organising references by service or case is often useful.

A prospective customer with many manual office steps looks for different examples than someone planning a new website. References about processes, contact management and forms should therefore be easy to find together. The article “Less manual work through automated processes” looks at these office tasks in more detail.

Service pages can also include short references to relevant cases. A preview only needs the initial situation and scope. Anyone who wants to know more can then read the full reference.

A few relevant cases are usually stronger.

Review references regularly

A reference does not stay current on its own. Contacts change, tools change and screenshots quickly become outdated. Review copy and images at regular intervals.

Also review the approval. Does it still cover all content on the page? If the scope of the project was expanded later, describe the new part separately.

State the status of an ongoing project clearly. For example, write that a system has been set up and that the team is now using it. This avoids statements about effects that cannot be substantiated later.

Current references show careful maintenance.

Frequently asked questions

How many references should I show on my website?

Start with a few cases that cover your most important services. Four good examples usually help more than many short entries. Add new projects only once the content and approval are clear.

Do I need to name customers in references?

No, a customer name is not required. An anonymous reference can be convincing when the task and work are clearly described. Names and logos always require explicit permission.

What information belongs in a reference?

A reference should state the situation before the project and the scope of work. Also describe what the customer team handled itself. This keeps the presentation clear and fair.

May I publish figures from the project?

Publish figures only with the customer’s permission and a reliable basis. Internal figures on revenue, quotations or contacts are often confidential. If in doubt, describe the change in the process instead.

Are screenshots useful on reference pages?

Yes, if they make a specific function easy to understand. Remove all data that identifies customers, employees or internal processes. A short note below the image explains the benefit more clearly.

How often should I review references?

Review references whenever a tool, point of contact or project status changes. Check images and approvals at the same time. This keeps the information on your website accurate.