Listen to the Article
Insurers have spent the better part of a decade acquiring technology designed to modernize how they underwrite, distribute, and service policies. Many of those investments have not returned what was projected, and not because the tools were wrong, but because the conditions required to make them work were underestimated at the point of purchase. This article explores where insurtech initiatives most commonly break down, from integration problems to workforce readiness.
Legacy Infrastructure: The Integration Problem That Precedes Everything Else
Most insurtech platforms are architected for modern environments: cloud-native, API-first, built to connect. Most carrier core systems, by contrast, are not. Many established insurers’ policy administration platforms, billing engines, and claims systems were built decades ago. Although many were extensively customized over time, most of these solutions were never designed to share data cleanly with external tools.As a result, integration becomes a project in its own right, often turning larger in scope and cost than the original implementation plan assumed. Timelines extend, and budgets absorb the overrun. And in the interim, staff are often asked to operate across both the legacy system and the new platform simultaneously, creating duplicate workflows that slow the very processes the new tool was meant to accelerate.In practice, this is where many insurtech deployments quietly lose momentum. The platform is live in a technical sense, but it is operating alongside the old system rather than replacing it. New tools get used for some functions and bypassed for others. As a result, the productivity gains projected at the business case stage never fully materialize.The integration problem also affects data downstream. When two systems run in parallel without clean data exchange, records diverge, creating reconciliation work. This, in turn, adds operational cost and introduces errors into processes that require high precision, such as underwriting and claims.Carriers that have navigated this most effectively tend to share one approach: they treat integration as a strategic workstream with its own governance, rather than a technical task that is managed solely by the insurtech vendor.
Workforce Readiness: The Skills Gap Behind the Dashboard
A platform deployment does not transfer capability. When employees lack the skills, confidence, or incentive to use a new tool effectively, adoption stalls, no matter how well the technology performs.Replacing legacy infrastructure ensures systems can talk to each other, but what happens when the people operating those systems do not understand what the technology is doing or trust its output? Without building workforce readiness, a new, faster way of working will remain out of reach.In insurance specifically, many operational roles have been shaped by years of working around system limitations. Experienced underwriters, claims handlers, and customer service staff have developed their own methods, and those methods work well enough to create resistance when new tools arrive promising improvement. Because the new process is slower to learn, and the output looks different from what they are used to checking, this kind of resistance is often practical. The first step toward change is ensuring key employees fully understand the case for deploying insurtech and what they, specifically, can gain from it. Without this, maintaining enthusiasm becomes too challenging.Another thing is training. A platform rollout accompanied by a few hours of vendor-led onboarding is unlikely to shift working habits built around years of manual underwriting or claims processing. Investing in training means empowering teams to navigate the new systems as deftly as possible and create value along the way. This creates the foundation for long-term success.
Data Governance: The Quality and Risk Problem
Insurtech tools, particularly those built around pricing, risk selection, and customer analytics, are only as reliable as the data they receive. Most carriers understand this in principle, but many implementations lack this in practice.The data governance problem in insurance has several layers. Historical data in legacy systems is often incomplete, inconsistently formatted, or structured around older product lines and business rules no longer in use. Cleaning and standardizing that data before it feeds a new platform takes time and resources that implementation budgets rarely fully account for.Ownership is a second issue. In many carrier organizations, data sits across multiple departments, each with its own standards, access controls, and interpretation of what a given field means. When a new tool needs to draw on claims data, underwriting data, and customer data simultaneously, unclear data ownership creates delays and, in some cases, compliance exposure.Regulatory requirements add another layer of constraint. Data residency rules, privacy obligations, and audit requirements vary by market and line of business. A tool that works cleanly in one jurisdiction may require significant reconfiguration in another, and those requirements are not always visible at the point of procurement.Investing in AI ops and data governance before deployment, rather than alongside it, shortens time-to-value for new platform rollouts while helping insurers manage risk. Transparent usage and well-defined governance structures make it easier to monitor progress and stay aligned with strategic objectives.Getting data infrastructure right upfront requires no small amount of resources, but getting it wrong tends to surface later as mispriced risk, failed audits, and tools that cannot deliver what was demonstrated in the vendor environment.
Culture and Leadership: Where Mandates Meet Resistance
Technology mandates issued from the executive level do not automatically translate into behavior change at the operational level. For many insurers, adoption decisions are made in practice by middle management, and that layer is often the least prepared and least incentivized to drive change.Middle managers in insurance operations are typically measured on throughput, accuracy, and cost control. A new platform that disrupts established workflows, at least in the short term, creates pressure on all three. Without making it clear that adoption success is directly tied to performance expectations, and changing how success is measured during this transition period, the most rational response for many managers is to minimize disruption to their team’s output. That means staff defaulting to familiar methods wherever the new process creates friction.This pattern is well documented in enterprise technology adoption broadly, and insurance is not an exception. If the process changes touch licensed activities and compliance obligations, the cost of a failed adoption extends beyond lost productivity to regulatory exposure and audit risk.Leadership attitudes and behaviors can either stall or drive insurtech adoption across the organization. What happens when executives and department heads do not make it a practice to use underwriting analytics or neglect to highlight that pricing decisions were informed by predictive risk models? Simply put, no amount of internal communications or mandatory training will convince the rest of the organization that these tools represent a genuine shift in how the carrier operates.Moreover, holding operational leaders accountable for adoption metrics alongside performance metrics gives middle managers a concrete reason to prioritize the transition over short-term throughput protection. At the organizational level, consistency between what leadership says about technology and how much it is actually used determines whether an insurtech investment transforms operations or simply adds to the technology stack.
The Common Thread
Each of these four challenges shares the same consequence: they convert technology investment into operational complexity rather than improvement. Legacy integration delays the benefit, workforce gaps limit adoption, and data quality undermines output. To top it all off, cultural resistance keeps old methods alive long after new ones are available.Insurance carriers that treat these as implementation details to be resolved after go-live tend to find them compounding at an alarming rate. Meanwhile, those that factor these issues in before the platform goes live are sure to recover their investment faster and with less organizational disruption.Ensuring the technology works is only part of the insurtech investment equation. The main question is: How soon will your organization be ready to start using it, and what can you do to get there as quickly as possible?
