Skip to content
Back to cases

Case · Northwynn Holdings

Pilot → Platform · 8 mo

Thirteen subsidiaries, six weeks.

A specialty insurer onboarded thirteen newly-acquired subsidiaries onto a single governance plane in six weeks. The auditors did not blink.

Headline metric

13.

Sector

Specialty Insurance

Region

New York, US

Engagement

Pilot → Platform · 8 mo

Org size

1,800 staff across 13 entities

Source

We onboarded thirteen subsidiaries onto a single governance plane in six weeks. The auditors did not blink.

F. Pereira·Head of Risk

The constraint

Northwynn closed on a portfolio of thirteen specialty insurance subsidiaries with overlapping but non-identical operating systems. The acquisition agreement required full governance integration within ninety days of close. Failure to meet the timeline triggered material adverse change clauses.

The internal team's estimate for native integration was nine to twelve months.

What we did

We deployed Anillion's runtime as a unifying governance plane in front of all thirteen environments, without modifying the underlying ERPs or claim systems.

The integration was sequenced as follows:

  • +Days 1–10: Inventory and policy mapping across all thirteen entities.
  • +Days 11–28: Connector deployment, with shadow-mode lineage capture across each entity.
  • +Days 29–42: Cutover to enforcement, one entity per business day.
  • +Days 43–48: Joint walkthrough with Internal Audit and the external auditor.

The cutover completed in forty-two days, well inside the ninety-day window.

What changed

  • +All thirteen entities reached governance parity in under six weeks.
  • +The first audit cycle returned zero remediation findings.
  • +Risk, Compliance, and Internal Audit now operate against a single evidence pipeline.
  • +The subsequent four acquisitions in the following twelve months were onboarded in under fourteen days each.

The pragmatic part

We did not solve the underlying ERP fragmentation. That was not what the deadline required. We solved the governance posture. The ERP work followed in its own time, on a saner schedule, against a clearer map.

N° 004.Y Engagement

Talk to the architect who would lead yours.

The first conversation is short, technical, and free. References available under NDA.