Choosing Insurance Core Software: Build vs Buy vs Partner Decision Framework for Mid-Tier U.S. Carriers in 2026

Why choosing insurance core software matters in 2026

In my experience working with U.S. P&C carriers between $500M and $5B GWP, the choice of insurance core software is the single most consequential technology decision a CIO will make in a 5-year window. The wrong choice consumes the next 36-48 months of IT budget, locks the carrier into a multi-vendor service contract, and constrains every product launch the carrier wants to make. The right choice produces an 18-36 month implementation, manageable 5-year TCO, and an architecture the carrier can extend.

The decision matters because the realistic 5-year TCO for a mid-tier P&C core platform replacement ranges from $5M to $50M depending on which approach the carrier picks. The decision matters because the typical implementation timeline ranges from 18 to 48 months, with the vendor’s published claims usually closer to the lower end and the carrier’s actual experience usually closer to the upper end. The decision matters because once the choice is made, the carrier has effectively committed to a 7-10 year relationship with the platform vendor.

I run the company that has shipped 100+ insurance projects since 2003, and I review 40+ vendor RFP responses every year for mid-tier carriers in this exact decision. What I tell every CIO who calls me before they sign: “The vendor scoring matrix you are about to build will rank features. The features are not the decision. The decision is which of three structurally different approaches - Build, Buy, or Partner - matches your carrier’s actual operating reality. If you pick the wrong approach, no amount of feature scoring will save the project.”

For mid-tier carriers specifically, the choice matters more than it does for $5B+ enterprise carriers because the mid-tier has less budget cushion, less in-house IT scale, and less Board patience for a 36-month program that started as 12. The same vendor that works for a $10B carrier with 500 in-house engineers can fail for a $1.5B carrier with 80 in-house engineers - not because the vendor is bad, but because the mid-tier carrier is the wrong fit for the vendor’s operating model.

This article is the strategic decision framework deep dive that pairs with our Pillar Main on legacy-to-modern modernization for U.S. carriers in 2026. The Pillar Main covers the broader modernization context; this one is the focused vendor selection decision: Build versus Buy versus Partner, with named vendors, 5-year TCO scenarios, and the KOB scoring framework I use when I review carrier vendor decisions.

What is insurance core software?

Insurance core software is the integrated technology platform that handles a P&C insurance carrier’s primary operational workflows: policy administration (quote, bind, issue, endorse, renew, cancel), claims management (first notice of loss, adjudication, payment), billing and premium collection, underwriting workbench, reinsurance ceded reporting, and regulatory compliance. The core software serves as the system of record for policy and claim data, the audit trail for regulatory examinations, and the operational hub that connects to distribution channels, partner integrations, and data sources.

Modern insurance core software is built around a modular architecture where each domain (PAS, claims, billing, UW workbench, reinsurance) can operate as an independent service while sharing a unified policy and party model. The platform supports configurable insurance products, real-time API integrations with external systems, ACORD standards compliance (P&C AL3 and modern digital standards), and regulatory reporting against NAIC standards and state DOI requirements.

What core software is not

Core software is not just a Policy Administration System. The PAS is the largest component, but the modern core platform includes claims, billing, and underwriting as integrated modules sharing a common data model. Vendors who sell standalone PAS are selling one piece of the core; vendors who sell core platforms package the modules together.

Core software is not generic enterprise software. Generic ERP platforms (SAP, Oracle, Microsoft Dynamics) do not handle insurance regulatory complexity, ACORD standards, or insurance-specific data models. Carriers who try to fit insurance into generic enterprise software discover the gap at month 18, and it costs millions to fill.

Core software is not the same as agent portal, customer self-service portal, or document management system. Those are adjacent systems that integrate with the core. The core is the system of record; the adjacent systems serve the core.

The five categories of core software approach

Each approach has a sweet spot and a failure mode. The remaining sections walk through Build, Buy, and Partner specifically. The Hybrid approach is covered in our insurance software integration with legacy systems article and applies when the carrier is not ready for a full replacement.

The mid-tier carrier dilemma - between expensive build and oversized enterprise

The mid-tier P&C carrier in the $500M-$5B GWP range faces a structural dilemma that does not exist at the extremes of the market. The largest carriers ($10B+) can afford to build proprietary platforms with 500+ engineer teams - Liberty Mutual, Travelers, Berkshire Hathaway, USAA all have meaningful in-house engineering. The smallest carriers (under $200M) typically pick a SaaS package and configure it. The mid-tier is squeezed between two paths that do not fit.

The build path is too expensive

In my experience, building a modern P&C core platform from scratch costs $30-80M over 36-60 months for a mid-tier carrier with 80-150 in-house engineers. The math: 30-50 senior engineers at fully loaded $250-350K per year, for 3-5 years, plus product, design, testing, infrastructure, and the opportunity cost of those engineers not working on customer-facing differentiation.

A few exceptions: P&C insurtechs with VC funding (Lemonade, Root, Branch, Hippo) built proprietary platforms because their distinctive distribution and underwriting models required it. Carriers with 100+ engineer in-house teams and specific competitive reasons to own the platform. Carriers whose core IP is the technology rather than the underwriting expertise. For everyone else - which is most mid-tier carriers - the math does not work. I have worked with two mid-tier carriers in the last 36 months who started down the build path and reversed course at month 18 when the engineering cost reality became visible.

I recommend most mid-tier carriers reject the build option early. The conversation usually goes: “We could build it ourselves” - and yes, in principle, but the carrier would spend 5 years building what a vendor has spent 15 years building, would burn $30-80M doing it, and would still need ongoing engineering capacity to maintain the platform. The build option is the right answer 5-10% of the time.

The buy enterprise path is too oversized

The opposite path - buying enterprise core software from Guidewire or Duck Creek - is the industry standard for $5B+ enterprise carriers. Guidewire has the deepest P&C feature set, the largest reference customer base, and the most mature implementation methodology. For Allstate, Progressive, Liberty Mutual, Nationwide, and similar enterprise carriers, Guidewire is the right answer. The implementation is 24-48 months, the 5-year TCO is $40-100M, and the platform fits the carrier’s operating scale.

For a mid-tier carrier writing $1.5B GWP in 8 states, the same Guidewire implementation is structurally oversized. The platform’s configuration depth requires a 30+ person implementation team. The vendor’s services cost runs $15-30M for the initial deployment. The ongoing platform maintenance requires a Guidewire-certified team that mid-tier carriers struggle to retain. The mid-tier carrier ends up paying for capabilities the enterprise carrier needs but the mid-tier never uses.

The conversation I have with Sarah-level CIOs at $1-3B GWP carriers: “We are not Allstate. We cannot afford full Guidewire. We also cannot build from scratch. What is the third option?” That third option is what Section 6 (mid-tier packages) and Section 7 (co-development partnership) cover.

Build option - when it makes sense (and when it usually does not)

The build option means the carrier’s own engineering team builds the core platform from scratch - typically over 36-60 months with 30-50 senior engineers and a $30-80M total investment. The platform is owned by the carrier, customized to the carrier’s exact workflows, and free of vendor lock-in.

When build actually makes sense

In my experience, the build option is the right answer in four specific scenarios:

Scenario 1: The technology IS the product. Insurtech players whose competitive differentiation depends on a proprietary platform - Lemonade’s instant claims, Root’s telematics underwriting, Branch’s bundle distribution model. The platform is the moat.

Scenario 2: The carrier has $10B+ GWP and 300+ in-house engineers. At enterprise scale, build is viable because the in-house team can sustain the platform indefinitely. Berkshire Hathaway, Liberty Mutual, Travelers, and similar carriers run substantial in-house engineering.

Scenario 3: The carrier writes a niche specialty line with no commercial platform fit. Some highly specialized programs (parametric weather, cyber for specific industries, novel reinsurance structures) have no commercial platform that fits, and build becomes the default.

Scenario 4: The carrier wants to be a technology company. A few mid-tier carriers genuinely want to differentiate on technology and have committed to building the engineering organization that supports it. They are uncommon but real.

When build fails

Build fails when the carrier underestimates the engineering scale required, when the project starts as “we will build the core ourselves” and discovers at month 24 that the team has 30% of the platform delivered, when key engineers leave during the project (typical attrition over 36-60 months is 40-60%), and when the carrier’s business changes (new products, M&A, regulatory shift) during the build and the platform has to be re-architected mid-flight.

In our coverage of the 8 critical implementation challenges in insurance software, I walk through the specific failure modes of long-running insurance software projects. The build option amplifies all eight failure modes because the timeline is longer and the scope is larger.

My take on build for mid-tier carriers

For mid-tier U.S. P&C carriers in the $500M-$5B GWP range, build is the right answer roughly 5-10% of the time. The remaining 90-95% should pick Buy or Partner. The carriers I have advised who chose build and finished successfully had three things in common: a CEO committed to the technology bet over 5+ years, an engineering organization already at 100+ people before the project started, and a competitive position that genuinely required a proprietary platform. If any of the three is missing, the build option will fail.

Buy enterprise (Guidewire) - when it is right and when it is oversized

Buying enterprise core software means licensing Guidewire or Duck Creek as the core platform, contracting with a system integrator (Accenture, Deloitte, EY, KPMG, or boutique Guidewire specialists), and running a 24-48 month implementation. The 5-year TCO for a mid-tier carrier ranges from $25M to $50M depending on scope, with the higher end being the realistic case for multi-line carriers.

When Guidewire is the right answer

Guidewire is the industry standard for $5B+ enterprise carriers. For Allstate, Progressive, Liberty Mutual, Travelers, Nationwide, and similar carriers, Guidewire’s deep feature set, mature implementation methodology, and large reference customer base make it the default choice. The 24-48 month implementation is acceptable at enterprise scale because the carrier has the budget and the IT operating model to absorb it.

For $5B+ carriers, the question is not whether to use Guidewire - it is which Guidewire products (PolicyCenter, ClaimCenter, BillingCenter) and which deployment model (Guidewire Cloud, Guidewire InsuranceSuite on-premise, hybrid). Duck Creek is the established alternative for similar carrier profiles with a stronger cloud-native commitment.

When Guidewire is oversized for mid-tier

For mid-tier carriers writing $500M-$3B GWP, Guidewire is often architecturally oversized. The platform’s configuration depth assumes a 30+ person implementation team plus ongoing 10-15 person operational support. The vendor and SI services cost $15-30M for initial deployment plus $3-8M annual maintenance. The platform delivers capabilities that enterprise carriers need (massive scale, multi-region deployment, complex reinsurance structures) but mid-tier carriers do not use.

The honest framing I give CIOs at mid-tier carriers considering Guidewire: “You can deploy Guidewire. It will work. The question is whether you can afford to deploy and operate Guidewire at scale. If you can, it is a defensible choice. If you cannot, you will spend 24-36 months struggling against the platform’s enterprise assumptions, and at the end of it the system that works will be a fraction of what Guidewire actually offers.”

The system integrator question

Enterprise Guidewire and Duck Creek deployments require system integrator services. The major SIs (Accenture, Deloitte, EY, KPMG) charge $250-500/hour for Guidewire-certified resources, with implementation team sizes of 25-50 people for 18-30 months. The SI cost typically exceeds the Guidewire license cost over the implementation period.

Mid-tier carriers should evaluate the SI selection as a separate decision from the platform selection. The carrier is signing up for two relationships: one with Guidewire (the platform) and one with the SI (the implementation and ongoing services). Both relationships are 5-10 year commitments.

Buy mid-tier package - honest vendor comparison

The mid-tier package option means buying a configurable insurance core platform from a vendor whose business model is mid-tier rather than enterprise. The major vendors in this category are Sapiens, Insurity, EIS, Majesco, and Decerto with the Higson product. Each has a sweet spot and a failure mode, and the carrier’s job is to match its profile to the vendor’s actual fit rather than the vendor’s marketing positioning.

Honest comparison of mid-tier alternatives

In my experience reviewing 40+ vendor RFP responses per year, the mid-tier vendor landscape sorts into specific niches based on the carrier’s primary need. Every vendor will say they “do everything.” The honest framing is which vendor genuinely is the best fit for which carrier profile.

Sapiens - strongest in life and annuity (IDIT, P&C, ALIS product lines). For P&C-focused mid-tier carriers, Sapiens is a capable choice but the platform’s L&A heritage shows in commercial lines depth. Sweet spot: mid-tier multi-line carriers with significant L&A exposure.

Insurity - SaaS-first deployment with a P&C focus and strong workers compensation and specialty programs depth. Sweet spot: mid-market P&C carriers wanting a SaaS deployment model with proven configurability for specialty programs.

EIS - cloud-native platform with a stronger focus on digital-first carriers and MGAs. Sweet spot: insurtech-adjacent carriers and MGAs prioritizing cloud-native architecture and customer experience capabilities.

Majesco - embedded insurance and cloud-native focus, with growing depth in personal lines and small commercial. Sweet spot: carriers pursuing embedded distribution strategies or small commercial automation.

Decerto Higson - mid-tier P&C carriers $500M-$5B GWP needing configuration flexibility, reinsurance depth, or specialty program support, often with a co-development partnership model. Sweet spot: mid-tier carriers wanting a configurable platform that absorbs product variation without forcing custom code, with the vendor’s engineering team available for shared development on carrier-specific extensions. Higson is not the right fit for $5B+ enterprise carriers - Guidewire is the industry standard there.

The mid-tier vendor selection trap

The selection trap I see most often: carriers run an RFP, all five vendors respond with similar-looking pitches, the scoring matrix produces a near-tie, and the carrier defaults to the lowest price or the most familiar brand. Both defaults are usually wrong.

The decision is not feature parity (every vendor has the major features). The decision is operating model fit. Sapiens implementations have a different rhythm than Decerto implementations. Insurity SaaS deployment requires different IT operating model than on-premise Sapiens. EIS cloud-native is a different commitment than Insurity SaaS. The mid-tier package option works when the carrier’s IT operating model and the vendor’s implementation model match.

For mid-tier P&C carriers considering Higson specifically, the BNP Paribas Cardif claims centralization on Higson and the Allianz Poland product management transformation are verified case studies showing the configurability pattern in production. The platform fits when the carrier wants configuration depth plus engineering partnership, not just configuration.

Partner with co-development vendor - the third path

The partner option is the third path between mainstream Buy and full Build. The carrier picks a vendor whose business model includes co-development - where the vendor’s engineering team is available to extend the platform with carrier-specific capabilities, where the carrier’s own team can contribute to the codebase, and where the relationship is structured as a multi-year engineering partnership rather than a software license plus annual support fees.

What partnership actually means

The partnership model has four distinguishing characteristics that separate it from traditional vendor relationships:

1. Shared engineering capacity. The vendor provides a senior engineering team that works alongside the carrier’s team on platform extensions, not just standard configuration. The team understands insurance domain and modern software architecture, and the engagement is sized to the carrier’s actual needs rather than the vendor’s services revenue targets.
2. Configurable platform with carrier IP retention. Carrier-specific business logic stays with the carrier as IP. The vendor’s platform provides the infrastructure, the data model, and the core capabilities; the carrier owns the unique extensions. This matters at renewal time and at exit time.
3. Honest scope and timeline conversation. The partnership includes the vendor saying “we should not build that” when the carrier asks for something that would create technical debt. I have signed off on Decerto walking away from RFPs where we were not the right fit. That discipline is what makes a partnership rather than a vendor sale.
4. Multi-year relationship structure. The contract is structured as a 5-7 year engineering partnership, not a 1-year SaaS subscription. The pricing reflects the deeper relationship; the value reflects the deeper engagement. Over 20+ years of building Decerto, the partnerships that have lasted longest are the ones that started with the carrier and vendor both committing to that relationship structure on day one.

When partnership fits

In my experience, the partnership model fits mid-tier carriers who need configuration depth that mainstream Buy cannot provide, but who do not need the full build approach. The partnership combines vendor platform maturity with carrier-specific extensibility. The 5-year TCO ranges from $8M to $20M for a mid-tier P&C carrier, which is meaningfully lower than enterprise Buy and dramatically lower than Build.

The partnership requires both parties to commit to a longer-term relationship. The carrier commits to working with one vendor’s engineering team for 5-7 years; the vendor commits to a long-term success of the carrier rather than just the next contract. The structural commitment is what makes the model produce different outcomes than vendor-led implementations.

The mid-tier P&C partnership reality

Decerto’s positioning is intentional: we are not the cheap option, and we are not the enterprise option. We are the right-sized option for $500M-$5B GWP P&C carriers who need configuration flexibility, reinsurance depth, or specialty-line capabilities that enterprise platforms struggle to deliver without significant custom services. Warta’s multi-line modernization with Higson is a documented partnership example - the relationship has spanned multiple lines of business and multiple modernization phases rather than being a single project.

For the broader composable architecture pattern that supports the partnership model technically, our coverage of composable insurance and MACH for insurance leaders covers how configurable platforms with API-first architecture deliver partnership value at scale.

5-year TCO comparison and decision matrix

The 5-year total cost of ownership comparison is where the Build versus Buy versus Partner decision often shifts. Carriers tend to compare headline license costs and underestimate the implementation, services, integration, and operational costs that dominate the actual 5-year TCO. The honest TCO scenarios for a mid-tier U.S. P&C carrier in the $1B-$3B GWP range:

5-year TCO scenarios

These ranges assume a mid-tier carrier with $1-3B GWP, 4-8 lines of business, and 15-20 states of operation. Larger carriers or more complex programs run higher; smaller or simpler carriers run lower.

KOB scoring framework for vendor selection

The KOB framework is a structured scoring approach I use when reviewing carrier vendor decisions. KOB stands for Knowledge fit, Operating model fit, and Business model fit. Each dimension is scored 1-5, with the total score guiding the decision.

Knowledge fit (1-5): Does the vendor have deep insurance domain expertise specifically in your line of business, geographic footprint, and regulatory profile? Vendors with shallow insurance knowledge score 1-2; vendors with deep multi-line P&C expertise score 4-5.

Operating model fit (1-5): Does the vendor’s implementation methodology match your carrier’s IT operating model? Enterprise vendors require enterprise SI teams; mid-tier vendors require mid-tier IT operating models; SaaS vendors require SaaS operating model commitment. Mismatched operating models score 1-2.

Business model fit (1-5): Does the vendor’s commercial relationship structure match your carrier’s needs? Software license plus annual support is one model; SaaS subscription is another; co-development partnership is a third. Vendors offering only the wrong model for your carrier score 1-2.

A vendor scoring 12-15 (high in all three dimensions) is a strong fit. A vendor scoring 8-11 is a possible fit with caveats. A vendor scoring below 8 is the wrong vendor regardless of features. The framework prevents the feature-checkbox trap that produces near-tie scoring matrices.

Decision matrix - 5 criteria × 4 options

For most mid-tier U.S. P&C carriers in the $500M-$5B GWP range, the decision matrix points to either Buy mid-tier package or Partner co-development as the structurally appropriate choice. Build is the right answer 5-10% of the time; Buy enterprise (Guidewire) is the right answer when scale, complexity, or specific feature requirements justify the cost.

FAQ

How do you choose insurance core software for a mid-tier P&C carrier?

You choose insurance core software by first deciding among four structurally different approaches: Build from scratch (typically wrong for mid-tier), Buy enterprise from Guidewire or Duck Creek (often oversized for $500M-$5B GWP), Buy a mid-tier package from Sapiens, Insurity, EIS, Majesco, or Decerto, or Partner with a co-development vendor for shared engineering. The approach selection determines the 5-year TCO range ($8-65M), implementation timeline (18-60 months), and vendor relationship structure. Feature scoring matters only after the approach decision is made.

Should you build or buy insurance software in 2026?

Mid-tier P&C carriers should typically buy or partner rather than build. Build makes sense for roughly 5-10% of mid-tier carriers - specifically insurtechs whose technology is the product, $10B+ enterprise carriers with 300+ in-house engineers, carriers writing niche specialty lines with no commercial platform fit, and carriers genuinely committed to becoming technology companies. For the remaining 90-95% of mid-tier carriers, Build’s $40-65M 5-year TCO and 36-60 month timeline do not produce proportional competitive advantage.

What is the difference between Build, Buy, and Partner for insurance software?

Build means the carrier’s own engineering team creates the platform from scratch - $40-65M over 36-60 months, no vendor lock-in, full customization. Buy means licensing a vendor’s platform with implementation by the vendor or a system integrator - $10-50M over 18-48 months, vendor lock-in proportional to platform depth, configuration-driven customization. Partner means a longer-term co-development relationship where vendor engineering capacity is part of the deal - $8-20M over 18-30 months, lower vendor lock-in than Buy, deeper extensibility than mainstream Buy.

How do mid-tier carriers choose technology partners?

Mid-tier carriers choose technology partners by evaluating Knowledge fit (insurance domain depth), Operating model fit (implementation methodology match), and Business model fit (commercial relationship structure) - the KOB framework. A vendor scoring high in all three dimensions is a strong fit; a vendor scoring poorly in any dimension is the wrong vendor regardless of features. The decision should be made before the RFP scoring matrix produces a near-tie among technically capable vendors.

What is the 5-year TCO for insurance core software for a mid-tier carrier?

The 5-year total cost of ownership for a mid-tier U.S. P&C carrier ($1-3B GWP) ranges from $5M to $65M depending on the approach. Hybrid Strangler Fig integration runs $5-15M, Partner co-development runs $8-20M, Buy mid-tier package runs $10-25M, Buy enterprise (Guidewire) runs $25-50M, and Build from scratch runs $40-65M. The TCO includes license, services, integration, and operational costs over 5 years - not just initial implementation.

How long does insurance core software implementation take?

Insurance core software implementation timeline depends on the approach. Build from scratch takes 36-60 months. Buy enterprise (Guidewire) takes 24-48 months. Buy mid-tier package takes 18-30 months. Partner co-development takes 18-30 months. Hybrid Strangler Fig integration produces first production go-live in 18-36 months with full legacy retirement at 36-48 months. Vendor claims of 12-month implementation should be evaluated skeptically against the carrier’s actual complexity profile.

What is the KOB scoring framework for insurance vendor selection?

The KOB framework scores vendors on three dimensions: Knowledge fit (insurance domain depth specific to the carrier’s lines of business and regulatory profile), Operating model fit (implementation methodology match with the carrier’s IT capacity), and Business model fit (commercial relationship structure alignment). Each dimension is scored 1-5; total scores of 12-15 indicate strong fit, 8-11 indicate possible fit with caveats, and below 8 indicate the wrong vendor. The framework prevents feature-checkbox scoring matrices from producing misleading near-ties.

Why does Decerto position Higson as not for $5B+ enterprise carriers?

Decerto positions Higson for mid-tier P&C carriers $500M-$5B GWP because that is where the platform’s configurable architecture and co-development partnership model produce the best fit. For $5B+ enterprise carriers, Guidewire is the industry standard with deeper feature coverage and a mature enterprise implementation methodology. We are honest about where Higson fits and where it does not, because the wrong vendor fit is the most expensive mistake a carrier can make.

Talk to Decerto about IT Audit and Architecture Review

Choosing insurance core software is the single most consequential technology decision a mid-tier carrier CIO makes in a 5-year window. The decision determines whether the next 36-48 months produces a working modern platform or an extended implementation struggle that consumes the IT budget and undermines the carrier’s competitive position. Getting this decision right matters more than getting any individual feature right.

In my experience, every carrier that has tried to make this decision from vendor demos has spent 6-12 months and significant consulting fees before reaching the same answer that a vendor-neutral 4-hour IT Audit would have produced. Vendor demos optimize for showing what the platform can do; they do not produce honest comparison across approaches, and they do not produce vendor-neutral 5-year TCO calibration.

What we offer: a free 4-hour IT Audit with a senior architect from Decerto. The output is a 25-30 page report covering the carrier’s current state, the approach recommendation (Build vs Buy enterprise vs Buy mid-tier vs Partner vs Hybrid), the KOB scoring framework applied to relevant vendors in the carrier’s context, and a 5-year TCO range with documented assumptions calibrated to the specific carrier profile.

It is not a product demo or a sales pitch. The audit can recommend that the carrier should stay on its current platform with targeted integration rather than committing to a full replacement, or that Guidewire is the right answer for a specific carrier even though we are not in that segment. I have written both recommendations more than once. The output is an honest vendor-neutral assessment the CIO can defend to the Board.

The 20+ year context: Decerto has shipped 100+ insurance projects since 2003, with carriers including Allianz Poland (product management on Higson), Warta/HDI/Talanx Group (multi-line modernization), BNP Paribas Cardif (claims centralization on Higson), and InterRisk (Vienna Insurance Group). The verified case studies are documented on our case study page. Higson, our flagship product after 20+ years of insurance delivery, is built for mid-tier P&C carriers $500M-$5B GWP. Higson is not the right fit for $5B+ enterprise carriers - Guidewire is the industry standard there. We are honest about that, and we are honest about where Higson does fit.

Sources and citations

1. Gartner. (2025). Magic Quadrant for SaaS P&C Insurance Core Platforms, North America.
2. McKinsey & Company. (2024). Insurance 2030: The Impact of AI on the Future of Insurance.
3. Deloitte. (2026). 2026 Global Insurance Outlook.
4. Datos Insights (formerly Aite-Novarica Group). (2024). P&C Insurance Technology Vendor Selection and IT Spend Research.
5. NAIC. (2024). Insurance Industry Cybersecurity and Vendor Risk Management Standards.
6. NY DFS. (2025). Cybersecurity Regulation 23 NYCRR 500, as amended (vendor and third-party risk management requirements).
7. ACORD. (2025). Property & Casualty Data Standards (AL3 and XML).
8. S&P Global Market Intelligence. (2024). Insurance Industry Data and Market Intelligence.