Buy-and-build's missing owner

The systems get integrated. The finance function gets integrated. The back office, the CRM, the reporting lines, eventually the brands — all of it, methodically, over eighteen months.

And then everyone waits for the cross-sell to show up.

It mostly doesn't. Overestimating revenue synergies is the single most-cited reason acquirers give for deals that disappoint — and cross-selling sits right at the centre of it. The number usually gets filed under "integration is hard" or "cultural fit takes time."

Sometimes that's fair. But two very different failures hide under the same heading, and telling them apart is most of the job.

The first is a deal-thesis problem. Occasionally the two customer bases were never going to converge — one business sells to the CIO, the other to the CMO; one lands with procurement, the other with a line-of-business head. The personas sit on opposite sides of the customer's own organisation, and no combined pitch deck or cross-sell incentive can bridge that, because there is nothing to bridge. The important thing about this failure is that it's knowable before the cheque clears. As BCG puts it, a revenue-synergy case assuming 20% cross-sell penetration is meaningless until it's been tested against actual conversations with the customers who'd have to buy the cross-sold product. That's a diligence question. It belongs at the deal table, and when it's missed, no amount of integration work fixes it afterwards.

But that's the rarer case. Most underperforming buy-and-builds aren't structurally impossible. The synergy was genuinely there — a real combined buyer, a bridgeable adjacency — and it leaked away for a much more ordinary reason: building the single commercial argument that reaches that buyer was nobody's job.

Here's how it happens. The platform thesis — together we're worth more than the sum — is true in the data room. It stays true in the board deck. It just never becomes true in the market, because no one ever rebuilt the commercial argument to match the new shape of the company. Ask the people doing these deals and they'll give you the honest version: the hard part isn't buying the companies, it's working out how to stitch them into something larger than a holding structure. And that work — the commercial architecture across the portfolio — sits in a gap. It's too commercial for the deal team, too cross-brand for any single CEO, too strategic for the functions. So it falls to nobody. And "nobody" is a poor owner of the number the whole thesis depends on.

You can see the gap in three places once you know to look. Proposition: each brand keeps its own story, its own category, its own idea of who it's for — the group has no argument of its own, just a stack of arguments that were never designed to stand together. Offer architecture: the offers were priced and packaged for separate buyers, so bundling them doesn't create a platform offer, it creates a longer menu, and buyers notice. Go-to-market: partners can carry one product, not the portfolio, and the cross-sell motion assumes a coherence upstream that was never built.

None of this shows up as a line item. It shows up as a synergy that quietly underperforms, a multiple that doesn't expand the way the model said it would, and a leadership team that concludes the problem must be execution.

Usually it isn't execution in the ordinary sense. Because the firms that make the second and third and fourth acquisition actually compound do one thing differently, and it's visible early. Before the systems are even talking to each other, someone is already asking the commercial question: after this deal, who is the combined business for? What is the one argument that makes the parts worth more together than apart — and who does that argument now deliberately exclude? They treat it as a design task, with an owner and a deadline, not as something that will surface on its own once the integration checklist is done.

It doesn't take a bigger budget or a better platform. It takes a decision, made early, that the commercial argument is something you build on purpose — and then hold someone accountable for.

The capability compounds. The argument doesn't. Not unless someone owns it.