Where the work has actually run.

A global specialty insurance and reinsurance broker had reached the point where its technology estate was holding the business back. The North American footprint ran across four data centers — two co-located in the US, two on-premises in Canada — on infrastructure old enough to be a genuine cost drag, an operational risk, and a ceiling on how fast the firm could scale its specialty and reinsurance platforms. Leadership wanted three things at once: get out of a managed-services arrangement that no longer served them, modernize the underlying estate, and have the operating model ready for a corporate transaction they expected within the planning horizon.

A straight lift-and-shift — relocating the estate to the cloud unchanged — was ruled out early, because it would have carried the same structural problems into a new environment. The brief agreed with the executive team was to redesign how technology underpinned the operating model, so the result was faster, materially cheaper to run, and ready for the transaction ahead, rather than the same estate in a new location.

We ran the program end to end, from the first readiness assessment through decommissioning the old data centers. In practice that meant coordinating eleven workstreams in parallel — the cloud-readiness assessment, the Azure landing-zone build, migrating end-user computing and virtualizing the desktop estate, moving the business's data, re-platforming and transforming applications, consolidating telephony onto a modern UCaaS footing, the automation and tooling underneath it all, and finally shutting down the co-located centers. Azure was the destination throughout.

None of that gets funded without a credible financial case, so we built one: a three-year and five-year model of what the program would cost and what it would return, and presented it directly to the firm's group-level executive committee. They approved it. Then, mid-program, the firm made two acquisitions — and rather than treat them as separate efforts, we folded both IT integrations in as concurrent workstreams. The first ran five months, bringing roughly 74 people across four offices and three states onto the platform. The second ran four months, covering about 55 people across nine offices and three countries. Because we carried the playbook and the hard-won lessons from the first integration straight into the second, we delivered it for materially less — cutting cost and time-to-market by roughly 25% year over year.

The transformation landed. Four data centers became one unified Azure environment, and the firm was out of the managed-services arrangement it had wanted to leave. The financial case held up under board scrutiny: more than $5 million in projected IT savings over five years against a one-time program investment of roughly $10 million — a return the executive committee had signed off on going in, and could see realized coming out. Both acquisitions were integrated on schedule, with no slip to the core program.

The most durable outcome wasn't the cost line, though. It was that the infrastructure and operating model this program established became the foundation the firm carried into its own subsequent acquisition by a global professional-services group. The disciplines that made it work — articulating a technology investment in board-level financial terms, sequencing many workstreams without losing the thread, and holding integration governance steady while the program was still in flight — are now core principles of the M² framework as we practice it today.

A leading global reinsurance broker — part of one of the largest professional-services groups in the world — was running the systems its Americas business depended on daily on aging on-premises infrastructure. These were the platforms behind broking, fiduciary operations, CRM, finance, and treasury: live production systems that book revenue, hold client money, and feed regulatory reporting. There was no quiet window in which to modernize them, and any disruption carried direct revenue and compliance exposure.

On top of the technical risk, the program had to satisfy a wide and demanding internal audience — engineering, security, networking, operations, disaster recovery — plus a set of external delivery partners, each with a stake in the outcome and a voice in whether it was judged a success. Modernizing the estate was the straightforward part to describe; doing it without interrupting live broking operations, across multiple regions, was the actual mandate.

We ran point as program manager for the core delivery effort inside the broader Americas client-service and enterprise-systems modernization. The scope was substantial in plain terms: just under 200 servers moved to Microsoft Azure, 13 platform services evaluated and built into the target architecture, and north of 13 terabytes of data migrated across broking, fiduciary, CRM, finance, and treasury systems. The central infrastructure team alone put more than 300 days of effort into it — and that was one team among many that had to move in step.

The defining challenge was not the server count. It was keeping a dozen internal functions and a set of external delivery partners aligned on a single direction and schedule, against live systems that could not go dark. Holding that together took the discipline large migrations actually depend on: governance reporting precise enough that every party worked from the same picture, resource forecasting that surfaced constraints early, and milestone tracking tight enough that a delay in one workstream did not cascade into the others.

The two-year program was delivered in full. Every core system — broking, fiduciary, CRM, finance, treasury — went live on Azure, with the platform services integrated into the target architecture as designed. More to the point: the firm's Americas client-servicing capability now ran on a modern operational foundation instead of infrastructure that was quietly aging out from under it. When the organization later went through a corporate reorganization, that foundation was solid enough to carry straight through.

The engagement was, above all, an exercise in integration governance across a crowded field of delivery partners — coordinating many hands to move as one. That experience directly informs how M² programs sequence multi-vendor, multi-region work today.