Here's the problem with most expansion motions.
They're not motions. They're reactions.
A customer asks for more seats. You sell them more seats. A customer mentions they're thinking about the enterprise tier. You schedule a call. A customer's usage spikes and their CSM notices. You have the conversation.
Reactive expansion works. It's just slow, inconsistent, and highly dependent on customers knowing what to ask for and when to ask for it. Most customers don't. They're heads-down running their own business. They're not thinking about whether now is a good time to expand their contract. That's your job to think about.
Systematic expansion looks different. It's a process you run every month, not a series of conversations you have when the opportunity presents itself.
Here's how it works.
Step one: expansion inventory. Before you can sell expansion, you need to know everything you have to sell — not just your pricing tiers, but every service, add-on, adjacent product, and capacity option available to your customers. Most companies have more inventory than they realize. Feature unlocks that exist in the product but aren't in the base tier. Services they've been delivering for free. Adjacent products they've never positioned as expansion opportunities. This step is about getting everything on the table.
Step two: mapping progress milestones. A progress milestone is a moment in the customer journey where they've achieved something meaningful — a specific behavior or outcome that signals they've gotten real value and are ready for the next level. These are not time-based. Month six is not a milestone. "They've onboarded their entire team and are running three active workflows" is a milestone.
Step three: mapping expansion opportunities to milestones. Which expansion offering fits which milestone? Your API access add-on maps to the moment they've built their first integration and started thinking about scale. Your training package maps to the moment they've got buy-in internally but the team isn't fully adopted yet. Your managed service maps to the moment they tell you they love the product but don't have the bandwidth to run it themselves.
Step four: building the value prop and social proof for each mapped opportunity. Not a generic pitch for your enterprise tier — a specific case for why this customer, at this milestone, should take this next step. Who else has done it and what happened for them.
Step five: identifying who's hitting milestones this month. This is where the system becomes operational. Every month you review your customer base and ask: who's at or near a milestone right now? This is the list you work from. Not the full book — just the customers who are actually ready.
Step six: orchestrating the conversation. Not a sales call. A milestone celebration that opens naturally into what's next. You acknowledge what they've achieved, you connect it to what becomes possible, and you make the offer. The customer can say yes, no, or not yet. All three are fine. Not yet gives you a date to come back.
Then you run it again next month.
The compounding effect is in the repetition. Customers who weren't ready in March might be ready in April. The system catches them.
Lincoln Murphy formally named and popularized Customer Success starting in 2010 and has spent 15 years connecting it to expansion revenue and commercial outcomes. Read The Premise.