Most B2B software companies treat review requests like a seasonal campaign. They batch them. They send them when the marketing calendar opens up. Then they wait months for anything to happen. The problem is obvious once you see it: customers are most willing to write a review when they've just experienced value, not when it's convenient for your ops team.
The real lever is timing. When you ask for a software review matters more than how many times you ask or how well you craft the email. The best time to request G2, Capterra, and Trustpilot reviews depends on where your customer is in their journey and which platform you're targeting. Get the moment right, and conversion climbs. Get it wrong, and you're just adding noise to an already crowded inbox.
The post-onboarding window is your strongest conversion point
After a customer completes onboarding, something shifts. They've moved from setup mode to actual use. They've seen the product work. They understand the value or they've hit friction. Either way, they're reflecting on whether they made the right choice. This emotional clarity is a gift.
Timing a review request here sees significantly higher conversion than batch campaigns because the experience is fresh and the customer has already invested mental energy in evaluating the product. They don't need to be convinced to think about your software; they're already thinking about it.
The window is narrow though. Aim for the day after onboarding completes or no later than a week out. If you wait a month, you've lost the momentum. If you ask during onboarding, you're asking someone who is still frustrated with setup. The post-onboarding moment is when customers have moved from pain to productivity. That's when they're most likely to write something genuine.
Use NPS and product milestones to trigger targeted asks
Not every customer is equally likely to write a review. An NPS score tells you who is. Promoters (score 9-10) are naturally inclined to advocate. Passives (7-8) need a nudge but respond to the right timing. Detractors shouldn't be asked for public reviews yet, at least not on G2 or Capterra where negative reviews are visible.
When you combine NPS data with customer milestones, you get precision. A promoter who just completed a major project milestone, added five new team members, or hit an expansion threshold is primed to write. They have a concrete story. They've seen the product scale. The conversion difference between asking a random promoter and asking one who just hit a milestone is real.
Similarly, watch for product wins. If a customer used your platform to hit a specific KPI, solve a known pain point, or replace an older tool, that's a signal. Ask them within days of that win. They can articulate the value. They're not guessing.
Renewal time and expansion moments are second-order triggers
Onboarding completion is the first-order trigger, but renewal and expansion are reliable second-order moments. When a customer renews, they've made an implicit vote of confidence. When they expand their seats or add modules, they've proven the product works for them.
These moments differ by platform. For Trustpilot, automated asks immediately after purchase or renewal work well because the experience is fresh and the platform's algorithm weights recency heavily. Consistent monthly or quarterly velocity matters more than sporadic campaigns. For G2, a single ask timed with a renewal or product update significantly improves freshness scores, which G2's algorithm weights more heavily than total review count. A product with 60 reviews that are fresh outranks one with 100 old reviews.
Capterra sees different behavior. 77% of B2B software buyers use it to evaluate before contacting sales, which means timing is critical. A review from a customer right after they've expanded usage reaches evaluators when they're actively deciding. The syndication also matters: when a review hits Capterra, it automatically syndicates to GetApp and Software Advice simultaneously. One ask reaches three platforms.
Avoid batch requests and build a review rhythm instead
The impulse to batch review requests is understandable. It's efficient. One email, one campaign, done. But it underperforms because it ignores the customer's state. You're asking when it's convenient for you, not when they're ready.
A better approach is to build review requests into your operational milestones. When a customer completes onboarding, trigger an ask. When they renew, trigger another. When their NPS check-in shows a score above 8, trigger a platform-specific ask. This feels like part of their experience, not a random favor.
Over time, this rhythm generates a steadier stream of reviews. You might get four reviews a month instead of twenty reviews in March followed by nothing until November. Most software ranking algorithms reward consistency more than volume. A review pipeline that delivers fresh reviews every week outperforms a bulk campaign that floods the zone once a quarter.