Healthcare

Zero-downtime Microsoft 365 migration for a 12-hospital network

Migrated 3,800 mailboxes and 24 TB of clinical documents to M365 with Defender & Intune hardening.

Microsoft 365SecurityMigration

6-month engagement Pod of 5 specialists Delivered remotely + on-site

Headline outcome

0 downtime, 38% IT cost reduction

Client: Multi-city Hospital Network

The context

What was actually happening at Multi-city Hospital Network

On paper, Multi-city Hospital Network was doing well. Revenue was up year-on-year, the team had grown, and a couple of flagship healthcare accounts had just renewed. Off paper, leadership could feel the cracks - the kind you notice when finance takes four days to close a month, or when a customer flags an issue that turns out to be the third time it's happened this quarter.

What made Multi-city Hospital Network unusual wasn't the problem. It was the honesty. On our first call, the healthcare leadership team walked us through two previous vendor engagements that hadn't worked. Not to complain - to make sure we understood what "success" and "failure" looked like from their side of the table. That single hour told us everything about why they'd probably win this time.

The problem, in one paragraph

Why the surface symptoms were misleading

The obvious pitch would have been "buy this platform, migrate to it, retire the rest." We've seen that play run enough times to know how it ends. Two weeks of paid discovery told us the real bottleneck wasn't tooling at all - it was ownership. Three teams were half-responsible for the outcome and nobody was fully responsible. Fixing the tools without fixing that would have bought a temporary win and a slower rebuild in eighteen months.

Before

·Seven disconnected tools, three of them barely used
·Monthly reporting cycle - by the time it landed, the month was over
·No single owner for the number leadership cared about
·Two failed vendor engagements in the previous 18 months

After

One integrated stack, one accountable owner, one dashboard
Weekly numbers - published every Monday, no exceptions
Fixed-price milestones, no scope-change ambush
Retainer renewed twice - the metric we trust most

How we ran it

The engagement, week by week

No secret sauce. Just the same rhythm we run on every senior engagement.

Weeks 1-2

Paid discovery

Interviews across Multi-city Hospital Network's ops, finance and IT teams. Systems audit. A written 90-day plan on the table before any code was touched.

Weeks 3-6

Foundations shipped

Highest-leverage fix went to production first. Reporting cleaned up. Data pipelines rebuilt. Weekly demos, no slide decks.

Weeks 7-12

Compounding wins

Second and third milestones landed. The metric on the wall started moving in the right direction, then kept moving.

Weeks 13+

Steady state

Handover documentation, SLA-backed support, quarterly reviews. The client's team runs it; we back them up.

Named senior lead from day one
Weekly demos, fortnightly reviews
Fixed-price milestone billing
Full documentation on handover

Under the hood

What we actually built with

The stack was chosen for Multi-city Hospital Network's team, not ours. Boring, well-documented, operable on a bad day.

Microsoft 365 Security Migration

The outcome

Numbers we can (and did) put on the board deck

0 downtime, 38% IT cost reduction

Delivered on time, within the fixed-price envelope, with a documented handover and SLA-backed support post go-live. Six months later Multi-city Hospital Network renewed the retainer - which, to be honest, is the only outcome metric we truly trust. Anyone can win a project once. Getting renewed twice is the number that pays our rent.

On-time delivery

100%

Budget variance

Retainer renewals

2×

"They didn't sell us hours. They took the number we cared about and moved it. Halfway through, we stopped treating them like a vendor and started treating them like an extension of the leadership team. That's a rare partner."

Head of Digital

Multi-city Hospital Network · Healthcare

What we learned

Three things we'd carry into the next engagement

01
Ownership is the intervention. Tools are the artefacts.
Every meaningful step change at Multi-city Hospital Network traced back to giving one person the pen. Every stall traced back to committee thinking.
02
Ship the boring 80% before the ambitious 20%.
Clean data, honest dashboards and a working weekly rhythm compound faster than any marquee feature. We resisted the pull to build the shiny thing first, and it paid off.
03
Write it down. All of it.
Weekly updates in writing. Decisions in writing. Handover in writing. Half the reason we get renewed is that we leave a paper trail nobody has to chase.