Home About Experience Projects Case studies Resources Articles Briefs Playbook Tools FAQ How we start Security Get in touch

Marketing operations

Review Requests That Fire on a Signal, Not a Schedule

Most businesses doing good work have almost no public evidence of it. The reason is rarely unwillingness. It is asking at the average moment, which is nobody's good moment.

Most businesses that do good work have almost no public evidence of it, and the reason is not that clients are unwilling. It is that nobody asks, or asks at the wrong moment, or asks in a way that requires effort.

ASK AT THE MOMENT OF RELIEF, NOT AT MONTH END ask here just after something went well and they said so themselves not three weeks later how positively they feel Goodwill has a half-life. The request should fire on a signal, not on a schedule.
Figure 1: the timing is the whole automation. A month-end batch asks everyone at the wrong moment.

Timing is the entire automation

Goodwill has a half-life. The moment to ask is immediately after something went well, ideally after the client has said so themselves. Three weeks later, the same client is thinking about something else and the request feels like an imposition.

This is why a monthly batch request performs badly: it asks everyone at the average moment, which is nobody's good moment.

Fire on a signal, not on a schedule. The signal is a completed milestone or a positive message, not the calendar.

How to build it

1. Pick a trigger that correlates with satisfaction

Project completion, a milestone delivered on time, a renewal signed. Not elapsed time. If you can detect a positive message from a client, that is the strongest trigger available.

2. Ask the internal question before the public one

A short private message asking how it went. Route the positive answers to a review request and the negative ones to a person who calls them the same day. This is not filtering; it is finding out before a public review tells you.

3. Make it one click

A direct link to the specific place you want the review, pre-authenticated where possible. Every additional step loses a meaningful share of people who genuinely intended to help you.

4. Ask a specific question, not for a review

People struggle with a blank box. Asking what specifically was useful produces a better review and takes them less effort than being asked to summarise an entire engagement.

5. Ask one named person, not a company

Reviews come from individuals. Send it to the person you actually worked with, from the person who actually worked with them, not from a shared address.

6. Never automate a reminder more than once

One follow-up after a week. Beyond that you are asking someone to do you a favour repeatedly, which converts goodwill into irritation.

Tools and what they cost

OptionWhat it costsHonest trade-off
CRM workflow on a stage changeIncluded in mid-tier plans.Fires from the deal or project record you already maintain. Requires your stages to reflect reality, which is often the actual work.
Review platforms (Trustpilot, Birdeye, and similar)Monthly, from tens to hundreds.Handle sending, reminders and display. Priced for businesses with high transaction volume, and rarely proportionate for a small agency.
Apps Script triggered from a trackerFree with Google Workspace.Full control of the trigger, the fork and the wording. A few hours of work.
A person sending a personal messageFree, and better than any automation.Genuinely the highest quality option and the first thing to stop happening when everyone is busy. Automate the prompt to send it rather than the message itself.
THE FORK THAT KEEPS THIS HONEST How did that go? well badly Ask for the review with a direct link, one click Route to a person who calls them, today Asking the internal question first is not gatekeeping. It is finding out before a public review does it for you.
Figure 2: ask privately how it went, then act differently on the answer.

What it is actually worth

The measurable output is volume of evidence. Count how many public reviews, testimonials or usable quotes your business collected in the last year against how many engagements you completed. For most small businesses the ratio is close to zero, and that gap is the entire opportunity.

The secondary value is early warning. The internal question catches dissatisfaction while it is still private and fixable, which is worth more than the reviews it generates. A client who tells you privately that something disappointed them is giving you a chance nobody else will.

I am not going to quote statistics about how many consumers read reviews or how much revenue they influence. Those figures come almost entirely from review platform vendors, vary by an order of magnitude, and are usually drawn from consumer retail contexts that do not transfer to business services.

How it breaks

It fires after a bad experience. The worst possible outcome and precisely what the internal question prevents. Never send a public review request without knowing how the client feels.

It comes from a no-reply address. Asking someone for a favour anonymously is a poor trade. Send from the person they worked with, and let replies reach a human.

The link is broken or requires a login. Test it yourself, as an outsider, on a phone, every quarter.

Reviews arrive and nobody responds to them. An unanswered review, especially a critical one, is worse than no review. Route new reviews to a person the same day.

How to tell whether it worked

Reviews or testimonials collected per completed engagement, which is the direct ratio. Response rate to the internal question, which tells you whether the timing is right. And issues surfaced privately before becoming public, which is the number that quietly protects you.

Sources. Pricing is list price at time of writing. I have deliberately not quoted statistics on review influence or consumer trust, because those come overwhelmingly from review platform vendors, vary by an order of magnitude between sources, and are usually drawn from consumer retail contexts rather than business services.

Paul Prado Pacardo is a Senior Executive Assistant and Operations professional with over ten years supporting C-level leaders, and the solo founder of a multi-product software studio. Available for remote Chief of Staff, Operations, Senior Executive Assistant and Project Manager roles.