What a Polished Deal Presentation Doesn't Tell You

What management presents and what management is prepared to execute are not always the same thing. Press until you get the honest version of the conversation, not just the case for why the deal should work.


Management teams are good at building a compelling case for a deal. What they need to be pressed on is how they talk about uncertainty, tradeoffs, and execution risk once assumptions start getting challenged.

That is usually where it becomes clear whether management has thought through the consequences of execution, not just the economics of the deal.

The Difference Preparation Makes

Management teams that understand the operational demands of a transaction tend to speak clearly about what could go wrong, where integration will be difficult, and which assumptions carry the most risk. They understand where the organization is exposed and where leadership attention will be required after close.

Less prepared teams present a different picture. The discussion becomes overly certain, downside scenarios receive little attention, and integration complexity gets treated as something operational teams will simply work through later. A financial model may show the deal works under several scenarios, but that does not mean the organization has the management capacity, reporting structure, incentive alignment, or leadership bandwidth required to execute successfully after closing.

The preparation gap between these two types of presentations is usually visible within the first round of substantive questions.

When the Questions Get Hard

One of the more important signals in a deal discussion is whether management can acknowledge tradeoffs without becoming defensive. Can they explain why the risks are acceptable? Can they identify which assumptions are least predictable? Can they explain where execution could break down if integration takes longer, costs more, or creates disruption inside the existing business?

Management teams sometimes spend months refining valuation models while giving far less attention to channel conflict, customer retention risk, management succession, or who will actually lead integration once the deal closes. The presentation may still look polished even when the organization itself is not prepared for the execution demands behind it.

Directors learn to read the difference between a team that has stress-tested its own assumptions and one that has primarily built the case for why the deal should work."

Creating the Conditions for an Honest Conversation

Very little comes from discussions built entirely around why a deal should work. The more useful conversations happen when management speaks candidly about where the organization is exposed, which tradeoffs are being accepted, and what execution will realistically require after closing.

That candor is not a sign of weakness in a management team. It is a sign that they have done the work. A team that can identify the three assumptions most likely to be wrong, explain what happens if they are, and describe what the organization will need to manage through integration is far better prepared than one that can only defend the upside.

The role in a deal discussion is not simply to approve or reject a financial model. It is to create the conditions where that kind of honest conversation can happen, and to keep pressing until it does.

About the author

Andy Tomat

Andy Tomat

Founder

Andy Tomat is a board director and corporate development executive with more than three decades of experience guiding organizations through acquisitions, strategic growth decisions, and financial oversight across industrial technology, automation, robotics, AI, and nonprofit settings.