Selling data modernization to insurers
How to sell data modernization into insurance carriers. Who buys, the pressures they carry, the signals that matter and an opener that gets a reply.
· 4 min read
Insurers don't buy data modernization. They buy faster pricing, cleaner claims and fewer surprises from the regulator. Sell the data work as the plumbing behind one of those, and you get a meeting. Sell it as a platform, and you get a polite no.
I've watched a lot of services firms walk into carriers with a slide about lakehouses. The room nods. Nothing happens. The firms that win start somewhere else.
Who actually buys
The economic buyer is rarely the person with "data" in the title. It's usually a business leader with a number on the line. The head of claims who can't see leakage until a quarter after it happens. The chief actuary waiting weeks for a clean dataset. The head of underwriting who wants to price a new product and can't get the history out of three policy systems.
The CIO or CDO controls the architecture and often the budget. They're the technical lead in most deals, and sometimes the economic buyer on a platform program. Your champion is often a director a level below, the person stuck running the reconciliations by hand.
You need all three. A carrier won't move a data program on the word of one person, and nobody in that building wants to be the only name on it.
The pressures they carry
Insurance runs on old systems. Many carriers still run policy administration on platforms older than half their staff. Every acquisition added another one. So the data lives in silos with different definitions of the same customer.
On top of that sits a constant drumbeat. Regulators want reporting faster and cleaner. Loss ratios swing with weather and inflation. Distribution partners want quotes in minutes, not days. And every carrier has heard that its competitors are pricing with better data.
That last one matters. Fear of falling behind on pricing moves budget faster than any architecture argument.
Signals worth watching here
A new leader in the buying seat is the strongest place to start. A new chief data officer, CIO or head of claims arrives with a mandate and a short window to show a plan. In the first 90 days they're open to a sharp outside view.
Business pressure shows up plainly in public carriers' filings. Look in the 10-K for language about legacy policy systems, modernization programs, expense ratio targets or a reserve charge. When a carrier tells investors its systems are slowing it down, believe it.
Hiring for the problem you solve is the tell that money exists. A posting for a data platform lead, a claims analytics manager or a Guidewire or Duck Creek architect says the work is funded and named. Stack-specific posts tell you which platform you'll be working next to.
Mutuals and private carriers don't file, so lean harder on hiring, new seats and what their leaders post. The buying signals guide covers the full set.
An opener that fits
Say a regional property and casualty carrier names a new head of claims. Two weeks later it posts for a claims data engineering lead and a reporting analyst. Its last annual report mentions a multi-year core systems replacement.
Here's how I'd open with the new head of claims.
Saw you joined as head of claims, and the team's now hiring a claims data engineering lead. In a new seat, the first ask from the board is usually a clear read on leakage and cycle time. My guess is the numbers you need live in two or three systems that don't agree, so every report takes a week to reconcile. Is that accurate, or is the bigger issue something else?
Notice what it doesn't do. It doesn't mention a platform. It doesn't claim to know their systems. It names what happened, says why it matters in her seat, guesses at the misery and lets her correct it.
If she writes back "not quite, the real problem is our TPA data," that's the meeting. Her correction just told you what to scope.
What to avoid
Don't lead with the cloud vendor. Carriers are buried in partner pitches, and they'll file you with all of them.
Don't send the same note to the CIO. Write to the technical lead about the architecture risk and to the champion about the hours lost to manual reconciliation. Same event, three seats, three messages.
And don't promise a transformation. Insurance buyers have lived through failed ones. Offer a narrow first step tied to one business number, like claims cycle time or time to a filed regulatory report. Win that, and the program follows.
The insurers that buy data work are the ones with a named leader, a funded role and a problem they've already admitted in public. Find those three at one carrier, and you're early instead of lucky. The method is the same everywhere. The pressures are what make insurance its own room.