How Many Reviews Do You Need to Beat Your #1 Competitor?

"We need more reviews" is not a plan. "We need 47 more reviews at 4.8+ stars, which at 6 per week takes 8 weeks" is a plan. This post turns the vague anxiety about your competitor's review count into arithmetic — and then into a system.

This is the strategy layer of the review engine. The pillar post covers the mechanics of getting reviews; this post tells you how many you need and how fast to get them.

Step 1: Map the competitive field

Search your main service + town on Google ("AC repair [Town]", "plumber near me") and look at the local map pack — the 3-business map box at the top. Write down, for each of the top 3–5 competitors:

• Review count (the number next to the stars).
• Star rating (to one decimal).
• Review velocity — scroll their newest reviews and note the dates. Are they getting 2 a week or 2 a month? A competitor with 400 reviews who's gone quiet for 6 months is catchable; one adding 10 a month is a moving target.

Do the same for yourself. Now you have the field, honestly measured. Most owners overestimate the gap — "they have hundreds" turns out to be 180, and 180 is a finite number.

Step 2: Do the gap math

The target isn't just matching their count — it's beating the impression their profile makes. The formula:

• The count gap: (their review count) − (your review count) = reviews needed to tie. Add a 10–20% buffer — you want to clearly lead, not barely tie.
• The rating floor: if they're at 4.8 and you're at 4.3, count alone won't save you — 68% of consumers won't use a business with under 4 stars (BrightLocal 2026), and the gap between 4.3 and 4.8 reads as a quality gap. You need volume and the recovery playbook for your low reviews.
• The velocity adjustment: if they're adding reviews too, your target moves. Needed reviews = count gap + (their monthly velocity × months it'll take you). This is why the timeline matters — a slow campaign against a fast competitor never closes.

Step 3: Set the weekly velocity target

Work backward from a deadline. Pick 90 days — long enough to be realistic, short enough to stay urgent:

• Reviews needed per week = total gap ÷ 13 weeks. If the gap is 60, that's ~5 per week.
• Asks needed per week = weekly target ÷ your ask-to-review conversion rate. Don't know your rate? Start by assuming 1 in 4 asks becomes a review (directional — measure your own after month one), so 5 reviews/week means ~20 asks/week.
• Reality check: can your job volume support 20 asks a week? If you do 15 jobs a week, no — and that's fine. The math just told you the timeline is longer, or that you need the passive surfaces (QR codes, invoice links) and the 48-hour nudge working alongside the active ask to lift the conversion rate.

Step 4: Build the engine to hit the number

The velocity target dictates the system. This is where the review engine's pieces combine:

• The active ask after every job (the pillar post's timed text) — your primary volume driver.
• The 48-hour nudge for non-responders — typically the cheapest incremental reviews you'll ever get.
• The passive surfaces — QR codes, invoice links, email signatures — catching the customers the asks miss.
• The weekly scoreboard — every Monday, one number: reviews gained last week vs. target. If you're behind two weeks running, the ask script or the timing needs attention, not more hope.

Assign one owner to the scoreboard. Review velocity dies the same way every time: nobody's watching the number.

What "beating" them actually looks like

A note on the finish line: you don't need 10× their reviews. In local search, the perceptual tiers are what matter — a 4.9 with 120 reviews vs. a 4.7 with 200 reviews is a genuine toss-up in a customer's mind, and review recency breaks ties (a profile with 10 reviews this month beats one whose newest review is from last year). Once you're in the same tier with fresher velocity, you've effectively won the review battle. Then the game becomes staying ahead, which the engine does automatically.

When the gap looks impossible

Sometimes the math comes back scary: the competitor has 600 reviews and you have 40. Three things to remember. First, recency compresses the gap — a profile adding 8 reviews a month looks more alive than one sitting on 600 stale ones, and customers notice. Second, you don't need to beat them everywhere — pick your money service ("AC repair [Town]") and win the review battle on the searches that produce your best jobs. Third, the gap is finite and your velocity compounds — every review you earn also trains your team to earn the next one faster. The shops that close 500-review gaps don't do it with one heroic campaign; they do it with 18 months of the engine running every week. Start the clock now.

A worked example

Example: a plumbing shop has 64 reviews at 4.6. The top competitor has 210 at 4.8, adding ~6/month. Count gap: 146. Buffer (15%): ~168. Velocity adjustment over a 6-month campaign: competitor adds ~36 more, so the real target is ~204 reviews. That's ~8.5/week for 24 weeks. At a 1-in-4 ask conversion, that's ~34 asks/week — but the shop only does ~25 jobs a week. Verdict: the 6-month timeline is unrealistic on job volume alone. Options: extend to 9 months (~5.7/week, ~23 asks/week — feasible), or lift conversion with the nudge + passive surfaces and re-measure after month one. The math didn't say "give up" — it said "here's the real timeline." That's what a plan looks like.

Related guides in this series

The engine that closes the gap is the contractor Google-reviews guide — the pillar post with the full ask system. The 48-hour nudge and the passive review surfaces are the two highest-leverage additions when your job volume can't support the velocity target alone. And keep every review you earn: the 3-star recovery playbook protects your rating while the count climbs.

The done-for-you version

This post is System 4 from the Leveraged Owner Starter Pack — the done-for-you version with the full 5-step setup guide, every script, the worksheets, and complete setup guides for all 8 systems. The Starter Pack includes the competitive gap worksheet with the velocity calculator.

Stats sourced as labeled: BrightLocal 2026 (review behavior figures). Conversion assumptions are directional — measure your own. The worked example is illustrative, not a customer result.