'The 30-Day Review Sprint: A Week-by-Week Plan to Double Your Reviews'
Most businesses that want more Google reviews know they should be asking customers — they just haven’t turned that into an actual plan with a start date. This is that plan. Four weeks, one week of work at a time, aimed at getting a real, visible jump in your review count instead of a vague intention to “get around to it.”
You don’t need new software or a big process overhaul to run this. You need a customer list, some texting or email time, and 30 days.
Week 1: Audit where you actually stand
Before asking anyone for anything, find out exactly what you’re working with.
Count your current reviews and rating. Pull up your Google Business Profile and note the exact number and star average today — this is your baseline, and you’ll want it in week 4 to measure the delta.
Look up your top 3 competitors. Search the terms your customers actually use — “[your service] near [your city]” — and note the review count and rating for whoever shows up above you in the map pack. This tells you the real target. There’s no universal “good” number of reviews; there’s only whatever it takes to match or beat the businesses currently outranking you.
Read your last 10-15 reviews, good and bad. Look for patterns — a recurring compliment worth leaning into, or a recurring complaint worth fixing before you go asking for more attention on your profile. If there’s an unanswered negative review sitting there, this is the week to handle it; see how to respond to negative reviews for exactly how.
Pull your customer list. Export or compile everyone you’ve done work for in the last 3-6 months, with a working phone number or email for each. This is the list you’ll work from in week 2, so get it into one place now.
By the end of week 1 you should have: a baseline number, a target number, and a workable customer list.
Week 2: Reach out to your best and most recent customers first
Don’t start with your oldest, most-forgotten customers. Start with the two groups most likely to actually respond:
Your most recent customers. Anyone from the last 30-60 days still remembers the job clearly. The closer to the actual service date, the higher the response rate — someone who worked with you three days ago is in a completely different mental space than someone from eight months back trying to recall which company even showed up.
Your best customers. People who complimented the work, tipped the crew, referred a friend, or were just clearly happy at the time. These are the highest-probability responders in your entire list, and they’re the ones a generic “ask everyone eventually” approach tends to bury instead of prioritize.
Send a direct, personal text or email — not a mass blast — with a one-tap link straight to your Google review box. Keep it short: their name, a specific reference to the job, and the link. If you don’t hear back in a couple of days, one short follow-up is fine; more than that starts to feel like nagging.
Work through this priority list across the week rather than sending everything at once — a steady trickle of new reviews looks more natural to Google than a single unexplained spike, and it’s a habit worth carrying past this sprint. What happens when you buy fake reviews covers exactly why an artificial spike is a bad idea, even a well-intentioned one.
Week 3: Build the ask into every job going forward
The first two weeks catch you up on the backlog. Week 3 is where you stop having a backlog in the first place — by making the review request a standard step after every completed job, not something you remember to do occasionally.
Pick the trigger point: the moment an invoice is sent, the moment a job is marked complete, whatever event already happens for every customer without exception. Attach the ask to that moment specifically, so it never depends on someone remembering.
Decide who sends it and how — a text from the technician, an email from the office, whatever fits how your team actually operates — and write it down as a real step, not a mental note. If it’s not part of the actual workflow, it quietly stops happening the first busy week, which is usually the same week you’d most want new reviews coming in.
This is also the week to make sure the ask itself is good: right timing (same day, while it’s fresh), one clear link, a personal tone. Our complete guide to getting more Google reviews covers exactly what separates a request that gets ignored from one that gets clicked.
Week 4: Respond to everything, then measure the delta
Respond to every review that came in during the sprint — the good ones with a short thank-you, the rare negative one calmly and specifically, never defensively. Reviews with an owner response tend to read as more trustworthy to the next person scrolling past, even the positive ones.
Compare your numbers to week 1. How many new reviews came in? What’s your rating now versus your baseline? Where do you sit against the competitor counts you found in week 1 — closer, tied, ahead?
Decide what becomes permanent. The week 3 process — asking after every job, automatically — is the piece that should outlast this sprint. The audit and backlog outreach were a one-time catch-up; the standing ask is what keeps the count climbing after the 30 days end. If it stops the moment this sprint is over, you’ll be running this same plan again in six months from a similar starting point.
Mistakes that derail the sprint
Blasting the entire customer list on day one. It’s tempting to send every request at once and get it over with. Don’t — a sudden, unexplained spike in reviews is exactly the pattern that looks unnatural, both to customers scrolling your profile and to Google’s own systems. Spread week 2’s outreach across several days instead of one afternoon. For more on why an artificial-looking spike specifically causes problems, see what happens when you buy fake reviews — the velocity issue is the same one, just at a smaller and entirely legitimate scale.
Skipping the negative reviews. It’s easier to focus only on collecting new positive reviews and let an old unanswered negative one sit there. Don’t — a visible, calm response to criticism does real work toward making the new reviews you’re collecting look credible, not staged.
Letting week 3 quietly not happen. The audit and outreach weeks have a clear finish line. The “ask after every job” habit doesn’t, which is exactly why it’s the step most likely to get skipped under the excuse of being busy. If nobody owns it as an actual step in your workflow, it stops.
What this looks like on autopilot
Running this sprint manually works, and it’s worth doing at least once so you understand the mechanics firsthand. But weeks 2 through 4 are exactly the parts that quietly stop happening once things get busy — the backlog outreach doesn’t get finished, the per-job ask gets forgotten during a rush, and reviews slow back down to whatever trickle happens on their own.
This is the exact cadence Review River automates: the moment a job wraps, a 5-touch sequence — two texts, three personalized photo emails — goes out on its own, spaced out instead of dumped all at once, with zero manual sending required. It’s the week-3 system running permanently, without needing to be re-launched as a sprint every time review count starts to slip. For the full case on why reviews are worth this much attention in the first place, see the real ROI of Google reviews.
If you’d like the system in place before you finish reading this, Review River’s 14-day trial gets you 25 new reviews guaranteed, or it keeps working free until it hits that number — no need to run the sprint by hand.