On a large insurance transformation programme, margin isn’t won in the strategy phase. It’s won (or lost) in the phases that depend on people who can actually build on the platform.
Every insurance transformation mandate reaches a point where it stops being about target operating models and starts being about whether someone on your team can configure ClaimCenter, migrate the data cleanly, or stand up the governance model in Collibra without breaking three things downstream.
That’s the phase where programmes slip, clients get nervous, and practice margin quietly erodes. And it’s the phase generalist bench doesn’t cover.
The skills the programme actually runs on
The platforms driving these programmes are deep, distinct specialisms. A Guidewire cloud implementation isn’t one skill set: PolicyCenter configuration, ClaimCenter, integration and data migration are different disciplines, and a specialist strong in one is rarely deep in the next.
Collibra is a different world again: data governance, lineage and the operating model behind regulatory reporting. Snowflake sits somewhere else entirely – the data platform work that consolidates policy, claims and actuarial data so any of the above is usable. One programme can need all three, at different phases, for defined windows.
None of these are skills a good generalist consultant picks up on the job. On a live core-system migration, the platform is unforgiving of people learning as they go. The client is paying for certainty, not a learning curve. An experienced Guidewire consultant with real UK cloud-implementation delivery behind them is a genuinely scarce profile. When you need one, you need one.
The two options that both cost you margin
Here’s the part that rarely gets said out loud, because it’s commercially uncomfortable: the way most firms resource these phases costs them margin either way.
Option one is to deploy your own senior people onto deep platform execution at your internal rate card.
That’s commercially painful – you’re putting expensive generalist time against work a specialist would do faster and better – and it often doesn’t solve the problem anyway, because rate-card seniority isn’t the same as Guidewire depth.
Option two is to carry permanent platform specialists on the bench so they’re there when a programme lands.
But insurance transformation pipelines are lumpy. Between programmes, a permanently employed Guidewire specialist on a market salary is one of the fastest ways to erode a practice’s economics. Utilisation is the whole game, and standing bench in a narrow specialism rarely clears the bar.
So firms end up choosing between margin erosion now and margin erosion later. Neither is a strategy. Both are what happens when a variable, deeply specialist demand is resourced with fixed, permanent headcount.
Why this is the lever, not just the problem
The reason specialist profiles are a margin lever (rather than simply a resourcing headache) is that these programmes make or lose their margin in exactly the phases those profiles cover.
Get the specialist-heavy phases delivered cleanly, at a cost that sits below permanent consultancy day rates, and the programme’s commercial shape works. Miss on them – slip the migration, under-resource the governance build, put the wrong seniority against the platform work – and the margin goes with it, along with the client’s confidence in your delivery.
That’s the case for treating specialist resourcing as a commercial decision, not an operational afterthought. The firms that protect margin on insurance transformation aren’t the ones with the biggest permanent bench. They’re the ones who can put the right platform specialist against the right phase, only for as long as the phase lasts.
The mid-programme version of the same problem
The other place this bites is mid-flight. A programme enters a phase you didn’t scope permanently (a specific integration, a data migration, a pricing or governance workstream) and suddenly needs depth the team doesn’t hold.
A permanent hire is too slow and too expensive for a window that might last three months. Passing the gap up to the client isn’t an option. This is a structural feature of how transformation delivery works, not a failure of planning – but it still has to be solved, at pace, without blowing the commercials.
What this looks like in practice
This is the work SR2 does alongside consulting delivery teams. We hold an active network of insurance transformation specialists – Guidewire cloud, Collibra, Snowflake, pricing and data engineering – who can be placed against a specific phase, named and mobilised within two weeks. It protects delivery margin without compromising on the seniority the client expects
On one major UK insurance transformation programme, we placed Guidewire specialists directly alongside a Tier 1 consultancy’s delivery team. The strategy and programme leadership were theirs; the deep platform execution needed hands the permanent team didn’t hold. The specialists slotted into delivery, the specialist phases landed, and the firm protected its margin on the work without carrying that bench between programmes.
We’re not a volume supplier and we’re not filling seats. We’re the specialist layer a delivery head can bring in for the phases that need it, and stand down when they don’t.
If your next phase needs platform specialists you haven’t got, let’s talk before it starts. Get in touch with the SR2 Consulting team.
