The Team Named the Risk and Moved Forward Anyway
Integration risk isn't always missed in diligence. Sometimes it's named clearly and still loses to enthusiasm for the deal. The fix: require a named objection to get a specific, resolved answer before a recommendation goes forward.
Somewhere in almost every diligence process, someone on the team says the thing everyone else is thinking. The target sells through a completely different channel from the acquirer. The customer base doesn't match. The two go-to-market models have nothing in common. It gets said out loud, in the room, on the record.
Then the deal moves forward anyway.
This is a different pattern from the one boards usually talk about, where a known issue gets waved off with "we'll deal with that after close" and never actually gets examined. Here, the issue was examined. It was discussed, named clearly, and weighed by the people responsible for weighing it. It lost anyway, before the deal was even structured. Diligence did its job. The organization didn't act on what diligence found.
A team that has spent months searching for a deal is tired of searching, and a strong market position or a differentiated product is enough to call the search over.
In one deal I advised on, a management team was weighing an acquisition of a small, well-regarded robotics company. The product was distinct, already selling in volume, and held a leading share in its niche. After months of chasing targets that hadn't worked out, the team wanted this one to work.
The objection came from inside the room. Someone on the team pointed out that the target sold almost entirely through distributors, to a small business customer base. The acquirer sold directly, to a different kind of buyer entirely, and had no infrastructure in place for the target's go-to-market model. The point was made plainly: we don't sell anything the way they sell everything.
That was accurate. It also wasn't new information that surfaced later. It was on the table while diligence was still open, stated by someone whose job was to raise exactly that kind of concern. It got weighed against the team's desire to make this deal work, and the desire won.
The objection, raised inside the process by someone with standing to raise it, lost to momentum. It didn't show up in a diligence report as a gap. It showed up as a sentence someone said in a meeting, that everyone nodded at, and that nobody followed up on.
The fix isn't asking diligence teams to be more thorough. Thoroughness isn't what failed here. What's missing is a mechanism that treats a named objection as a required line item with an action plan and KPIs rather than a comment that gets absorbed into the recommendation anyway.
If the go-to-market models don't align, the team needs to specify what must change, who owns the change, and what it will cost before anyone puts a recommendation in front of the board. A concern without an assigned owner and a resolution isn't resolved.
In an era where pristine, perfectly aligned deals are hard to come by, management teams and boards need to put the work into naming the risks, addressing them with an action plan, and commit to follow up after the deal closes.
The next objection like this one gets resolved when someone assigns it an owner before the meeting ends.
