Every time I lay out expansion orchestration, somebody asks a version of the same question. What if the customer's path changes after the sale? You mapped A to B, and now C is the obvious next thing. What happens to your plan?
It's a fair question, and the first thing wrong with it is the word "if."
Customers' paths change. All of them, eventually. The business moves, the champion leaves, a market shifts, a new exec arrives with different priorities. Treating that as the exception is what makes it feel like a problem, because you end up building for the case that never happens and improvising the one that always does.
So the answer isn't a patch for a rare event. It's that the question contains two completely different situations wearing one sentence, and they have opposite responses.
We Already Do This For Sales
Start with the part nobody notices.
Sales deals go differently than expected constantly. The champion leaves. Procurement appears out of nowhere. The budget moves a quarter. Nobody treats that as an argument against having a sales process. They build for it. Territory design, segment playbooks, deal desk, stage criteria, different motions for different deal types.
The variation is real, and the response was to name the variants and build for each one. Not to conclude the whole thing is unmodelable. It's the same asymmetry I've written about in the process map: the expansion version of that work runs on better material at every step, because these are customers you already have rather than strangers you're guessing about.
Two Situations, One Sentence
"The customer's path changed" hides two things.
One: they're not succeeding. The path changed because what they bought isn't working. That's not an expansion question at all. It's a delivery question, and expansion isn't on the table until it's answered. A customer who hasn't gotten what they already paid for isn't a candidate for anything else. Fix that first, and nothing else on this page applies to that account.
Two: they're succeeding, on a different route than you expected. They're getting value. Their business moved. B stopped being the obvious next thing and C started being it.
Only the second one is the question people think they're asking, and it has a different answer than the first.
Name the Routes
Here's the answer, and it's less exotic than the question implies.
There are only so many ways your customers actually go.
Not infinitely many. The routes that matter recur, because customers cluster. You have the customers. You have watched them for years. If you sat down and wrote out where accounts actually end up, you would not fill a page, and the same four or five shapes would account for most of the base.
So write them down. Each route gets its own progress milestones, and each milestone gets the expansion opportunity that becomes useful when a customer arrives at it.
Now C isn't a surprise. C is a route you already mapped, with a milestone you already named and an offer already attached to it.
A customer's path changing is a when. Being surprised by it is an if, and the if is the only part you control.
The Number Moves, And That's the Argument For Doing It
The honest objection to all this is that latent revenue depends on which route a customer takes, so the number is softer than it looks.
True. Route A might be worth $40,000 across a lifetime and route C might be worth $70,000, and until a customer commits you're holding a range rather than a figure.
That's not a reason to skip the work. It's the strongest reason to do it.
Right now, without the map, you don't know which route anybody is on. You don't know what any route is worth. You don't know which one you'd rather they took, or what would move a customer from the cheaper one to the better one. Every one of those becomes a question you can answer once the routes have names, and every one of them stays unanswerable while the objection stands.
Uncertainty about which path a customer takes is an argument for mapping the paths. It has never been an argument for having no map.
The Map Isn't a Prediction
The last piece is why the original question doesn't land, and it's worth saying plainly because it's the thing that dissolves the objection instead of answering it.
A route map doesn't claim to know which route a customer will take.
I've made this argument about the other engine already: a revenue forecast that gets revised three times before it resolves isn't a prediction, it's a plan being defended. The same applies here, with the difference that the map never pretended otherwise. It's an enumeration of the ways this can go and what each one is worth.
So "what if they go a different way" is answering a claim nobody made. Going a different way is the thing the map is for.
What This Costs You To Try
Write down where your customers actually end up. Four or five routes, not forty. You are not predicting anything. You're writing down what has already happened, repeatedly, to people you already have.
For each one, name the progress milestones along it, and the thing that becomes useful at each milestone.
Then look at your accounts and put each one on a route.
That last step is the one that pays immediately, and it usually pays badly at first, because the common finding is that nobody can say which route half the base is on. Which was true yesterday too. The difference is that today you can see it.
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.