You do good work. Ask anyone who's hired you twice. Then you check the review page and the outfit down the road, the one with the beat-up truck and the crew that never calls back, has more stars than you do.
It stings more than it should, because it isn't fair, and fair has nothing to do with it. Reviews don't measure the work. They measure whether the work turned into a review, and that's a different question with a different answer.
That's not bad luck and it's not a review-site problem. Somebody built a system, and you're still relying on a customer's memory of a good day, weeks later, to do something they've already stopped thinking about the second the invoice cleared.
It's not a marketing problem
The instinct is to ask harder. Put a sign on the last truck. Tell the crew to mention it on the way out. Send a text a week later, if you remember.
That's the whole failure mode in one sentence: if you remember. Anything that only happens when you remember to make it happen isn't a system, it's a chore wearing a system's costume. Chores get skipped the first busy week of the season, and busy weeks are the only kind you get. I've made this argument before about the rest of the business: the fix was never working harder, it was building something that runs on its own.
Anything that only happens when you remember to make it happen isn't a system, it's a chore wearing a system's costume.
Generate: the link goes out every time
The review link rides the invoice. Every job, not just the ones you're proud of, sent by whoever's already sending the bill. That's the office, not you. Satisfaction peaks the moment the work is done and the invoice lands, so that's the moment the ask goes out too, folded into a step you're already running instead of one more thing you have to remember to do.
Notice what that fixes on its own. You don't have to decide which jobs deserve the ask, because every job gets it. You don't have to catch the customer at the right moment, because the invoice already is that moment. One step, attached to a step that already happens without fail, and the whole question of remembering disappears.
Incentivize: pay the crew, never the customer
Pay your crew for reviews. Not the customer, the crew. A small bonus when a review names the crew, good or bad, gives the guys actually doing the work a reason to care how the job lands, because now it's theirs too.
Here's the rule the whole thing runs on, plain: rewarding your own people for work that earns a good review is fine. Paying, discounting, or gifting a customer to leave one is not, and neither is only sending the ask to the customers you already know are thrilled. The link goes out with every invoice, not a curated few.
Rewarding your own people for work that earns a good review is fine. Paying, discounting, or gifting a customer to leave one is not.
Monitor: someone has to be watching
Someone owns watching for new reviews, and it can't be a mental note you make when you happen to think of it. Most review platforms can alert you when one lands. The system isn't a paid reputation tool. It's an alert plus a rule for what happens next, and it belongs to whoever runs the front desk, not to whoever happens to check their phone that day.
Route: a bad review is a phone call, not a fight
A review that names the crew gets flagged so the bonus lands. A bad one goes straight to whoever runs the business, fast, and gets handled the way you'd want any mistake handled: acknowledge it calmly where people can see it, take the real conversation off the public page, and fix what's actually fixable. A calm, accountable answer to a bad review isn't damage control. It's the trust signal, because the public reply isn't really for the unhappy customer, it's for every future customer reading it before they ever call you.
Never argue with a customer where strangers can read it. Never put the details of someone's job in a public reply. And never let the fix look like you paid to make a bad review disappear. That crosses the same line as paying for a good one in the first place.
A calm, accountable answer to a bad review isn't damage control. It's the trust signal.
What you get for it
Do all four and the flywheel spins whether you're standing next to it or not. New reviews stop depending on which crew had a good week, or whether you remembered to ask, or whether today was one of the days you had the bandwidth to care. A review that used to require you noticing, asking, and following up now requires nothing from you at all, and it still shows up.
The business gets found by people who've never met you, without you doing anything that day beyond the parts you were already doing. That's freedom first: one more thing that used to require your attention every single day now runs without it. The growth, more stars, more first impressions won before you ever quote a job, is real. It's just not the reason to build this. It's what happens after.
The business gets found by people who've never met you, without you doing anything that day.
Find the rest of your bottlenecks
Reviews are one system out of dozens hiding in a business that still runs through you. The Bottleneck Scorecard finds the rest in five minutes: seven questions, a score, and the one thing to fix first. No email required to see your result.