Somewhere in a company right now, a customer has emailed their account manager asking about the next tier.
Nobody sold anything. Nobody made an ask. The revenue arrived on its own.
That event has two completely different causes, and from the outside they look the same.
The Two Versions
Version one: you were waiting. Waiting for the right moment. Waiting until the relationship felt solid enough for a commercial conversation. Waiting until the customer brought it up, because that felt cleaner than raising it yourself. And eventually one customer did, because they happened to hit a wall obvious enough to act on.
That's the failure I've written about. The customer got there on their own, in spite of you, and for every one who did there are a dozen who didn't and quietly went somewhere else.
Version two: they were told two quarters ago. Somebody named the next thing while they were nowhere near ready, said what would earn it, and left it alone. The customer has been carrying it since. They hit the milestone, recognized it, and reached out.
Same email. Same revenue. Opposite mechanisms.
One of them is a customer rescuing you from your own avoidance. The other is a customer completing a sequence you started. Only one of those happens again next month.
How to Tell Which One You're Running
The event is identical, so stop looking at the event.
Count them. A team running version one gets these occasionally, at no predictable rate, from the customers who were always going to figure it out. A team running version two gets them at roughly the rate customers reach milestones, which is a number you can forecast.
Read what they said. This is the fastest tell and it's in your inbox already. A version-two customer uses your language. They reference the thing by the name you gave it, and often the condition too: we've finally got the second region live, so I think we're at the point you mentioned. A version-one customer describes a problem and asks whether you have anything for it.
Check who else knew. In version two, the account manager can tell you this was coming and roughly when. In version one, the email was a surprise to everybody, and the pleasant kind of surprise is still a surprise.
Why This Distinction Earns Its Keep
Because version one is the most flattering data in your business, and it teaches exactly the wrong lesson.
A company that gets a handful of inbound expansions a year concludes that their customers come to them when they're ready, that the relationship is healthy, and that pushing would damage something that's working. Every one of those inbound emails confirms it.
What the emails can't show you is the denominator. You see the customers who arrived. You never see the ones who hit the same point, didn't connect it to you, and solved it elsewhere, because that failure is silent. Nobody complains. They just stop being available.
So version one produces confidence that scales with the size of the thing you're missing. The more customers you have, the more inbound you get, and the more certain you become that the system works.
What Version Two Actually Requires
Less than people expect, and it isn't a motion you bolt on.
You need something to name, which is the inventory question. You need to know when it becomes useful, which is the milestone question. And you need somebody to say it out loud early, while the customer is still short of it, and then decline to sell it.
That last part is five minutes on a call you were already having. Name it at the moment they can see the current thing is going to work, tell them they're not ready, say roughly how far off they are at their pace, and agree that's the conversation you'll have when they get there.
Then you wait, except the waiting is doing something now. They're carrying it. And when the milestone lands, they know what it means, because you told them months before it mattered.
The Part That Feels Strange
You build the whole apparatus in order to make an ask, and then you don't make it.
The first time it happens it reads as luck. The tenth time it happens, in the same month, at roughly the rate you predicted, it stops reading as luck and starts reading as the thing you built.
And the ask you were preparing for turns out to have been the least important part of 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.