Getting a testimonial worth putting on the site

Collecting client testimonials that earn a place on your site means asking at the right moment, for specific outcomes, with permission to publish the person's name and role. A testimonial worth publishing names the problem, the measurable result and the constraint you worked under — vague praise like "great work" is not worth the pixels.

Key Takeaways

• Ask when the win is fresh — at handover, after a measurable result, not months later.
• A usable testimonial names the person, their role, the problem and a specific outcome.
• Written permission to publish the name, role and quote is non-negotiable.
• Generic praise converts poorly; specific, checkable claims reduce buyer risk.
• Publish testimonials next to the service or project page they support, not only on a wall.
• Verify every quote against the original message before it goes live.
• Review testimonials quarterly — quotes age, claims change, clients leave.

What makes a testimonial worth publishing?

A testimonial earns its place when a future buyer can picture themselves in the client's shoes. The quote names the person, their role and company, the problem they brought you, the work you did, and a specific measurable outcome — "orders up 18%" beats "great job" every time. That specificity is what lets a stranger trust it.

Why do vague testimonials fail to convert?

Generic praise is unfalsifiable, so buyers discount it. "Very professional" could describe any supplier. Specific claims — a deadline met, a migration with zero downtime, a store that took its first online order — create a checkable story. That checkability reduces the perceived risk of hiring you, which is the entire job of the page.

When should you ask a client for a testimonial?

Ask when the outcome is fresh and the relationship is warm: at project handover, after a measurable result, or right after you fix a problem well. Waiting six months means the client has moved on and the details have faded. As the website handover checklist shows, the end of a project is also the moment to capture what changed.

How do you ask without making it awkward?

Make it easy and specific. Ask for two lines, offer to draft from their own words, and give them a clear prompt rather than a blank page. Most clients want to help; they just don't want to write marketing copy. Tell them exactly what would help: the problem, what you did, and what changed for them.

Subject: A quick line for our site?

Hi [name],

You mentioned [specific result] after we [specific work]. Would you be
open to a short quote for our website? I can draft something from your
words — you just approve it. I'd like to include your name, role and
company if you're comfortable.

Two lines is plenty. What would you want a future client to know?

Thanks,
[your name]

What is the actual sequence for collecting client testimonials?

You don't need a survey tool or a review widget to start. The sequence below works with plain email, a shared document and a page on your site. Each step protects the two things that make a testimonial usable: the client's consent and the claim's accuracy.

1. Pick the moment. Ask right after a measurable win, at handover, or once you've fixed a problem well — while goodwill is fresh and details are sharp.
2. Ask in writing. Use email or a message so you both have a record. Keep the ask to three sentences and make clear you'll draft from their words.
3. Offer a draft. Write a rough quote from what the client already told you, then ask them to correct or approve it. This removes the blank-page problem.
4. Confirm the specifics. Ask for numbers: time saved, orders gained, errors reduced. If there's no number, ask for a before-and-after description.
5. Get written permission. Confirm in the same thread that you may publish their name, role, company and quote, and that they can withdraw later.
6. Edit lightly. Fix typos and trim repetition. Keep their voice. Read the final version back to them before it goes live.
7. Place and review. Publish next to the relevant service or project page, then revisit quarterly to remove stale claims.

What should you ask the client to include?

Cover four things: the situation before, the constraint, what you did, and the measurable result. Ask for numbers where they exist — a percentage, a time saved, an order count. If the client can't give a number, a before-and-after description works just as well. The contrast is what makes the quote believable.

Where should testimonials live on the site?

Place them next to the service or proof they support, not only on a single wall. A quote about a rebuilt site belongs on the website redesign service page. One about a mobile app belongs on the app development page. The closer proof sits to the buying decision, the more it earns its place.

How do you verify a testimonial is real and safe to publish?

Keep the original email or message. Check every published quote against that source before it goes live, and keep a record of the client's permission. If you edit for length, read the result back to the client. A quote that has drifted from what the client actually said is a liability, not an asset.

What are the common failure modes?

The anonymous quote — "CEO, logistics company" — reads as invented. The over-edited quote loses the client's voice and sounds like your marketing team wrote it. The stale quote references a feature or a price that no longer exists. Each failure erodes trust instead of building it, and a single fake-looking quote can cast doubt on the honest ones beside it.

What does this cost in time and operational overhead?

Collecting a good testimonial costs roughly an hour or two of your time per quote, spread across asking, drafting, approval and publishing. There is no licence fee, but there is ongoing maintenance: quotes age, clients leave, claims change. Treat testimonials as content you review quarterly, not a one-time task. Our team can help you plan where proof fits best — contact us for a review.

What legal and consent considerations apply?

Written permission is the baseline: the client agrees that you may publish their name, role, company and words, on your site and in proposals. For clients in the EU or UK, treat that consent as personal data under GDPR and let them withdraw it. Never publish a private message or a review copied from another platform without asking.

What are the most common mistakes?

Fabricating or embellishing a quote is the fastest way to lose a client and a reputation. Asking for a testimonial before the work is actually finished produces thin praise. Burying quotes on a page nobody visits wastes the effort. And publishing a screenshot of a five-star review without the reviewer's knowledge can breach the platform's terms.

A concrete realistic scenario

Consider Royal Trek Nepal, a trekking agency we worked with on a faster booking site. At handover, the owner said: "It's much better now, thank you." That's warm but unusable. We asked three follow-up questions: What was broken before? What changed for your staff? What changed for customers? The result was a specific quote we could publish with confidence.

"Bookings used to take four phone calls. Now customers book in under a minute, and we've cut missed reservations by a third."

That quote now supports the work on our Royal Trek Nepal case study. The difference is measurable, so a future client can imagine the same outcome for their own booking flow.

Alternatives compared

Written quotes are not the only proof you can collect. The right format depends on where the proof sits, how much effort you can spend, and whether you need third-party credibility. Here is how the common options compare in practice.

Format	Best for	Main limitation	Effort
Written quote	Service pages, proposals	Reads as generic if not specific	Low
Short video	Home page, high-trust decisions	Production and consent overhead	Medium to high
Mini case study	Complex projects with numbers	Takes longest to write	High
Review platform	Third-party credibility	You don't control placement or removal	Low to medium
Screenshot of message	Quick informal proof	Looks temporary, ages poorly	Very low

The effort involved is the real cost driver here — see how project scope shapes a web development quote breakdown before you promise a client what the proof will look like.

In short, a testimonial earns its place when it names a real person, a real problem and a measurable result, with permission on record. Collect them at the moment of success, place them beside the service they prove, and review them like any other content.

People also search for

• What should I include in a website handover checklist?
• What does a web development quote actually include?
• Should I rebuild my website or keep improving it?
• How do I write website requirements a developer can use?
• What is the true cost of a cheap website?
• Where can I see common questions about web projects?
• Which IT Gurkha services include website and app development?
• How do I contact IT Gurkha about a project?

If you're planning a site or app and want the proof to match the work, our team can help you plan where testimonials, case studies and project evidence fit best — contact us for a review, or see how we've delivered for clients on our portfolio.