There's a question hiding inside every orchestration conversation that almost nobody answers explicitly: when do you name the next thing.
The common answer is after the win. Get a result, show the result, then talk about what's next. It feels responsible. Earn the right, then ask.
It's late, and it's late in a way that costs you the best moment you had.
Two Different Moments
Value arrives in two forms, and they don't arrive at the same time.
Value realized is when something happened. A result exists, you can point at it, the customer can count it.
Value potential is earlier. Nothing has been delivered yet, and the customer can now see concretely that it's going to work. The system is configured, their data is in it, the path from here to the result is visible and believable. Not a promise from your marketing. Something they worked out for themselves.
That second moment is real, it's observable, and it is where you should be orchestrating.
Why Earlier Is Better
Three reasons, and the third is the one that matters.
They're paying attention. The moment a customer sees it's going to work is the most engaged they will be for months. After the result arrives they're busy operationalising it and their attention moves on. You're spending a peak or you're missing one.
Nothing has to be sold. Naming the next thing before the current thing has paid off can't read as extraction, because there's nothing to extract yet. You're describing a road, not asking for money. That's the cheapest version of the conversation you will ever get.
And the wait becomes the point. This is the part people miss. You name the next thing and then tell them they're not ready for it, and say why, and say roughly how far off it is at their current pace. That's introduce, deny, agree, and the denial is what makes the whole thing credible. It also converts waiting from dead time into a stretch of the relationship where the customer is heading somewhere specific that both of you named.
Orchestrate at potential. Transact at realization. They're different moments and most companies collapse them into one, which is why the expansion conversation shows up cold.
What This Looks Like
The customer finishes setup. Their data is loaded, the thing runs, the first outputs look right. No business result yet.
That's the moment. Not a QBR three months later.
What gets said is short. Here's what happens next for companies at your stage. Here's the thing that becomes useful when you get there. You're not ready for it and I don't want you buying it yet, because it does nothing until you're running at volume. Based on where you are, that's probably a couple of quarters. When it happens, that's the conversation we'll have. Fair?
Nobody says no to that. And more importantly, nobody forgets it.
What It Requires
Two things, and one of them is usually missing.
You have to know when potential lands. That's a point in your delivery process, and most companies can find it in an afternoon by asking which moment customers stop asking whether this was a good idea. It's earlier than people guess, and it's rarely the same as the completion of onboarding.
You have to have something to name. This is the one that stops people. Orchestration with nothing at the end of it is a conversation about the weather. If there's no next thing, that's not a timing problem, it's an inventory problem, and it gets solved first.
The Failure This Prevents
The expansion conversation that arrives out of nowhere at renewal, and lands as a vendor looking for more money at exactly the moment the customer is evaluating whether to keep paying the current amount.
That conversation isn't badly executed. It's late by about a year, and it was late from the moment somebody decided to wait for proof before mentioning what came after it.
The proof was never for them. It was for you.
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.