How to ask a client for a review politely (8 scripts that don’t feel like begging)

Most review requests fail for the same reason: they’re written to protect the sender’s feelings rather than to make the client’s decision easy. They hedge, they apologise, they leave the size of the favour undefined, and they end with something like “no pressure of course!” that quietly gives the reader permission to do nothing.

A polite request isn’t a timid one. It’s a clear one that’s easy to decline. Below are five rules and eight scripts you can send as-is.

Five rules that decide whether you get a reply

Ask for something specific. “Any feedback is welcome” is not a request. “A short review of the migration — how it went, and whether you’d work with us again” is. The second one tells the reader exactly what to type, which is the actual bottleneck.

Name the size. Two or three sentences. Thirty seconds. A rating and a line. People don’t postpone small tasks; they postpone undefined ones. Saying how small it is does more work than any amount of charm.

Give one link, not instructions. If your ask contains the words “you’ll need to create an account,” you have lost roughly everyone. One link that opens straight into a form is the whole game.

Give a real out. “If now isn’t a good time, just say so and I’ll close it off.” This feels like it lowers your odds. It raises them, because non-replies are usually avoidance, and you’ve just made the cheap answer a reply rather than silence.

Cap the follow-up, in writing. “I’ll follow up once and then leave it alone.” Clients ignore requests partly because they expect a campaign. Tell them there isn’t one, then keep your word.

1. The first ask, at handover

Sent the day you hand over, while the outcome is still fresh and the relationship is at its warmest. This is the highest-yield message in the whole set.

Hi Priya,

Everything is handed over: the repo, the credentials doc and the walkthrough recording are all in the shared drive, and the support window runs until the 30th.

One small favour before I get out of your way. Would you leave a short review of the project? Two or three sentences is plenty — what you needed, how the work went, and whether you’d work with us again.

Here’s the link: [your review link]

It takes about a minute and it genuinely helps us win the next project like this one. If now isn’t a good time, just tell me and I’ll close it off.

It was a pleasure — good luck with the launch.

Sagar

2. The line you add to the final invoice

The invoice is the one email that never gets ignored. Attaching the ask to it costs nothing and doubles the number of asks that actually get sent, because the invoice is already in your process.

Hi Tom,

Attached is the final invoice for the rebuild, due on the 30th as agreed.

While it’s in front of you: if you have two minutes, a short review of how the project went would be a real help to us — link below. Completely optional, and it has no bearing on anything to do with the invoice.

[your review link]

Thanks for a well-run project on your side too.

Sagar

Note the explicit separation between the review and the invoice. Say it plainly; otherwise a careful client may wonder whether one is a condition of the other.

3. The one-week nudge

Short, capped, and easy to say no to. Send it once, roughly seven days after the first ask.

Hi Priya,

Nudging this once and then I’ll stop: the review link is below if you have a couple of minutes.

[your review link]

Two or three sentences is all I’m after. And if you’d rather not, just say the word — no hard feelings at all.

Sagar

4. The final, no-pressure close

Sent two to three weeks after the nudge. Its job is not really to get a review — it’s to close the loop cleanly so that neither of you carries an open request into the next project.

Hi Priya,

Last one from me on this — I’m closing the review request out so it stops sitting in your inbox.

If you ever do want to leave one, the link stays live: [your review link]

Either way, thanks for the project. Give me a shout when the next phase comes round.

Sagar

5. When you’re asking on behalf of the delivery team

For account managers and project leads asking on behalf of people the client worked with directly. Name the individuals — it makes the request concrete and makes it feel like recognition rather than marketing.

Hi Tom,

Now that phase two is signed off, I wanted to ask for something on behalf of Devi and Arun, who ran the day-to-day with you.

Would you leave a short review of how the engagement went? A few sentences on what we delivered and what it was like to work with the team is exactly right.

[your review link]

We use these both externally and internally — the team reads every one. It takes a minute or so, and if you’d rather pass, that’s completely fine.

Thanks Tom.

Meera

6. The retainer with no finish line

Ongoing work has no handover moment, which is why retainer clients are so often the ones you have nothing published from. Manufacture a moment: a quarter boundary, a renewal, or a milestone worth naming.

Hi Tom,

Q3 summary is attached: 14 tickets closed, the checkout latency work finished, and uptime held at target through the sale weekend.

Since we’ve been working together for about a year now, would you be willing to leave a short review of how the retainer has gone? Something that speaks to the ongoing relationship rather than a single project is ideal — responsiveness, reliability, whether you’d recommend us.

[your review link]

Three or four sentences would be perfect. Happy to hear it if the answer is not right now.

Sagar

7. When the client praised you in passing

Someone says something generous on a call, in Slack, or in an email thread. That is the single best moment to ask, and it has a shelf life of about a day. Ask while the sentence is still theirs.

Hi Priya,

You said on the call that this was the smoothest launch your team has had. That was a nice thing to hear, and I have a slightly cheeky follow-up: would you be willing to write that down?

[your review link]

Honestly, more or less what you already said would be perfect — two or three sentences, in your own words.

Thanks Priya.

Sagar

8. The late ask, months after delivery

The one everybody avoids. It works far more often than people expect, as long as you name the delay instead of pretending it isn’t there.

Hi Tom,

This is a late one — we finished the portal back in March and I never properly asked.

If the work has held up on your side, would you leave a short review of it? A few sentences about what we built and how it went is all I need.

[your review link]

Totally understand if it’s too far in the rear-view. Either way I hope the platform is treating you well.

Sagar

Phrases to cut

Most weak requests share the same handful of tics. Each of these signals that you don’t think the ask is reasonable — and the reader takes your word for it.

• “Sorry to bother you…” You aren’t bothering them. Open with the request or with something useful to them.
• “If you have a spare moment sometime…” Two vague time words in one clause. Say what it costs: two minutes.
• “It would really help us out.” Fine once, at the end. As the entire justification, it makes the review about your needs, and gives the reader nothing to write about.
• “Any feedback, good or bad!” You’re asking for a published review, not a retrospective. Keep private feedback and public reviews as two separate conversations, or you’ll get neither.
• “Just following up!” (for the fourth time) After two follow-ups, stop. A third and fourth chase costs you goodwill worth more than the review.

Handling the three common replies

“Sure — can you draft something and I’ll approve it?” Common, and reasonable from a busy client. It’s also a trap: a review you wrote in their name isn’t their review, and readers can smell it. A better answer is to send three specific questions and let them answer in their own words — what problem you solved, what the work was like, whether they’d recommend you. Then submit exactly what they wrote.

“I need to check with marketing/legal.” Normal in larger organisations. Ask what they need: an approved wording, a role-only attribution (“Head of Engineering, mid-market retailer”), or an internal-use-only quote. A constrained review beats no review.

Nothing at all. Nudge once, close the loop once, then let it go and make sure the next project’s ask goes out on time. The cure for a low review count is more asks, not more chasing per ask.

Make the ask the easy part

Every script here assumes one thing: that “[your review link]” is a real link, tied to that client, that opens straight into a form with no account required. That’s exactly what Reviewee generates — one link per client or project, sent from Reviewee or pasted into your own email, with each link showing as pending or completed so you know who still owes you one. Reviews land with you for approval before anything is published.

If your problem is less about wording and more about reviews falling through the cracks between account managers, read the review gap in outsourced work. If you want to know when to send each of these, see when to ask a client for a review.