I've written before about thoughts-and-prayers expansion: the company that has an expansion number and no mechanism, hoping the revenue shows up because everyone is working hard.
That's real. I've been describing it one step too late.
When people push back on orchestration, the question is always some version of what if the process breaks down after the sale. What if the customer stalls. What if the plan stops.
Buried in that question is an assumption worth dragging into the light: that customers move through their own progress on their own, and your job starts when they arrive.
They don't, and it doesn't.
Two Places to Put Your Hope
The version I've written about is hoping at the end. You know the customer is somewhere useful, and you hope somebody has the conversation.
The earlier one is hoping they get there at all.
Nobody planned the movement from where the customer started to the point where the next thing becomes obviously useful. Nobody named the steps. Nobody decided who was responsible for any of it, or what would happen if a customer stopped halfway. The whole passage is assumed.
You can't orchestrate the arrival if nothing in your company is producing arrivals.
So when the expansion number misses, the finding gets filed as expansion not working here. What actually happened is that the customers never reached the place where the offer made sense, and nothing was watching the part where they didn't.
Why This Is the More Expensive Version
A missing expansion conversation costs you one sale. A missing passage costs you the customer.
Because a customer who never gets from A to B isn't just an expansion miss. They're a renewal risk, a support cost, and a reference you won't get. The expansion was the visible loss. It was the last thing to fail, not the first.
And it explains a pattern that otherwise looks strange: companies with genuinely good products and honest retention numbers that can't expand anybody. Nothing is broken. The customers are fine. They're just parked, at a point that no longer surprises anyone because it's where everybody parks.
The Move Is Not to Wait Better
The instinct is to instrument the arrival. Watch for the milestone, catch it when it fires. That's necessary and it's not sufficient, because it still treats the customer's progress as weather.
Progress is something you influence. You can't make another person act, and you can absolutely change the conditions that make acting more or less likely, which is the entire difference between watching a customer stall and doing something about it.
Customers stall for ordinary reasons. The work is boring, or it's ambiguous, or it requires a decision they don't want to make, or the person who cared has other priorities this quarter. None of that resolves itself because you're monitoring it.
So the question underneath expansion turns out to be a much older one: how do you get a person to do a thing they don't want to do, can't easily do, or won't get to on their own, when you need them to do it and they don't work for you.
That's not a revenue question. It's a behavior question, and there's a body of work on it that most Customer Success teams have never been pointed at.
What Changes When You Accept It
The expansion motion stops being a layer you bolt on at the end and starts being the same work you're already doing, aimed on purpose.
If you're good at delivering what you sell, you're already moving customers through progress. You just haven't looked at it that way, so nobody wrote down where the movement happens, what it produces, or which of those points has something worth selling attached to it.
And the answer to "what if the process breaks down after the sale" turns out to be that it already did, at a point earlier than anyone was looking, and the expansion number is just where it finally became visible.
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.