Where The Capability Cliff Opens

Earlier in this series I introduced the Capability Cliff: the distance between what the deal thesis assumes and what the integration team can deliver.

In this post I want to show you where it opens. Because it is not where most people look.

It Does Not Open at Close

The instinct is to think execution risk starts at Day One. That is when the integration team shows up, the workstreams launch, and the clock starts running.

I've watched enough deals to know the cliff opens much earlier, usually in a spreadsheet, in a cell nobody owns.

The model assumes a 90-day systems migration. Nobody asked IT whether they have a 90-day team. The model assumes 85 percent retention of the sales force. Nobody asked what the sales force has been told. The model assumes leadership will be aligned on the operating model by close. Nobody scheduled the meeting where that alignment would happen.

Every one of those is a capability assumption dressed up as a financial input. The cliff opens the day the assumption goes into the model without anyone checking whether the organization can honor it.

The Assumptions Nobody Owns

The pattern I see is consistent. Corporate Development builds the thesis. Finance builds the model. Both are working from what the deal needs to be true. Neither is accountable for whether the operating organization can make it true.

By the time HR, IT, and the integration lead see the numbers, they are already in the board deck. Pushing back on a number that has been approved feels like pushing back on the deal.

So nobody does. I've sat in those meetings, watching an HR lead who knows the retention number is wrong say nothing, because the deck is already in front of the board. The assumptions ride through to close, and the cliff is waiting on the other side.

What Winners Do Differently

The organizations with a real execution edge do something simple and uncomfortable: they assign an owner to every capability assumption in the model before signing.

Not a workstream lead. An owner. Someone who has looked at the assumption, looked at their actual team, their actual calendar, their actual dependencies, and said either "yes, we can deliver that" or "no, and here is what it would take."

That conversation changes deals. Sometimes it changes the price. Sometimes it changes the timeline. Sometimes it just changes the plan so that the integration team is not set up to fail on the first Monday.

And sometimes it kills the deal, which is the right answer more often than deal teams want to hear.

Where the Check Belongs

The place to run that check is diligence, and it is the part of diligence almost nobody does. The next post is about that.

The Bigger Picture

The Value Gap does not appear at month six. It is baked in at signing, in every assumption that nobody tested against reality. Integration Debt is what you pay later for the capability check you skipped earlier.

The execution edge starts with refusing to skip it.

Come Test Your Own Assumptions

At the People Synergy Summit, the Day 2 hackathon puts you in front of real deal scenarios with peers and asks the question this post is about: can your organization deliver what the model says?

Details and registration at https://peoplesynergysummit.com.