Up from a trickle, the month after switching to a pipeline-embedded review platform in mid-February 2025 (versus a prior tool that had almost no measurable effect).
Across both of the business's Google Business Profile listings, with the older listing alone holding 235 reviews.
Tracked directly in the Google Business Profile dashboard, on the listing that had been active for years before switching platforms.
On a second, newly built listing with a fraction of the review history, already outperforming its size once the same automated request system was applied to it.
Reviews had gone quiet for a concrete repair contractor running 2 Google Business Profile listings, both stuck at roughly the same count for months at a time. Automating the ask turned that silence into 37 new reviews in a single month.
That's what happened for Owen (not his real name), whose $3.1 million business had been getting "lucky if we got 30 a year" out of its old review process. Switching to a platform built into his own job pipeline changed what Google's algorithm saw.
Owen's business wasn't short on customers, closing 2024 with $3.1 million in sales across 2 install crews and a small sales team.
What it was short on was fresh reviews. Years of relying on staff to remember to ask had left both Google listings stuck at roughly the same count for months at a stretch, and he'd already tried to solve it once, on Stuart Trier's earlier recommendation, with a different review-request tool. It didn't work.
"It's almost no effect. But we did sign up for Liktify. It works in our pipeline, so it's seamless."
— Owen
Why would a tool built to generate reviews produce almost none? Because it still asked a busy crew to remember an extra step, and busy crews don't remember extra steps. That single word, seamless, is the whole difference between a review tool that fails and one that doesn't. His prior tool asked Owen's team to remember an extra step every time. Liktify didn't ask anyone to remember anything.
Local rankings can slip for a business with 300 reviews and none in the last 6 months, as long as a competitor's reviews keep arriving on a steady weekly schedule. Does that sound backward? Instead of a trophy case, Google's local ranking system treats a business's review history like a pulse.
Stuart named the mechanism directly on the call:
"The velocity at which we get those reviews impacts the number of leads that the Google business profile will send... that's the contribution that you guys really own."
— Stuart Trier, Founder & CEO, Clear Results
Not the marketing agency. Not the website. That pace of real customer feedback is the one piece of local ranking a business fully controls.
Review velocity is the speed and consistency at which a business earns new customer reviews. It has little to do with the running total. Google's local search algorithm treats reviews less like a lifetime scoreboard and more like a signal of whether a business is currently active: a steady, weekly drip tells it a business is trustworthy right now, while a stalled profile, even one with hundreds of old five-star reviews, reads as dormant and loses ground to competitors. Once a business has 300 reviews and hasn't received a new one in months, its velocity is effectively zero, and its local ranking will slide regardless of that historical total. By contrast, a business earning even 2 to 3 fresh reviews a week tells the algorithm it's an active option, which shows up directly in local search placement and the calls that follow it. Buying or begging for 50 reviews in one burst doesn't substitute for that steady pace; Google's system is built to notice the difference between momentum and a one-time spike, and it rewards the former.
Owen's version of that fix wasn't a new script or a reminder taped to the wall. It took the step out of anyone's hands.
Liktify sits inside the job pipeline itself, triggering a review request automatically once a job closes out, and routing that request to whichever of the business's 2 Google listings matches the job's location. "They are, whenever somebody does it, it goes to the right one," Owen said of the routing, confirming the system handled a detail his prior tool never touched. Retroactively, it also mined past completed jobs, giving the new pipeline a head start instead of starting from zero.
Owen paired the software with a small incentive: $10 to $20 whenever a review named a specific technician by name.
Google doesn't allow businesses to pay for reviews, but it has no objection to a business rewarding the employees behind them, and that distinction mattered enough that Stuart flagged it directly on the call. Results showed up within weeks: 37 reviews came in during the first full month, dropping to 19 the next month as the retroactive backlog thinned out, then settling into a steadier single-digit monthly pace by early summer, still consistent, still weekly, exactly the pattern the algorithm rewards.
Not every part of Owen's push to get customers talking worked, and one exception deserves a direct look.
Around the same time as the Liktify rollout, Owen's team launched a separate referral app meant to turn satisfied customers into active recommenders. It didn't take.
"I need to know why this isn't working for you."
— Owen, sitting his team down to diagnose the stalled referral program
The review platform worked because it took the human step out of the process. The referral push didn't, because it still depended on customers and staff remembering to act on their own. Owen hasn't fully solved that second piece yet, and it makes a real point: automating the ask only works where the ask can be automated, and not every version of "get people talking about us" reduces to a pipeline trigger.
| Metric | Before | After |
|---|---|---|
| Review request method | Manual, staff-dependent; a prior tool produced "almost no effect" | Automated, pipeline-triggered on every job close |
| Reviews in a strong month | "We'd be lucky if we got 30 a year" | 37 in a single month (March 2025) |
| Combined Google rating | Not tracked as a combined figure | 4.9 stars across 2 listings |
| Weekly organic calls, established listing | Not tracked | 23 in a single tracked week |
Any trade that treats reviews as a box to check once, instead of an ongoing signal, runs a version of Owen's problem.
An HVAC contractor sees the same pattern every summer. Techs collect a burst of reviews during peak summer diagnostic season, then the ask disappears once the heat breaks. By the fall shoulder season, when preventative-maintenance leads matter most, the profile has gone quiet for months, and rankings have already slipped before the owner notices the call volume dropping.
Plumbing companies feel it in the seam between emergency work and planned installs. An office admin batch-emails review requests once a month from the accounting software, days or weeks after a customer's gratitude has cooled. Consistency alone lets a newer, smaller competitor pull ahead in local search, as long as its request fires the moment a ticket closes.
None of this is exotic. It's the same failure mode wearing a different trade's uniform.
Roofing companies feel it after a storm. Sales reps chase 40 reviews in a single frantic month during peak claims season, then the request stops once winter work slows to gutter jobs and small repairs. To the algorithm, that pattern looks like a business that only shows up once a year, and ranks a steadier, smaller competitor above it in the months that matter most.
Yes, and the risk is often invisible until rankings have already slipped. Size doesn't protect a listing once new reviews stop arriving. Google's local algorithm reads an inactive history as a sign the business may no longer be active, no matter how many five-star reviews sit in that total. A smaller competitor adding just 2 or 3 reviews a week can out-rank a much larger, stalled profile.
Only if it's artificial. A single burst followed by months of silence draws scrutiny. A request tied to every job close scales with real, ongoing work instead, which is the pattern Google's system is built to trust.
Not on its own. An agency can optimize a listing's content and structure, but it can't manufacture the actual customer contact that produces a review. Stuart's own framing on the call was direct: the review-request relationship is "the contribution that you guys really own," because no outside agency has the kind of access to a business's actual customers that its own crews do.
It shouldn't, if the request follows an actual job closeout instead of going out to everyone at once. Owen's team times the ask to the final walkthrough, right after a customer signs off on completed work. That's a different moment than a generic mass request sent regardless of how the job went.
That's a real risk, and not every part of a reviews push goes as planned. Owen's own team struggled with a related referral program that depended on staff remembering to act on their own, and he had to sit his crew down directly to find out why it wasn't working. A pipeline-embedded review platform doesn't have that problem: it never depends on anyone remembering anything. The incentive rewards performance; the system itself does the actual work.
In this case, review volume shifted within the first month of switching platforms, and the jump in organic calls was visible on the Google Business Profile dashboard about 5 weeks after rollout. Results depend on a business's job volume and how its existing listing history responds, but the mechanism (steady weekly reviews driving steady weekly search visibility) starts compounding once the request step stops depending on memory.
Stuart Trier is the Founder and CEO of Clear Results. Over the past 20 years, Stuart has built, bought, and sold 11 companies across the home service, healthcare, and marketing industries. He built his first company from startup to $8M in revenue in 3 years before a successful exit, then built a chain of 28 healthcare clinics and sold the business to a publicly traded company. Following that acquisition, Stuart spent 3 years working alongside the CEO, helping lead the organization through a take-private transaction before participating in a nine-figure exit to a Fortune 10 company. Today, he's the lead investor behind an electrical services platform operating across 3 U.S. states, and has worked directly with owners through 1,800+ strategic advisory sessions.
A concrete repair contractor ran one service at a 60% gross margin and another at 45%, and neither his marketing spend nor his sales commissions were built to tell the difference. Redirecting both toward the higher-margin work, and capping the rest, came months before a deeper pricing fix.
A specialty concrete contractor hit $3.1m in sales and had just $16,000 to show for it, then borrowed on credit cards to cover payroll. Fixing how the business priced its own overhead exposed a $190/hour burden hiding in every job, and one price increase turned the year around.
A concrete repair contractor kept losing candidates to no-shows and scrambling every time someone quit. Paying applicants to prove themselves through a staged tryout, instead of hiring off an interview alone, built a 28-candidate bench and a record $364,000 install month.
