How Often Should You Do Account Reviews for Expansion?
Account reviews for expansion serve a different purpose from account reviews for retention. Retention reviews ask: is this customer satisfied enough to renew? Expansion reviews ask: is there an opportunity to deepen or broaden this relationship? The question, the information needed, and the timing are all different.
The Right Frequency
Quarterly reviews for top accounts is the right cadence for most companies at the $5M-$20M stage. Here is the reasoning:
Too frequent (monthly or more): Expansion opportunities do not typically develop on a monthly cycle. Business changes, the signals that indicate expansion readiness, happen on a quarterly or slower cadence for most customers. Monthly reviews produce the overhead of the review without proportional new signal.
Too infrequent (annually or semi-annually): Expansion signals have a shelf life. A customer who experienced a significant success outcome in March may not be in the same state of mind when you check in November. A business that was in a growth phase when you last reviewed may have shifted priorities. Annual reviews miss too many windows.
Quarterly is the cadence that catches meaningful changes in the customer's situation while not creating unsustainable overhead.
Which Accounts to Review
Not every account deserves quarterly expansion reviews. Focus on:
Top 20% by current revenue value. These are the accounts where expansion would have the most significant impact on NRR and total revenue. If your average account is $50K per year, the top 20% are likely $100K or above. The expansion potential is proportionally higher.
Accounts with recent success signals. Even if an account is not in the top 20%, a significant success event, a major result delivered, a positive unsolicited testimonial, a referral made, warrants an out-of-cycle expansion review.
Accounts with business signals. Hiring, funding, new markets — these events are expansion triggers that should prompt a review regardless of when the account was last reviewed.
The Account Review Structure
A well-structured expansion review covers four dimensions:
Health (5 minutes) Is the customer getting value from the current engagement? Are there any satisfaction or retention risks that need to be addressed before expansion is appropriate? An account that is at risk of churning is not an expansion candidate. It is a retention priority.
Context (5 minutes) What has changed in the customer's business in the last 90 days? New hires, new initiatives, leadership changes, performance changes. This is where you identify business signals that indicate new needs.
Opportunity (5 minutes) Which expansion signals are present? Review the signal library and apply it to what you know about this account. Be specific: not "there might be an opportunity" but "they hired three new sales reps last month and the outbound process we built for them is now being run by people who were not involved when we built it, that is a training and SOP opportunity."
Next action (5 minutes) Given the above, what is the single best action to take with this account in the next 30 days? Who owns it? The review is only complete when a specific action is assigned.
Total review time with a prepared template: 15-20 minutes per account.
Running the Reviews
The quarterly account review should be a scheduled, structured process, not an ad-hoc exercise. Options for running it:
As part of the regular cadence: Add an account review segment to the monthly revenue review for the top accounts, or run a dedicated quarterly account review session with the customer success and sales teams.
As a pre-QBR preparation step: Before any scheduled quarterly business review with a customer, run an internal expansion review first. The internal review identifies expansion opportunities that can be naturally surfaced in the customer-facing QBR.
As a solo exercise for the founder or account owner: For companies where expansion conversations happen primarily through the founder or a senior account owner, a quarterly solo review using the template is sufficient.