A high star rating is not the whole story
Most local service businesses treat reviews as a scoreboard: get the average above four and a half stars, keep it there, done. That mindset misses the metric that separates growing firms from stalled ones. Review velocity is the rate at which new reviews arrive, week after week, and it deserves its own system.
Reputation management as usually practiced is defensive. You monitor mentions, respond to complaints, and protect the score you already have. Review velocity is offensive. It is a production process, run like any other part of operations, that turns finished jobs into fresh public proof on a schedule. This article is about building that process.
Why recency beats totals
Put yourself in the buyer's seat. Two roofing companies both hold strong ratings. One earned its most recent review eight months ago. The other has reviews from this month, last week, and yesterday. The second company looks alive and busy. The first raises a quiet question: are they still any good, or did something change?
Review platforms feed that instinct. Google surfaces recent reviews prominently on a Business Profile and lets searchers sort by newest. A profile whose latest review is a year old fails that sort no matter how many five-star reviews sit underneath it.
Recency also carries information a lifetime total cannot. A review from last week describes your current crew, your current pricing conversation, your current cleanup habits. A review from three years ago describes a business that may have turned over its entire staff since. Buyers understand this without being told, which is why a smaller competitor with a steady stream of fresh reviews can out-convert an older firm with a bigger but stale pile.
Velocity is an operations problem, not a marketing problem
Businesses with slow review velocity rarely have an unhappiness problem. They have an ask problem. Nobody owns the ask, the ask happens late or never, and satisfied customers drive away and forget you within a day.
So treat review generation like invoicing or job-site safety: a defined step in the workflow with a named owner and a checkable record. Five pieces make it work:
- A trigger. Define the exact moment the ask happens. For most trades that is the final walkthrough, when the customer is looking at finished work and feeling relief. Not three days later by email, when the feeling has faded and the request competes with everything else in an inbox.
- An owner. The person standing in front of the customer makes the ask. Usually that is the lead technician or crew chief, not the office. The office can send a follow-up, but the face-to-face request is the one that converts.
- A script. Give the crew exact words so nobody has to improvise. Something as plain as: it really helps our small business when happy customers say so publicly, would you mind leaving us a Google review while I finish packing up? Rehearse it once at a team meeting and it stops being awkward.
- A zero-friction link. Every step you remove raises completion. A text message with a direct review link, sent while the crew is still in the driveway, beats an email with instructions. A QR code on the final paperwork works for customers who prefer it.
- A record. Log every ask against the job in your job management software, or even a shared spreadsheet. If you cannot see who asked and when, you cannot manage the system, and it will quietly die within a month.
Steady beats bursts
A tempting shortcut is the blitz: blast your whole past customer list this weekend and harvest a pile of reviews at once. Resist it, for two reasons.
First, it reads wrong. A profile that gains a burst of reviews in one week and then goes silent for six months looks odd to an attentive buyer, and unusual spikes are exactly the pattern automated platform filters watch for. Second, a blitz spends your entire backlog in one shot. Velocity is a flow metric. The point is that next month, and the month after, new proof keeps arriving because jobs keep finishing.
The sustainable source of steady velocity is your job schedule itself. If you complete jobs every week, and asking is a standard step at every completion, reviews arrive at a natural, believable pace that mirrors the real rhythm of your business. You can still work the past-customer list, but drip it: a handful of asks per week, starting with the most recent jobs, folded into the same logging system.
The lines you do not cross
Two practices look like clever accelerants and are actually liabilities.
Do not pay, discount, or otherwise reward customers for reviews. Google's review policies prohibit incentivized reviews, and undisclosed incentives create regulatory risk on top of the platform risk. One removed batch of reviews, or one public accusation from a competitor, costs more than the incentive ever earned.
Do not gate. Gating means surveying customers first and only sending the review link to those who answer positively. Google's policy forbids selectively soliciting positive reviews, and gating also robs you of the honest negative feedback that tells you which crew, process, or subcontractor is creating problems. Ask everyone, the same way, every time. If your work is good, the math works out.
Respond to what arrives, including the rough ones, but keep response as its own discipline. Velocity is about generation. Mixing the two jobs is how both end up half-done.
How to measure it
Three numbers, reviewed monthly, tell you whether the system is alive:
- Asks made, from your log. This is the number you control directly. If it drops, the system has a compliance problem, and the fix is management attention, not marketing spend.
- Reviews received, from the platforms. Divide by asks to get a conversion rate. Track it as your own baseline and watch for changes rather than chasing someone else's benchmark.
- Days since last review, per platform. This is the buyer's eye view. If it stretches past the length of your typical sales cycle, prospects researching you right now are seeing a stale profile.
When velocity stalls, the diagnosis order is always the same: did asks stop, did conversion drop, or did job volume itself fall? Each has a different fix, and the log is what lets you tell them apart.
Make it someone's job this week
Review velocity is one of the rare marketing levers that costs almost nothing, compounds monthly, and sits fully inside your control. Pick the trigger moment, write the script, set up the direct link, and start logging asks this week. If you want the asks, the logging, and the follow-up wired into an automated system that runs without daily supervision, contact Brand Advertisers and we will map it to how your jobs actually flow.