In most companies, expansion is among the rarest customer conversations — an annual renewal, a quarterly QBR, an occasional upsell email. It should be among the most common. Customers bump into the edges of what they're paying for constantly; each of those is an expansion moment, and treating expansion as a rare event means ignoring the steady stream of moments that occur between the scheduled ones.
The frequency mismatch. Expansion intent arises continuously and unpredictably — a cap hit on a Tuesday, a feature need on a Friday, a question that reveals a tier gap any time. Scheduling expansion into rare events guarantees you miss the moments that fall between them, which is most of them. The cadence of your expansion motion should match the cadence of expansion intent, and that cadence is "continuous," not "quarterly."
What "most common" looks like. It doesn't mean badgering customers constantly. It means being present to have the expansion conversation whenever the customer reaches a moment that warrants it — frequent because the moments are frequent, welcome because each one is timely and relevant. The volume comes from responsiveness to real moments, not from more outreach.
Why it's usually rare. Continuous presence across every account is unscaleable for human teams, so expansion defaults to the few scheduled touchpoints they can staff. A conversational layer present in the product changes the economics: the expansion conversation can happen every time a customer hits a relevant moment, making it as common as the moments themselves.
Frequently asked questions
How often should expansion conversations happen?
As often as customers hit expansion moments — caps, feature needs, tier-gap questions — which is continuously, not on a quarterly or annual schedule that misses most of them.
Why is expansion usually a rare conversation?
Because continuous presence across every account is unscaleable for human teams, so expansion defaults to the few scheduled touchpoints they can staff.