How to use these formats
Each format shows the structure in brackets, explains why it persuades and suggests where it belongs on your site. These are patterns for reading and for asking, not text to publish. A real testimonial is always in the reviewer's own words, with their name as published and a link to the source. If a review only fits a format after you rewrite it, it does not fit.
- Brackets show the parts a strong quote usually contains
- Look for these shapes in reviews you already have
- Never fill a template yourself and present it as a customer quote
Formats that prove results
1. Before and after. "[Problem we had] until [product]. Now [result] in [time]." Why it works: the reader sees the change, not just the end state. Where: homepage, near the first call to action.
2. The number. "We went from [old metric] to [new metric] in [time frame]." Why it works: a figure the reviewer gave is easy to remember and hard to dismiss. Where: case studies and the pricing page.
3. Time saved. "What used to take [time] now takes [shorter time]." Why it works: time is a cost every buyer understands. Where: feature pages and signup.
4. Money saved or earned. "[Product] paid for itself within [period] because [reason]." Why it works: it answers the value question before finance asks it. Where: pricing page, next to the plan cards.
5. The unexpected win. "We bought it for [main job], but [unexpected benefit] turned out to matter more." Why it works: it shows depth beyond the headline feature. Where: features page.
Formats that answer objections
6. Setup time. "We were up and running in [time], without [feared obstacle]." Why it works: setup fear stops many signups. Where: next to the signup button.
7. Price justification. "I hesitated at [price concern], but [result] made it an easy decision." Why it works: it admits the doubt the reader has. Where: pricing page.
8. Switching. "We moved from [previous tool or method] and [what got better]." Why it works: it lowers the perceived cost of change. Where: comparison and pricing pages.
9. Skeptic converted. "I did not think [category] would work for [our situation], but [result]." Why it works: skeptical readers identify with a former skeptic. Where: homepage below the fold.
10. Learning curve. "Our [role] picked it up in [time] with no training." Why it works: it removes the fear of a long rollout. Where: product pages and onboarding emails.
11. Integration fit. "It worked with our [existing tool] from day one." Why it works: buyers worry about breaking their stack. Where: integration pages.
Formats about support and people
12. Support moment. "When [problem happened], support [what they did] within [time]." Why it works: it proves help exists when things go wrong. Where: pricing page and checkout.
13. Partnership. "They treat [our goal] like their own, for example [specific action]." Why it works: specific behavior, not vague praise. Where: agency and enterprise pages.
14. Responsiveness to feedback. "We asked for [feature or change] and [what happened]." Why it works: it shows the product improves with its users. Where: features page.
Formats tied to a role or situation
15. Role specific. "As a [role], I use it to [job], and it [result]." Why it works: readers in the same role see themselves. Where: role or use case pages.
16. Team size. "For a team of [size], [product] gives us [benefit] without [cost]." Why it works: it tells small and large teams the product fits them. Where: pricing page by plan.
17. Industry fit. "In [industry], [specific constraint] matters, and [product] handles it by [how]." Why it works: it answers "is this for companies like us". Where: industry and use case pages.
18. Scale. "We now handle [larger volume] with the same [team or budget]." Why it works: it reassures growing companies. Where: higher plan descriptions.
Formats defined by shape
19. The one liner. "[Short, specific claim about the result]." Why it works: it can sit almost anywhere without clutter. Where: buttons, forms and checkout.
20. The story. "[Situation]. [What we tried]. [Why it failed]. [What changed with the product]. [Result]." Why it works: narrative holds attention on long pages. Where: case studies.
21. The comparison. "Compared with [alternative approach], [product] is [specific difference]." Why it works: it frames the choice for the reader. Where: alternatives and pricing pages. Never present this as your own claim about a named competitor.
22. The recommendation. "If you are [reader's situation], [specific reason to try it]." Why it works: it speaks directly to the next buyer. Where: final call to action sections.
23. The video clip. A short public video in which [reviewer] explains [result] in their own words. Why it works: face and voice add credibility. Where: homepage and case studies, with a link to the original.
24. The rating plus line. [Star rating as published on the source] plus "[one specific sentence]". Why it works: the rating gives context, the sentence gives substance. Where: widgets near pricing. Show the rating only as the source shows it.
25. The thread reply. A public reply in which [user] recommends [product] for [specific job]. Why it works: unprompted advice to a stranger reads as honest. Where: community and social proof walls, with the link and the author as published.
Which format fits which page
| Page | Best formats |
|---|---|
| Homepage | Before and after, skeptic converted, video clip |
| Pricing | Money saved, price justification, team size, support moment |
| Signup and checkout | Setup time, one liner, support moment |
| Feature pages | Time saved, unexpected win, responsiveness to feedback |
| Integration pages | Integration fit, switching |
| Case studies | The story, the number, partnership |
For a page by page plan, read our guide to website testimonials.
How to find these formats in reviews you already have
Your customers have probably written many of these shapes already, scattered across G2, Capterra, Trustpilot, Google, app stores and social threads. The work is reading all of it and noticing which sentence does which job. Search reviews for words like "before", "switched", "hours", "setup", "support" and "worth it". Each hit is a candidate for one of the formats above.
Then trim carefully. You can shorten a long review to its strongest sentence, as long as you mark the cut with an ellipsis and keep the meaning. Keep the author as published and the link to the source. Our customer testimonials guide explains attribution in more detail.
If a format is missing entirely, for example you have no setup time quote, that is the gap to fill with a request. Our article on requesting testimonials shows how to ask questions that produce these shapes.
What never to do with these templates
- Do not fill a template with invented details and publish it as a quote
- Do not attribute a sentence to a person or company that did not say it
- Do not merge parts of two reviews into one quote
- Do not add numbers the reviewer did not give
- Do not present an unusual result as typical without saying so
These rules are not just good manners. In the United States they connect directly to FTC rules on endorsements and reviews, covered in our article on using online reviews as testimonials.
Let the formats find themselves
TestimonialScraper reads public reviews from 12+ sources, scores each quote for strength and tags it by use case, such as results, setup, support, value and switching, and by persona. In practice that means the before and after quotes and the setup time quotes are already grouped when you open your register. Publish them with a testimonial widget or see how the review aggregator collects them.