Your client didn’t forget you. They forgot the review.

The project shipped. The client said something warm on the last call — “this was genuinely the smoothest launch we’ve had” — and then the thread went quiet. You sent one message asking for a review. Nothing came back. Three weeks later you’re on a sales call, describing that exact project from memory, with nothing to show for it.

This is the most common way good work fails to compound. Not a bad outcome, not an unhappy client. Just a review that never got written.

Silence is not a verdict

The first thing to get straight, because it changes how you follow up: a client who doesn’t leave a review is almost never a client who disliked the work. Unhappy clients tell you. They tell you during the project, in scope disputes, in the invoice conversation. Silence after a clean delivery is not disapproval. It’s attention moving on.

That matters practically, because teams who read silence as a bad sign stop following up. They tell themselves they’re being respectful. What they’re actually doing is protecting themselves from an imagined rejection — and losing a testimonial the client would have been glad to give.

Four reasons happy clients don’t write reviews

In practice the missing review nearly always traces back to one of these, and each has a different fix.

1. The ask arrives after attention has left. The day you hand over is the day your project stops being your client’s problem. Their calendar refills within hours. A review request sent a month later isn’t landing on the person who was grateful — it’s landing on someone three priorities down the road.

2. The ask was vague. “Let us know if you have any feedback” is not a request. It’s a door left open. Nobody walks through a door for you. A request has a verb, an object and a place to do it: leave a review, about this project, here.

3. The effort is unbounded. A blank text box is a homework assignment. Your client doesn’t know if you want two sentences or five paragraphs, whether they should mention the budget, whether marketing has to approve it. Unbounded effort with unclear stakes is the definition of a task that gets postponed forever.

4. Nobody owns the follow-up. On solo work you forget because you’re already on the next project. On team work it’s worse: the project manager assumes the account lead asked, the account lead assumes the founder asked, and nobody did. Reviews fall into the same gap that unbilled hours fall into.

What the silence actually costs

It’s tempting to treat a missing review as a minor loss. It isn’t, because the cost shows up somewhere other than where the mistake happened.

• You end up vouching for yourself. On a sales call, “we did a similar migration last year and it went really well” is a claim. A dated review from the client who lived through it is evidence. You are competing against firms who can produce the second thing.
• Your best work is the least documented. The projects that go smoothest generate the least correspondence, which means they generate the fewest artifacts you can reuse. The messy ones you remember in detail. The excellent ones evaporate.
• The window closes permanently. Your champion changes jobs. The company rebrands. Eighteen months on, a request to review a project the client barely remembers is an awkward ask, and you’ll feel it and not send it.

The fix is structural

The teams that collect reviews consistently aren’t better at asking. They’ve just removed the moments where a human has to decide to ask. Four changes do most of the work.

Make the trigger an event, not a mood. Pick a moment that already happens on every project — sign-off, final invoice, handover call — and attach the request to it. “When I send the final invoice, I send the review link” is a rule you can follow when you’re busy. “I’ll ask when it feels right” is not.

Give the request one specific home. One link, tied to that client and that project, that opens straight into a form. No account to create, no password, no app to install. Every extra step is a place where a willing client quietly drops out.

Shrink the effort out loud. Tell them what you want: two or three sentences, a rating, thirty seconds. Naming the size of the task is what converts it from “someday” to “now, while I’m reading this.”

Make outstanding requests visible. You chase unpaid invoices because you have a list of them. Reviews need the same treatment — a list of who was asked, who responded, and who is still outstanding. Anything without a list depends on memory, and memory is exactly what fails here.

A follow-up that isn’t begging

One reminder, sent about a week after the first ask, recovers a surprising share of the silence. The tone that works is short, low-stakes, and genuinely easy to decline.

Hi Priya,

Following up once on this and then I’ll leave it alone: if you have two minutes, a short review of the rebuild would mean a lot to us.

Link: [your review link]

Two or three sentences is plenty — how it went, and whether you’d work with us again. And if now isn’t the time, no problem at all, just say so and I’ll close it out.

Thanks again for a genuinely enjoyable project.

Sagar

Three things make that work. It caps the follow-up (“once, and then I’ll leave it alone”), so the client isn’t bracing for a campaign. It states the size (two or three sentences). And it gives a real out — which, counterintuitively, is what makes people say yes, because you’ve removed the pressure they were avoiding by not replying.

There’s more on wording, and scripts for the harder cases, in how to ask a client for a review politely.

What this looks like in Reviewee

Reviewee exists because this problem is boring and mechanical and deserves a boring, mechanical fix.

• Create a review link for a specific client or project. It’s unique and secure, and your client needs no account to use it.
• Send it from Reviewee by email, or copy it into your own handover message or invoice — whichever fits how you already close a project.
• Every link shows as pending or completed, so the outstanding ones are a list you can work through, not something you have to remember.
• If a client stalls on the blank box, the review form can draft a short review from a few bullet points they type, which they then edit in their own words before submitting.
• Reviews come to you first. You approve what gets published, then publish it to an embeddable widget or a public wall — so the proof ends up where buyers actually see it.

None of that is clever. It just means the ask happens every time, and the ones that didn’t land are visible instead of forgotten.

Start with the last five

Before you change anything about your process, do this: list the last five projects you delivered and delete the ones where the client was genuinely unhappy. What’s left is a set of people who liked working with you and never got asked properly. Send each of them one link this week.

Most of them won’t reply. Enough of them will that you’ll stop treating the review as an awkward favour, and start treating it as the last step of delivery — which is what it is.