The composition of European private-equity exits has shifted, and the shift changes what an exit-ready platform has to withstand. A growing majority of mid-market exits now clear as trade sales — sold to a strategic acquirer already operating in the sector — rather than as secondary buyouts or IPOs. At the same time, hold periods have lengthened; assets are held longer, and platforms accumulate more technical history before they are put back on the market. Those two facts compound. You are holding the asset longer, and you are selling it to a more technically literate buyer than the one who sold it to you.
That matters because a financial buyer and a strategic buyer run fundamentally different diligence. A financial buyer is underwriting a thesis about a market and a management team. Technical due diligence, when it happens at all, is often a light-touch, checklist exercise run by a generalist advisor: does it run, is the stack recognisable, are there obvious red flags. A strategic acquirer is underwriting integration. Their engineers will have to own this codebase on Monday morning, merge it with their own, and answer for it. They read the platform the way a mechanic reads a used engine — not "does it start" but "what will it cost me to run for the next five years."
What a financial buyer's review lets through
Platform risk does not announce itself. It sits quietly inside a business that is growing revenue and hitting its numbers, invisible to anyone reading the P&L. The categories that survive a light-touch review and then surface under an acquirer's engineers are consistent:
- Key-person dependency. The architecture lives in one or two people's heads. There is no written system of record, and the founding engineer is the single point of failure. An acquirer models what happens when that person leaves eighteen months post-close — and prices the risk accordingly.
- Undocumented architecture. The system works, but no one can explain why it is shaped the way it is. Decisions are archaeology. That is fine until someone who did not build it has to extend it.
- Brittle deployment. Releases are manual, semi-ritualised, and understood by one team. An acquirer who deploys hundreds of times a week sees a bottleneck they will have to rebuild.
- Security debt. Dependencies years out of date, secrets in the repository, no meaningful access discipline. A strategic buyer with a real security function treats these as liabilities they are inheriting, not curiosities.
- Scalability ceilings. The platform performs at today's load and has no credible answer for ten times it — the exact question a buyer acquiring for growth will ask first.
Why the acquirer's engineers change the outcome
The decisive difference is who is doing the reading. A financial buyer's advisor is incentivised to complete a process. An acquirer's engineering team is incentivised to protect the people who will inherit the work — themselves. They ask sharper questions, they ask them of the code rather than the pitch, and crucially they have standing to translate what they find directly into price. A finding that a generalist would note as a footnote becomes, in an integration team's hands, a line item in the deductions: months of remediation, headcount to absorb it, risk that justifies a lower multiple or a larger escrow.
The platform risk that survives a financial buyer's review will not survive a trade buyer's technical team.
This is not a reason to fear the trade sale — it is the most valuable exit route on the table, and it should be. It is a reason to prepare for the buyer you will actually face rather than the one who sold you the asset.
The hold period is the window
None of this is fixed in the ninety days before a sale. Key-person dependency is unwound by documenting architecture and transferring capability, which takes real calendar time. Deployment is de-risked by rebuilding the pipeline and letting it prove itself across release cycles. Security debt is retired in the order that a competent reviewer will test it. These are hold-period problems with hold-period timelines — and the longer hold periods that now define the market are, read correctly, the runway to solve them.
The work that matters is not "modernise everything." It is to sequence remediation by what a strategic acquirer's engineers will actually test, and to close those gaps in the years you hold the asset rather than discovering them in the weeks you are trying to sell it. Prioritise the findings that move the diligence outcome; leave the cosmetic ones. Done in the hold period, that work is an investment in the exit multiple. Discovered in the data room, the same findings are a discount you negotiate against — from the weaker side of the table.