Every rating-recovery plan starts with the same question: how many positive reviews does the target require? The answer is one line of algebra, and it works on any platform that displays an average.
The formula
needed = ceil( count × (target − current) ÷ (5 − target) )
…where count is your existing review count, current your average, and target the rating you want. Assumes added reviews are 5-star.
…where count is your existing review count, current your average, and target the rating you want. Assumes added reviews are 5-star.
Worked examples
- Google, local business: 120 reviews at 3.8, target 4.3 → 120 × 0.5 ÷ 0.7 ≈ 86 five-star reviews.
- G2, SaaS product: 40 reviews at 4.0, target 4.5 → 40 × 0.5 ÷ 0.5 = 40 reviews — doubling the profile. B2B volumes are small; single reviews move real weight.
- Google Play app: 800 ratings at 3.6, target 4.0 → 800 × 0.4 ÷ 1.0 = 320 ratings — app stores are a volume game, which is why app packages run cheaper per unit.
Platform adjustments
- Trustpilot: recency weighting means the real requirement is usually lower — see the TrustScore formula explainer.
- Google: displays one decimal, so you only need to cross the rounding boundary (3.85 displays as 3.9).
- Yelp: rounds to half-stars and filters aggressively — budget headroom and pace conservatively.
The step everyone skips: pacing
The formula outputs a volume, not a schedule. Delivering 86 reviews in a week onto a 120-review profile is how campaigns get flagged; the same volume over six weeks reads as growth. Convert your number into daily and weekly velocity with the Review Velocity Planner before you order anything.
Skip the spreadsheet
The free TrustScore Calculator runs this math for you — then the pricing page matches the output to a package.
Open the calculator →