The architectural decision every specialty acquirer is making implicitly

The last twelve months have produced more than $35bn of M&A in specialty insurance. Zurich and Beazley agreed terms in March. Onex and AIG completed Convex in February.

Starr is closing on IQUW. Radian has bought Inigo. Different acquirers, different price points, different rationales. One pattern.

In every case a property and casualty (P&C) heritage acquirer has bought a specialty book. In every case the integration team will encounter the same architectural problem.

And in every case the generalist M&A advisors steering the integration will treat that problem as a Phase 3 technology workstream – by which point the architectural decision has already been taken.

The decision is being made implicitly, by the sequence of the integration itself. That is the failure mode worth naming.

The specialty/P&C inversion

P&C and specialty insurance are not the same product in different wrappers. A P&C policy is a standardised product sold at volume. A specialty risk is individually negotiated, structured across multiple underwriters, and placed through a broker workflow that has no equivalent in P&C at all.

The platforms that govern these two businesses reflect that difference. Guidewire, Duck Creek, and their peers were built for P&C. They handle P&C risk correctly. They handle specialty risk by approximation: custom fields, workaround configurations, functionality bolted on rather than designed in.

When a P&C carrier acquires a specialty book and attempts to run the acquired business on its existing platform, the mismatch surfaces immediately. The underwriting workflow does not map.

The data model does not capture the fields that Lloyd’s CDR requires. The placement process – broker slip, line structure, syndicate participation – has no equivalent in the P&C architecture.

This is the inversion problem. P&C architecture inverts the specialty workflow rather than accommodating it. The integration team can either rebuild the specialty logic on top of an unsuitable platform, or rebuild the platform around the specialty logic.

The first costs less in year one and substantially more across the deal’s commercial life. The second is the harder conversation to have at month three of an integration.

Why integration playbooks miss it

The standard integration playbook for a specialty acquisition focuses on legal entity consolidation, reinsurance programme harmonisation, and financial reporting alignment. These are legitimate priorities.

They are also the easy ones – the workstreams that produce visible day one progress and that generalist M&A advisors can govern with confidence.

Technology integration is treated as a later-stage workstream. Rationalise platforms, migrate data, retire legacy systems.

The sequence seems logical. The problem is that the architectural decision, which platform governs the integrated business, and how specialty risk logic is accommodated within it, is being made implicitly by the sequence itself.

By the time the technology workstream begins in earnest, three things have already happened.

The organisational structure has been set around an assumption about which platform survives.

The specialty underwriting team has been told, formally or otherwise, which system they will eventually be working in.

And the integration governance has been built around milestones that depend on the platform decision being final.

Reversing the architecture at that point is a multi-year remediation project. The firms that avoid it make the architectural decision first – before the integration governance is set, before the platform rationalisation roadmap is drafted, and before the specialty team is told what tools they will be using.

The CDR complication

Blueprint Two’s formal sunset on 19 March added a specific complication to every active integration in the Lloyd’s specialty market. The central re-platforming has slipped to 2028.

The market engagement team has been disbanded. 86% of managing agents are proceeding with their own CDR-compatible architecture without a central delivery mandate.

For a P&C acquirer integrating a Lloyd’s specialty book, this means the platform decision now has to accommodate CDR architecture independently.

The acquired syndicate may be partway through its own CDR programme. The acquiring P&C platform almost certainly does not capture data at source in the way CDR requires.

Forcing the specialty workflow onto a P&C platform does not just inherit the inversion problem – it inherits a regulatory readiness gap that has to be remediated before the integrated business can place risk through CDR-compliant channels.

That is a problem the integration sponsor needs to know exists in month one, not month eighteen.

What to ask in the first 90 days

The architectural decision cannot be deferred to the technology workstream because the technology workstream cannot make it.

By the time the CIO’s team is engaged, the decision has been pre-made by every other workstream.

The integration sponsor – the group COO, the integration director, the corp dev lead – is the only person in the organisation positioned to ask the right question early enough.

Three questions, in the first 90 days:

• Which platform will govern the combined business, and was that decision made on the basis of specialty workflow fit or P&C platform incumbency? If the second, the architecture is wrong and the cost will surface in year two.
• What is the CDR readiness profile of the acquired book, and does the chosen platform support capture-at-source data architecture? If not, the integration has inherited a regulatory remediation programme that nobody has scoped.
• Who in the integration team has both Lloyd’s specialty domain depth and platform architecture capability? If the answer is nobody, the architectural decision is being made by people who do not know what they do not know.

The firms that ask these questions early have a different integration trajectory from the firms that do not. The cost difference is measured in years and in the value of the specialty book that survives the integration intact.

What good looks like

A well-architected specialty integration treats the platform decision as a Day 1 problem, not a Day 360 one.

It separates the workstreams that produce visible day one progress – legal entity, reinsurance, reporting – from the workstream that determines whether the deal’s commercial logic is preserved through year three.

The platform decision sits in the second category, and the integration sponsor governs it directly rather than delegating it to a technology workstream that will be set up to inherit the consequences of decisions it did not make.

The acquirers that get this right will compound the value of their specialty acquisitions.

The acquirers that do not will spend years explaining why the integrated book is underperforming the standalone forecast.

The decision is being made now, in integration governance meetings happening across the market this quarter. It is worth making it deliberately.

Grant Bodie is principal consultant for insurance transformation at Cavehill Consulting Group, advising Lloyd’s syndicates, MGAs, and P&C acquirers on transformation strategy, CDR readiness, and M&A integration design.