How to get testimonials and case studies
To get a testimonial, ask at the moment the client is happiest — right after a result lands, not weeks later — and do the hard part for them: three questions (what the problem was, what changed, what they would tell the next client), a promise to show them the wording before it is used, and permission in writing. Then keep two shapes of every answer: a one-liner for proposals and emails, and a paragraph — or a short case study — for your website. One rule governs all of it: a testimonial is the client's words, not yours. You may trim them. You may never improve them.
That rule is not decoration. Inventing, embellishing or quietly tidying up a client's words into something they did not say loses the two things testimonials exist to build: trust, and a reputation that survives a phone call. A real quote from a real client, asked for properly, beats a polished invention every time.
When to ask: at the result, not the invoice
Timing does most of the work. Ask too early — before anything has shipped or improved — and the client has goodwill but nothing concrete to say; you get "great to work with", which persuades nobody. Ask months later and the warmth has cooled: the work is mentally filed, and your message sinks under newer emails. The right moment is the result moment: launch day, the first report showing the change they hired you for, the message where they tell you it worked. That is when the project is vivid, and saying yes costs them least.
So build the ask into the project: note the expected result date while you work, and send the request the same week the result lands — while they are still telling colleagues about it. If you miss that window, the day the final invoice goes out is the acceptable second chance: the ask reads as a natural closing step rather than a favour from the past.
The ask: one short message
The request should be short, warm, and specific to this project. It names what went well, asks the three questions inline so they can answer in the same thread, states where the words will appear and under what name, and promises they will approve the wording before anything is published. It also makes saying no costless: a client who can decline without awkwardness says yes without resentment.
Hi Daniel —
The refreshed pages have been live a month now, and you mentioned enquiries are up. Would you be willing to give me a short testimonial for my website and proposals? To make it easy, three questions — a sentence each is plenty:
1. What was the problem before we started?
2. What has changed since?
3. What would you tell someone thinking of hiring me?
I will send you the exact wording to approve before anything is published, and I will only use your name and Northwind Traders with your OK. And no is a perfectly fine answer.
Thanks again for the project,
Sam
Notice what the message never does: it does not suggest an answer, offer a pre-written quote to rubber-stamp, or apply any deadline pressure. The words have to be theirs, or they are worth nothing.
Three questions that produce usable words
"Would you write me a testimonial?" fails because it hands the client a blank page — a task that gets postponed forever. Questions remove the blank page. These three, in this order, produce almost everything you will ever publish:
1. What was the problem before we started? This anchors the quote in a situation the next client recognises as their own. Praise without a problem is decoration; praise that starts "our product pages described everything and sold nothing" is evidence.
2. What changed afterwards? This is the outcome — and it carries the guide's strictest rule. If numbers appear, they must be the client's own, from their own results, in their own words. Never suggest a figure, never round one up, never supply the metric you hope they will confirm. If Daniel says enquiries doubled, that is his figure and it can be quoted. If he says things simply feel busier, publish that instead — a modest true sentence outsells a grand borrowed one.
3. What would you tell someone thinking of hiring me? This produces the recommendation line, usually the strongest sentence of the three — the client stops describing the project and starts advising a peer. It is the sentence that ends up in proposals.
Three answers, a few sentences each, is a harvest: everything in the next section is cut from them, with no further effort from the client.
Shape the answers: one line, one paragraph, one case study
Keep every testimonial in up to three shapes, all cut from the same answers. The one-liner — a single sentence — goes in proposals, emails and profile pages, where space is short. The short paragraph — two to four sentences — sits on your website, beside the service it describes. The mini case study is the full structure: the problem, what you did, and the outcome, in the client's own words. One good project, properly asked, fills all three.
Here is that shape. Fictional example — invented client, invented words, shown for structure only: Sam Carter is a copywriter; Daniel is operations manager at Northwind Traders, the client from our invoicing guides.
| The problem | Northwind's product pages listed every specification and persuaded no one; enquiries through the site had dwindled to a trickle. [From Daniel's answer to question one.] |
| What Sam did | Rewrote the 24 highest-traffic product pages: buyer problem first, specifications second, one clear enquiry route per page. [From the project record — no client quote needed.] |
| The outcome | "Enquiries through the site doubled in the first month, and they are the kind we used to have to chase." [Daniel's own figure, from his answer to question two — Sam asked what changed; she did not suggest a number.] |
| The one-liner | "Sam turned pages that described our products into pages that sell them." — Daniel, Operations Manager, Northwind Traders. [Question three's answer, trimmed — with Daniel's approval of the final wording.] |
Permission and honesty: the non-negotiables
Get permission in writing. The client's reply to your ask is enough — but it must exist, and it must cover where the words will appear and whether their name, role and company go with them. Verbal enthusiasm on a call is not permission.
Show them the final wording before it publishes. Send the text in the shape it will appear — the trimmed one-liner, not the full email they wrote. Wait for the yes: silence is not approval, and publishing on it converts a happy client into a surprised one.
Edit for length, never for meaning. Cutting a sentence, dropping a tangent, fixing an obvious typo: fine. Strengthening an adjective, adding a result, merging two remarks from different days into a single quote: not fine — each turns their words into yours while keeping their name attached. If you offer to draft from their answers to save them time, build the draft only from words they actually wrote, and let them change anything.
Respect the name, and the exit. Use a name, role and company exactly as agreed; if the client prefers to be anonymous — "Operations Manager, a wholesale supplier" — that is their call, not a lesser favour. And if a client ever asks for a quote to come down, take it down promptly and without argument — the relationship is worth more than the sentence.
Where testimonials earn their keep
In the proposal, at the credibility point. A proposal's brief "about you" section is where one permitted quote does its best work — reassurance at the exact moment the client is deciding. Its place in the full document is covered in our guide to the freelance proposal template, section by section, and the free proposal generator leaves space for the quote in the same position.
On your website, beside the matching service. A quote about product pages belongs on the copywriting page, not stacked on a general wall of praise. A reader considering that service meets proof about that service, from someone who bought it.
On profiles and directories, where the rules allow, a specific one-liner outperforms a paragraph of self-description. What testimonials do not belong in is a new client's onboarding: proof is for the decision, which happens before the yes — the client onboarding checklist that follows a yes is admin, and a client asked to admire your other clients' words during it is being sold to after buying.
Keep them fresh
Ask after every project that ends well — a step in your close-out routine, alongside the final invoice, not an occasional campaign. Then prune: a quote praising a service you no longer offer, or a wall whose newest words are five years old, quietly argues your best work is behind you. Retire the stale; keep the set small and current.
And note where the best words come from: relationships that ended well, including clients you parted with deliberately. An exit handled cleanly — proper notice, a real handover, no rancour — leaves a client who will still describe you well. Our guide to firing a client professionally is written for exactly that outcome; the testimonial is sometimes its dividend.
Questions
Related: put the words where they work
A testimonial earns nothing in a folder. Keep the one-liner inside the proposal you build with the proposal generator, the paragraph beside the service it praises, and the case study where a client will read it slowly. Ask at the result, ask with questions, publish only what was actually said — and the proof accumulates, one honest project at a time.