← All Posts

Ready Is Not Prepared

There's a customer who hits every milestone you'd want. The need is real, the next thing genuinely makes sense, and if you put it in front of them they'd agree it's time.

They say no anyway.

Then two months later they buy it.

Nothing changed about their readiness in those two months. What changed is that they had time to get prepared, and readiness and preparedness are different things that get treated as one.

What each one means

Ready means the need is real. They arrived somewhere, the thing you held back has become relevant, and the case for it makes sense to them on the merits. This is what readiness milestones are for. Observable moments, things that either happened or didn't, that tell you the next thing is now on the table.

Prepared means they can act on it this quarter. Budget exists or can be moved, somebody internally has heard about it before you brought it up, and the people who'd have to sign off aren't meeting the idea for the first time in the meeting where they approve it.

A customer can be entirely ready and completely unprepared. That customer says no, and the no has nothing to do with whether you read the signal correctly.

The number that gives it away

In my experience an account you've orchestrated takes the expansion north of 80% of the time. One you haven't, where the readiness is just as real and the offer is identical, runs around 40%.

Same readiness. Same offer. Half the yes.

If that gap were about readiness, the 40% would be gone. They'd have been wrong-timed, the moment would pass, and you'd move on.

That's not what happens. Most of that cohort comes back the following quarter and takes it anyway. They were ready the whole time. They found out too late to plan for it.

What orchestration actually is

Orchestration sounds like sequencing. Better timing, sharper triggers, catching the moment.

It isn't. Timing is the part everybody already tries to do.

Orchestration is telling somebody what's coming far enough ahead that when the moment arrives, the budget arrived with it. The held-back item was named at the initial sale. The milestone that earns it was named. So when they hit that milestone, the conversation isn't news. It's the thing they were told to expect, and they've had a quarter to make room for it.

That's what strategic unbundling buys you that nobody counts. Not just something left to sell. Something they're waiting for.

Where this shows up in the forecast

An expansion forecast built on readiness alone will be wrong by roughly half, and it'll be wrong in a way that looks like the method failed.

Which accounts hit which milestone this quarter is the easy part. The take rate is where orchestration shows up, and it's the difference between a forecast you can defend and one that misses by 40 points while every underlying signal was correct.

Everybody waits for the readiness signal. Almost nobody sets the expectation that makes the signal actionable.


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.

Access the 5x LTV Case Study.

See how one CRM SaaS drove 5x LTV in 90 days. Full framework, milestone breakdown, and cohort analysis.

← Previous
Your Expansion Ceiling Was Set at Pricing