My happiest clients almost never left me a review, and for a long time that was my fault. I did great work and then never asked. The fix wasn't willpower, it was automation: I set a trigger that sends a short thank-you and a review link one day after the job is done, right when the client is still thinking about how well it went. No chasing, no awkward ask weeks later. More reviews mean more trust, and more trust brings more customers.
Every video in my "30 Hacks From Dahlia" series ends with the same line, and this one is a good example of why I keep saying it: I help small teams do big things, and most of what that looks like day to day is quietly automating the parts of the job I kept meaning to get to and never did. Asking for reviews was one of those. I was good at delivering the work. I was terrible at the five-minute follow-up that turns a satisfied client into a public vote of confidence for the next one.
Why my happiest clients almost never left a review
For a while I told myself my clients just weren't the review-leaving type. That wasn't true. When I actually got around to asking, most of them said yes without hesitation, and a few seemed almost surprised I hadn't asked sooner. The problem was never their willingness. It was that I finished a project, moved straight into the next one, and the moment to ask quietly closed behind me.
Reviews aren't a vanity metric for a small service business. They're trust infrastructure. A prospective client deciding between me and someone else isn't reading my portfolio first, they're reading what my past clients said about working with me. Every review I never asked for was a piece of that infrastructure I left unbuilt, not because clients wouldn't give it to me, but because I never opened the door.
The best time to ask is not when you think
My instinct used to be to ask for a review the moment I hit send on the final deliverable. That's actually the wrong moment. Right at delivery, a client is still absorbing the work: checking it, maybe still waiting to see it in action, often just relieved a project is off their plate. Ask too early and the request gets buried under everything else that happens the day a project wraps, or you get a rushed line that doesn't say much.
The moment that actually works is a day later. By then the client has had time to sit with the result and feel the relief of the project being done well. That's when the goodwill is highest and the ask feels like a natural next step instead of an interruption to the handoff. A day is short enough that the project is still fresh in their mind, and long enough that I'm not competing with the delivery itself for their attention.
What the message should actually say
The content of the message matters less than people think, but it still has to feel like it came from a person, not a system. I keep mine short and warm, and I lead with the thank-you, not the ask. Something close to this:
Hi [name], it was genuinely a pleasure working on [project] with you. If you have two minutes, a review would mean a lot, and it helps other people find their way to the right kind of help. Here's the link: [review link]. No pressure at all, and thank you again for the trust.
Notice what's missing: no guilt, no "we'd really appreciate it if," no three follow-up nags stacked into one email. One link, one sentence about why it matters, and a close that sounds like the way I'd actually talk to that client. The tone has to survive being sent by a machine, which means I write it like I'm the one sending it, because the client should never be able to tell the difference.
Keep it to one link
The biggest mistake I made early on was giving people three places to leave feedback and letting them pick. That's not a choice, it's friction. One clear link, pointed at the one place I actually want the review to live, gets far more responses than a menu of options.
How I set the trigger without hiring a developer
This doesn't require custom software. It just needs a moment my business already tracks, connected to a message that sends itself. There are a few versions of that trigger, and any of them work:
- A form submission. If clients (or I) mark a project complete through an intake or project form, that submission itself can be the trigger, with a delay attached before the message goes out.
- A project-status change. If I run work through a project management or task tool, moving a project to "Done" can kick off the same delayed send.
- A calendar-based delay. The simplest version: a delivery date gets logged somewhere, and a scheduled rule fires one day after that date, no status change required.
Most project management, invoicing, and CRM tools already have some version of a scheduled or delayed action built in. I didn't build anything new. I just pointed an existing trigger at a message I'd already written, and stopped being the one responsible for remembering.
Don't build a new step into your workflow just for this. Find the moment you already mark a project finished, whether that's a status field, an invoice going out, or a calendar entry, and attach the delayed message to that. The less new process you introduce, the more likely it actually stays on.
I didn't need to get better at asking. I needed to stop being the one who had to remember to.
Where the review link should point
For most client-facing businesses, a Google Business Profile review carries the most weight, because it's public and it shows up directly when someone searches your name or your business. That's the destination I default to. A testimonial page on my own site is a useful second stop, especially for pulling quotes into proposals or social posts later, but it shouldn't be the only place I send people, since a testimonial I control myself doesn't carry the same trust as a public, third-party review.
If there's an industry-specific review platform your clients already trust, that can outperform a general one. The rule I follow either way: pick one primary destination, make sure the link goes straight to the review form (not a homepage the client has to navigate from), and don't change it project to project.
Why chasing after the fact never worked for me
Before I automated this, my fallback was to ask weeks later, usually when I remembered because I was writing a proposal and needed a fresh testimonial. That version of the ask always felt off. It landed like I was calling in a favor rather than closing a loop, and it was easy for a client to skip because the moment of goodwill had already passed. Worse, I skipped asking entirely more often than not, because remembering depended on me having a free minute at exactly the right time, which almost never happened.
The automated version removes that dependency completely. The ask goes out on schedule whether I'm slammed that week or not, and it goes out while the client still remembers exactly why they were happy. That's the actual reason this works better, not because the wording is clever, but because the timing is no longer something I have to hold in my head.
Before you turn this on
One hack, out of thirty
This is hack 7 in a series I never expected to keep going this long, because there's always one more piece of the day quietly worth automating. The rest of the series is linked in my bio. If you run a service business where every client relationship ends the same way, project delivered, client happy, review never asked for, this is the smallest fix I've made all year with the biggest effect on how many new people actually find me.
Frequently Asked Questions
About a day after the project or job is delivered, not the moment it's finished. Right at delivery, a client is still absorbing the work. A day later, they've had time to sit with the result, and the goodwill from a job well done is still fresh enough that the ask feels natural instead of like an interruption.
Keep it short and warm, not transactional. Lead with a genuine thank-you, mention the specific project by name if you can, include one link, and explain in a single sentence why it matters. Skip the guilt-tripping language and skip stacking multiple asks or follow-up nags into one message.
For most local or client-facing businesses, a Google Business Profile review carries the most weight because it's public and shows up directly in search results. A testimonial page on your own site is a useful complement, especially for quotes you want to feature in proposals or on social media, but it shouldn't replace a public, third-party review.
No. The trigger just needs a moment your business already tracks: a form submission marking a project complete, a status change in whatever tool you use to manage work, or a calendar-based delay counted from a delivery date. Most project management, invoicing, and CRM tools already have a way to schedule a message off one of those events.
