Customers can want the outcome without having capacity to absorb the change.

The customer wants to move.

The problem is real. The sponsor is engaged. Budget appears serious. Everyone agrees that the current state is no longer acceptable.

The opportunity looks ready.

Then delivery planning begins.

The data needed for the transition is incomplete. Subject-matter experts are committed to other priorities. Nobody has been assigned to make operating decisions. The security team has a six-week queue. Business units support the outcome but do not agree on the process. The people expected to adopt the change are already absorbing two other transformations.

The customer had demand.

They did not yet have readiness.

A customer can be ready to buy before they are ready to change.

This distinction matters in complex technology, outsourcing and transformation sales.

Demand tells us that the customer wants an outcome. Readiness tells us whether the organization can participate in creating it.

The two are related, but they are not the same.

Sellers naturally focus on demand. Is the problem important? Is there urgency? Is funding available? Does an executive care enough to act?

Those are essential questions.

But an ambitious solution still depends on customer capacity: people, decisions, data, governance, access, change leadership and time. When those conditions are missing, the contract does not remove the gap. It transfers the gap into delivery.

This is not an argument for blaming the buyer.

Organizations often need outside help precisely because their internal capacity is stretched. The problem may be urgent because teams are overloaded, processes are fragmented or critical knowledge sits with too few people.

Waiting for perfect readiness would mean never starting.

The seller’s responsibility is therefore not to demand that every condition already exists. It is to make the readiness gap visible and design around it.

Who will own decisions after signature? Which customer resources are genuinely available? What data and access must be prepared? Which dependencies sit outside the sponsor’s control? How much change is the organization already carrying? What happens when an approval or subject-matter expert is unavailable?

These are not delivery questions that can safely wait until kickoff.

They shape scope, sequencing, risk, price and the credibility of the promised outcome.

Sometimes the answer is a phased start.

Sometimes the engagement needs a mobilization period, stronger governance, dedicated customer roles or additional supplier support. Sometimes the first commercial conversation should be about building the conditions for transformation rather than pretending the organization is ready for full scale.

And sometimes the honest answer is that the initiative should pause.

That judgment must be used carefully. “Readiness” should not become a vague excuse to slow a motivated customer, sell unnecessary assessment work or avoid accountability for supplier delivery.

Readiness can be built while progress continues.

What matters is that both sides know what must become true, who owns it and how the plan changes if it does not happen.

A strong sales process does more than confirm that the customer wants the future state.

It tests whether the organization can travel the path—and helps create the conditions when it cannot.

If demand is strong but readiness is uncertain, I am always happy to compare notes.