How to get client testimonials and case studies that win work

Ask for a testimonial right after a clear win, not months later, and ask four specific questions instead of "can you write something nice?". Then turn the answers into a short quote, and for bigger projects into a case study built around one number. Get written permission before you publish anything.

Ask right after the win, not at the end of the project

The best moment to ask is the week the client feels the result. A launch that went live, a campaign that hit its number, a stuck project that finally moved. That is when the value is concrete and the relief is fresh.

Most people wait until the last invoice is paid. By then the client has moved on, the details have faded, and your request feels like a chore. A client who watched you rescue a late project on Tuesday will write you a much better quote on Friday than they will in six months.

You do not have to wait for the contract to end either. On a long engagement, every approved milestone is a candidate. In Delivvo, the client approves each deliverable inside the client portal, and that approval is recorded against a specific version with a date. The approval is a natural prompt: the client has just said yes to the work, so a short follow-up message in the same portal thread lands while they are still in a good mood.

If you are still building your first few wins, the work comes first. Our guide to getting your first client covers that, because nobody can quote a project you have not delivered.

Why proof matters before the first call

Buyers check other people before they check you. BrightLocal's Local Consumer Review Survey 2026 found that 97% of consumers read online reviews for local businesses, and 49% trust them about as much as a recommendation from someone they know. In B2B, Sopro's roundup of buyer research reports that 77% of buyers consult user reviews and 54% speak with current customers before buying.

Volume matters less than you might expect. Northwestern's Spiegel Research Center found that a product with five reviews was 270% more likely to sell than one with none, and that the benefit of each extra review shrinks quickly after the first five. That research looked at products, but the lesson carries over to a small service business: five strong, specific quotes do most of the work. You do not need fifty.

Ask questions that force specifics

"Would you mind writing a testimonial?" gives the client homework with no prompt, so they write the safest sentence they can think of. "Great to work with, would hire again" is kind and useless.

Ask four pointed questions instead and let the answers become the quote:

1. What was the problem before we started?
2. What worried you about hiring someone for this?
3. What changed after the work shipped? Give a number or a before and after if you can.
4. What would you tell another business owner who is on the fence?

The second question matters most. When a client says "I was nervous about handing off our whole checkout flow, but it shipped two days early and conversion went up," that sentence answers the next buyer's exact fear.

Take the answers on a short call, over email or as a voice note. Then write a clean draft from their own words and send it back for approval. Most clients are relieved to edit a draft rather than face a blank page, and you get a tighter quote.

Build a case study around one number

A testimonial is a quote. A case study is a short story with evidence, and it carries more weight when a buyer is comparing two or three providers. It needs four parts:

1. The situation. Who the client is and where they were before you arrived. Two or three sentences.
2. The problem. What was broken or stuck, in concrete terms. "Their booking page lost a third of visitors at the payment step" beats "they had conversion issues".
3. What you did. The decisions, not just the task list. This is where you show judgment.
4. The result. One number with a before and after: sign-ups, hours saved, load time, revenue, support tickets.

Most case studies fall apart at step four because nobody measured anything. Fix that at the start of the project. Agree on one success metric in the proposal or the contract, write down where it stands today, and the case study nearly writes itself at the end. If you truly cannot get a number, use a direct quote in which the client describes the change.

Keep it short. A case study of 300 to 500 words with one image is read. A six-page PDF is not.

Get permission, and keep the quote honest

Get a clear yes before you use the client's name, logo or numbers. A one-line email is enough: "Happy for you to use this quote and these figures as written." Keep that email. If the client is nervous about exact figures, offer a relative number. "Cut support tickets by 30%" says nothing sensitive and still proves the point.

There is also a legal side in the US. The FTC's final rule on fake reviews and testimonials bans fake or AI-generated reviews, bars paying for reviews that carry a set sentiment, and requires insiders to disclose their ties to the business. The agency's questions and answers on the rule add that a business should not supply testimonial text without a reasonable basis to think it is true, and that showing only unrepresentative praise can be deceptive. You can offer a thank-you for a review, but you cannot tie it to a positive one.

So the rules are simple. Write drafts from what the client actually said. Let them edit freely. Never invent a quote, and never reword one so it claims more than the client meant. This is general information, so check it with your lawyer if you sell into regulated sectors.

Put the proof where buyers are deciding

A testimonials page that nobody visits does nothing. Put the proof next to the decision:

• On each service page, next to the offer it supports.
• Inside proposals and quotes, as a one-paragraph mini case study that matches the prospect's situation.
• On your portfolio, with the outcome first and the screenshots second.
• In the follow-up email after a discovery call, as a single link.

Matching gets easier as the library grows. If you keep a simple note for every finished project (client, problem, metric, quote, permission), you can pull the right story in two minutes. For a busy roster, our post on managing multiple clients at once shows how to make that note part of closing a project instead of a separate chore.

How Delivvo gets you proof at the moment of the win

Delivvo puts the ask where the happy moment already happens: the client portal, right after the client signs off.

1. Agree the metric at the start. Put the success measure in the quote or the contract. In Delivvo a quote built from packages and add-ons, a contract and a deposit invoice all travel on one link, so the number lives next to the scope.
2. Deliver in the portal. The client opens a branded portal with a one-time code, with no password to forget. They see files, versions and the money line under your name and colour.
3. Let them approve. Each deliverable gets a client approval, recorded against a version with a date. That record also protects you if someone later says they never approved it.
4. Ask in the same thread. Right after the approval, send the four questions as a portal message. The client answers where they already are, while the win is fresh.
5. Send the final invoice. Because the invoice, the contract and the files all sit in one place, closing the project feels finished, and the client leaves on a good note.

A detail a typical portal skips: every quote, contract and invoice carries a verification code, so a prospect you send a case study to can also check that your documents are real. Clients pay you directly through your own gateway, and Delivvo takes 0% of the payment.

See how the approval step works on the client approvals page, or look at the whole flow in the client portal.

For the wider picture, see Delivvo for teams and the CRM for service businesses.

FAQ