Here’s a conversation we have all the time.
An operator tells us reviews are handled. They have a platform. It sends requests, reviews come in every month, the rating looks strong, and the dashboard is green. By every visible measure the box is checked.
Then we look at their job volume.
A company completing 2,000 jobs a month and collecting 190 reviews looks productive in isolation. Nobody asks the harder question: how many reviews were actually available? How many customers finished a job happy, would have left a review if asked the right way at the right moment, and never did?
That difference is the capture gap. It’s expensive, and nothing about it looks broken, which is the problem.
Why the gap is invisible
Your review platform reports its own output. Requests sent, reviews collected, rating trend. What it doesn’t report is the denominator: the total pool of customers who were willing to leave a review this month.
Without the right context, or the right denominator, 190 reviews a month reads as a healthy program. It isn’t. On 2,000 jobs, that’s under 10% capture, which is what a basic one-message, no-follow-up ask produces. A well-run system captures over 20% of completed jobs. On those same 2,000 jobs, that’s more than 400 reviews a month. It never occurs to anyone the number should be that much higher, because there’s no line on the dashboard showing the reviews that got away. A report that only measures its own output will always look good.
When operators switch to Liftify, we routinely find their old solution was leaving 30 to 40 percent of available reviews uncollected. The customers weren’t unhappy. The ask was just a single message, sent at a generic time, through one channel, with no follow-up. The customer meant to do it, life got in the way, and the review never happened.
What the gap actually costs
A missed review isn’t a rounding error, and the cost shows up in more than one place.
Start with the part that’s permanent: you can’t re-ask a customer from eight months ago. Every month at a low capture rate is inventory that expires. An operator leaving 100 reviews on the table monthly loses 1,200 in a year while a competitor down the street collects theirs.
There’s also a visibility cost you’re paying right now. Review volume, velocity, and recency are core inputs to local search and the map pack, and the stakes recently went up. Google Business Profiles now surface directly inside AI answers for local searches, and independent research puts home services among the most disrupted verticals. Reviews you don’t capture are visibility you don’t get, in the channel where your next customer is deciding.
And if you’ve spent decades earning a reputation, a capture gap means your online presence reflects a fraction of it. You show up to every estimate with less proof than your service record justifies, and paid media has to make up the difference. You end up buying back attention you already earned.
There’s a defensive reason volume matters too. Bad reviews are inevitable; run enough jobs and someone will have a bad day. What decides whether that one-star dents your rating is how many five-stars surround it. At 190 reviews a month, a handful of bad ones move your average. At 400, they get absorbed. Volume is insulation, and the gap is the insulation you didn’t collect.
Why “we already have a platform” is the trap
The capture gap is hardest to fix at companies where reviews look handled, because there’s no crisis forcing the question. The program produces output. The rating is fine. Switching feels like risk with no obvious payoff.
The math says otherwise. Closing a 40 percent gap doesn’t require your team to work differently or your customers to become more generous. The jobs and the goodwill are already there. What changes is how and when the ask happens: the channel, the timing, the sequencing, and whether anyone follows up when the first message gets buried.
That’s a mechanics problem, and mechanics problems are solvable. When the gap closes, results show up fast because the demand existed all along. Operators typically see it in the first full month, not the second quarter. Volume jumps while the rating holds steady, which tells you the missing reviews were never a quality problem. They were a capture problem.
How to find out if you have one
You don’t need to take anyone’s word for it. Take your completed jobs per month, take your reviews per month, and divide. Under 10% means a basic ask is running and a gap is almost certain. Over 20% is where a well-run system lands. If your ratio has been flat for a year while job volume grew, or it sits meaningfully below that mark, you have a gap.
The clearest tell: your monthly review count has become a stable, predictable number. Capture rates near the ceiling don’t behave that way. They track job volume.
Then ask your current vendor one question: what percentage of available reviews are we capturing? If the answer is a description of requests sent rather than a number, you’ve learned something.
The takeaway
The most dangerous reputation problem isn’t a bad review. It’s the good ones that never existed, and they don’t show up on any dashboard you look at.
So the question worth asking isn’t “do we have a review platform.” It’s “are we getting the number of reviews we should be getting?”
Your reviews should keep up with your work. If you want to know what your capture rate actually is, we’ll show you on your own locations. Free 30-day pilot, up to 5 locations, no commitment to start.
