Why Insurers' Internal Software Builds Never Finish

Internal software builds at insurers routinely stretch past two years and $30 million because of a structural misunderstanding. 

Insurance

This year I spoke with several people in insurance and insurtech whose internal software builds started in 2025. Almost two years later, they are still building. The spending they described ran from $12 million to $30 million plus. None of these teams lacked smart people. The problem is structural, and it is worth naming so carriers and MGAs can plan around it.

Core versus context

Geoffrey Moore's distinction between core and context is a useful lens. Core is what the market pays you for. Context is everything else that has to work but does not differentiate you. For an insurer, core is underwriting, claims, and distribution. Software is context.

At a software company, the engineer is the product, and the budget, the career ladder, and the roadmap all follow from that. At an insurer, engineering is a support function. It competes for budget with claims, underwriting and compliance, and its roadmap gets bumped by the next regulatory filing or system outage. None of that reflects on the engineers. It reflects where engineering sits in the business, and the strongest engineers tend to go where it is the product.

What the data shows

The numbers point the same way, with caveats on scope.

MIT's NANDA initiative studied generative AI deployments across industries, drawing on 150 leader interviews, a 350-person employee survey, and 300 public deployments. It found that purchased tools and partnerships succeeded about 67% of the time, and internal builds succeeded one-third as often. That study covers AI projects broadly, not insurance alone, and its headline failure rate has been debated, but the build-versus-buy gap is consistent with what insurers report about their own technology.

A West Monroe survey of 300 insurance executives, covered here on ITL in December 2025, found that more than half of insurers spend 51% to 75% of IT budgets keeping existing systems running. Two-thirds expect another three to seven years just to move core systems to the cloud. And 52% said they had delayed or canceled two to three strategic technology programs in the past 12 months, citing budget constraints.

An internal team inherits that environment. The people who should be building the new system are often the same people holding the old one up.

The coordination problem

Fred Brooks explained a second cause in The Mythical Man-Month. The number of communication paths in a team of n people is n(n-1)/2. A team of six has 15 paths. A team of 60 has 1,770. Ten times the people means 118 times the coordination. Adding headcount to a stalled build usually adds more overhead than output.

What to do instead

None of this means insurers should never build. It means they should be deliberate about what they build and who builds it.

First, buy where a mature product exists. The MIT data suggests purchased tools and partnerships succeed more often, so reserve internal builds for what truly differentiates the company.

Second, when something has to be built, keep the team small and senior. Six people who have shipped products quickly, who understand how carriers and MGAs actually operate, and who are accountable for the result will usually move faster than 60 people spread across committees.

Third, scope to one workflow and set a go-live date. A named workflow, real policy and claim files from day one, and security and compliance involved before the first build, remove most of the surprises that stall projects.

Fourth, measure the project by production use, not by activity. A system that adjusters and underwriters do not use is not finished, however much has been spent.

The question for leaders

If your longest internal software project has been running for more than a year, the useful question is not who is to blame. It is whether the structure around that project, including budget priority, team size, and ownership, can ever produce a finish. For many insurers, the honest answer is no, and the fix is a structural one.


Anderson Whittle

Profile picture for user AndersonWhittle

Anderson Whittle

Anderson Whittle is CEO of WYEA, an engineering firm that builds AI workflows into the policy and claims operations of specialty insurers, MGAs, program administrators and reinsurers.

Read More