How to gather client testimonials that prove ROI and commercial value

How to gather client testimonials that prove ROI and commercial value

“Great to work with” is a nice thing to hear.

So is “highly recommended”, “brilliant session” or “fantastic”.

There is nothing wrong with any of that. It tells a potential client that you are probably decent people and that the experience of working with you was pleasant.

But it does not prove that buying from you was a good commercial decision.

That is the problem with a lot of testimonials on business websites. They reassure the reader, but only up to a point. They say the client liked you. They do not show what changed because of your work.

If you run a service business, consultancy, training company, coaching business or any organisation that trades in expertise, that distinction matters.

The buyer is not reading your testimonial for entertainment. They are trying to answer a fairly blunt question:

Will this work for us?

To help them answer that, your testimonials need to show the problem you solved, the outcome you helped create and the value that made the investment worthwhile.

Why “great to work with” is not enough

Weak testimonials usually prove one thing: the people involved were nice.

That has value. Nobody wants to hire someone who is brilliant in theory and impossible in practice.

But friendliness is only part of the journey, testimonial-wise. The stronger question is: what did the work do for the client?

• Did it save time?
• Did it help the client retain important people?
• Did it improve customer contact?
• Did it make teams more confident, better prepared or more able to share ideas clearly?
• Did it help avoid an expensive problem?

This is where testimonials become commercially useful. They stop being polite applause and start becoming evidence.

A potential client does not only want to know whether you are good. They want to know whether you have solved a problem like theirs for an organisation they recognise as being similar to their own.

Decide what success means before the work starts

The best testimonial often begins before you have delivered anything.

That sounds slightly odd, but it is usually true.

If you wait until the end of a project to ask what value it created, you may find everyone is pleased but nobody has a clear answer. The session went well. The client enjoyed it. The room was lively. Lovely. But now you are trying to reconstruct the commercial argument after the event.

It is much easier to have that conversation at the start.

During onboarding, talk about the problem the client is trying to solve. Not just the surface version, but the business version.

• What is this costing them?
• What do they want to achieve?
• What would success look like?

If a client comes to you because a section of its leadership team has communication problems, that may sound like a soft issue. But the cost can be very real. Poor communication can waste time, drain energy and make it harder for people inside the organisation to share ideas coherently.

If a sales team needs help preparing better client presentations, the value might show up in faster preparation, clearer conversations and more focused contact with customers.

You do not have to pretend every outcome can be pinned neatly to a financial figure. Some of this is difficult to measure. But you do need to know what you are trying to improve.

That gives you something to come back to when you ask for feedback later.

Ask better testimonial questions

If you want a better testimonial, ask better questions.

The most useful one is simple:

What exactly did our work solve for you?

That question moves the conversation away from general praise and towards evidence. It encourages the client to think about the thing that was frustrating them, slowing them down or costing them money before they asked for your help.

From there, you can ask:

• What problem were you trying to solve?
• What was that problem costing you in time, money or energy?
•  What did you want to achieve from the work?
•  What changed afterwards?
•  What evidence shows that the work made a difference?
•  Has the value become clearer over time?

These questions do not need to feel like an interrogation. They can be part of a normal post-project conversation.

In fact, that is often the best way to do it. Clients are busy. Once the work is finished, they are usually back to running the organisation and dealing with the next thing. If you send a blank email saying, “Could you write us a testimonial?”, you have given them another job.

Make it easier.

Tell the client at the start that you will ask for feedback afterwards. Then, when the work is complete, hold a short conversation. Ask how it went, what changed and whether the work met the success measures you discussed earlier.

You can take notes and offer to draft the testimonial for their approval. Some clients will prefer to write it themselves. Fine. But many will appreciate you turning the conversation into a clear first version, as long as you keep it accurate and give them proper control over the final wording.

Follow up when the evidence has had time to appear

An immediate testimonial can be useful, but it is not always the best one.

Straight after a workshop, training session or project, people can usually tell you how it felt. They may say it was useful, practical or engaging. That is worth knowing, but it may not yet show the real value.

Sometimes the stronger evidence appears later.

Two, three, four or six months after the work, the client may be able to say whether people are applying what they learned, whether teams are preparing faster or whether managers have noticed a change in behaviour.

That later follow-up can turn a pleasant reaction into a much stronger success story.

So if the client does not have the data straight away, do not force it. Ask whether you can come back to them later. You can then update the testimonial, expand it into a case study or create a fuller success story for your website.

Use ROI evidence without overstating it

The strongest testimonials include specific evidence, but you need to handle that evidence carefully.

For example, Shawbrook Bank told us that its investment in our work had delivered at least a tenfold return. The work involved a group of managers and helped the bank retain key people in the business. Because the cost of recruiting replacements was measurable, the client could connect the work to a clear commercial saving.

That is useful because it is not just a compliment. It links the work to a business problem and a measurable outcome.

Beijer Ref UK and Ireland gave another clear example. After work with its sales teams, the client reported a fourfold increase in customer contact.

Again, that matters because it shows a change in behaviour. It is not simply “we liked the session”. It is “this helped us do more of something commercially important”.

The careful wording matters here.

If the client estimated the return, say that. If the client reported the increase, say that. If the figure comes from their own assessment, make that clear.

That does not weaken the testimonial. It usually makes it more believable, because you are not trying to make the claim sound bigger than the evidence allows.

ROI is not always pounds and pence

When people hear ROI, they often think it has to mean direct revenue.

Sometimes it does. Very handy when the number behaves itself.

But commercial value is broader than immediate income.

A project might create value by helping a business retain important people, avoiding the cost and disruption of recruiting replacements.

It might help a sales team prepare more quickly and deliver better-focused client presentations.

It might increase customer contact.

It might improve confidence, reduce mistakes, shorten delays or help people take action after the work.

Those are all commercially relevant outcomes, provided they relate to the problem the client wanted to solve in the first place.

The mistake is to use the wrong evidence for the wrong claim.

Participant feedback can show that people valued the work. A survey can show confidence, usefulness or whether people have applied what they learned. Manager observations can show whether behaviour changed afterwards.

But that is not the same as proving a direct financial return.

So keep the claim in proportion. If you have evidence that people found the work useful, say that. If you have evidence that it helped retain staff, increase customer contact or reduce wasted time, say that. Do not stretch one kind of evidence until it pretends to be another.

What to do when clients cannot share commercial figures

Some clients will not want to share exact figures. That is completely understandable.

The data may be commercially sensitive. The outcome may be hard to separate from other things happening inside the organisation. Or the client may simply be uncomfortable putting a financial number on it publicly.

That does not mean you are stuck with “highly recommended”.

You can still build a credible body of evidence.

Use exit polls, feedback forms and short follow-up surveys. Ask for feedback as you move through the project. Keep the process low-friction, but make sure it gives you something more useful than a polite score.

For example, participant feedback might show that people found the work useful, felt more confident afterwards or had already applied what they learned. Managers may notice people approaching their work differently.

Evidence from a sizeable group can be more useful than one enthusiastic comment, as long as you explain what it does and does not prove.

If you are using survey evidence, give enough context for the reader to trust it. Who gave the feedback? What were they asked? Was it gathered immediately afterwards or later, when people had time to apply the work?

You do not need to bury the reader in methodology. This is a testimonial, not a PhD. But you do need to avoid turning a small or informal piece of feedback into a claim that sounds much bigger than it is.

Keep feedback forms short

You do not need to collect tonnes of data.

In many cases, one good question is better than a long survey nobody wants to complete.

A Net Promoter Score-style question can work well because many organisations understand it:

On a scale of 0 to 10, how likely are you to recommend our service to a friend or colleague?

If most respondents select nine or ten, you have a simple dataset you can use. It gives you a consistent way to understand whether people would recommend the service.

That can support a useful claim about the response to your work.

It will not, by itself, prove every commercial outcome. Again, use the right evidence for the right job.

Do not cut away the useful testimonial detail

Another common mistake is making testimonials too short.

Businesses often slim down the copy on their websites, which I find odd because search engines and AI thrive on text. So don't cut away the very detail that made the testimonial useful.

A two-line quote might work on a homepage:

“Excellent workshop. Highly recommended.”

But on its own, it does not tell the reader very much.

If you have a strong client story, let it breathe somewhere. On a homepage, no, you probably do not want 500 words. On a success story page, that length can be absolutely fine if the client uses the space to explain:

• The exact problem they were trying to solve
•  How you worked together to agree the approach
•  How the work was delivered
•  How people responded
•  What changed afterwards
•  What evidence showed success
•  What return or commercial value the work provided

At that point, some people will call it a case study rather than a testimonial. That is fine. The label matters less than the job it does.

Where possible, include the full name, job title and photograph of the senior person involved in the project. Those details help credibility.

But the strongest credibility still comes from useful detail. A named person saying “fantastic” is still vague. A named person explaining the original problem, the work and the result gives the reader something they can compare with their own situation.

Use client stories across the website

Strong client stories can work in several places.

• You might use a high-impact quote on the homepage.
• You might use a more specific extract on a relevant service page.
• You might include a short testimonial beside a blog article on the same topic.

Then you can link through to a fuller success story that explains the problem, the work and the outcome in more detail.

This helps because different readers need different levels of proof.

Some people only need a quick reassurance that you have worked with credible clients. Others want to drill into the detail before they make contact.

The important thing is relevance.

If a reader recognises the client, or recognises the problem, the testimonial becomes far more useful. It helps them think, “This sounds like the thing we are dealing with.”

That is the real purpose of a good testimonial. Not to decorate the website. Not to fill a carousel. Not to collect nice things people have said about you and hope they somehow do the job.

It should help a future client see the problem you solved, the change you created and the value they might reasonably expect from working with you.

A simple structure for an ROI-focused testimonial

If you want a practical structure, use this:

1. What problem was the client trying to solve?
2. What was that problem costing them?
3. What approach did you agree together?
4. What work did you deliver?
5. How did people respond?
6. What changed afterwards?
7. What evidence shows the value or return?
8. Who is giving the testimonial, and what is their role?

That structure will not fit every project perfectly. It does not need to.

The point is to stop asking only for praise and start asking for the story of the change.

Because a good testimonial does not have to shout. It just has to prove something useful.