The review gap in outsourced work: why mid-sized agencies collect the fewest testimonials

There’s a pattern that shows up again and again in mid-sized service businesses — the 20-to-200 person agencies, dev shops and outsourcing partners that deliver dozens of projects a year. They have more satisfied clients than a solo freelancer will meet in a decade, and a testimonials page with four quotes on it, two of which are from 2022.

The instinct is to read that as a marketing failure. It isn’t. It’s an operations failure, and it has a specific structural cause.

Why growth makes this worse, not better

A freelancer who forgets to ask for a review has one person to blame and one habit to fix. Once delivery is split across roles, the ask stops belonging to anyone.

The person with the relationship isn’t the person who needs the review. Your engineer or designer has the client’s trust and no reason to think about marketing collateral. Your marketing lead needs the review and has never spoken to the client. The ask requires both, so it requires a handoff, and handoffs without owners don’t happen.

Sign-off is not the same as satisfaction. On larger engagements the person who signs the acceptance document may be a procurement or finance contact who never used what you built. The person who is actually delighted is a product manager or a team lead two levels down — the one who’ll write you a genuinely good review, and the one nobody thought to ask.

Delivery never really ends. Retainers, phased work and support windows blur the moment where a project is “done.” Without a clean finish line, there’s no obvious trigger for the ask, so it drifts until it’s too late to send.

Account managers change. When the person who ran the relationship leaves, the informal knowledge of who was happy and who owed you a testimonial leaves with them. Anything held in one person’s head is one resignation away from gone.

Subcontracted work hides behind a prime. If you deliver through a partner agency, your client-of-record may be contractually the only party allowed to talk about the work at all. That’s solvable, but only if someone raises it early rather than discovering it when the review is already written.

Decide who you’re actually asking

Before any process, settle this. On most B2B engagements there are three different people, and they give you three different things.

• The economic buyer — signs the contract, cares about budget and risk. Their review is the most persuasive to other buyers and the hardest to get, because they’re furthest from the work.
• The day-to-day champion — the PM, tech lead or marketing manager who worked with your team weekly. Easiest to get, most specific, most credible to practitioners evaluating you.
• The end user — the support agent or salesperson who uses what you built daily. Rarely appropriate to ask directly, but their words, quoted with permission by the champion, are the most vivid material you’ll get.

Ask the champion first. They say yes most often and write the most useful review. Then, if it went well, ask the champion whether the buyer would be willing to add a line. A warm internal introduction beats a cold request every time.

A process that survives handovers

Five parts. None of them clever — the point is that each one works when the people involved are busy, distracted, or new.

1. Pick one trigger and write it down

Choose a moment that already happens on every engagement and bind the request to it. Good candidates: final invoice sent, acceptance signed, handover call completed, or — for retainers — the end of each quarter.

The trigger has to be an event in a system somebody already touches, not a feeling somebody has to have. “When the final invoice goes out, the review request goes out” survives a busy week. “When it feels like the right moment” doesn’t.

2. Give it one owner per account

Name the role, not the person: the account manager sends the ask, or the delivery lead does. Write it in the delivery checklist alongside the handover doc and the credentials transfer. If two roles could plausibly do it, neither will.

3. Create the link at kickoff, not at the end

This is the change that makes the biggest practical difference. If a review link exists for the engagement from day one, sitting in the project record as a pending item, then it shows up in every status review as an unfinished task. If it only gets created at the end, it depends on someone remembering — at exactly the moment they’re starting the next project.

4. Track outstanding asks like outstanding invoices

You would never run a mid-sized agency without a list of who owes you money. Reviews deserve the same visibility for the same reason: anything not on a list depends on memory, and memory is the thing that failed in the first place.

A single view of every request — sent, responded, still outstanding — turns “we should get more testimonials” into a list of six names you can work through on a Friday afternoon.

5. Put it on a recurring agenda

Ten minutes in the monthly ops or account review. Three questions: which engagements closed since last time, which of those have a review request out, and which requests have gone quiet for more than three weeks. That’s the entire meeting. It’s enough.

The handover script nobody writes

The most common single point of failure is the moment the delivery person hands the relationship back to the account lead. Making that handoff explicit costs one message.

Meera — Northwind phase two is signed off as of today.

Client contacts:
- Priya Rao (Head of Product) — day-to-day champion, ran weekly calls with us, said on the final call this was the smoothest launch her team has had. Best person for the review.
- Tom Alderton (Ops Director) — signed the contract, low engagement with the work itself. Worth a second ask only if Priya says yes first.

Review link is created and pending under the Northwind client record. I sent the first ask today with the handover email.

Flags: none. No NDA restriction on naming them — checked the MSA, clause 11 covers confidential data only, not the existence of the engagement.

Devi

Three weeks later, when someone asks why Northwind never left a review, that note answers it — even if Devi has left the company.

When the client can’t give a public review

In outsourced and white-labelled work this comes up constantly, and agencies too often treat it as a dead end. It usually isn’t. Ask what constraint you’re actually working with, because each has a workaround.

• They can’t be named publicly. Ask for role-and-sector attribution: “Head of Engineering, mid-market logistics platform.” Less powerful than a logo, far better than nothing.
• Marketing has to approve external quotes. Ask the champion to write the review first, then route it internally. Approving existing words is a much smaller job than composing new ones.
• You worked as a subcontractor. Ask the prime contractor, not the end client. They’re also a client, they know exactly how you performed, and they have no confidentiality problem describing their own supplier.
• Nothing external is possible at all. Ask for an internal-use quote you can show under NDA in sales conversations, and a LinkedIn recommendation for the individual who led the work. Neither goes on your website; both still sell.

Whatever you agree, record the restriction against the client record. The expensive mistake isn’t failing to get a review — it’s publishing one you weren’t allowed to publish because the person who agreed the terms left last year.

What to do with them once you have them

A testimonials page nobody visits is where reviews go to be politely ignored. Put them where a decision is being made:

• On the service pages that match the work — a review of a migration belongs on the migration page, not in a general carousel.
• In proposals, next to the case study for that same client, so the claim and the corroboration sit together.
• On a public wall you can link to directly from an email, so a prospect can look at a body of evidence rather than three curated quotes.

And date them. An undated wall of praise reads as marketing; a review dated last month reads as a fact.

Where Reviewee fits

Reviewee is built for exactly this shape of problem. You keep a client list, create a review link per client or project, and send it from Reviewee or paste it into your own handover email. Every link shows as pending or completed, so outstanding requests are a visible list rather than something an account manager holds in their head. Reviews arrive for your approval before anything goes public, and approved ones publish to an embeddable widget or a public wall you can link from a proposal.

The free plan covers up to ten review links, which is enough to run the process for a quarter and see whether it sticks before you pay for anything.

For the wording of the asks themselves, see eight scripts that don’t feel like begging. For the timing, see when to ask a client for a review.