Download

Insurance Agencies: Don't Panic on AI ROI

Insurance agencies investing in AI are seeing productivity gains but not yet revenue lifts—a predictable adoption phase, not a failure.

Insurance Agencies Shouldn't Panic About AI ROI

As insurance agencies continue to invest in AI, not all are seeing a return on investment. Some are seeing productivity gains right away as employees get certain work done faster. But often when leadership looks for the corresponding lift in revenue, client satisfaction, or operational transformation, the numbers aren't there yet. A recent study of new AI use cases announced by some of the world's largest insurers in the first quarter of 2026 found that only 18% reported a measurable result, and four out of five of those were productivity gains with no revenue or satisfaction figures attached.

The instinct for many organizations is to throw their hands up and label their AI investments a failure, but the delayed effect AI-driven efficiency has on measurable business outcomes is a predictable stage in a technology adoption cycle. AI is moving through a pattern that starts with broad adoption, shifts to prioritization, and eventually produces measurable results. Most agencies are somewhere between the first and second stage.

Expecting bottom-line transformation during what is still an adoption phase puts organizations at risk of making reactive decisions, such as pulling back on investments or doubling down in the wrong places. Rather than scrambling to justify AI spending or scrapping programs that haven't paid off yet, agencies should use this interim to make three deliberate moves: Focus AI on the priorities that matter most to their business, measure success with the KPIs they already trust, and keep human expertise at the center of how AI work gets reviewed and governed.

This is especially relevant given where the insurance brokerage business is in its own cycle. The industry has been acquisition-driven for the last three to five years, but the transaction pace has slowed. Firms that brought together multiple organizations are now looking inward, trying to create uniformity in process across disparate systems and teams. AI can play a large part in creating internal efficiencies, as long as organizations are deliberate in how they apply it. That standardization is what ultimately drives greater cost-effectiveness, particularly as firms look to shift toward outcome-based approaches.

The sharpest insurance brokerages right now are making those deliberate choices. Many are prioritizing front-of-office work because they want to drive greater client experience, and they know this will have a clear effect on satisfaction, NPS, and retention.

Similarly, measuring the impact of AI should go beyond speed or cost savings. Think about the shift from typewriters to personal computers. The work was done a little differently and certainly got faster, but that didn't change the standards for what qualified something as well-written. The same thing happened with the BlackBerry, and then again with the iPhone. These tools had a massive effect on how effective people were in their daily lives, but the underlying measures of success stayed the same.

We don't need to reinvent the wheel to measure AI's success. If any agency was tracking client satisfaction, retention rates, and growth before the technology, those metrics still apply. A meaningful early indicator might be straightforward: Are KPIs that the organization was previously falling short on starting to get hit? If so, the tools are working, and the agencies don't need to change how they measure success. They need to figure out what's most important to their business, aim AI at it, and measure with the instruments they already trust.

Even as agencies focus AI on the right priorities and track the right metrics, none of it holds together without human oversight. Anyone who has used an agent to summarize a meeting knows the technology doesn't catch everything. When AI agents are handling workflows that touch claims, coverage, or regulatory obligations, the margin for error shrinks considerably.

Agencies that are just bolting third-party AI onto their workflows without understanding what's under the hood are taking a big risk. When there is no ability to show what work has been done, you cede control to an AI agent. The right path is to have comprehensive quality assurance processes and regression testing capabilities around every agent doing day-to-day work, with checkpoints and compliance oversight built into the workflow.

There hasn't yet been a major AI-related claims dispute, but that day is coming. When it does, firms will need to understand exactly what happened and where. They can't just point to the black box of an agent. This is where domain expertise paired with that technology becomes the differentiator. Agencies working with partners who bring decades of insurance operations knowledge alongside the technology — and who maintain human oversight as a fundamental part of the process — can actually govern what their AI is doing. And as AI adoption grows, the demand for people with the expertise to oversee and evaluate what agents are producing will grow with it.

The effect of the decisions that agencies are making now will be clear by the first quarter of 2027. Nearly 60% of carriers and managing general agents expect AI to transform their business models within the next one to three years. That's when we'll be able to look back at the first two quarters of 2026 and see where speed and efficiency gains actually translated into revenue and operational results. That's when those lagging indicators will catch up.

MGAs Don't Have an AI Problem

MGAs have grown to $114 billion in premium but lack time and capital to build AI infrastructure themselves.

MGAs Don't Have an AI Problem.

I've spent most of my career building insurance companies and working with the people who build them. One thing has stayed true that entire time: almost everyone has significant ambition for what technology could do for their business, and very few have the time, expertise, and capital it takes to realize it.

Right now, the clearest example is the MGA channel. The segment has grown from $47 billion to $114 billion in written premium since 2020, yet fewer than 7% of MGAs have AI agents working in production. [Source: The Specialty MGA Operating Model Inflection Point.] It would be easy to read the lack of production AI as caution, or a lack of appetite. I read it differently. 

Every MGA operator already knows submission triage is slow, that bordereaux reconciliation eats a disproportionate share of ops headcount, that claims intake could move faster than it does. The people best at underwriting, distribution, and servicing are spending their days underwriting, distributing, and servicing, which is exactly what they should be doing. Standing up a technology function from scratch takes a year or more and a seven-figure hiring spree, and most MGAs would rather spend that time and money growing the book. Correctly, in my view.

I've seen what that tradeoff costs firsthand. We spent a decade at Clearcover investing in proprietary technology to run our business. We built it ourselves, and it worked: by early this year, more than 90% of our claims intake ran through AI agents, and 93% of our policies were bound digitally. The work was also nothing like a straight line. We built things that didn't pay off, not because they failed, but because the ROI wasn't there. Those lessons about where to invest shaped how we operate just as much as our wins did.

One of the main lessons is that the hard problems are workflow problems, not model problems. A submission arrives missing three data points: what happens next? A servicing request touches four systems that don't talk to each other: who reconciles it? A claim needs a coverage decision at 11 p.m. on a Saturday: does anything move before Monday morning? Can we accelerate the workflow using AI? 

Answers to those questions come from people who have sat inside an underwriting or claims operation, redesigned the work, and then built the system that runs it. They do not come from a better model, and they definitely don't come from a slide deck.

That points to a different shape of help than this industry usually gets offered. What closes the gap is a build partner: people who bring the insurance operating experience and the pre-built technical foundations with them, stand the system up inside the MGA's actual workflow, and leave the MGA owning it when they're done. 

That is a different deliverable than a platform license the MGA has to configure and hope fits, and a very different one than a strategy roadmap. The MGA channel has spent decades outsourcing specialized functions to people who show up with the expertise already built, from actuarial to claims administration. Technology should work the same way.

The economics have to change shape, too. If adoption requires an MGA to write a large check before seeing results, most of the market will rationally pass, including plenty of the best-run shops. Adoption moves when the risk sits with whoever is doing the building and payment is tied to outcomes the business already counts: submissions triaged, servicing events completed, claims closed. Insurance has priced plenty of vendor relationships this way for decades. The approach just hasn't been applied to AI infrastructure yet.

We believe that enough to test it with our own capital. This month, we opened applications for Launchpad, a program where we fund and build the AI infrastructure for a small cohort of MGAs, the MGA owns what we build, and we earn as it produces results. I don't know yet whether this exact model is the one that closes the gap. I do know that the ambition in this channel was never the problem and that the operators who are best at this business shouldn't have to become something else to get the technology their book deserves.


Kyle Nakatsuji

Profile picture for user KyleNakatsuji

Kyle Nakatsuji

Kyle Nakatsuji is the founder and CEO of Clearcover, an AI-native auto insurance carrier, and Dearborn Labs, which helps P&C carriers and MGAs operationalize artificial intelligence. 

Before founding Clearcover, he was a venture investor at American Family Insurance, where he led insurtech investments. He speaks regularly on AI strategy in insurance.

Pet Insurance Hindered by Outdated Technology

Many pet insurers find their platforms can't scale beyond direct-to-consumer, turning promising B2B2C partnerships into costly technology projects.

Pet Insurance Growth Hindered by Outdated Technology

The next phase of growth in pet insurance will likely not come from selling more policies through existing channels alone. It will also come from expanding and improving the routes through which insurers reach customers. Retail partnerships, employer voluntary benefits and veterinary networks are pushing the market toward a B2B2C model. Yet many insurers are discovering that while they can support a direct-to-consumer journey, launching and scaling new partner channels remains painfully slow. That is the distribution trap.

Most pet insurance platforms were built around a primary sales channel rather than for a genuinely multi-channel distribution model. Introduce retailers, employers, affinity groups or veterinary networks, and complexity rises quickly. What should be a commercial opportunity becomes a technology program instead. In a fast-growing market, that friction becomes a competitive disadvantage.

Distribution Has Changed. The Operating Model Has Not.

Direct-to-consumer distribution is comparatively simple because it is built around one primary relationship between the insurer and the customer. The operating model can be built around a single customer journey. The insurer controls the brand, acquisition journey, payment method, service experience, and operating model.

Partner-led distribution is different. A retail partner may want its own customer-facing brand proposition and tailored product bundle. An employer offering often requires eligibility rules, payroll deduction and a clear process for employees who leave the business. Veterinary networks will seek offerings that are designed around the point of care, with distinct data-sharing, consent and servicing requirements.

These are not exceptional demands. They are the ordinary realities of distributing insurance through multiple routes. Yet many platforms were designed to support one primary channel, usually direct or broker-led. When the platform cannot accommodate partner requirements as configurable variations of the same operating model, each new relationship becomes an exception. Instead of configuring a new route to market, the insurer creates a new version of the business.

Commercial teams know what follows: requirements documents, competing technology priorities and months of delivery effort. By the time the proposition is live, the partner's appetite may have shifted, or a more agile competitor may already be in the market.

The Employer Channel Makes the Problem Impossible to Ignore

Employer voluntary benefits expose both the scale of the opportunity and the operational limitations holding it back. In most households, pets are an essential member of the family. In that regard, an employer does not need to fund the policy for benefit to create value. Simply offering employees access, convenience and choice can make the proposition meaningful.

But the mechanics differ sharply from a conventional annual policy sold online. Employees may enroll at different points in the year, insure multiple pets and choose payroll deduction, direct debit, or another payment method. They may change employers, alter working arrangements or leave the scheme altogether. Coverage may need to continue seamlessly when the employment relationship ends. The employer may need reporting, while the employee remains the customer and the insurer remains responsible for the policy.

These are the normal mechanics of an employer-led proposition. But systems designed around a single annual policy journey often support these requirements through manual intervention and exception processing, leaving operational teams to bridge the gap between what the product promises and what the platform can deliver. That is not a scalable distribution model. It is a workaround disguised as a channel strategy.

The real test is not whether an insurer can launch one employer scheme. It is whether it can launch 10, 50 or 100 without creating a new operational burden every time. Can it onboard partners quickly, configure eligibility and payment rules without changing core code, and support the customer after they leave their employer?

If the answer is no, the insurer does not yet have a scalable employer distribution strategy. It has an employer pilot program.

Why Channel-Specific Workarounds Are the Wrong Answer

Some might argue that the best response is to build a channel-specific solution: a separate portal for employers, a bespoke integration for a retailer, or a standalone proposition for a veterinary partner.

While this may solve an immediate launch requirement, each separate solution can introduce another product variant, data model, servicing process and set of technical dependencies. The insurer may appear to be expanding distribution while multiplying complexity behind the scenes. Over time, the business becomes harder to change, more expensive to run and less able to maintain a coherent view of the customer.

The alternative is a unified distribution model: a shared core platform that supports multiple partners, brands and routes to market without requiring a separate operating model for each. Each partner can have tailored journeys, propositions, brands permissions and business rules, while product, policy, customer and servicing capabilities remain connected.

This is where architecture becomes essential. APIs matter, but only as part of an open, configurable and connected operating foundation. The real test is whether an insurer can reuse proven product, policy, billing, customer and servicing capabilities while configuring the journeys, permissions, eligibility rules and payment methods required by each partner. If every new connection still triggers a bespoke technology project beneath the surface, APIs alone have not solved the distribution problem.

On this foundation, a new partner is no longer an integration problem to be solved from scratch. It becomes a repeatable route to market that can be launched, adapted and scaled without multiplying operational complexity.

The result is not simply faster partner onboarding. It is a different distribution model. One in which commercial teams can build partner ecosystems with confidence, because the underlying platform is designed to support multiple brands, journeys and channels without creating a separate business behind each one.

That changes the economics of distribution. Instead of asking whether a new partnership is large enough to justify a major technology project, insurers can ask: how quickly can we test, learn and scale this route to market?

Winning Insurers Will Treat Distribution as a Core Capability

The bottom line? The pet insurance market will not be won by the insurer with the most channels. It will be won by the insurers that can launch, operate and scale those channels effectively.

Rather than treating distribution as a series of integrations, insurers must transform it into a core business capability where they can launch new partners without destabilizing operations, support different enrolment and payment models without forcing customers into the wrong journey.

The result is an approach that gives commercial teams the freedom to pursue opportunities without negotiating a technology transformation every time. Retailers, employers, affinity groups and veterinary networks can open valuable new routes to growth. But those routes will remain theoretical for any business whose platform was designed for a single-channel world.

The question is no longer whether insurers want to diversify distribution. Most already do. The question is whether their technology stack will let them.

DEMO: Fenris

Fenris provides real-time data enrichment and predictive intelligence through a suite of APIs that deliver quality information about individuals, households, vehicles, properties, and businesses. Insurers, MGAs, agencies, and platforms use Fenris intelligence to improve automation, decision-making, and customer experiences.

Fenris Logo
 
Watch Our Demo: 

Learn More

Are you interested in learning more about Fenris and this product? Please visit these sites to learn more:

Why We Are the Right Solution For Your Needs

The quality of every underwriting decision traces back to the quality of data at intake. Fenris delivers real-time data enrichment APIs that return verified, multi-sourced information the moment an address or vehicle is entered. Carriers and MGAs receive accurate, comprehensive data from the first step of the workflow. When the right data is present at intake, everything downstream improves: quotes move faster, underwriters work from a stronger foundation, and risk assessments reflect the full picture.

Fenris covers the full scope of property and auto risk intelligence: residential and commercial property characteristics, hazard and peril profiles, replacement cost estimates, vehicle and driver data, and predictive analytics to optimize acquisition workflows, reduce risk, and personalize customer experiences. Across all of it, the principle is the same: comprehensive, accurate data returned instantly so carriers and MGAs can make better decisions earlier. From intake to quote to underwriting, Fenris equips every step of the workflow with the risk intelligence needed to write business with confidence.

Three Main Benefits of the Product: 
  • Real-time data at intake reduces drop-off, accelerates quotes, improves early decisioning, and creates a better experience for agents and applicants alike.
  • Predictive AI improves risk assessment, optimizes acquisition, and delivers personalized experiences that drive higher conversions and reduce losses.
  • Non-contributory across all products, so enriched data never feeds a shared pool. Predictive models stay specific to your book and your customers.
What Part(s) of the Insurance Industry Can Benefit From Our Product: 
  • Customer Experience
  • Distribution
  • Operational Efficiency
  • Underwriting efficiency

Fenris

Profile picture for user Fenris

Fenris

At Fenris, we are revolutionizing the way businesses harness data and predictive AI to drive smarter decision-making. Our cutting-edge solutions provide insurers, financial institutions, and other industries with instant insights that accelerate customer acquisition, reduce risk, and optimize growth opportunities.

Fenris is on a mission to transform the customer journey through predictive intelligence. We empower businesses with AI-driven insights that streamline onboarding, improve conversion rates, and enhance customer retention—helping them make faster, smarter, and more profitable decisions.

3 Steps to Assess a Fleet's Insurability

Insurers must evaluate fleets' claims processes, data usage and operational discipline to write profitable commercial auto policies amid soaring liability costs.

Three Steps to Assess Fleet Insurability Today

An underwriter writes a $5 million commercial auto liability policy for a large trucking fleet and sees it as a big win, especially if the fleet doesn't incur any losses until the second, third or fourth year. However, the insurer hasn't really made $5 million. Instead, it has assumed years of potential liability that could ultimately make the policy woefully unprofitable.

Research from the American Transportation Research Institute (ATRI) released in May shows why. Per-mile liability losses rose an average of 33% between 2021 and 2024 due to a sharp rise in crash claims expenses, despite a 2.6% reduction in crash rates involving heavy-duty trucks.

It only takes one serious accident to turn a sure win for a carrier into a stinging underwriting loss. That is why insurers should take these three steps to assess a commercial auto client's risk management practices and determine whether its fleet demonstrates the operating discipline required to reduce its risks throughout the policy term.

Step 1: Look Beyond Historical Loss Runs

One of the biggest challenges underwriters face when reviewing commercial fleets is selecting and pricing a policy based solely on past performance. While historical loss runs may seem favorable, subpar claims processes will amplify loss severity in the event of a reportable incident.

Strong claims management is an equally strong indicator of future performance. Fleets that recognize an incident, report it and respond by improving both operational and risk management practices will perform better over time.

During underwriting, insurers should review each prospect's claims processes in detail. Ask how quickly they identify and report claims and whether they have any policies in place for investigation and escalation. Explore whether they use data to recognize recurring accident patterns and look for evidence the fleet has changed its procedures or behaviors based on their claims experience. Use the answers to objectively assess how responsive the fleet is likely to be throughout the policy period.

Step 2: Review How Fleets Use Data

Telematics, on-board camera systems, electronic logging devices (ELDs) and other monitoring systems provide fleets and carriers with a wealth of operational data. Yet the mere presence of these technologies alone does not necessarily make a fleet more insurable.

To see why, consider telematics devices. They deliver a seemingly endless stream of data points, from GPS location and vehicle speed to engine hours, fuel consumption, hard braking, harsh acceleration and following distance. There is so much data, however, that fleets can become overwhelmed quickly. They may not know which data is most important, and they might not have a set process for using that data to improve driver behavior and reduce their risk for accidents.

For these reasons, both carriers and brokers should look beyond a fleet's technology adoption when assessing a client's insurability. Underwriters should ask which data points a fleet monitors, who reviews them and what triggers an intervention. Fleets that manage their risks well will focus on a small handful of meaningful data points, then use them to tailor their continuing training efforts to each driver based on their individual behaviors.

Brokers have a complementary role. If they find a prospective client is experiencing data paralysis, they should partner with carriers with a proven track record of helping fleets make their vehicle safety data actionable. Doing so will position brokers as trusted advisors to their clients while also helping their carrier partners write profitable business.

Step 3: Use Technology to Identify Leakage

A fleet can look like a favorable risk when the policy is bound. It can also become unfavorable six months later. To understand why, consider a carrier that insures 100 trucks, but the fleet actually has 150 power units operating on the road. If the policy is priced on a per-power-unit basis, the carrier is taking on extra exposure it never priced.

The challenge for most insurers is finding those extra vehicles before a claim or renewal exposes the problem. Some carriers are solving this by developing proprietary AI tools that can compare scheduled vehicle data with inspection and operational records. If a vehicle identification number (VIN) shows up in the records but not on the policy, the carrier can talk with the client, find out why and add the vehicle to the policy midterm if applicable.

While AI can stop leakage, carriers should also realize technology should not replace human judgment. Predictive models can help insurers analyze more accounts and surface risk signals faster, but greater underwriting volume does not necessarily mean better underwriting. Experienced professionals must still determine which specific underwriting criterion matters the most.

Insurability Is More Than Pricing Risk

With premiums and claims costs continually rising, carriers can no longer focus solely on rising rates. They must also reduce their losses. Insurers that thoroughly assess a fleet's loss history and claims processes, help it use data to improve driver safety, and check in regularly to prevent leakage will write good business and reduce claim frequency and severity, thereby creating more value than pricing adjustments alone.

Winning on the AI Pilot Is the Easy Part

AI pilots often succeed technically but fail commercially because companies neglect to fund and staff the business case alongside the proof of concept.

AI Pilots Fail Without Business Planning

Every enterprise AI pilot depends on two separate tracks to run smoothly for success. Both tracks require thoughtful planning and execution, but many companies fall short, and their AI pilots fail before they begin.

My team spent months on a proof of concept for a large insurer. This potential client created a bake-off scenario with high stakes: our document processing system, based on AI small language models, against their internal build and a leading frontier model. Their test would use their charts, images, handwritten notes, etc. and be scored on their terms. We won, and not by a little.  

The deal died anyway. Not on our side of the table, but on theirs. What happened? They didn't have a funded business case, an approved timeline, or a budget line waiting on the other side of the demo. Our champion was sharp and genuinely bought in, but he didn't directly own the business line, and without that he had neither the budget nor the political capital to carry the work across the organization. When the business case finally went up the chain, it didn't get the backing it needed, and it missed. Months of their work and ours evaporated.

It was frustrating for everyone, and it was entirely avoidable.

In the months and years since, I've run dozens of these demos, mostly in insurance for claims, underwriting, and submission intake. The most crucial advice I have for every executive greenlighting an AI project is to understand that every pilot runs on two separate tracks, and they have almost nothing to do with one another.

Track one is technical. Can it work? How accurate is it? Does it fit the architecture, clear the security review, connect to the systems you already run? This is the track everyone obsesses over. It's where vendors compete, where the POC is scored, where the demo lives.

Track two is the business. Is there a funded case? An owner with authority? An approval path, a realistic timeline, a budget that's still there when next year's planning cycle hits? Who actually signs, and can they? This is the track that decides whether anything ships, and it's the one almost nobody staffs.

Here's the trap: winning track one tells you almost nothing about track two. A dazzling demo feels like progress, so everyone relaxes, but the fact is you've only cleared half of the problem that was never really in doubt. We won track one decisively for that insurer, and the pilot still died because no one was running track two with the same seriousness.

The uncomfortable part about my side of the table? Vendors are paid to win track one. The entire machinery of a POC, mine included, is engineered to produce an impressive technical result. Almost none of it is built to produce a funded production plan, because that's the customer's job, and unless a leader explicitly hands it to someone it doesn't belong to anybody. The result is two parties pouring themselves into the demo and neither one carrying the business case. The pilot succeeds. The initiative stalls. The post-mortem blames "the technology," which is usually the one thing that actually worked.

Sometimes the roadblock appears after you've "won" the client. A partner of ours sailed through the evaluation and moved into real use, and then they hit the roadblock. The rate limit on their plan was well below what production needed to run their document count. The technology worked, but they were missing a throughput plan. They neglected the commercial terms of their project; they didn't have a who-pays-for-scale conversation, also known as track two. It was never started because the "win" made everyone on their team feel as if the project was finished.

So what do success stories look like? Here's what's humbling as a technologist: my production successes run on the same technology as my graveyard. They use the same models with the same accuracy. The deciding factor isn't track one.

One of my most successful clients is a high-volume document operation that is running in production against a real backlog. From day one their leadership ran track two out loud. There was a clear, identified pain point and a commitment to the project with a budget to fix it. There was a named owner who could say "yes, integrate it," and mean it. The success criteria were concrete. And when we later hit a genuine platform limit, they escalated it into a road map conversation instead of using it as an exit. Their success can be traced to their strong leadership.

So, if you're about to greenlight an AI pilot it's critical to understand that track two will decide whether your project succeeds or fails before you hit the finish line.

You need to ask, and answer, specific questions before you begin. Who owns this project in production? Name an actual person who will hold accountability because the moment responsibility is spread out among a committee your project will stall. Who can be the executive to say yes and sign the check? It needs to be someone with the political standing in your company to see it through, rather than the person most enthusiastic about the project.

What's the funded path and timeline to scale if the project works? This needs to be decided before the kickoff because "if it works" is exactly when these projects tend to die.

Go ahead and run track one to prove it's possible. But you also need to fund, staff, and lead track two from day one. It is a mistake to hand over the entire project to an employee who is enthusiastic but doesn't own the line of business, no matter how much they believe in it.

The technology will do its job. The real question is whether anyone built the plan to see the project through.


Sam Gobrail

Profile picture for user SamGobrail

Sam Gobrail

Sam Gobrail is the U.S. head of delivery and solutions at Upstage.

Before Upstage, he led transformation programs for Fortune 100 companies and federal agencies. Earlier, he practiced law and managed multimillion-dollar federal portfolios.

Gobrail holds a juris doctor and MBA from American University, where he also teaches.

Data Center Boom Tests Insurers' Capacity Limits

Explosive growth of AI-driven hyperscale data centers is forcing insurers to innovate underwriting for unprecedented exposures and capacity demands.

Data Center Boom Testing Insurers' Capacity Limits

The growth of cloud computing and the amplified use of artificial intelligence across different industries has fueled the creation of massive, state-of-the-art data centers, and with that, increased the need for innovative property/casualty industry solutions to meet nontraditional insurance exposures.

Data centers, which process and store large amounts of essential information, tend to be warehouse-sized facilities that house computer servers and require significant cooling, power backup, fire suppression and security systems. Initially, their proliferation was seen in the 1990s with the rise of the Internet, but the current expansion is unfolding at a much larger scale and even faster pace, fueled by billions of dollars in private investment and federal directives to fast-track certain projects.

Larger data centers, or "hyperscale" data centers, are drawing the greatest attention and scrutiny because of their size, rapid growth and substantial impact on local communities. Given the customized technology that's in these data centers and the fact that they'll be very hard to replace and difficult to repair, any kind of covered cause of loss that keeps any of these data centers out for any significant period of time would likely cause a significant financial loss, and business interruption is one of the main prospective causes of loss. Contingent business interruption comes into play as well as in these scenarios: it's not just AI companies that would be losing revenue it would also be the clients that are leasing services from these AI companies that are losing their business. Disruptions to data center operations would create a domino effect.

Insurance considerations should come into play from the very start of the planning and building of a data center. Builders' risk exposure is high with the potential for physical damage to the data center during its construction. Supply chain issues or labor shortages that affect the construction industry, especially acute issues in a specific state or region, could be problematic for insurers of data center builders or owners of completed data centers. Depending on the area where these facilities are constructed, they could put a significant drain on locally available skilled labor or construction expertise.

Once built, a data center could experience first-party financial loss stemming from a direct, covered cause of loss; for example, a fire that damages the physical structure, and its interior components (e.g., computer servers and other equipment) and other contents. Because the data centers use servers that generate unprecedented heat loads, the risk of ignition is higher than in traditional large commercial facilities such as warehouses. Physical damage from failed systems outside the data center, such as an off-premises power failure, could create an insured loss as well depending on the property coverage extensions within an insured's policy. Commercial property coverage would also be necessary to cover damages from other natural or man-made disasters.

From a general liability standpoint, any bodily injury or property damage to third parties from a fire or explosion at the facility could create major losses, and from an environmental liability standpoint, if there's any discharge associated with the operation of the center that contaminates the water supply of the surrounding communities, that is another liability exposure.

Another obvious potential exposure to loss concerns cyber. Losses from failed or inadequate cybersecurity could be costly, especially if any of these data centers are housing proprietary, private or sensitive information of any type.

At the same time, data center development can create significant economic opportunities, including numerous jobs for technicians, electricians, facility managers and other local building trade workers. State and local governments can also benefit greatly from property and sales taxes associated with these centers. Overall, the benefits of data centers should ultimately be weighed against public costs.

The risks posed by data centers apply beyond the United States and are generally the same in international markets. These data centers built internationally will also need to satisfy domicile-specific regulations, such as those related to cybersecurity, the environment and diverging online content regulation.

Time will tell if insurance supply can keep up with demand. The sheer size of hyperscale data centers necessitates (re)insurers making determinations concerning their risk tolerance and where their preferred placement is within a layered property insurance program. Innovative structures such as captive formations could become part of the picture, but clearly, as data center development and construction spreads, required insurance coverage should evolve as it is currently beyond what the traditional property/casualty industry has previously experienced. Setting risk tolerances and building a history of loss experience are all factors in developing needed underwriting expertise.

Given the significant capital required to finance data center infrastructure projects, insurers may have exposure on the asset side of their balance sheets through private credit investments, private equity partnerships or other financing arrangements. Insurance investment managers also will need to monitor associated risks closely, including regulatory changes or legislative developments that could affect the long-term performance and viability of these investments.

With AI becoming a more critical component for society in general, how well the headwinds associated with the availability and affordability of energy to power data centers are addressed will be of major importance. Insuring these facilities will continue to be a complex undertaking involving an integration of multiple coverages, some of which will be needed in phases as different stages of data center development are completed.


David Blades

Profile picture for user DavidBlades

David Blades

David Blades is an associate director within the Credit Rating Criteria, Research & Analytics Department of AM Best, a global credit rating agency with a focus on the insurance industry.

It Wasn't a Decision. It Was a Default.

There is a question about AI no one is asking out loud: Are the efficiencies worth more as a cost saving, or as time freed up for other work? 

AI Cost-Cutting Defaults Undermine Insurance ROI

A head of claims operations walks the executive team through the results of an AI-assisted document review rollout: a sharp, real cut in average review time. The room comes alive over it: not skeptical, enthusiastic. Someone's already running expense-ratio math out loud before she's finished the slide. Someone else wants to know if the same approach works in underwriting. The head of claims tries to steer the conversation toward what else those hours might be worth doing instead of cutting them, but there are three more items on the agenda, 15 minutes left in an hour that's already running long, and a room half-checked-out toward the next meeting.

The cost-savings read isn't wrong. It's just the only idea that got any airtime.

By the following week, the number is sitting in the forecast as a bottom-line improvement, and HR has scheduled a meeting to talk through the actual headcount reductions. Nobody chose this outcome over another one; it's just the one with momentum, and momentum in a room with an hour on the clock beats an idea nobody had time to finish developing. The room did what rooms do under time pressure: it ran with the fastest, most defensible read, and by the time anyone might have asked a second question, the decision was already operational.

This is the mechanism I keep running into with insurance and financial-services leaders working through AI at scale. It isn't that no one owns the question of what to do with freed capacity. Someone owns it, in exactly the moment described above: usually whoever's in the room when the result lands, or Finance once it's in their model. The problem is they're answering a question nobody asked out loud: is this time worth more as a saving, or as something redirected? By default, the answer is savings, because savings is the fastest, most comfortable story a room on the clock can agree on.

There's a harder truth underneath the reflex, too. Even if the head of claims had been able to keep the floor, she probably couldn't have made the case: nobody had set up a way to measure what those hours would be worth doing something else. Under real forecast pressure, with downside risk already sitting in the numbers, the room isn't choosing the fast story over the slow one. It's choosing the only story it actually has data for.

The default doesn't hold up, and two firms now say so independently

Gartner surveyed 350 business executives this spring at companies with at least $1 billion in revenue. Eighty percent of the organizations that had piloted an AI or autonomous technology followed with a workforce reduction. But there was no meaningful ROI difference between companies that cut staff and those that didn't. The strongest returns weren't at the companies that cut deepest; they were at the ones using AI to make people more productive, not to replace them. Gartner's Helen Poitevin put it directly: chasing value through headcount reduction alone leads most organizations toward limited returns, not the returns they modeled.

Deloitte's research puts a number on the other half of that same gap. Eighty-four percent of organizations are increasing their AI investment. Only 20% report meaningful revenue impact. But organizations that redesign the work itself, rather than just removing roles, are roughly twice as likely to exceed their AI ROI expectations, and nearly two and a half times more likely to see real financial gains.

Two firms, two survey populations, the same finding: cutting the role doesn't reliably convert a technology gain into a business gain. Redesigning the work does, by a wide margin. This isn't a values argument about protecting jobs. It's a return argument, made with the same data the cost-saving case leans on.

Why the default survives unquestioned

Part of why this default never gets challenged is that the dashboard isn't built to challenge it. A rollout dashboard answers one question the week the tool launches: did the tool work? It was never built to ask the second question: now that the tool freed something up, what's the best use of it? Nobody updates the dashboard to ask that, because nobody built a version where the question has a place to live.

The result is a familiar split. Leadership sees a rollout that delivered the projected time savings and reads that as ROI, declared and closed. The people managing the work six months later are living inside whatever happened to that time, usually nothing or usually cost-cutting, and see a different number entirely. Both readings are accurate: they're reading two different moments, off two different instruments, and only one of those instruments ever looks past launch week.

This lands harder in insurance and financial services for a specific reason: the executive team is tracking results weekly, which is exactly the speed that produces a room like the one above. A real redesign case takes longer than a week to build. By the time underwriters or claims reviewers could show what redirected hours would be worth against loss ratios or retention, the quarterly external reporting cycle has already locked in the launch-week number as a win, and the budget conversation has moved on.

What interrupts the default

Naming the pattern doesn't fix it, so here's what I'd tell a claims or underwriting leader sitting inside this right now.

Put the redirection case on the roadmap when the rollout is designed, not after the results land. That claims leader's slide only had one story on it because only one story had data behind it. Building the other one is real work: further experimentation and analysis, beyond what it takes to simply validate that the tool works. Naming that work up front, as part of the rollout plan rather than an afterthought raised in the meeting, is what gives the room something to weigh against the savings read before momentum decides for everyone.

Reuse a review cycle you already trust. Regulated organizations already run disciplined quarterly and annual reviews for compliance and audit. Add one standing question to that cadence: what did we say this rollout would free up, and which path, saved or redirected, did it take? You don't need a new process. You need one more question inside a process that already has teeth.

Track what changed in the work, not what changed in usage. A login count says the tool got turned on. It doesn't say whether a reviewer, underwriter, or claims handler is doing anything differently on Thursday than in January: the real measure of whether freed time went anywhere.

The open question underneath this one

There's a third factor sitting under both of these that I don't think the data above fully answers, and I'd rather name it honestly than force a tidy conclusion: why doesn't anyone stop to ask the redirection question at all? Do organizations reward speed and visible activity over the slower work of finding a better use for freed time? Is the savings number just easier to defend than a redirection bet that might not pay off for multiple quarters? I don't have a clean answer, and I'd rather leave the question open than manufacture certainty. It's worth its own room, not a paragraph tacked onto this one.

What the data above does settle is narrower, and it's enough: cutting the role may feel like the safe, obvious way to capture value from AI. Two independent studies now say the opposite is the better path. The next time a rollout result lands in a room, and everyone reaches for the cost-savings read in the same breath, it's worth asking whether anyone had a number for the alternative, or whether the room just did what rooms do.


Amy Radin

Profile picture for user AmyRadin

Amy Radin

Amy Radin is a strategic advisor, keynote speaker, and Columbia University lecturer focused on why transformation succeeds or stalls in large, complex organizations. 

Drawing on senior leadership roles at Citi, American Express, and AXA, including one of the world’s first corporate chief innovation officer roles, she helps leaders build the capabilities required to absorb, scale, and sustain change.

Learn more at amyradin.com.

 

The Flaw in Most Policy Admin Systems

Many insurers mistake their system of record for a true policy administration platform, a confusion that now costs them speed, distribution reach, and competitive ground.

Policy Administration Platforms Versus Systems of Record

Ask a room full of insurance technology leaders whether their organization has a policy administration platform. Nearly everyone says yes.

Ask what that platform actually does beyond storing, retrieving, and displaying policy data, and the room tends to go quiet.

This is not a semantic issue, but a strategic one!

Across P&C, life, and health carriers, the terms "system of record" and "policy administration platform" are used almost interchangeably. But in practice, they describe two very different relationships between technology and the business it supports.

One preserves information, while the other operationalizes it.

The distinction matters more now than at any point in the last decade, because the cost of getting it wrong has changed. It used to show up quietly, as a slow IT backlog. Today it shows up publicly: a missed product launch, a rate change that can't go live before renewal season closes, a distribution partner who walks because integration takes months instead of weeks.

Understanding that difference is becoming fundamental as insurers reassess the role of insurance policy administration software in their broader transformation strategies. Moreover, modernization is no longer about replacing legacy applications. It is about building an operating foundation that enables continuous innovation, operational resilience, and faster decision-making.

The Cost of Confusing PAS with a System of Records

Three forces have converged to expose insurers whose "platform" is really a repository in disguise. These are:

I. Product Velocity

Specialty lines, embedded insurance, and usage-based products are compressing the time between an underwriting idea and a bindable product. Carriers used to multi-month product builds are now competing against MGAs and insurtechs that configure and test a new product variant in weeks.

II. Distribution Complexity

Policies originate through APIs, partner portals, comparison platforms, and embedded checkout flows. This is done not solely through agents keying data into a core system. A system built only to store the finished policy record cannot support real-time, multi-channel origination.

III. Margin Pressure

The cost of getting this wrong is now measurable, and it cuts both ways. BCG's research puts the failure rate of large-scale core system transformations at roughly 74%. And most of those failures trace back to insurers treating modernization as a system swap rather than an operating-model change. That risk profile is exactly why capability-led, incremental modernization increasingly wins out over wholesale replacement: it lets carriers gain product speed and integration reach without betting the whole transformation on a single, high-risk cutover.

None of these pressures are new. What has changed is the timeline. A decade ago, a slow product build was an internal frustration, absorbed quietly by underwriting and IT. Today, it is visible externally in the form of a distribution partner who chooses a faster-moving competitor.

Decoding the Repository in Disguise

A system of record is, at its core, a system of truth for stored data. It holds the authoritative version of a policy, including coverages, limits, endorsements, billing history, and document trail.

It is often very good at what it was built to do, such as auditability, compliance reporting, and a single reference point for policy status.

But where it falls short is in everything that happens before and around that stored record.

Product configuration is typically hard-coded or requires a vendor development cycle. Rating logic lives in spreadsheets, bolted-on rules engines, or the heads of a few actuarial and underwriting staff. Workflow runs on email and task lists rather than being orchestrated inside the system. Integration, where it exists, is point-to-point, brittle, and expensive to extend.

A system of record answers one question very well: what does this policy currently say?

However, it fails to answer the question that actually determines competitiveness: how quickly can we bring a new product to market, price it accurately, and route it through underwriting without manual intervention?

Take a mid-sized commercial lines carrier launching a cyber endorsement for its existing package policy. Legal and product teams finalize the wording in days. But the rating logic then has to be translated into something the development team can build, tested against the existing rating engine, and slotted into a release calendar that may already be full for two quarters.

Nobody lacks urgency here. The system was simply never designed to let underwriting or product teams make that change themselves.

That gap between what the business wants to do and what the system will let it do is where competitive advantage is won or lost.

The In-and-Out of Policy Administration System

A policy administration platform is built around the operating rhythm of the insurance business, not around the storage of policy data. Product, pricing, workflow, and data access are treated as first-class, configurable capabilities, not customizations layered on top of a repository.

The difference shows up immediately at the moment of a product launch or a rate change.

On a system of record: a change request, a development queue, a testing cycle, a release window measured in months.

On a true platform: a configuration exercise, carried out largely by business and product teams, tested in a sandbox, deployed on a schedule the business controls.

That, in a sentence, is the whole argument. A system of record preserves information. A policy administration platform operationalizes the insurance business.

Seven Capabilities That Separate a PAS from a Data Repository

The cyber endorsement above isn't an edge case. It's the everyday test every core system eventually fails or passes, and it's the reason all seven capabilities below have to work together, not in isolation.

1. Product Configuration

Underwriting and product teams should be able to define new products, coverages, and rating variables through configuration. That's what turns a six-month product build into a matter of weeks. Back to the cyber endorsement: on a real platform, the product team models the new coverage, attaches it to existing package products, and sets eligibility rules directly, with IT involved for governance and testing, not as the sole author of the change.

2. Rating and Pricing Built-In

Rating should live inside the platform as a governed, versioned, and testable capability. This matters most at the moment of a rate change, when actuarial teams need to model, test, and deploy new logic without a separate development cycle, and without risking a mismatch between the rate quoted and the rate bound.

3. Workflow That Runs Itself

Underwriting referrals, endorsement approvals, renewals, and exception handling- all of it should be orchestrated within the platform, with clear rules for what's automated and what needs a human. A system of record pushes this work out to people and email threads, which is exactly where errors and delays accumulate.

4. Access Data in Real Time

Underwriters, claims handlers, and distribution partners need current information at the point of decision, not a batch-refreshed snapshot from the night before. Real-time access is also what makes straight-through processing possible for low-complexity policies.

5. APIs as the Front Door

A platform is built to be consumed by other systems through documented APIs, not one-off interfaces built for a single use case. For instance, rating engines, comparison sites, telematics feeds, agency management systems, and embedded distribution partners. Exposing discrete functions such as issuance or renewal through APIs is often a more practical modernization route than wholesale replacement. That's precisely because it lets insurers extend capability incrementally.

6. Extensibility for What Hasn't Happened Yet

New products, jurisdictions, and distribution models will keep emerging. A platform extends into them without re-architecture. A system of record usually needs a parallel project or a separate vendor every time the business needs to do something it wasn't originally built for.

7. Configurability for the Business, Scalability for Growth

Configuration should sit with underwriting, product, and operations, not exclusively with IT. And the platform needs to scale, in transaction volume, product lines, and geographies, without the cost curve becoming a brake on growth.

Most carriers don't have all seven. Some have none. The question is which gaps are showing up in the operations right now.

Signs You're Still Running a Repository

Certain patterns recur across carriers that believe they have a platform but are, in practice, operating a repository. A handful of questions tend to surface quickly:

  • Does a product change routinely take a full underwriting cycle or longer?
  • Does rating logic live outside the core system, reconciled manually against what it produces?
  • Does IT hold the backlog for anything resembling configuration, while business teams submit tickets rather than making changes themselves?
  • Is every integration custom-built per partner, rather than a repeatable pattern?
  • Does renewal and endorsement processing depend on manual review because the workflow was never built into the system?
  • Does reporting on in-force business require a data extract and a separate analytics layer?

If more than one of these sounds familiar, the answer isn't a resourcing problem. It's an architecture built to store policies, not run a business, and no amount of additional headcount changes that underlying design.

The Stakes of Running the Insurance Business Solely on a System of Records

As business models shift toward composability, traditional core systems risk being reduced to little more than record keepers by the end of the decade. Here, product, pricing, and distribution logic will be managed in more agile layers around them. That framing captures the stakes precisely: insurers treating their core as a passive repository are, in effect, competing with one hand behind their back on product speed, distribution reach, and operational cost.

The benefits of the alternative are greater than those of sitting in isolation.

Faster product iteration compounds across every launch that follows. Straight-through processing lowers unit cost on every policy that passes through it, not just the first. API-first integration means each new distribution partner costs less to onboard than the last one did.

None of this shows up in a single quarter. It shows up over several product cycles, which is exactly why the gap between a repository and a platform is so often underestimated, right up until a competitor's speed becomes impossible to ignore.

By then, the gap is no longer a technology conversation. It's a market-share conversation.

It's little surprise, then, that insurers across P&C, life, and health lines are increasingly seeking modern policy administration software that can support this kind of agility, rather than treating core system replacement as a purely technical upgrade.

The Bottom Line

The confusion between a system of record and a policy administration platform is understandable. Both can look identical from the outside. Both will happily tell you what a policy currently contains.

The difference only becomes visible under pressure. For instance, when a new product needs to launch, when a rate change needs to go live before a renewal deadline, or when a distribution partner asks for an API instead of a batch file.

A system of record will always have a place in the insurance technology stack; audit and compliance requirements demand it. But it is not, on its own, a platform.

The insurers who compete effectively over the next decade will be the ones who have already made peace with that distinction. Meaning, treating product configuration, rating, workflow, and integration as capabilities to be built and governed, not afterthoughts bolted onto a repository.

A system of record preserves information.

A policy administration platform operationalizes the insurance business.

The gap between the two is, increasingly, the gap between insurers who set the pace of the market and those who follow it.

Are AI Systems Capturing Insurers' IP?

Insurers risk inadvertently transferring proprietary expertise to AI systems through everyday use, creating a vulnerability beyond traditional cybersecurity concerns.

AI Systems May Be Capturing Your Proprietary Knowledge

For at least the past two years, insurers have focused on an essential question: How can AI make us smarter?

Another concern is beginning to emerge.

Who, exactly, becomes smarter every time we use it?

The insurance industry has spent decades building intellectual capital that doesn't appear on any balance sheet. Underwriting judgment. Claims workflows. Fraud indicators. Distribution strategies. Product pricing logic. Regulatory expertise. Customer communications. The institutional knowledge that carriers, MGAs, and brokerage use to create a distinct competitive advantage from other businesses in their competitive space.

Today, much of that knowledge is quietly flowing into AI systems - oftentimes without the knowledge owners' (or originators') knowledge.

Not through a data breach.

Not through cybercrime.

But through ordinary, everyday business use.

The New Information Leak

When people think about information security, they typically picture hackers wearing hoodies in darkened rooms stealing customer records or ransomware shutting down operations. (Throw in some empty Mountain Dew cans to add extra "flavor" to the image…)

Generative AI introduces a different type of risk actor.

Insurance workers don't simply upload documents into AI systems. They explain how their business works. They refine outputs. They correct mistakes. They describe edge cases. They reveal why one underwriting decision differs from another. They basically fine-tune the model using the organization's life-blood – its processes, judgment, and expertise.

Each prompt adds context. Every correction adds nuance. Any successful interaction between a person and an insurance-trained LLM captures another piece of proprietary institutional knowledge.

Individually, these exchanges seem harmless. Collectively, they represent an organization's most valuable asset.

The Trojan Horse Problem

Spoiler alert for people who are still reading The Iliad before going to theaters to see The Odyssey: The ancient Achaeans didn't breach the gates of Troy by force.

They were invited inside.

That's why the "Trojan horse" analogy has gained traction among AI observers. The concern isn't that foundation model providers are intentionally harvesting proprietary information for competitive purposes. Rather, the architecture of AI creates a fundamental asymmetry: organizations must reveal increasingly detailed information about how they operate to receive increasingly valuable assistance.

The more context AI receives about your operations...

...the more effectively it can replicate (and share) your expertise.

Microsoft CEO Satya Nadella recently framed this as a "reverse information paradox," arguing that organizations effectively pay twice for AI: once financially, and again by revealing proprietary knowledge required to make the models useful. His observation reflects a growing debate across enterprise technology about ownership of prompts, feedback, workflows and organizational know-how.

Whether organizations agree with that assessment, it raises an important governance question for insurance CIOs/CISOs.

Insurance Has More At Stake Than Most Industries

Insurance isn't simply another knowledge business.

It is a judgment business.

Competitive advantages rarely come from a single algorithm or dataset. They're the result of thousands of successful decisions accumulated over years:

  • Why adjusters escalate certain claims.
  • How underwriters evaluate emerging risks.
  • Which variables consistently predict profitability.
  • How service teams de-escalate difficult customer situations.
  • Which regulatory interpretations have proven successful across jurisdictions.

These are not trade secrets, per se, but they are critical operational intelligence.

Unlike customer data, operational intelligence often isn't classified or labeled as confidential. Employees may share it with AI tools because they're simply trying to work faster.

Yet this institutional knowledge may ultimately prove more valuable than the documents themselves. And, not to belabor the Homeric allusions, the safety of this institutional intelligence can be an insurance business's Achilles Heel…

Why Governance Must Expand its Purview Beyond Privacy

Most AI governance discussions inside insurance organizations focus on familiar concerns:

  • Personally identifiable information
  • Regulatory compliance
  • Security controls
  • Model accuracy
  • Bias and explainability

These remain essential elements to a robust governance strategy.

But these may no longer be sufficient as the core of governance.

Organizations should also ask:

  • Which AI platforms retain prompts?
  • Can customer interactions be used to improve future models?
  • What proprietary workflows are employees revealing?
  • Which business processes should never leave controlled environments?
  • When should an organization rely on internally hosted or private AI models instead of public services?

Such questions nudge AI governance beyond compliance and into competitive strategy.

Institutional Knowledge Is Intellectual Property

Historically, insurers have protected code, customer databases, actuarial models, and other vital information.

Tomorrow's competitive asset may be something less tangible: the accumulated knowledge generated every day through interactions between employees and AI.

The irony is striking.

Organizations adopted AI to preserve and amplify institutional knowledge.

Without thoughtful governance, they may also be exporting it.

Insurers' response should not be to slow AI adoption. The lost productivity gains will be consequential across every insurance function from underwriting to claims to policy servicing.

But as organizations race to become AI-enabled, their practices should be centered around the principle that cybersecurity communities have understood for years:

The most valuable information isn't always the data you store. Sometimes it's the knowledge your people create.

The evolution of AI governance won't be defined around cybersecurity, privacy, or compliance concerns. It will also require insurers to identify, classify and protect institutional knowledge as another key strategic asset.

Organizations that rise to this challenge will capture AI's productivity gains without inadvertently teaching competitors how they do business. Those that don't may discover that the greatest risk wasn't exposing customer data; it was giving away the expertise that made them different in the first place.


James Ballot

Profile picture for user JamesBallot

James Ballot

James P. Ballot is an insurance research, thought leadership, and content strategy leader with more than a decade of experience helping industry, regulatory, business, consumer, and higher education audiences understand and navigate complex industry transitions.