Ask a happy agency or consulting client for a testimonial and you will almost always get the same sentence: "They were great to work with." It is warm, it is sincere, and it converts almost no one — because the buyer reading your case-studies page is not trying to find out whether you are pleasant. They are trying to find out whether you can deliver an outcome under real constraints, and "great to work with" answers a question nobody asked.
Professional-services testimonials are harder than product testimonials for a specific reason: the thing being sold is a relationship and a judgment call, not a feature set. The proof a buyer needs is therefore different, and the default quote points in exactly the wrong direction. This guide covers why relationship praise fails for services buyers, the outcome-and-relationship template that fixes it, how to get a usable quote past a client's legal or comms team, and how to handle confidential engagements where the client cannot be named.
Why "great to work with" fails for services buyers
A services buyer carries two fears that a product buyer does not. The first is delivery risk: will this firm actually ship the outcome, or will the engagement drift, balloon in scope, and end in finger-pointing? The second is relationship risk: will working with them be a constant management burden, or will they operate like a trustworthy extension of the team?
"Great to work with" gestures vaguely at the second fear and completely ignores the first. It tells the reader the engagement was pleasant without telling them it was effective. And because every agency's testimonials say the same thing, the phrase carries no discriminating signal — it is the services equivalent of a SaaS testimonial that says "I love it!" The same principle we cover in the quantitative-results testimonial template applies here: vague warmth converts at roughly half the rate of a quote that names a concrete outcome.
The fix is not to drop the relationship praise. For services, relationship is part of the product. The fix is to pair it with a delivered outcome, so the testimonial answers both fears at once.
The outcome-and-relationship template
The highest-converting services testimonial has three parts, in this order:
- The situation and constraint — what the client needed and what made it hard. ("We had eight weeks to rebuild our checkout flow before peak season, with no internal front-end capacity.")
- The delivered outcome — what actually happened, ideally with a number or a clear before/after. ("They shipped the rebuild in seven weeks and cart-abandonment dropped from 71% to 58%.")
- The relationship signal, made specific — not "great to work with" but how they were good to work with, tied to the delivery. ("They flagged a scope risk in week two instead of week six, which is why we hit the deadline.")
The third part is where most agencies leave value on the table. "Great to work with" becomes powerful the moment it is made falsifiable: proactive about scope risk, never needed chasing, brought a solution to every problem they raised. These are relationship claims a buyer can map onto their own delivery-risk fear, which is exactly what generic warmth cannot do.
Extracting the template from a client who only gives you warmth
Clients default to relationship praise because that is what they feel; the outcome is something they have to be prompted to articulate. Your request has to do the prompting. Instead of "Would you write us a testimonial?", which produces "great to work with," ask three targeted questions:
- "What was the situation before we started, and what made it urgent or risky?"
- "What changed after the engagement — is there a number or a clear before/after you'd be comfortable sharing?"
- "What's the one thing about how we worked that you'd want a peer to know?"
Then assemble their answers into the three-part structure and send it back for approval. This mirrors the request-and-assemble workflow in our guide to collecting testimonials from customers: you are not asking the client to write well, only to confirm that an accurate quote is accurate. Doing the drafting removes the blank-page friction that produces lazy defaults.
Getting sign-off past the client's legal or comms team
Services engagements are often covered by confidentiality clauses, and the moment you ask for a public endorsement, the client's legal or communications team may step in. This is where most agency testimonials die. Three moves keep them alive:
Pre-clear the format, not just the quote. Tell the client up front exactly where the testimonial will appear, whether their logo will be used, and whether you will name the individual or only the company. Legal teams reject open-ended requests far more readily than scoped ones.
Offer a tiered attribution menu. Give the client a choice: full attribution (name, title, logo), company-only, or anonymized by role and industry ("VP of Engineering at a Series B fintech"). Many legal teams that block a full endorsement will approve a role-and-industry version, because it carries no brand risk. A specific anonymous quote still converts far better than no quote.
Strip anything that reads as a marketing claim about the client's own results. Legal teams worry that a quote naming the client's revenue or customer numbers becomes a quasi-public financial statement. Frame the outcome around your deliverable ("rebuilt the checkout flow in seven weeks") rather than the client's headline metrics, and approval gets dramatically easier.
The named-vs-anonymous tradeoff for confidential work
For consulting and agency work, you will frequently be unable to name the client at all. The instinct is to skip the testimonial — but a specific anonymous quote outperforms a named-but-vague one, because the discriminating signal lives in the outcome and the specificity, not the logo.
A quote attributed to "the Head of Operations at a national logistics company" that names a real constraint and a real result is credible. A named quote from a recognizable brand that says only "great partner" is not. When you cannot use the name, compensate by tightening every other detail: the industry, the role seniority, the constraint, and the number. The same trade-offs we cover in the video-vs-text testimonial comparison apply to attribution: richer signal beats thinner signal, and specificity is the richest signal you control.
The four mistakes that make services testimonials fall flat
- Stopping at the relationship. A quote that praises the working relationship but names no outcome answers only one of the buyer's two fears.
- Naming an outcome with no constraint. "They redesigned our site" is not proof; "They redesigned our site in six weeks with no downtime during a peak sales period" is. The constraint is what makes the outcome impressive.
- Letting legal turn it into mush. A quote that survives legal review by removing every specific has been optimized for safety, not conversion. Trade attribution for specificity, never the reverse.
- Using one testimonial for every buyer. A testimonial from a fintech client carries little weight with a healthcare prospect. Segment your testimonials by industry and engagement type so the buyer sees proof from someone in their situation.
The takeaway
Professional-services testimonials fail when they default to relationship warmth, because the buyer's primary fear is delivery risk, and warmth says nothing about delivery. Use the three-part outcome-and-relationship template, do the drafting so the client only has to approve, pre-scope the format to get past legal, and trade attribution for specificity when confidentiality forces your hand. A specific quote about a delivered outcome under a real constraint is the one piece of proof a services buyer cannot get anywhere else.