Instanda is one of the most visible names in policy administration. It sponsors the conferences, takes the stand space and runs the marketing, so for many buyers it is the first system that comes to mind when a no-code platform is mentioned. The product itself is a software-as-a-service platform on Microsoft Azure, with a licence fee that wraps hosting, maintenance and support into one number [1], and INSTANDA MAX (launched in March 2026) extends it into complex commercial and non-admitted lines [2].

Visibility is not the same as fit. Being present at every event tells you a vendor has a marketing budget, not that its system is the right answer for your operating model. Buyers on review sites such as Capterra and G2 describe a real bedding-in period, configuration that takes time to master and a reliance on the vendor for parts of the user experience [3][4]. Pricing is bespoke rather than published, which makes early comparison harder than it should be [1]. The sensible move is to put two or three credible alternatives next to Instanda and score them against the same requirements before anyone signs anything.

The policy administration system is the part of the stack that holds the definitive record of who is insured, for what risks and under what terms. It is the engine that calculates premium, drives mid-term changes and renewals, and feeds billing and claims. For most carriers and MGAs it is the single most consequential piece of software they buy, and replacing it is a multi-year commitment rather than a quick swap. That is exactly why the choice deserves more scrutiny than a vendor demo allows, and why a like-for-like comparison against Instanda is worth the effort before you commit.

This piece looks at five alternatives that earn a place on that shortlist. They sit at different points on the market, from enterprise heavyweights built for tier-one carriers to lean systems aimed at MGAs and brokers who want to be trading within a fortnight. For each one I have set out who it suits, where it is strong, where it frustrates, what is known about price, how it connects to the rest of your technology and how it actually feels to use. There is no ranking here and no running order to read into. The right answer is the system that removes the most friction from the operating model you genuinely want to run.

Duck Creek Technologies

Duck Creek is the name that turns up on almost every enterprise property and casualty shortlist. The company was founded in Boston in 2000, is backed by Vista Equity Partners and holds Leader status in Gartner's Magic Quadrant for the category [5]. Its core proposition is breadth. Duck Creek Policy, Billing and Claims run on a shared Intelligent Core, with a low-code Product Factory for modelling coverages, rules and rating, and an Active Delivery model that keeps the SaaS version current. For a large carrier with a deep book and a sizeable IT function, that breadth is the draw.

The strengths are real. Reviewers on G2 and Gartner Peer Insights consistently praise the configurability of the suite across the full policy lifecycle and the scale it handles [5]. Duck Creek maintains a forms library of more than 10,000 documents covering ISO, AAIS and NCCI circulars, with a circular adoption tool to help carriers decide what to take on [6]. Its integration ecosystem runs to more than 2,000 partners through the Content Exchange, with managed integrations that Duck Creek maintains and enabled integrations the carrier manages [5]. The platform is deployed on Microsoft Azure and leans on Azure services for search, storage and logging [6]. The rating engine is built in.

The weaknesses follow directly from the breadth. Configuration of that depth needs specialist skills, which usually means experienced consultants or a dedicated in-house team. Gartner Peer Insights reviewers note that version upgrades with heavy customisation can take many months and expert help, and several flag a data architecture that makes integration and analysis harder than expected [5]. The user interface draws the most criticism. More than one G2 reviewer describes it as basic and dated, and the overall G2 score sits around 3.9 out of 5 [7]. Implementation cost, timeline and complexity are the recurring negative themes across the review sites [5].

On price, Duck Creek does not publish list figures. It is a subscription model structured by module, user count and term, priced for enterprise budgets rather than for a new MGA finding its feet. SelectHub's analysts place the entry point above $1,000, but the real number for a multi-module deployment is far larger once implementation and services are added [8]. Duck Creek suits large carriers and complex MGAs that have the money and the people to harness it. Smaller and more nimble operators tend to find the weight a poor trade.

Genasys

Genasys is the platform I would put in front of any mid-market insurer, MGA or broker who likes the Instanda pitch but wants more of the core in one place. It has been serving the insurance industry for close to 30 years, is headquartered in London with offices in South Africa, and unifies policy administration, claims and billing in a single cloud platform rather than stitching those functions together from separate modules [9]. That single-core design is the difference that matters day to day, because the policy that calculates the premium, the billing that invoices it and the claim that pays against it all read from the same record.

The functional depth is built for the work MGAs and delegated-authority businesses actually do. Genasys handles complex rating, multi-currency, multi-jurisdictional tax, co-insurance, capacity splits and delegated authority arrangements out of the box, and supports alternative models such as parametric, micro and embedded insurance [11][12]. The no-code product builder ships with more than 350 pre-configured templates, so teams configure and launch products without writing code or waiting on developers [9]. Speed-to-market is where customers see it. King Price grew its premium income from around R500 million (roughly £21.5 million) toward R4 billion (roughly £172.5 million) on the platform [10], and Genasys cites a client taken from start to a market-ready product in ten days [11]. New business, mid-term adjustments, cancellations and renewals all live in the one system.

Connectivity is a clear strength and the answer to the most common reason core projects stall. Genasys is built on an open API architecture with more than 450 documented RESTful endpoints, so external systems can create, read and update data across the policy, claims and billing modules [9]. That covers integration with pricing engines, CRM systems, general ledgers, premium finance providers, data enrichment services, payment platforms and distribution partners [9]. The "citizen developer" model lets a customer's own team amend and build products in real time, which removes the over-reliance on the vendor that frustrates so many buyers of rigid systems [12]. The platform supports complex insurance structures across multiple regions, with native handling of the binder regulations that govern delegated authority in markets such as South Africa and the delegated-authority frameworks the FCA and Lloyd's expect in London, so the audit trail a capacity provider asks for is there by design rather than bolted on later [13].

Usability is treated as a first-class concern rather than an afterthought. The platform gives a real-time single view of each customer across policies, documents, claims and communications, with dashboards designed for underwriters, brokers and back-office staff. Document generation is strong, with tokenised templates and live data producing on-brand policy, claims and customer documents, plus bordereaux generation and reconciliation for commissions, claims and insurer reporting [12]. Genasys has been recognised by Celent, by CNBC and Statista and by BusinessCloud as one of the better insurance technology platforms available, and its client roster includes Simplyhealth, Hamilton, GuardRisk, Arma Karma, Hayes Parsons, CTU and Cornish Mutual [9].

On price, Genasys runs a flexible commercial model based on gross written premium processed through the platform [10]. That GWP-linked approach is worth weighing carefully against the per-seat and per-module structures elsewhere, because it ties what you pay to the premium you write rather than to the size of your team. For a scaling MGA that wants its software cost to track its book, that alignment is attractive.

The honest limitations are about reach rather than capability. Genasys does not have the global brand recognition of Duck Creek or Sapiens, and a tier-one multinational that wants thousands of pre-built North American statutory forms on day one will find the giant suites carry more of that specific content. As with any core platform, configuration is real work and a migration is a project, not a switch you flip. For the mid-market and the delegated-authority world it is built for, though, the combination of one unified core, deep connectivity, no-code control and premium-linked pricing is the strongest blend on this list.

Socotra

Socotra is the platform to look at if your team has engineers and you want a clean, modern core to build on. It is cloud-native and API-first in the literal sense, with every capability exposed through a consistent and well-structured API. Customers include IAG, AXA and Symetra, and the company reports more than 70 product launches and 15 migrations across property and casualty and life [15]. Poncho Insurance in Australia is one of the named builds [14]. Socotra positions itself as the most mature modern core, and the architecture backs a lot of that up.

The standout strength is the data model. Socotra represents products through a policy, exposure and peril hierarchy with characteristic versioning, which lets teams model a wide range of product structures through configuration rather than custom code, with native auditability across the lifecycle. Gartner Peer Insights reviewers single this out as genuinely well thought through [15]. Scale is the other strength. In an AWS-audited test, Socotra handled more than 11,000 policies per minute across a system holding over 10 million policies, with sub-90-millisecond average response times. Customers average better than 99.997% uptime across 48 backward-compatible upgrades a year, which removes the version-upgrade pain that dogs older systems [14]. All data is available through the Socotra Data Lake, with clean paths into Snowflake, Databricks and Azure Data Factory [14].

The weaknesses are the flip side of that flexibility. Socotra gives you a core, not a turnkey product. SelectHub and Gartner Peer Insights reviewers both describe limited out-of-the-box functionality, which means you build much of the frontend and many features yourself, and a learning curve that rewards fluency in the underlying concepts before teams can make sound decisions [15][16]. One detailed Gartner review describes renewal and instalment workflows as areas that benefit from careful upfront architecture and sometimes external orchestration, and notes documentation gaps that you fill through support and trial and error [15]. The honest summary from that reviewer is that Socotra is a strong choice for greenfield builds and modernisation provided you treat it as a platform engineering effort.

Connectivity is the point of the product, so it is excellent, with webhooks, plug-in points and a real-time event system alongside the API. Usability depends entirely on what you wrap around the core, since the configuration-over-code approach and domain-specific concepts take time for business users to absorb. On price, Socotra uses a subscription model driven by usage and chosen modules. SelectHub cites an entry range of $500 to $1,000, though the genuine number is bespoke and scales with deployment [16]. Socotra is well matched to tech-forward insurers and MGAs that value technical independence and have the engineering resource to use it.

Sapiens

Sapiens is the established global suite on this list. Founded in 1982, it runs more than 600 insurers across 30-plus countries and employs over 5,000 people, with operations spanning North America, Europe, the Middle East and Asia Pacific [17][18]. For property and casualty its main offering is IDITSuite, a modular core covering policy administration, claims, billing and customer engagement across personal, commercial and specialty lines, built for insurers, MGAs and brokers. Sapiens took the Celent XCelent award for policy administration in EMEA and APAC in 2025, and analysts at Gartner and Celent rate it a category leader [19].

The strengths come from four decades of domain depth. Sapiens covers the full lifecycle and spans multiple lines, including life and workers' compensation and reinsurance, under one vendor. It is multilingual and multicurrency, highly configurable, and carries the regulatory knowledge that comes from operating in dozens of jurisdictions. The platform is proven at enterprise scale, supporting carriers that process millions of policies a year. Recent investment in cloud enablement on AWS and Azure, in AI and analytics through the embedded DataSuite, and in low-code configuration through pre-built "Smart Packs" shows a long-standing vendor modernising its stack. Integration runs through the API Conductor (ACE), with a Java and .NET base, microservices and REST APIs [19].

The weaknesses are the familiar ones for a large, long-established suite. SelectHub reviewers describe a steep learning curve and an interface that needs training to navigate [20], and Gartner Peer Insights carries several accounts of implementation timelines that slipped, with one reviewer noting a committed timeline that in hindsight was never achievable [17]. Offshore configuration has caused communication friction for some customers during first builds [17]. SectorPunk's review makes the broader point that the legacy roots can mean slower adoption of cloud-native patterns than born-in-the-cloud rivals [18].

Price puts Sapiens firmly in the enterprise bracket. SectorPunk reports minimum engagements above $500,000 with hourly rates in the $150 to $350 range [18], and SelectHub lists an annual starting figure around $500,000 [20]. ITQlick estimates implementation alone from $50,000 for smaller deployments to well beyond $500,000 for large ones, with customisation and training adding more [21]. Sapiens suits mid-to-large carriers that want a proven full-stack replacement from a single vendor with deep regulatory coverage, and that can absorb the cost and the implementation effort that come with it.

Insly

Insly is the budget-conscious, fast-to-launch option built specifically for brokers, MGAs and small-to-mid insurers, mostly across Europe. Founded in Tallinn in 2013, it runs a team of around 80 and a cloud-native platform built on Azure with a .NET backend and a React frontend [22][26]. The pitch is accessibility. Insly delivers a multi-tenant SaaS product that brokers and MGAs can start using within weeks, and its MGA packages advertise going live in 7 to 14 days, a published transparency that most vendors on this list avoid [23].

The strengths are ease of use, speed and domain fit. Insly covers the whole non-life lifecycle from quote-to-bind through policy administration, claims, billing, accounting, reporting and commission tracking, with a drag-and-drop tool for building automations and bordereaux reporting baked in [26]. Its FormFlow AI product captures broker submission data in any format and removes the re-keying step into quote-and-bind systems [26]. SectorPunk rates the multi-country compliance highly, with regulatory reporting across the UK, the Baltics and Scandinavia from one platform [22]. The modular approach lets a business start with what it needs and add functionality as it grows. SelectHub records a 98% user satisfaction score across 35 reviews, with buyers praising how intuitive the dashboards are even for less technical staff [24].

The weaknesses match the size and focus of the company. The 80-person team is small for a SaaS vendor in a regulated industry, which SectorPunk notes caps the ceiling, and the European focus shows in the markets it knows best [22]. SelectHub and Software Advice reviewers report occasional bugs and gaps in customer support, and the real-time quote feeds over XML connections carry a slight delay when gathering comparative prices [24]. This is not a system aimed at tier-one carriers with very complex multinational portfolios.

Connectivity is solid for the segment, with open APIs, carrier integrations and self-service portals for brokers, insurers and clients. On price, Insly is the most transparent here. Its MGA software is advertised from €5,000 per month [23], SelectHub lists an entry point around $49 per user per month [24], and ZipDo cites roughly €99 per user per month depending on users, policies and modules [25]. Insly is a pragmatic choice for brokers and MGAs that want modern, domain-specific software without an enterprise budget or a year-long implementation. The trade is reach and depth: a buyer planning to write specialty business across several continents will outgrow it, but a broker or MGA digitising European books will find the value hard to beat.

How to choose

Feature lists are the wrong place to start, because every vendor on this page can produce one that looks complete. The better approach is to score each option against your own operating model, your gross written premium, your distribution and your appetite for engineering work, using the same demo script and the same written scenarios for all of them. The enterprise suites, Duck Creek and Sapiens, give breadth and pre-built regulatory content, and they ask for time, money and specialist skills in return. Socotra gives a clean, fast, API-first core with the lowest ceiling on flexibility, on the condition that you bring developers. Insly gets brokers and smaller MGAs trading quickly at a published price. Genasys sits in the mid-market with policy, billing and claims unified, deep connectivity and premium-linked pricing.

Three questions separate the contenders faster than any feature matrix. Ask how pricing is structured, GWP-linked against per-seat or per-module, and model it against your three-year growth plan. Ask who owns product configuration after go-live, because a system you cannot change without raising a vendor ticket becomes a constraint within a year. Ask how upgrades land, since the difference between continuous backward-compatible releases and a heavy periodic upgrade cycle is enormous over a contract's life. Reference calls with customers who run the system at your scale will tell you more than any sales deck.

For insurers, MGAs and brokers in the mid-market who want their core in one place, configurability without vendor lock-in and a cost that tracks the premium they write rather than the headcount they carry, Genasys is the platform I would put at the top of the shortlist. Whatever you choose, choose it against your own requirements rather than someone else's.

References

Pricing figures below come from vendor pages where published and from third-party review aggregators otherwise. Bespoke and aggregator pricing is directional and should be confirmed with the vendor. Sources accessed June 2026.

[1] Instanda. "Digital Insurance Solutions: Built for Agility and Control." instanda.com/platform-overview

[2] ProgramBusiness. "INSTANDA MAX Launches to Enable AI-Powered Large-Scale Underwriting for Commercial Insurers." 31 March 2026. programbusiness.com/news/instanda-max-launches-to-enable-ai-powered-large-scale-underwriting-for-commercial-insurers/

[3] Capterra. "Instanda Software Pricing, Alternatives and More 2026." capterra.com/p/137071/Instanda/

[4] Software Finder. "INSTANDA: Pricing, Free Demo and Features." softwarefinder.com/customer-service-software/instanda

[5] RFP.wiki. "Duck Creek Technologies: Rating Snapshot, Score and Reviews." rfp.wiki/specialty-industries/saas-pc-insurance-core-platforms-north-america/duck-creek-technologies

[6] Celent (reprinted by Duck Creek). "Policy Administration Systems: P&C Insurance, North America Edition." duckcreek.com/wp-content/uploads/2024/07/DCT-Celent-Reprint-Policy-Admin-Vendors-NA-2023.pdf

[7] G2. "Duck Creek Policy Reviews 2026." g2.com/products/duck-creek-policy/reviews

[8] SelectHub. "Duck Creek Reviews 2026: Pricing, Features and More." selecthub.com/p/insurance-software/duck-creek/

[9] Genasys. "Insurance Software for Insurers, MGAs and Brokers" (homepage). genasystech.com/

[10] Genasys. "Policy Admin Refresh July 2025." genasystech.com/policy-admin-refresh-july-2025/

[11] Genasys. "Modern Policy Administration System for Insurers and MGAs." genasystech.com/policy-administration/

[12] Genasys. "MGA Insurance Software: Modern, Cloud-Based Platform." genasystech.com/product/mga-insurance-software-solutions/

[13] Genasys. "What Is Policy Administration Software? 10 Critical Uses." genasystech.com/what-is-policy-administration-software/

[14] Socotra. "Enterprise Core Platform for Insurance Carriers." socotra.com/

[15] Gartner Peer Insights. "Socotra Platform Reviews and Ratings 2026." gartner.com/reviews/product/socotra-platform

[16] SelectHub. "Socotra Reviews 2026: Pricing, Features and More." selecthub.com/p/insurance-software/socotra-insurance/

[17] Gartner Peer Insights. "Sapiens Insurance Platform Reviews and Ratings 2026." gartner.com/reviews/product/sapiens-insurance-platform

[18] SectorPunk. "Sapiens International Review 2026: Pricing, Pros and Cons." sectorpunk.com (Sapiens International review)

[19] Sapiens. "IDITSuite for Property and Casualty." sapiens.com/property-and-casualty/iditsuite/

[20] SelectHub. "Sapiens Reviews 2026: Pricing, Features and More." selecthub.com/p/insurance-software/sapiens-insurance/

[21] ITQlick. "Sapiens P&C Reviews 2026: Real Pros, Cons and Expert Value Verdict." itqlick.com/sapiens-p-c

[22] SectorPunk. "Insly Review 2026: Pricing, Pros and Cons." sectorpunk.com/en/reviews/insly

[23] Insly. "MGA Software: Low-Risk Insurance Software." insly.com/en/mga-insurance-software/

[24] SelectHub. "Insly Reviews 2026: Pricing, Features and More." selecthub.com/p/insurance-software/insly/

[25] ZipDo. "Top 10 Best Insurance Broker Management Software of 2026." zipdo.co/best/insurance-broker-management-software/

[26] Insly. "2025 Top Insurance Software Products for MGAs." insly.com/en/blog/top-insurance-software-products/

Policy administration software is where an insurance policy lives from quote to renewal, and for decades it has also been where speed goes to wait. Ask underwriters or product managers at an insurer or MGA where their best ideas stall, and many point to the change request queue for the policy admin system.

That is changing. The next generation of policy administration software is open, configurable by business users, extensible without touching the core code, and delivered as continuously updated cloud software. This piece sets out what that shift means for insurers and managing general agents, and how to plan around it.

The cost of the old model

The numbers explain the move. Celent has found that insurers spend the majority of their IT budgets, commonly between 70 and 80 per cent, on maintaining legacy systems rather than building new capability.¹ The installed base is old and expensive to keep alive, which is why investment keeps flowing into replacement.

Why legacy hurts. Many in-force platforms were designed decades ago for paper files and static products. Launching a new product can take months and a specialist developer. Data sits in silos, so a complete view of the policyholder is hard to assemble. Closed architectures make it difficult to connect modern tools.

From monolith to composable

The architectural answer is composability. Instead of one monolithic suite, the modern system unbundles core functions, rating, quoting, document generation, issuance, endorsements and billing, into discrete services exposed through documented APIs. Datos Insights calls the emerging pattern a skinny core, where carriers assemble best-in-class components rather than buying one closed suite.²

API-first is the enabler. When every capability is an endpoint, integration friction drops. Accenture has shown how a process such as first notice of loss can be broken into small API services and recombined into new digital journeys.³ Datos Insights also notes that large insurers have largely finished core replacement, and smaller specialty insurers are now the active buyers.²

No-code configuration and who controls change

The biggest day-to-day change is no-code and low-code configuration. A product manager, actuary or underwriter changes a product, a rate table or a workflow through a visual interface, with no developer and no vendor change request. Gartner forecasts that 70 per cent of new applications built by organisations will use low-code or no-code technology by 2025, up from less than a quarter in 2020.⁴

Speed needs governance. Putting configuration power in business hands creates a risk of ungoverned change. KPMG has warned that low-code adoption without defined controls leads to shadow IT.⁵ The platforms that handle this well build guardrails into the tool: sandboxed changes, peer review, version control and IT sign-off for structural edits. Configuration with a full audit trail is an asset in a regulated industry.

Plugins, extensions and surviving the upgrade

Extensibility is where good architecture pays off over years. The historic problem was that customisation broke on upgrade. Insurers customised a core system heavily, then found the next release wiped out their changes, which is the upgrade-lock that froze many carriers on old versions.

Build on top, not inside. The modern model keeps customer-built extensions separate from the core. Users deploy plugins that sit on top of the platform and read and write through APIs. Because they never modify the core, they carry forward when the platform updates. A validated extension for fraud checks or document reading can be adopted in days rather than built from scratch.

Cloud-native delivery and the evergreen platform

Underpinning all of this is cloud-native, SaaS delivery. The distinction that matters is between cloud-hosted, a legacy system lifted onto cloud infrastructure but still carrying monolithic logic and manual upgrades, and cloud-native, a system built as small services with continuous integration and deployment.

Always on the current version. Continuous deployment means features, compliance fixes and new products ship without scheduled downtime, and every customer runs the latest release. The multi-year upgrade project goes away. Microservices also contain failure, so a problem in one service does not stop the rest, and each service scales independently when claim volumes surge.

AI in policy administration, kept realistic

AI in policy administration is real but uneven, and worth describing precisely. The dependable uses today are document ingestion, risk scoring, underwriting triage and straight-through processing for well-defined risks. Hiscox, working with Google Cloud, reported cutting some London Market specialty quote times from around three days to roughly three minutes using generative AI.⁶

Agentic AI needs the right foundations. Agentic systems that carry out multi-step tasks rather than just scoring are moving from pilot to production. They only work in environments that are cloud-native, modular and rich in clean data, which is the same architecture this shift describes. Regulation is now a hard constraint. The EU AI Act, the FCA's Consumer Duty and the NAIC Model Bulletin all require explainable, auditable automated decisions.⁷

Embedded insurance raises the stakes on APIs

Embedded insurance, cover sold inside another company's purchase journey, is the clearest commercial reason to expose policy administration capabilities through APIs. Deloitte has warned that if a fifth of the United States personal motor market moves to embedded distribution by 2030, at least 50 billion dollars in premium could shift away from traditional channels.⁸

Real-time, partner-facing APIs. To sell through a retailer's checkout or a bank app, a carrier must expose quote, bind and pay as APIs a partner can call in real time. A monolithic system with poorly documented interfaces cannot do this without expensive middleware. This is the composable model applied to distribution, where the policy administration system becomes one of many front ends calling shared underlying services.

What it means for MGAs and carriers

The two audiences face different versions of the same shift. For MGAs the calculus favours speed and low IT overhead. Conning put United States MGA premium at about 114 billion dollars in 2024, up 16 per cent on the year, outpacing the wider P&C market.⁹ A configurable cloud platform lets a small team launch and iterate without a large engineering function.

Capacity follows trust. Delegated authority is a substantial share of the Lloyd's market, and capacity providers back MGAs they can see clearly.¹⁰ The platform must produce audit-ready bordereaux and delegated authority controls natively. For larger carriers the problem is migration, and the pragmatic route is coexistence. New services are stood up around the legacy core and gradually take over functions until the old system retires. Thoughtworks recommends starting where legacy most constrains value, a single product line or claims process, rather than everything at once.¹¹

How to evaluate a future-proof platform

A short list of questions separates genuinely modern systems from repackaged legacy. Ask the vendor to show each one live in the demo rather than describe it.

The pattern across these questions is the same. The core is no longer meant to be the constraint. The platforms worth buying let a business change its own products, connect to anyone, extend without breaking and update without stopping. The ones that cannot do these things are the legacy systems of the next decade, whatever year they were built.

References

1. Celent. Insurance IT spending and legacy system maintenance research. Celent (Oliver Wyman Group), 2024.
2. Datos Insights. "P/C Policy Administration Systems: Key Trends Transforming Insurance in 2025." Datos Insights, 2025. https://datos-insights.com/blog/p-and-c-policy-administration-systems-trends-2025/
3. Accenture. Core insurance modernisation and microservices for claims and policy administration. Accenture, 2024.
4. Gartner. Forecast on low-code and no-code application development adoption to 2025. Gartner, 2021.
5. KPMG. Low-code governance and citizen development risk guidance. KPMG, 2024.
6. Hiscox and Google Cloud. Generative AI for London Market specialty underwriting, quote cycle time reduction. Hiscox media release, 2023 to 2024 (self-reported).
7. European Union, EU AI Act, 2024; Financial Conduct Authority, Consumer Duty, 2023; National Association of Insurance Commissioners, Model Bulletin on the Use of Artificial Intelligence Systems by Insurers, 2023.
8. Deloitte. Embedded insurance and personal lines distribution analysis. Deloitte Insights, 2024.
9. Conning. "2025 MGA Study." Conning, 2025. https://www.conning.com/about-us/news/ir-pr---mga-2025
10. Lloyd's of London. Delegated authority and binding authority market data. Lloyd's of London.
11. Thoughtworks. Legacy modernisation and incremental core replacement in insurance. Thoughtworks, 2024.

Sources note: the Deloitte personal motor figure is a forward projection. The Hiscox quote-time result is self-reported. Percentage figures from Celent and Gartner are widely cited industry estimates rather than audited counts.

Guidewire is the dominant core platform in property and casualty insurance. More than 540 insurers across 40 countries run on it, and for large carriers with deep pockets and multi-year transformation budgets it remains a credible choice. But dominance does not mean suitability for everyone. A growing number of insurers and MGAs are finding that Guidewire's enterprise pricing, proprietary Gosu scripting language and lengthy implementation cycles do not match what they actually need.

The reasons vary. Some organisations are scaling MGAs that need to be live in weeks, not years. Others are mid-market carriers tired of paying enterprise rates for functionality they will never use. A few are Guidewire customers themselves, frustrated by change order costs and the difficulty of making modifications without specialist developers. The common thread is a market that now has genuine alternatives, and buyers who are increasingly willing to explore them.

This article looks at five platforms that insurers and MGAs should evaluate alongside (or instead of) Guidewire: BriteCore, EIS Group, Genasys, Insurity and Openkoda.

Why Insurers Are Looking Beyond Guidewire

Guidewire's strength is its completeness. PolicyCenter, ClaimCenter and BillingCenter cover the full insurance lifecycle on a single data model, backed by more than 200 systems integration partners and a marketplace of pre-built applications. For Tier 1 carriers running complex, multi-line books at scale, that breadth is hard to replicate.

The trade-offs become visible further down the market. Implementation timelines for a full InsuranceSuite deployment commonly run 18 to 36 months, and total programme costs can reach eight figures before a single policy is written. Guidewire's proprietary Gosu language means that even routine configuration changes often require certified developers, creating ongoing dependency on external consultants.

Gartner Peer Insights reviewers have flagged excessive change order costs and difficulty handling large data schedules as recurring pain points. For MGAs and mid-market insurers operating on tighter margins and shorter planning horizons, these constraints can be disqualifying.

The broader market has also shifted. Cloud-native, API-first platforms now offer comparable core functionality with faster deployment, lower total cost of ownership and configuration tools that put control in the hands of business users rather than developers.

BriteCore

BriteCore is a cloud-native core platform used by more than 100 insurers across North America. It covers policy administration, billing and claims within a unified system and includes agent and policyholder portals as standard.

The platform's main strength is configurability. Users can tailor workflows, data fields and interfaces to match their specific processes without heavy development work. BriteCore also has strong API capabilities for connecting third-party systems such as payment gateways and analytics tools. Pricing starts at approximately $5,000 per month, which positions it well for mid-size carriers looking to modernise without Guidewire-level investment.

The limitation is geographic. BriteCore is focused almost entirely on the North American market. Insurers and MGAs operating in the UK, Europe or international markets will find less regulatory and product coverage out of the box. For US-based P&C carriers wanting a modern, affordable alternative to Guidewire, it is a solid choice. For anyone else, the fit is narrower.

EIS Group

EIS Group (now EIS) has OneSuite, a cloud-native, API-first core platform covering policy, billing and claims across all lines of business, including life, health and P&C. The company is based in San Francisco and works with carriers globally.

Multi-line capability is the distinguishing feature. Where most Guidewire alternatives focus on P&C, EIS supports composite insurers running personal lines, commercial, specialty and life products from a single platform. Industrial Alliance Auto and Home (iAAH), named Canada's best auto insurer in 2025 by Forbes, went live on EIS OneSuite in early 2026. EIS also holds MACH Alliance certification and ISO 42001 certification for responsible AI governance.

The trade-off is complexity. EIS is an enterprise platform with enterprise pricing and implementation requirements. For Tier 1 composite carriers looking to replace Guidewire across multiple lines of business, it is a genuine contender. For MGAs and smaller carriers, it may be more platform than they need.

Genasys

Genasys is a cloud-based insurance platform that brings policy administration, claims management and billing together in a single environment. Headquartered in London with offices in South Africa, the company has worked in the insurance industry for nearly 30 years and is used by enterprise carriers transacting hundreds of millions in GWP as well as fast-scaling MGAs launching new products in days.

Where Genasys differs most obviously from Guidewire is in speed to market. The platform has more than 350 pre-configured product templates across all lines of business and a no-code product builder that lets business users configure products, rating structures and workflows without engineering support. Implementation timelines reflect this. Arma Karma, a UK subscription-based MGA, received its foundational platform in one week. GENRIC Insurance went from concept to market in 50 days. King Price replaced legacy technology in six weeks.

Genasys Unify, the latest platform release, is cloud-native on Microsoft Azure and built on a MACH architecture (microservices, API-first, cloud-native and headless). It has 450+ documented REST API endpoints, enabling integration with pricing engines, CRM systems, general ledgers, premium finance providers and data enrichment services. That open architecture is particularly relevant for organisations building connected ecosystems rather than monolithic stacks.

Pricing follows a GWP-based model with an initial setup cost plus a monthly licence fee, designed to scale with revenue rather than penalise early-stage growth. Genasys is aimed at insurers and MGAs that need full-stack coverage (policy, claims and billing) without enterprise-tier pricing or multi-year implementation timelines.

The limitation is market presence. Genasys is less established in North America than Insurity or BriteCore, and its systems-integrator ecosystem is smaller than Guidewire's. Carriers that want a deep bench of local implementation partners, or that weight vendor scale and Tier 1 brand recognition heavily, may find fewer options around it.

Insurity

Insurity is the largest cloud software provider in P&C insurance by deployment count, with more than 400 cloud-based deployments and over $20 billion in insurance premiums running on its solutions. The company is used by 22 of the top 25 P&C carriers and 7 of the top 10 MGAs in the United States.

The platform covers policy, billing, claims and analytics, with particular strength in commercial and specialty lines. Insurity's analytics layer, powered by its proprietary Data Hub on Snowflake and the Valen Data Consortium, gives underwriting teams access to embedded risk intelligence that most competitors require third-party integrations to match. The company also invested $50 million in AI and R&D through its Andromeda release, adding AI-driven underwriting insights and real-time risk intelligence.

Insurity's scale and US market dominance make it a natural Guidewire alternative for large North American carriers. Like BriteCore, however, it is primarily a US-focused platform. Insurers and MGAs operating outside North America should weigh that geographic limitation.

Openkoda

Openkoda takes a fundamentally different approach. It is an open-source platform built on Java 17 and Spring Boot, released under the MIT licence, with the full codebase available on GitHub. For insurers who want to own their core technology rather than rent it, that distinction matters.

The platform provides pre-built modules for policy administration, claims processing and customer management, along with configurable workflows, client portals and embeddable quote forms. Because the codebase comes with foundational components (authentication, multi-tenancy, role-based security, dashboards), development teams can start adding insurance-specific logic immediately rather than rebuilding infrastructure. Openkoda claims this approach can deliver proofs of concept up to 60% faster than building from scratch.

The trade-off is self-sufficiency. Openkoda requires in-house development capability or a relationship with Openkoda's team in Wrocław, Poland, who provide custom development services. There is no managed SaaS option in the way that Genasys, BriteCore or Insurity provide. For technology-forward insurers with strong development teams who want full code ownership and zero vendor lock-in, Openkoda is a genuinely differentiated option. For organisations that want a managed platform they can configure rather than build, it is not the right fit.

What to Look for When Choosing an Alternative

The right platform depends on what you need it to do today, where you expect the business to be in three years and how much disruption you can absorb during the transition.

Full-stack vs modular is the first decision. If you need policy, claims and billing in one platform, the realistic options are BriteCore, EIS, Genasys and Insurity. If you want full code ownership and are prepared to build, Openkoda gives you the foundation.

Implementation timeline matters more than most buyers acknowledge upfront. A platform that takes 24 months to deploy carries real opportunity cost. Organisations that need to be live and writing business within weeks or months should weight speed to market heavily in their evaluation.

Total cost of ownership includes not just licence fees but implementation services, ongoing configuration costs and the availability (and cost) of skilled resources. Platforms that require proprietary language skills or certified consultants for routine changes will always cost more to run than those with no-code configuration tools.

For insurers and MGAs evaluating Guidewire alternatives in 2026, the market has moved far enough that compromise is no longer necessary. Several of these platforms now provide full lifecycle coverage, open API architectures and implementation timelines measured in weeks, at a fraction of Guidewire's total cost.

Frequently Asked Questions

What is the main disadvantage of Guidewire for smaller insurers? Cost and implementation time. Guidewire is built for large enterprise deployments, and total programme costs (licensing, implementation, integration and ongoing change orders) can run into millions. Implementation timelines of 18 to 36 months are common, which is impractical for MGAs and mid-market carriers that need to move faster.

Do these alternatives support multi-line and specialty business? It varies. EIS is built for composite insurers running personal, commercial, specialty and life from one platform. Insurity has particular depth in commercial and specialty lines. Genasys covers personal, commercial, specialty and London Market business. BriteCore is more focused on standard North American P&C. Match the platform's line-of-business strength to your actual book rather than assuming parity across vendors.

Is BriteCore available outside North America? BriteCore is primarily focused on the North American P&C market. Insurers operating in the UK, Europe or other international markets should consider platforms with broader geographic coverage.

How long do these platforms take to implement compared with Guidewire? Most cloud-native alternatives deploy in weeks to months rather than the 18 to 36 months common for a full Guidewire InsuranceSuite programme. Documented examples range from one week for a simple MGA setup to a few months for more complex enterprise deployments. Actual timelines depend on scope, data migration and integration requirements.

What makes Openkoda different from other Guidewire alternatives? Openkoda is open-source under the MIT licence, meaning insurers own the full codebase with no vendor lock-in. It requires development capability to implement, making it better suited to technology-forward organisations with in-house engineering teams than to those looking for a managed SaaS platform.

The insurance software market is full of platforms that claim to do everything. Strip away the marketing language and most of them do some things well, a few things badly and leave gaps that require bolt-on integrations, manual workarounds or expensive custom development.

For insurers and MGAs evaluating core systems in 2026, the question is not which platform has the longest feature list. It is which platform delivers the capabilities that actually determine whether a technology investment pays off or becomes an expensive anchor. Celent's 2024 policy administration research identified configurability, speed to market and ecosystem connectivity as the three factors most correlated with successful platform implementations¹. BCG's 2026 insurance technology outlook added workflow automation and unified data models as the capabilities most likely to drive operational improvement over the next three years².

These are the five features that matter most.

Unified Policy, Claims and Billing in a Single Platform

Most insurance technology stacks are assembled from separate systems. One platform handles policy administration, another manages claims, a third runs billing. Data moves between them through batch uploads, manual re-keying or fragile middleware integrations. The result is duplication, inconsistency and a permanent dependency on technical resources to keep the pieces connected.

A modern insurance platform eliminates this by bringing policy, claims and billing into a single environment with one shared data model. When a claim is filed, the platform already knows the policy terms, coverage limits and payment history. When a premium is collected, the billing module is working from the same risk and customer data as the underwriting team. There is no reconciliation between systems because there is only one system.

This architecture reduces operational overhead, eliminates data reconciliation errors and gives management a complete view of the book without pulling reports from multiple sources. For insurers still running separate systems for policy and claims, the cost of maintaining that separation, in staff time, error rates and reporting complexity, is almost certainly higher than they think.

When evaluating platforms, ask whether the vendor built policy, claims and billing as one product from the start or bolted them together through acquisitions and integrations. The difference shows up in data consistency, user experience and long-term total cost of ownership.

No-Code Product Configuration

The ability to design, test and launch insurance products without developer involvement is no longer optional. Markets move too quickly. Regulatory requirements change too frequently. And the cost of raising a change request with an internal development team or an external systems integrator for every product modification is unsustainable for any business that wants to compete on speed.

No-code product building means business users, not developers, control product configuration. Rating tables, question sets, coverage structures, document templates and compliance rules should all be created, modified and deployed through visual tools. Version control ensures that changes are tracked and reversible. Pre-configured templates accelerate the starting point so teams are not building from scratch every time.

The practical test is simple. If your organisation needs to raise a ticket, write a specification document or engage a consultant to change a rating factor or add a question to a quote journey, your platform does not have genuine no-code product configuration.

Look for platforms where the template library is deep enough to cover your lines of business out of the box, where the rating engine uses drag-and-drop logic rather than scripting languages and where multi-currency and multi-language support is native rather than bolted on. The best platforms in this space let business users build a market-ready product in days, not months.

Open API Architecture

An insurance platform that cannot connect easily to external systems is a closed loop. Modern insurance operations depend on dozens of third-party services: pricing engines, CRM systems, payment gateways, premium finance providers, data enrichment services, accounting platforms and distribution portals. If the core platform treats each of these integrations as a custom project, the total cost of ownership escalates with every connection.

An open API architecture provides documented, standardised endpoints that external systems can call to create, read and update data across the platform. It turns the core system into the operational hub of a connected ecosystem rather than a standalone application.

The benchmark is specificity. A platform that says it "supports API integration" is not the same as one that publishes hundreds of documented RESTful endpoints covering every module, with real-time eventing and webhook support. Ask vendors for their API documentation before you sign. If the endpoint count is vague, the coverage is incomplete or the documentation requires an NDA to access, those are warning signs.

Open architecture also matters for future-proofing. As AI-driven pricing models, embedded distribution channels and agentic underwriting tools mature, the insurers that can plug them in through standard APIs will adopt them faster and cheaper than those that need custom middleware for every new connection.

Configurable Workflow Automation

Insurance operations are process-heavy. New business workflows, renewal cycles, claims triage, settlement approvals, compliance checks, document generation and bordereaux reporting all follow defined sequences that vary by product, distribution channel and regulatory jurisdiction. When those workflows live in people's heads or in spreadsheets rather than in the platform, errors multiply and bottlenecks form.

Configurable workflow automation means the platform lets business users design, modify and deploy process workflows through visual tools. Auto-renewals, electronic FNOL triage, quote-and-bind journeys, settlement approvals and task assignments should all be configurable as rules-based processes that execute without manual intervention.

The distinction from basic automation is control. Many platforms offer automated renewals or claims assignment. Fewer let the business define the rules, exceptions and escalation paths themselves without writing code. A workflow engine that requires developer involvement for every rule change is not genuinely configurable. It is just automation with a bottleneck in a different place.

For insurers processing high transaction volumes, the difference between manual and automated workflow management is measured directly in headcount, processing time and error rates. Look for platforms where the workflow designer covers the full lifecycle (policy, claims and billing) rather than just one module, and where audit trails and role-based access are built in rather than added as afterthoughts.

Cloud-Native Deployment with Rapid Implementation

Cloud hosting alone is not enough. Many legacy platforms now offer a cloud-hosted version of software that was originally designed for on-premise deployment. The architecture underneath has not changed. Updates are still quarterly or annual. Scaling still requires infrastructure planning. And implementation still takes 12 to 36 months.

Cloud-native deployment means the platform was built for the cloud from the ground up. Microservices architecture. Continuous delivery. Elastic scaling. Updates that deploy without downtime. And implementation timelines measured in weeks, not years.

The proof is in documented deployments. Ask vendors to name customers who went live in under eight weeks. Ask for the case studies. If the fastest documented deployment a vendor can reference took six months, the platform was not designed for speed, regardless of what the architecture diagram says.

For insurers and MGAs evaluating platforms in 2026, implementation timeline should be treated as a first-order evaluation criterion, not an afterthought. Every month spent in implementation is a month of dual running costs, delayed product launches and unrealised revenue. A platform that can move from contract to live in weeks rather than months delivers commercial value before the first invoice is even paid.

The platforms that achieve this share common traits: pre-configured product templates that eliminate blank-page builds, no-code configuration that reduces consulting dependency, phased migration tooling that avoids big-bang cutovers and a deployment model where the vendor's implementation team has deep insurance domain knowledge rather than just technical certification.

How to Evaluate Against These Five Features

When assessing any insurance platform, ask five questions. Can it run policy, claims and billing in one system with one data model? Can business users configure products without developers? Does it publish documented APIs with specific endpoint counts and real-time eventing? Can the business design and modify workflows without code? And can the vendor demonstrate documented, named-customer deployments in weeks rather than months?

Any platform that cannot answer yes to all five is either incomplete, inflexible or both. The technology exists today to deliver all of them in a single, unified solution, and the platforms that do will be the ones that insurers and MGAs are still running in five years rather than replacing.

Frequently Asked Questions

Why does unified policy, claims and billing matter more than best-of-breed? Separate systems require integration, reconciliation and ongoing maintenance between each module. A unified platform eliminates data silos, reduces operational overhead and gives every team a single source of truth. The cost of maintaining separate systems is almost always higher than organisations estimate, particularly when factoring in staff time spent on manual data reconciliation.

What does no-code product configuration actually mean? It means business users can design, test and launch insurance products through visual tools without writing code or raising development tickets. This includes rating structures, question sets, document templates and compliance rules. If a change requires a developer or a systems integrator, it is not genuinely no-code.

How many API endpoints should a modern insurance platform have? There is no universal number, but specificity matters. Platforms that publish hundreds of documented REST endpoints across policy, claims and billing, with real-time eventing, give integration teams a concrete, predictable foundation to work from. Vague claims about "API support" without published documentation should be treated with scepticism.

Can cloud-native platforms handle enterprise-scale transaction volumes? Yes. Cloud-native architecture with microservices and elastic scaling is designed for exactly this. The strongest platforms in this space are used by enterprise carriers transacting hundreds of millions in gross written premium as well as early-stage MGAs launching their first products.

What is a realistic implementation timeline for a modern core system? It depends on scope and complexity, but platforms designed for rapid deployment can go live in weeks. If a vendor is quoting 18 to 36 months, the platform was not built for speed. Ask for documented, named-customer deployments with specific timelines before committing.

References

1. Celent, "Policy Administration Systems: Trends and Vendor Landscape," 2024.
2. BCG, "Agentic AI Can Power Core Insurance IT Modernization," January 2026. https://www.bcg.com

Choosing a core insurance platform is one of the most consequential technology decisions an insurer or MGA will make. Get it right and the business gains speed, flexibility and operational control. Get it wrong and you are locked into a multi-year programme that drains budget and slows everything else down.

Duck Creek Technologies and Genasys both offer cloud-based policy administration, claims and billing for the P&C insurance market. Both have real customers, proven deployments and credible technology. But they are built for different buyers, priced for different budgets and deployed on very different timelines. This article compares them across the dimensions that matter most to mid-market insurers and MGAs: speed, cost, control and flexibility.

Duck Creek at a Glance

Duck Creek is an enterprise P&C insurance platform covering policy, billing, claims, rating, loss control, reinsurance and distribution management¹. The company was founded in 2000, went public in 2020 and was taken private by Vista Equity Partners in March 2023 in a $2.6 billion all-cash transaction². More than $150 billion in annual premium now flows through Duck Creek's platform³.

The company reports double-digit year-over-year SaaS ARR growth and was named a Leader in the Everest Group 2025 Underwriting Orchestration Products PEAK Matrix Assessment³. Its ecosystem includes more than 6,000 trained systems integration resources and 80+ solution partners⁴. For large carriers with complex multi-line books and the budget to match, Duck Creek is a credible choice.

The concerns sit in three areas. Implementation complexity remains a recurring theme in user reviews, with Gartner Peer Insights reviewers citing difficult data architecture, excessive change order costs and performance issues when handling large data volumes⁵. SelectHub's 2026 analysis notes that Duck Creek's pricing structure, including licensing, implementation and ongoing maintenance costs, can be prohibitive for smaller organisations⁶. And Glassdoor reviews from current and former employees flag internal disruption since the Vista acquisition, including layoffs, capacity constraints and quality issues during upgrades⁷.

Genasys at a Glance

Genasys is a cloud-based insurance platform that unifies policy administration, claims management and billing in a single environment. Headquartered in London with offices in South Africa, the company has been serving insurers for nearly 30 years and is used by enterprise carriers and fast-scaling MGAs across multiple geographies⁸.

The latest release, Genasys Unify, is cloud-native on Microsoft Azure and built on a MACH architecture (microservices, API-first, cloud-native and headless). It has more than 350 pre-configured product templates across all lines of business and a no-code product builder that lets business users configure products, rating structures and workflows without developer involvement⁹. The platform has 450+ documented REST API endpoints⁸, enabling integration with pricing engines, CRM systems, general ledgers and data enrichment services.

Where Genasys differs most from Duck Creek is in who it is built for. While Duck Creek's natural buyer is a large enterprise carrier with a dedicated IT function and systems integration budget, Genasys is designed for organisations that want enterprise-grade functionality without enterprise-grade cost and complexity. That includes mid-market insurers modernising legacy systems, MGAs launching new programmes and delegated authority businesses that need to be live in weeks rather than months.

Implementation and Speed to Market

This is where the gap between the two platforms is widest.

Duck Creek's own pre-acquisition filings reference 1,100+ successful implementations⁴, but implementation timelines for full-suite deployments are measured in months, not weeks. Gartner Peer Insights reviewers note that version upgrades with heavy customisation frequently require many months and specialist assistance¹⁰. One reviewer described a Phase 1 implementation that finished 11% over the original timeline⁵.

Genasys operates on a different scale entirely. Arma Karma, a UK subscription-based MGA, received its foundational platform in one week. GENRIC Insurance went from concept to market in 50 days. King Price replaced legacy technology in six weeks⁹. These are not theoretical benchmarks. They are documented deployments from named customers.

For mid-market insurers and MGAs, speed to market is not a nice-to-have. Every month spent in implementation is a month without premium income, a month of paying dual running costs and a month of delayed product launches. An organisation that can be live on Genasys in weeks rather than months has a material commercial advantage over one that is still configuring Duck Creek.

Configuration and Ongoing Control

Both platforms are configurable, but the question is who does the configuring.

Duck Creek's customisation capabilities are well-regarded. G2 reviewers praise the out-of-the-box templates and the ability to manage different lines of business within a single environment¹¹. But that configurability comes with a dependency. Reviewers consistently flag that Duck Creek requires significant technical expertise for customisation, often necessitating experienced consultants or a dedicated in-house team⁶. API integration is described as "quite complex" by G2 users¹¹, and stored procedure modifications became harder after recent upgrades.

Genasys takes a different approach. The platform's no-code product builder puts configuration directly in the hands of business users, not developers. Products, rating tables, workflows and documents can be designed, tested and deployed without writing code. That distinction matters not just at implementation but on every day after it. An MGA that can modify a product or adjust a workflow without raising a change order has permanently lower operating costs and faster time to react.

For organisations that have (or want to build) a large internal development team, Duck Creek's configurability is a strength. For organisations that want to run lean and move fast, Genasys removes the bottleneck entirely.

Pricing and Total Cost of Ownership

Duck Creek does not publish pricing. Its model is modular, with costs determined by selected features, deployment method and transaction volume⁵. What is clear from user feedback is that total cost of ownership, including licensing, implementation services, change orders and ongoing maintenance, is at the enterprise end of the spectrum. SelectHub's 2026 analysis specifically flags cost as a barrier for smaller businesses⁶.

The Vista acquisition adds a layer of uncertainty. Private equity ownership typically brings pressure to optimise revenue per customer, and Vista's track record with enterprise software suggests pricing is unlikely to become more accessible for mid-market buyers.

Genasys uses a GWP-based pricing model with an initial setup cost plus a monthly licence fee⁹. The model is designed to scale with revenue, meaning an MGA writing £5 million in GWP is not paying the same platform costs as a carrier writing £500 million. InsTech's profile of Genasys notes that the platform is aimed at organisations that want to avoid multi-million-pound transformation programmes¹². For a mid-market insurer or MGA, the difference in total cost of ownership between the two platforms is likely to be substantial.

API Architecture and Integration

Both platforms offer API-based integration, but the depth and accessibility differ.

Duck Creek provides API connectivity and a partner ecosystem of 80+ solution providers. However, G2 reviewers describe API integration as complex, and Gartner reviewers flag the data architecture as difficult to work with for integration and analysis⁵.

Genasys has 450+ documented REST API endpoints covering policy, claims and billing modules⁸. The open architecture supports integration with pricing engines, portals, CRM systems, premium finance providers, payment platforms and data enrichment services. Documentation is publicly referenced and the endpoints are designed for modern, ecosystem-based architectures where the core platform connects to multiple specialist services.

For organisations building connected technology ecosystems, Genasys's API-first architecture is more accessible and better documented than Duck Creek's equivalent.

Which Platform Fits Which Buyer

Duck Creek is a strong platform for large enterprise carriers that need deep functionality across policy, billing, claims, rating, reinsurance and distribution. Organisations with $500 million+ in GWP, dedicated IT departments and the budget for a multi-year transformation programme will find Duck Creek a credible option, particularly in the North American market where its customer base and partner ecosystem are most concentrated.

For everyone else, Genasys is the more practical choice. Mid-market insurers that cannot justify eight-figure implementation programmes. MGAs that need to be live and writing business in weeks. Delegated authority operations that want enterprise-grade policy, claims and billing without enterprise-grade cost. Organisations that want business users configuring products rather than relying on external consultants for every change.

The insurance technology market has moved past the point where choosing the biggest vendor was the safest option. For mid-market insurers and MGAs in 2026, the safest option is the one that gets you live, keeps you agile and scales with your business. That is Genasys.

Frequently Asked Questions

Is Duck Creek or Genasys better for MGAs? Genasys is the stronger fit for most MGAs. Its no-code product builder, GWP-based pricing and implementation timelines measured in weeks make it better suited to the speed, budget and operational model of MGA businesses. Duck Creek is built for larger enterprise carriers with more complex requirements and bigger budgets.

How long does a Duck Creek implementation take? Timelines vary by scope, but full-suite Duck Creek deployments typically take several months. User reviews reference implementations running over timeline and budget. By comparison, Genasys has documented deployments from one week (Arma Karma) to 50 days (GENRIC Insurance).

Does Genasys cover the same lines of business as Duck Creek? Yes. Genasys covers personal lines, commercial, specialty and London Market business across policy administration, claims and billing. The platform has more than 350 pre-configured product templates and supports complex multi-line and multi-risk configurations.

Is Duck Creek more expensive than Genasys? Duck Creek does not publish pricing, but user reviews consistently describe it as an enterprise-tier investment. Genasys uses a GWP-based model designed to scale with revenue, making it significantly more accessible for mid-market insurers and MGAs.

What happened when Vista Equity Partners acquired Duck Creek? Vista acquired Duck Creek in March 2023 for $2.6 billion. Since the acquisition, Duck Creek has continued to invest in its platform, but Glassdoor reviews from employees flag internal disruption including layoffs and capacity constraints. The long-term impact of private equity ownership on product development and pricing remains to be seen.

References

1. Duck Creek Technologies, "SaaS Solutions." https://www.duckcreek.com/
2. SEC Filing, "Duck Creek Agrees to be Acquired by Vista Equity Partners for $2.6 Billion," January 2023. https://www.sec.gov/Archives/edgar/data/0001160951/000119312523004161/d442317dex991.htm
3. Duck Creek Technologies, "Formation '26 Kickoff," April 2026. https://www.duckcreek.com/blog/formation-26-kickoff-intelligent-core-insurance/
4. SEC Filing, "Duck Creek Technologies DEFA14A," January 2023. https://www.sec.gov/Archives/edgar/data/0001160951/000119312523006570/d449384ddefa14a.htm
5. Gartner Peer Insights, "Duck Creek Claims Reviews & Ratings 2026." https://www.gartner.com/reviews/product/duck-creek-claims
6. SelectHub, "Duck Creek Reviews 2026: Pricing, Features & More." https://www.selecthub.com/p/insurance-software/duck-creek/
7. Glassdoor, "Duck Creek Technologies Reviews." https://www.glassdoor.com/Reviews/Duck-Creek-Technologies-Reviews-E21155.htm
8. Genasys, "Insurance Software for Insurers, MGAs and Brokers." https://www.genasystech.com/
9. InsuranceNerd, "The Best MGA Platforms in 2026: Five Options Compared." https://medium.com/@edwardjameshalsey/the-best-mga-platforms-in-2026-five-options-compared-bdec6f743eca
10. RFP.wiki, "Duck Creek Technologies Rating Snapshot." https://www.rfp.wiki/specialty-industries/saas-pc-insurance-core-platforms-north-america/duck-creek-technologies
11. G2, "Duck Creek Policy Reviews 2026." https://www.g2.com/products/duck-creek-policy/reviews
12. InsTech, Genasys company profile (referenced in source 9).

There is no shortage of guides telling you how to choose a policy admin system. Most of them are written by vendors, commissioned by affiliates or assembled from product brochures with a thin editorial layer on top. They share a common feature: they are not particularly useful if you actually have to make the buying decision.

This comparison started from a different place. Over the past several months, I worked through the platforms that genuinely dominate buying conversations in the UK market, not every product with a listing on a software review site, but the systems that appear on shortlists at insurers, MGAs and Lloyd's managing agents with any regularity. The goal was to assess each policy admin system against the criteria that will actually determine whether an implementation succeeds or quietly drains budget for a decade.

The UK insurance market is not a small testing ground. It manages approximately £2.35 trillion of customer assets across around 90 million policies¹ and is expanding across commercial lines at a compound annual growth rate of 7.8% between 2019 and 2026.² The systems that administer those policies are, in many cases, older than the teams now responsible for maintaining them. McKinsey has documented cases of individual insurers running more than 300 active IT systems, with over 40% flagged for decommissioning and cost ratios running at twice the market average.³ That is not a technology problem in the abstract. It is a competitive problem with a measurable cost.

What surprised me in this process was not that legacy systems carry technical debt. Everyone knows that. What surprised me was how consistently procurement teams underweight the criteria that expose that debt fastest. Configurability, integration depth, time-to-quote and total cost of ownership are the measures that separate platforms at scale. They are also the measures least likely to appear in a vendor demo, where the best-case scenario is always what gets shown.

The comparison that follows covers the platforms that actually matter in the UK market, grouped by tier, and assessed on consistent criteria. Where a platform performs well, that is noted. Where the reputation exceeds the technology, that is noted too. Large-scale core system transformations fail more than 70% of the time, and almost a quarter become full write-offs.⁴ Some of that failure rate is attributable to change management. A significant portion is attributable to choosing the wrong system in the first place, often because the evaluation process was not rigorous enough to catch the problems that only appear after go-live.

This is an attempt at a more rigorous process, set out in full so you can apply it yourself.

The UK Policy Admin System Landscape in 2026

The UK policy administration system market is not homogeneous, and treating it as such is one of the more reliable ways to end up on the wrong shortlist. Platforms that work well for a Lloyd's syndicate writing complex specialty lines will often be poorly suited to a personal lines MGA needing rapid product iteration. Understanding which tier a platform belongs to is the first filter, not the last.

Tier 1: Enterprise incumbents. These are the platforms with multi-decade histories, global client bases and sales cycles measured in quarters. They dominate by volume of installed policies rather than by the pace of their development roadmap. Their strength is proven stability at scale. Their weakness is that stability and agility are not the same thing. Launching a new product on a legacy policy admin system can take between 18 and 24 months,⁵ a timeline that compounds badly when market conditions shift quickly. The 61% of insurers now investing in cloud platforms to enable real-time digital operations⁶ are often doing so precisely because their incumbent system cannot provide it natively.

Tier 2: Mid-market challengers. These platforms have been built or substantially rebuilt within the past decade. They carry enough maturity to handle complex insurance logic but are designed with configurability and integration in mind from the start. This tier is where the most interesting competition is currently happening, and where the gap between brand recognition and actual capability is widest.

Tier 3: Point solutions and niche platforms. Vertical specialists, low-code builders and embedded insurance tools occupy this space. They can be effective within narrow parameters but rarely carry the breadth to serve as a primary policy admin system across multiple product lines.

The comparison that follows focuses on Tier 1 and Tier 2, since those are the platforms that appear on serious shortlists.

What the Evaluation Actually Measured

Most system comparisons stop at feature checklists. A vendor either has document generation or it does not. Either it supports API integration or it does not. That binary framing misses almost everything that matters in practice, because the question is never whether a capability exists but how well it works, how much it costs to configure and how long it takes to change.

This comparison assessed four criteria consistently across every platform reviewed.

Configurability. Not whether a system can be configured, but how. Who does the configuring? Does it require vendor professional services, internal development resource or can a trained business analyst do it without writing code? The distinction matters because it determines your speed of response to market changes and your ongoing cost of ownership. Fewer than half of insurers met or exceeded their latest transformation goals, with unexpected integration complexities cited as a primary obstacle.⁷ Many of those complexities trace back to systems where configuration requires specialist vendor access rather than internal control.

Integration depth. Modern insurance operations depend on connections to rating engines, third-party data sources, claims platforms, bordereaux tools and broker portals. The question is not whether a system has an API but whether that API is well-documented, stable across versions and capable of supporting real-time data exchange rather than batch processing.

Time-to-quote. This is the metric that separates aspiration from reality for any insurer trying to compete on speed. It reflects the cumulative effect of product configuration tools, workflow design and underlying system performance. Where vendors provided figures, those are included. Where they did not, assessments are based on publicly available case study data and market intelligence.

Total cost of ownership. Licence fees are the visible part. Implementation costs, ongoing configuration charges, integration work and the internal resource required to maintain a system over a five-year horizon are what determine whether a platform is genuinely affordable. Digital leaders in insurance achieve five times the growth rate and eight times the profitability of peers.⁸ The gap between them and the rest is rarely explained by licence cost alone.

The UK Policy Admin System Market in 2026

The UK insurance market is not a small playing field. Insurers here manage approximately £2.35 trillion of customer assets across around 90 million policies,⁹ and commercial lines premiums grew at a compound annual rate of 7.8% between 2019 and 2026.¹⁰ The systems that administer those policies are, in many cases, decades old.

Three tiers, one market

The policy admin system market in the UK breaks into three reasonably distinct tiers, though vendors rarely describe themselves this way.

At the top sit the enterprise incumbents. These are platforms with long implementation histories, large client reference lists and sales cycles measured in years rather than months. Their scale is real. So is their complexity, and so is their cost. Launching a new product on a legacy policy administration system can take 18 to 24 months,¹¹ a figure that enterprise platform users will recognise immediately.

The second tier contains what the market loosely calls mid-market challengers. These are platforms that have been built or substantially rebuilt in the last decade, designed with configurability and integration in mind from the start. This tier is where the most interesting competition is currently happening, and where the gap between brand recognition and actual capability is widest.

Why incumbency distorts buying decisions

Large-scale core system transformations fail more than 70% of the time, and almost a quarter become full write-offs.¹² That risk does not disappear by choosing the biggest name on the shortlist. It often increases, because the larger the incumbent platform, the more complex the implementation and the harder the eventual exit.

Yet brand recognition continues to drive shortlisting. Only 41% of insurers met or exceeded their latest transformation goals,¹³ and the gap between intention and outcome is rarely caused by choosing an obscure vendor. It is usually caused by underestimating what a platform actually requires to deliver on its promises.

Tier 3 and why it falls outside this comparison

Point solutions, vertical specialists and low-code builders occupy the third tier. They serve narrow use cases well. A specialist agricultural liability platform or an embedded insurance tool built for a single distribution channel can be genuinely effective within its parameters. But none of these qualifies as a primary policy admin system capable of carrying multiple product lines at scale, so they fall outside the scope of what follows. The comparison concentrates on Tier 1 and Tier 2, because those are the platforms that appear on serious shortlists in the UK market today.

What I Actually Evaluated (And How)

Most policy admin system comparisons are structured around what vendors want you to ask. They assess interface attractiveness, the smoothness of the demo and whether the sales team could name a client in your sector. Those criteria are not useless, but they are insufficient. The evaluation framework used here was built around the questions that determine whether a platform will still be working for you in year five, not just year one.

Configurability without code

The first criterion was how far a system could be reconfigured by a business analyst or product manager without involving a developer. This matters because the cost of product change accumulates quietly. When every adjustment to a rating factor, an endorsement logic or a document template requires a development ticket, the effective cost of product agility is hidden inside IT headcount and sprint cycles rather than the licence invoice. Insurers running legacy platforms spend, on average, more than 70% of their IT budget on maintenance rather than innovation.¹⁴ The ability to configure without code is one of the clearest signals of whether that ratio is structurally fixable.

Integration depth and API maturity

The second criterion was integration capability. A policy admin system does not operate in isolation. It sits alongside claims platforms, finance systems, distribution channels, bordereaux tools and increasingly a growing set of data and AI services. The question is not whether a system has an API, but how mature that API is, how well it is documented and how reliably it handles real-world data volumes. Sixty-one percent of insurers are already investing in cloud platforms to enable real-time digital operations,¹⁵ which means integration architecture is now a board-level concern rather than a back-office one.

Time-to-quote and product launch speed

The third criterion was speed. Specifically, how long it takes to take a new product from a blank configuration to a live quote. This is where the gap between Tier 1 and Tier 2 platforms is most visible. The 18 to 24 month product launch timeline associated with legacy policy administration systems¹¹ is not just a competitive disadvantage. In a market where commercial lines are growing at nearly 8% annually¹⁰ and cyber policy uptake grew 17% in a single year,¹⁶ it is a structural barrier to participating in the growth that is actually happening.

Why I Did This (And Why Most Comparisons Are Useless)

If you search for a policy admin system comparison today, you will find no shortage of results. What you will find far less of is anything written without a commercial interest in the outcome. Most guides are produced by vendors, affiliates or analyst firms whose methodology is opaque and whose conclusions tend to align suspiciously with whoever is paying for the research. The buyer is left trying to extract signal from a document designed to obscure it.

The problem with most evaluations

The typical policy admin system comparison is built around vendor-supplied information. Briefings, demos and reference calls with pre-selected clients are the primary inputs. That is not evaluation. It is a structured opportunity for a vendor to present the version of their product that photographs best. The resulting comparisons rank systems on criteria that are easy to measure but often irrelevant at scale: interface design, the number of pre-built integrations listed in a brochure, or whether a named insurer in your segment appears somewhere in the client list.

Why the market is overdue a corrective

The UK insurance market is significant. It manages approximately £2.35 trillion of customer assets across around 90 million policies.¹ The policy admin systems underpinning that volume deserve more rigorous scrutiny than they typically receive. Large-scale core system transformations fail more than 70% of the time, and nearly a quarter become full write-offs.² Those are not abstract figures. They represent real capital destruction, and much of it is traceable to selection decisions made on incomplete information.

What this comparison covers

This evaluation concentrated on the platforms that genuinely dominate buying conversations in the UK market today. That means the established enterprise incumbents and the serious mid-market challengers. Products listed on software review sites but absent from real shortlists were excluded. The aim is practical usefulness, not exhaustiveness.

Section 2: The UK Policy Admin System Landscape in 2026

The UK policy administration system market is not a level playing field, and it has not been for some time. Understanding where the dominant platforms sit, and why they sit there, is the necessary starting point before any meaningful evaluation can happen.

Tier 1: Enterprise incumbents

The top tier is occupied by a small group of platforms that built their market positions over decades, often by displacing mainframe systems in the 1990s and 2000s. They are embedded deeply in large composite insurers and Lloyd's carriers, and their staying power comes less from technical superiority than from switching costs that have accumulated over years of customisation. These are the systems that sales teams at large brokers and insurers recognise by name, and that recognition carries significant weight in procurement decisions regardless of whether the underlying technology still merits it. Their scale is real, their reference lists are long, and their implementation partners are plentiful. What they frequently cannot offer is speed. The 18 to 24 month product launch timeline documented across legacy policy administration systems¹¹ is a ceiling that affects this tier most directly.

Tier 2: Mid-market challengers

Below the enterprise incumbents sits a more varied group of platforms serving MGAs, specialist insurers and regional carriers. This tier has attracted the most meaningful investment and development activity in recent years. Sixty-one percent of insurers are already investing in cloud platforms to enable real-time digital operations,¹⁵ and much of that investment is flowing towards mid-market systems better architected for cloud from the outset. The competitive differentiation here is sharper and more genuinely technical.

Tier 3: Niche and emerging platforms

The third tier covers point solutions, early-stage platforms and products with a narrow product line or geographic focus. They appear on software review sites and occasionally on longlist spreadsheets, but rarely survive to final evaluation in serious procurement processes. This comparison does not spend time on them.

Section 3: The Six Criteria That Actually Matter

Most procurement teams build evaluation scorecards around the wrong things. Brand familiarity, the quality of a vendor's demo environment and the length of their client list are all poor proxies for the variables that will determine whether a policy admin system delivers or disappoints at scale. After working through the platforms that genuinely appear on UK shortlists, six criteria emerged as the ones that separate systems worth deploying from those worth avoiding.

Configurability without code

The ability to change rating logic, product structure and workflow rules without raising a development ticket is not a luxury feature. It is a baseline requirement for any insurer or MGA operating in a market where product velocity matters. Launching a new product on a legacy policy administration system takes 18 to 24 months by documented industry benchmarks.¹¹ Platforms that require vendor involvement for routine configuration changes push buyers straight back towards that ceiling regardless of how the sales conversation was framed.

Integration depth

No policy admin system operates in isolation. The real test is how cleanly a platform connects to third-party data sources, payment providers, document management tools and claims systems. Shallow integration via bespoke connectors creates technical debt that compounds quickly. Sixty-one percent of insurers are already investing in cloud platforms to enable real-time digital operations,¹⁵ which raises the bar for what integration architecture needs to support.

Time to quote

Rating engine performance under real load conditions, not demo conditions, is a differentiator that rarely appears in vendor materials but surfaces immediately in live environments.

Total cost of ownership

Licence fees are the smallest part of the number. Implementation, integration, ongoing configuration and the cost of change requests over a five-year horizon frequently dwarf the initial contract value. Modernising legacy systems can reduce IT costs per policy by 41%,¹² which indicates how much headroom exists between efficient and inefficient platforms.

Regulatory adaptability

The UK regulatory environment changes. A policy admin system that requires significant re-engineering to accommodate FCA rule changes or new product disclosure requirements is a liability, not an asset.

Vendor stability and roadmap transparency

A platform is only as reliable as the organisation maintaining it. Only 41% of insurers met or exceeded their latest transformation goals,¹⁶ and insufficient vendor alignment is among the primary obstacles cited. Understanding where a vendor's product investment is actually going, rather than what their roadmap deck claims, is due diligence that most buyers skip.

Section 4: What the Enterprise Platforms Get Right (And Where They Break)

The enterprise incumbents earned their market position. They carry deep insurance logic built across decades, they have processed millions of policies and their implementation teams understand the operational complexity of large carrier environments in a way that newer platforms genuinely cannot replicate from a standing start. For a tier-one insurer running commercial lines across multiple geographies, that institutional knowledge has real value.

Where they perform

At scale, enterprise platforms typically handle complex multi-line products, large bordereaux volumes and sophisticated reinsurance structures with a reliability that reflects their heritage. Their compliance frameworks are mature. Their audit trails are thorough. Insurers running 90 million policies across the UK market²¹ need systems that will not buckle under volume, and the enterprise incumbents have that credibility.

Where they break

The cost structure is the first problem. Large-scale core system transformations fail more than 70% of the time, and almost a quarter become full write-offs.²² That figure is not an argument against modernisation. It is an argument against the implementation models that enterprise vendors have normalised, where projects run for years, customisation accumulates and the original business case dissolves under the weight of change requests.

The second problem is velocity. Launching a new product on a legacy policy admin system takes 18 to 24 months.¹¹ Enterprise platforms serving large incumbents are often the systems that created that benchmark rather than the ones challenging it. Configuration changes that should take days require vendor involvement, and vendor involvement means queuing behind every other client on the same support model.

The incumbency trap

Digital leaders in insurance achieve five times the growth rate and eight times the profitability of peers.²³ Enterprise platforms that cannot support rapid product deployment are not neutral infrastructure. They are a competitive disadvantage dressed as stability.

References

1. McKinsey, "IT Modernisation in Insurance: Three Paths to Transformation", 2019. https://www.mckinsey.com/industries/financial-services/our-insights/it-modernisation-in-insurance-three-paths-to-transformation
2. GrowthNavigate, "How Outdated Core Systems Are Quietly Draining Insurance IT Budget", 2025. https://www.growthnavigate.com/how-outdated-core-systems-are-quietly-draining-insurance-it-budget
3. Capgemini, "World Property and Casualty Insurance Report 2024", 2024. https://www.capgemini.com/insights/research-library/world-property-and-casualty-insurance-report-2024/
4. FCA, "Wholesale Insurance Market Priorities 2023", 2023. https://www.fca.org.uk/publication/correspondence/wholesale-insurance-market-priorities-2023.pdf
5. ABI (via RSM UK), "UK Insurance in 2025: Inflation, Tech and Climate Risks", 2025. https://www.rsmuk.com/insights/advisory/uk-insurance-in-2025-inflation-tech-and-climate-risks
6. ABI (via Insurance Edge), "ABI Calls for Cyber Risk Awareness in Every Organisation", 2025. https://insurance-edge.net/2025/11/12/abi-calls-for-cyber-risk-awareness-in-every-organisation/
7. Lloyd's Market Association, "Lloyd's Market Association Announces 2025 Priorities", 2025. https://lmalloyds.com/lloyds-market-association-announces-2025-priorities/
8. Capgemini, "World Life Insurance Report 2025", 2024. https://insurtechdigital.com/articles/capgemini-life-insurers-grappling-with-digital-expectations
9. Capgemini, "World Property and Casualty Insurance Report 2025", 2025. https://www.capgemini.com/insights/research-library/world-property-and-casualty-insurance-report/
10. McKinsey (via TDAN), "Digital Transformation in Insurance: Overcoming Legacy Challenges", 2025. https://tdan.com/digital-transformation-in-insurance-overcoming-legacy-challenges/32345
11. GrowthNavigate, "How Outdated Core Systems Are Quietly Draining Insurance IT Budget", 2025. https://www.growthnavigate.com/how-outdated-core-systems-are-quietly-draining-insurance-it-budget
12. McKinsey, "IT Modernisation in Insurance: Three Paths to Transformation", 2019. https://www.mckinsey.com/industries/financial-services/our-insights/it-modernisation-in-insurance-three-paths-to-transformation
13. Astera (citing McKinsey), "Insurance Legacy System Transformation", 2024. https://www.astera.com/type/blog/insurance-legacy-system-transformation/
14. McKinsey (via GrowthNavigate), "How Outdated Core Systems Are Quietly Draining Insurance IT Budget", 2025. https://www.growthnavigate.com/how-outdated-core-systems-are-quietly-draining-insurance-it-budget
15. Capgemini, "World Property and Casualty Insurance Report 2024", 2024. https://www.capgemini.com/insights/research-library/world-property-and-casualty-insurance-report-2024/
16. Capgemini, "World Life Insurance Report 2025", 2024. https://insurtechdigital.com/articles/capgemini-life-insurers-grappling-with-digital-expectations
17. Capgemini, "World Property and Casualty Insurance Report 2025", 2025. https://www.capgemini.com/insights/research-library/world-property-and-casualty-insurance-report/
18. McKinsey (via TDAN), "Digital Transformation in Insurance: Overcoming Legacy Challenges", 2025. https://tdan.com/digital-transformation-in-insurance-overcoming-legacy-challenges/32345
19. ABI (via RSM UK), "UK Insurance in 2025: Inflation, Tech and Climate Risks", 2025. https://www.rsmuk.com/insights/advisory/uk-insurance-in-2025-inflation-tech-and-climate-risks
20. Capgemini, "World Property and Casualty Insurance Report 2024", 2024. https://www.capgemini.com/insights/research-library/world-property-and-casualty-insurance-report-2024/
21. FCA, "Wholesale Insurance Market Priorities 2023", 2023. https://www.fca.org.uk/publication/correspondence/wholesale-insurance-market-priorities-2023.pdf
22. McKinsey/BCG (via Carrier Management), "Large-Scale Core System Transformations", 2026. https://www.carriermanagement.com/features/2026/03/04/285258.htm
23. McKinsey (via TDAN), "Digital Transformation in Insurance: Overcoming Legacy Challenges", 2025. https://tdan.com/digital-transformation-in-insurance-overcoming-legacy-challenges/32345

Choosing between Genasys, Guidewire, Duck Creek and Sapiens is one of the most consequential decisions a mid-market insurer can make, yet the process of identifying the best mid-market insurance software too often begins with a shortlist borrowed from the wrong playbook. Enterprise buyers at tier-one carriers have shaped the dominant narratives around these platforms for years, and mid-market insurers, MGAs and brokers frequently inherit those narratives without questioning whether they apply to their own scale, budget or implementation capacity.

The global insurance market is growing at a pace that makes this decision more urgent than ever. Global insurance premiums grew by 4.6% in 2024, outperforming the 1.6% average of the prior five years,¹ while commercial P&C lines averaged 8% annual premium growth over the past five years with a combined ratio trending down to an estimated 91%.² In the UK, Lloyd's reported gross written premium of £55.5bn for full year 2024, up from £52.1bn the previous year, with a profit before tax of £9.6bn.³ These are conditions that reward insurers who can move quickly, price accurately and deploy technology that keeps pace with their ambition.

Technology investment is accelerating alongside premium growth. Ninety-nine per cent of insurers are already investing in generative AI or planning to do so,⁴ and 73% of insurance CEOs are prioritising AI investment to improve underwriting, claims and customer experience.⁵ The pressure to modernise is not theoretical. It is embedded in CEO mandates, board-level KPIs and the expectations of brokers and policyholders who interact with digital-first experiences in every other area of their lives.

What this article examines is whether the four platforms most commonly appearing on mid-market shortlists are equally well positioned to meet that pressure. Guidewire is a mature, deeply capable platform with an installation base built largely on large carriers and tier-one groups. Duck Creek has repositioned toward cloud delivery but carries architectural history that affects its implementation profile. Sapiens offers a broad product suite with genuine international reach, though its cost and complexity profile sits closer to enterprise than mid-market in practice. Genasys is built specifically for the segment where speed-to-market, total cost of ownership and configuration flexibility matter most.

This comparison does not treat all four platforms as interchangeable options on a feature grid. The more useful question is not which platform has the longest list of capabilities, but which platform is actually designed for the buyer reading this article. The answer that emerges from an honest assessment of deployment models, pricing structures, implementation timelines and real-world fit is not the same for every organisation, but it is far less ambiguous than most vendor-neutral comparison sites would have you believe.

References

1. Accenture Insurance Blog, 5 Reflections on the Insurance Industry in 2024, November 2024. https://insuranceblog.accenture.com/5-reflections-on-the-insurance-industry-in-2024
2. McKinsey, Global Insurance Report 2025: The Pursuit of Growth, November 2024. https://www.mckinsey.com/industries/financial-services/our-insights/global-insurance-report
3. Lloyd's, Full Year Results 2024, March 2025. https://www.lloyds.com/about-lloyds/media-centre/press-releases/lloyds-reports-2024-full-year-results
4. EY, cited in IRMI, 2024 Insurance Year in Review and 2025 Developments, May 2025. https://www.irmi.com/articles/expert-commentary/2024-insurance-year-in-review-and-2025-developments
5. KPMG, 2025 Insurance CEO Outlook, January 2026. https://kpmg.com/uk/en/insights/finance/ceo-outlook-insurance.html

The Wrong Shortlist Problem

Mid-market insurers frequently arrive at vendor shortlists that include Guidewire and Duck Creek by default. These names carry weight because they appear in enterprise RFPs, industry analyst reports and peer conversations at conference tables where the attendees are, more often than not, representing organisations with budgets and headcounts far larger than the mid-market norm. Borrowing a shortlist from a peer twice your size is not a procurement strategy. It is a category error that adds months to evaluation cycles and sets expectations that do not survive first contact with an implementation quote.

The scale mismatch is real. Guidewire's customer base is built substantially on large carriers and tier-one groups. Its platform depth is genuine, but that depth comes attached to implementation timelines, professional services costs and internal change management requirements that reflect the complexity of the organisations it was designed to serve. A mid-market insurer, MGA or broker evaluating Guidewire is, in most cases, looking at a platform engineered for a problem they do not have.

Duck Creek presents a different version of the same issue. Its cloud repositioning is ongoing, but the architectural history of a platform built across multiple acquisition cycles remains visible in its implementation profile. Sapiens has genuine international reach and a product suite that spans life, non-life and reinsurance, yet its commercial and delivery model in practice sits closer to the enterprise end of the spectrum than mid-market procurement teams typically anticipate before they receive a proposal.

The result is predictable. Evaluations stall. Budgets are revised. Go-live dates move. In some cases, projects are abandoned after significant sunk cost. The global insurance market grew premiums by 4.6% in 2024, outperforming the prior five-year average of 1.6%.¹ That growth creates opportunity, but only for organisations whose technology can keep pace. Choosing the wrong platform at the shortlist stage forfeits that advantage before implementation begins.

Mid-Market Insurance Software Showdown: Genasys vs Guidewire vs Duck Creek vs Sapiens, Which Platform Actually Wins?

The global insurance industry is in a period of sustained expansion. Global insurance premiums grew by 4.6% in 2024, well above the 1.6% average of the previous five years, with non-life lines rising 4.3% and life insurance reaching a decade-high 5%.¹ In the UK alone, Lloyd's reported gross written premium of £55.5bn for full year 2024, up from £52.1bn the prior year, with a profit before tax of £9.6bn.² The commercial opportunity is substantial. The technology question is whether mid-market insurers, MGAs and brokers are positioned to capture it.

The platform decision sits at the centre of that question. Core systems determine how quickly a business can launch products, respond to regulatory change, integrate new data sources and manage the end-to-end policy lifecycle. Get the platform right and the organisation can move at the speed the market now demands. Get it wrong and technology becomes the ceiling rather than the floor.

This comparison examines four platforms that appear with regularity on mid-market shortlists: Genasys, Guidewire, Duck Creek and Sapiens. Each has genuine capability. Each serves real customers. But capability is not the same as fit, and the differences between these platforms matter considerably more at the mid-market level than most comparison articles acknowledge.

The argument here is direct. Guidewire is an enterprise machine. Duck Creek carries architectural complexity its cloud repositioning has not fully resolved. Sapiens has broad reach but a delivery model that in practice sits closer to enterprise than its positioning implies. Genasys is the platform purpose-built for the segment where speed-to-market, configurability and total cost of ownership are the metrics that actually determine project success.

What follows is an honest assessment of all four, structured around the criteria that matter most to mid-market buyers in 2025.

What This Comparison Actually Is

Most insurance software comparisons are written from the enterprise buyer's perspective. They assume eight-figure budgets, dedicated programme management offices and implementation timelines measured in years. That framing serves a narrow audience. It does not serve the mid-market insurer, MGA or broker trying to make a sound platform decision with a realistic budget and a board that expects to see results within eighteen months.

This article takes a different position. The thesis is that Genasys is the standout choice for mid-market insurance organisations, not because it out-features every rival in every category, but because it delivers Tier 1 platform capability at a price point and implementation model that the mid-market can actually absorb. That is a meaningful distinction. A platform that is technically superior but operationally inaccessible is not a better choice. It is simply an expensive problem with better marketing.

The competitive picture is honest, not promotional. Guidewire is a genuinely powerful system. It dominates large carrier deployments for good reason, and its technology investment is real. The difficulty is that its commercial and delivery model was built for organisations operating at a scale most mid-market readers will never reach. Duck Creek has invested in cloud repositioning, but an architectural history assembled across multiple acquisition cycles does not disappear with a rebranding exercise. Sapiens offers genuine international breadth across life, non-life and reinsurance, which matters in certain contexts. Its delivery model, however, carries cost and complexity that tends to surprise mid-market procurement teams when proposals arrive.

The stakes are not abstract. Insurance CEOs are prioritising technology investment at levels not seen in prior cycles, with 73% of insurance CEOs now prioritising AI investment to improve underwriting, claims and customer experience.³ That investment requires a platform capable of supporting it. Choosing a system misaligned to organisational scale is not a conservative decision. It is the riskiest decision available.

Understanding the Four Platforms

Before any meaningful comparison is possible, it helps to be clear about what each platform actually is, who built it and for whom.

Guidewire was founded in 2001 and listed on the New York Stock Exchange in 2012. It has built its reputation on PolicyCenter, BillingCenter and ClaimCenter, a suite of core systems deployed predominantly at large Tier 1 and Tier 2 carriers. Its cloud platform, Guidewire Cloud, has accelerated adoption among established carriers with the infrastructure to absorb multi-year transformation programmes. The company reported annual recurring revenue exceeding $900 million in its most recent financial year, which gives a reasonable indication of the scale at which it operates and the scale it expects of its customers.

Duck Creek Technologies emerged through a combination of organic development and acquisition, resulting in an architecture that reflects that history. Its cloud repositioning, Duck Creek OnDemand, represents a genuine attempt to modernise delivery. The platform covers policy, billing and claims for P&C insurers and has a meaningful presence in the North American market in particular. Whether the cloud repositioning has fully resolved the underlying complexity is a question that procurement teams consistently raise.

Sapiens International offers one of the broadest stacks of the four, covering life, pension, non-life and reinsurance across a global customer base. That breadth is a genuine differentiator in certain contexts, particularly for carriers operating across multiple lines and geographies. The trade-off is a delivery model that carries corresponding weight. Global insurance premiums grew 4.6% in 2024, outperforming the prior five-year average of 1.6%,⁴ and Sapiens has benefited from that growth cycle. The question for mid-market buyers is whether its engagement model is calibrated to their size.

Genasys takes a different starting point. Purpose-built for the mid-market, it covers the full policy lifecycle across personal lines, commercial lines and specialty, with an implementation model designed around the realities of smaller programme teams and tighter timelines.

Section 2: Meet the Contenders, A Brief Vendor Overview

The four platforms in this comparison are not interchangeable products competing for the same buyer. They were built at different times, for different purposes and at different scales. Understanding that context is what makes a genuine comparison possible.

Guidewire is, first and foremost, an enterprise carrier platform. Founded in 2001 and publicly listed in 2012, it has spent two decades embedding itself into the core systems of large Tier 1 and Tier 2 carriers. Its cloud platform, Guidewire Cloud, has extended that reach, but the underlying commercial and implementation model remains calibrated to organisations with the budget, internal resource and multi-year appetite that transformation at that scale demands. This is not a criticism. It is a description of what the product is and who it serves best.

Duck Creek Technologies has a meaningful presence in North American P&C insurance, covering policy, billing and claims. Its OnDemand cloud offering represents a deliberate move toward more flexible delivery. The platform's architectural history, assembled across development cycles and acquisitions, continues to generate questions during procurement. Cloud repositioning addresses deployment. It does not automatically simplify what sits beneath.

Sapiens International brings genuine breadth, covering life, pension, non-life and reinsurance across a substantial global customer base. For carriers operating across multiple lines and geographies, that breadth has real value. Global insurance premiums grew 4.6% in 2024, outperforming the prior five-year average of 1.6%,⁴ and Sapiens has benefited from that growth environment. The delivery model, however, carries a cost and complexity profile that consistently places it closer to the enterprise end of the market than its marketing sometimes suggests.

Genasys is purpose-built for mid-market insurers, MGAs and brokers. It covers the full policy lifecycle across personal lines, commercial lines and specialty, with an implementation model designed around realistic programme teams, tighter budgets and the expectation that going live in months rather than years is not an unreasonable demand.

Section 3: Who Are These Platforms Actually Built For?

Every platform in this comparison has a natural buyer. The marketing materials rarely admit it plainly, but the pricing models, implementation structures and case study portfolios tell the story clearly enough. Target market is not just a positioning choice. It shapes architecture, contract terms, partner ecosystems and the day-to-day experience of going live.

Guidewire is built for large carriers. Its reference customers are household names with dedicated technology functions, substantial SI budgets and the organisational depth to run multi-year transformation programmes. The platform assumes a buyer who can commit significant internal resource alongside the implementation partner. That model produces excellent outcomes at the right scale. It produces overruns, scope complexity and cost exposure when applied below it.

Duck Creek is built for North American P&C carriers, primarily in the mid-to-large segment. Its policy, billing and claims modules have genuine depth for that market. Buyers outside North America, or those looking for a truly modern cloud-native architecture rather than a hosted version of an older platform, will find the fit less clean. The OnDemand offering has moved things forward, but architectural heritage does not disappear through rebranding.

Sapiens is built for breadth. Its appeal lies in covering life, non-life, reinsurance and pensions across a wide geography. With global insurance premiums growing at 4.6% in 2024 against a prior five-year average of 1.6%,⁴ carriers operating across multiple lines have had real commercial reasons to invest at scale. Sapiens serves that profile well. The delivery model, however, reflects that complexity, and mid-market buyers frequently find the engagement structure heavier than their programmes require.

Genasys is built for the mid-market specifically. That specificity matters. With 73% of insurance CEOs now prioritising technology investment to improve underwriting, claims and customer experience,⁵ mid-market carriers need platforms that can actually deliver on that ambition within realistic budgets and timelines.

Section 4: Feature Comparison, The Five Dimensions That Matter Most

Comparing insurance platforms on feature lists alone produces a misleading picture. Every platform in this group can generate a policy, process a claim and produce a bordereau. The questions that actually separate them are about configurability, implementation speed, total cost, integration capability and cloud architecture. These five dimensions reveal where genuine differences lie.

Configurability without code. Mid-market insurers change products frequently. Waiting weeks for a development team to adjust a rating algorithm or add a coverage option is not a viable operating model. Platforms that allow product and pricing changes through configuration rather than code give business teams meaningful autonomy. This capability varies significantly across the four platforms, with legacy architectural layers in some cases limiting what non-technical users can do in practice.

Implementation speed and programme risk. 99% of insurers are either already investing in AI and digital capabilities or planning to do so,⁶ which means transformation queues are long and internal capacity is stretched. A platform that requires an 18-month implementation before it delivers any business value compounds that pressure considerably. Time-to-value is not a marketing metric. It directly affects budget exposure and organisational stamina.

Total cost of ownership. Licence fees are only part of the calculation. Implementation costs, SI partner fees, ongoing customisation and the internal resource required to maintain configuration all contribute. For mid-market buyers operating without enterprise-scale technology budgets, the full cost picture frequently looks very different from the initial commercial proposal.

Integration and API capability. Modern insurance operations depend on data flowing cleanly between the core platform and third-party services, whether rating data providers, document management systems or bordereaux tools. Open, well-documented APIs reduce integration friction and lower the cost of connecting new services over time.

Cloud architecture. A platform built natively for the cloud behaves differently from one that has been migrated or rehosted. Scalability, release cadence, disaster recovery and the ability to adopt new capabilities without disruptive upgrade cycles all depend on how thoroughly cloud principles are embedded in the original design, not applied to it retrospectively.

References

1. Lloyd's, "Full Year Results 2024", March 2025. https://www.lloyds.com/about-lloyds/media-centre/press-releases/lloyds-reports-2024-full-year-results
2. ABI / Wikipedia, "Association of British Insurers", 2024. https://en.wikipedia.org/wiki/Association_of_British_Insurers
3. RSM UK citing ABI data, "UK Insurance in 2025: Inflation, Tech and Climate Risks", 2025. https://www.rsmuk.com/insights/advisory/uk-insurance-in-2025-inflation-tech-and-climate-risks
4. Accenture, "5 Reflections on the Insurance Industry in 2024", November 2024. https://insuranceblog.accenture.com/5-reflections-on-the-insurance-industry-in-2024
5. KPMG, "2025 Insurance CEO Outlook", January 2026. https://kpmg.com/uk/en/insights/finance/ceo-outlook-insurance.html
6. EY, cited in IRMI, "2024 Insurance Year in Review and 2025 Developments", May 2025. https://www.irmi.com/articles/expert-commentary/2024-insurance-year-in-review-and-2025-developments

Insurance has changed a lot in the last decade.

Insurers now have to navigate a hardening market and a shifting risk landscape while simultaneously managing the weight of historic infrastructure. At the centre of this operational challenge sit Policy Administration Systems (PAS).

For many insurance carriers and Managing General Agents (MGAs), the PAS is the single most critical component of their technology stack. It is the system of record for all policies that an insurance company has written. It is the core database and processing engine that holds the definitive truth about who is insured, for what risks and under what terms.

However, for too many organisations, the PAS has become a constraint rather than an enabler. Fragmented processes and rigid legacy systems force highly skilled underwriters to rely on manual workarounds. This slows down product launches and creates data silos that obscure profitability.

In this guide, we will break down exactly what a PAS is and how it functions across the entire policy lifecycle. We will explore the critical differences between legacy mainframes and modern cloud-native platforms. We will also examine how new regulatory requirements from the Financial Conduct Authority (FCA) and Lloyd’s of London are reshaping what insurers must demand from their core systems.

What Is a Policy Administration System?

A Policy Administration System (PAS) is the heartbeat of an insurance carrier’s IT landscape. It is the software platform used to manage the entire lifecycle of an insurance policy.¹

To understand the PAS, it is necessary to distinguish it from the other major systems that make up the insurance technology stack. While other systems play supporting roles, the PAS is the definitive system of record. It handles the essential transaction processing. This includes creating quotes, binding coverage, issuing documents, processing endorsements (mid-term changes) and managing renewals and cancellations.

It ensures that every policy issued complies with the insurer’s rules and regulatory requirements. It is the “factory” where the insurance product is manufactured and maintained.

Distinguishing the PAS from Connected Systems

Confusion often arises regarding where the PAS stops and other systems begin. In a traditional “best-of-breed” architecture, these functions are often separated into distinct silos:

• Claims Management Systems (CMS): These systems handle the adjudication and settlement of losses after an incident occurs. The PAS acts as the source of truth for the CMS. When a claim is filed, the CMS queries the PAS to verify that the policy was active on the date of loss and that the specific peril was covered. The PAS confirms coverage while the CMS manages the reserving and payout.
• Billing Systems: The PAS calculates the premium due based on the risk data. It then passes this financial data to the billing system. The billing system handles the invoicing, payment collection, direct debit processing and commission calculations for brokers.
• Customer Relationship Management (CRM): A CRM manages the sales pipeline and client interactions. It focuses on the relationship (leads, emails and calls) whereas the PAS focuses on the contract (coverage limits, deductibles and risk data).

However, the industry is increasingly moving away from this fragmented approach. Modern platforms often consolidate these critical functions to reduce complexity. With Genasys, for example, we do however offer a core insurance administration platform which incorporates policy admin, claims management and billing all in one solution. This unified approach eliminates data silos and ensures that a change in one area, such as a policy endorsement, is immediately reflected in billing and claims without complex integration work.

Why Policy Administration Systems Matter for Modern Insurers

The PAS is no longer just a database for storing records. It has evolved into a strategic driver of performance and competitive advantage.

Operational efficiency and straight-through processing A modern PAS reduces the friction of manual data entry. By automating routine tasks such as data validation and document generation, insurers can achieve “Straight-Through Processing” (STP). This allows simple risks to be quoted and bound without human intervention. This significantly reduces the cost-per-policy and frees underwriters to focus on complex cases that require their expertise.²

Regulatory compliance and auditability In a tightening regulatory environment, particularly with new operational resilience requirements from bodies like the FCA and the Prudential Regulation Authority (PRA), a robust PAS is essential.³ It provides a complete audit trail of every transaction. This ensures that insurers can prove exactly when a policy was changed, by whom and what rating rules were in effect at that specific moment.

Customer and agent experience Policyholders and brokers expect the speed of modern retail experiences. They do not want to wait days for a quote. A modern PAS supports real-time portals where agents can quote business in seconds. It enables self-service capabilities so customers can download documents or renew policies online without waiting for a call centre.⁴

Product agility and speed to market Perhaps the most critical advantage is speed. Legacy systems often require hard-coding to change a rate or a question on an application form. Modern platforms allow business users to configure rating rules and launch new products in weeks rather than months or years.

Core Components of a Policy Administration System

A comprehensive PAS is composed of several integrated modules that work in concert to manage the risk.

New business and underwriting This module handles the intake of data. It is the front door of the system. It validates the applicant’s information and assesses the risk against underwriting guidelines. It acts as the gatekeeper to ensure only risks within the carrier’s appetite are accepted.

Rating and rules engine This is the brain of the system. The rating engine executes the complex mathematical algorithms that determine the price. It must handle multi-variable logic involving location, construction type and claims history. Simultaneously, the rules engine enforces underwriting logic. For example, it might enforce a rule such as “Do not quote properties within 100 metres of a coastline” or “Refer all risks with a sum insured over £5 million to a senior underwriter”.⁵

Policy issuance and documentation Once a risk is bound, the PAS must generate the legal contract. The document generation engine assembles the policy packet. It dynamically pulls in the correct forms, endorsements and statutory notices based on the specific coverage details selected during the quote process.

Endorsements, renewals and cancellations Insurance is dynamic. The PAS manages the complex logic of mid-term adjustments (endorsements). It calculates pro-rata premiums accurately to the penny. It also automates the renewal process by re-rating the policy based on the latest rates and generating renewal invites automatically.

Integrations and data flows No PAS operates in a vacuum. It must integrate seamlessly with third-party data providers. This includes calls to credit bureaus, property data providers (for flood or subsidence scores) and sanction checking services. It must also feed data downstream to the general ledger and data warehouse.

Legacy Policy Administration Systems vs. Modern Platforms

The industry is currently divided between those maintaining the past and those building for the future. Understanding the architectural differences is key to evaluating your own position.

Common pain points with legacy PAS Legacy systems are often built on mainframe architectures or outdated codebases from the 1990s or early 2000s. They are characterised by rigidity.

• Hard-coded rules: Changing a simple rating factor often requires a change request to the IT department. This enters a development queue and can take months to implement.⁶
• Data silos: Data is often trapped in proprietary formats or unstructured tables. This makes it difficult to extract for analytics or reporting.
• Poor UX: Green screens or clunky, tab-heavy interfaces frustrate underwriters and slow down processing times.
• Maintenance costs: A significant portion of IT budget is spent solely on “keeping the lights on” rather than innovation.⁷

Characteristics of a modern policy administration system Modern platforms are designed for the cloud era.

• Cloud-native architecture: These systems are built on microservices. This means the application is broken down into small, independent services (like “Rating” or “Document Generation”) that can be updated independently. This offers infinite scalability and resilience.⁸
• API-first: Modern systems are designed to connect. They expose every function via an Application Programming Interface (API). This allows insurers to plug into the wider insurtech ecosystem easily.⁹
• Low-code/No-code tools: These platforms empower business analysts to make changes to products and workflows using visual interfaces. This reduces reliance on deep technical skills and speeds up iteration.
• Real-time data: They provide immediate visibility into portfolio performance, allowing executives to spot trends as they happen.

How a Policy Administration System Supports the Policy Lifecycle

The lifecycle of a policy is a journey of data. A modern PAS manages this journey through distinct stages.

From quote to bind It begins with the submission. The PAS ingests data from a broker portal, an API or manual entry. It enriches this data with external sources (such as flood scores or credit checks). It then applies the rating logic to produce a quote. If the customer accepts the quote, the “Bind” process converts this temporary offer into a permanent legal record.

Policy issuance and servicing Upon binding, the system triggers the issuance workflow. It assigns a unique policy number and generates the PDF contract. It sends this to the customer or broker. During the policy term, the PAS handles servicing requests. This includes changing an address, adding a driver or increasing coverage limits. The system handles the financial adjustments automatically, calculating any additional premium or refund due.

Renewal and retention As the policy approaches expiration, the PAS initiates the renewal workflow. It re-evaluates the risk. Has the customer made claims? Has the rate set changed? It then generates a renewal quote. Advanced systems can even flag policies at risk of churn for proactive intervention by the sales team.

Data and reporting Throughout this process, the PAS acts as a data warehouse. It feeds critical information to dashboards that allow executives to monitor loss ratios, premium growth and operational bottlenecks in real time.

Signs You Have Outgrown Your Current Policy Administration System

Many insurers tolerate subpar performance because “it is how we have always done it”. However, certain signs indicate that a legacy system is actively harming the business.

Frequent manual workarounds If your underwriters are using spreadsheets to rate risks because the system cannot handle the math, you have a problem. “Shadow IT” creates compliance risks and data errors.

Slow product launches Speed is a competitive advantage. If it takes 6 to 12 months to launch a new product or change a rate, you are losing ground to agile competitors who can do it in weeks.⁶

Integration nightmares The modern insurance ecosystem relies on connectivity. If you cannot easily connect to a new data source or distribution partner API, your system is a barrier to growth.

Inconsistent data When the premium in the billing system does not match the PAS, or claims data cannot be reconciled with policy data, it indicates a failure of system integration.

Staff frustration Talented underwriters want to underwrite, not fight with technology. When staff spend more time on data entry than risk assessment, morale and productivity suffer.¹⁰

The Regulatory Context: FCA and Lloyd’s Requirements

In the UK, the pressure to modernise is not just commercial. It is regulatory.

FCA Operational Resilience (PS21/3) The Financial Conduct Authority (FCA) and Prudential Regulation Authority (PRA) have introduced strict rules on operational resilience. By March 2025, firms must be able to remain within “impact tolerances” for their important business services.¹¹ This means insurers must prove they can recover from IT failures or cyber-attacks within a specific timeframe. Legacy systems, with their lack of redundancy and modern disaster recovery capabilities, pose a significant compliance risk.

Consumer Duty and Fair Value The FCA’s Consumer Duty requires insurers to prove that their products offer “fair value”. This requires data. Insurers must be able to analyse claims ratios, commission structures and service levels across different customer cohorts. Legacy systems often trap this data, making it difficult to produce the “Fair Value Assessments” required by the regulator.¹²

Lloyd’s Blueprint Two and the Core Data Record (CDR) For insurers operating in the London Market, Lloyd’s “Blueprint Two” initiative is driving a shift to digital. Central to this is the Core Data Record (CDR). This is a standardised set of data fields that must be captured at the point of binding.¹³ A modern PAS must be capable of capturing and validating this structured data to ensure seamless processing through the Lloyd’s digital gateway.

How to Evaluate Policy Administration Systems

Choosing a new PAS is a defining decision for any insurer. It is a partnership that will likely last for a decade or more.

Functional criteria Does the system support your specific lines of business? A system built for personal auto may struggle with the complexity of commercial liability or specialty lines. Look for depth in rating capabilities and workflow flexibility.¹⁴

Technical criteria Is it truly cloud-native or just hosted? An API-first architecture is non-negotiable for future-proofing. Security and scalability must be proven. Ask vendors to demonstrate their API documentation and integration capabilities.¹⁵

Implementation and change management Technology is only half the battle. Evaluate the vendor’s delivery track record. Do they have a clear methodology? What is the “Time to Value”? Look for a partner that offers training and support to ensure adoption.

Questions to ask vendors

• Configurability: Can we configure rates and rules ourselves without vendor intervention?
• Upgrades: How do you handle upgrades? Are they automatic SaaS updates or do they require disruptive capital projects?
• Data Migration: What is your approach to migrating our historic data? This is often the most complex part of any project.
• Data Ownership: Who owns the data and how easily can we extract it if we leave?

When to Move from Learning to Action

Understanding the mechanics of a Policy Administration System is the first step towards modernisation. You now recognise that a PAS is not just a back-office utility but the engine of your insurance product. You understand the risks of legacy infrastructure. These risks include high maintenance costs, slow speed to market and operational fragility.

The difference between leading insurers and the rest often comes down to the agility of their core systems. If your current technology is dictating your business strategy rather than enabling it, the time to act is now.

Insurers have spent decades arguing about core systems, the great buy versus build debate. The panels at every conference, the consultants, the procurement teams, all working through the same trade-off.

Build means control. You design exactly what you need and the system fits your business.

Buy means speed. Someone else has solved the problem, you implement their answer and move on.

Both arguments are familiar and both come with trade-offs that have become harder to live with. Building is slower and more expensive than anyone admits in the business case. Buying is more rigid than the sales pitch suggests.

There is a third option, firmly in the middleground, that most of these conversations skip past. Configure. For most insurers it is the one that actually makes sense.

The case against building

The argument for building has always been control. Build it yourself and you get exactly what you want with no compromises and no vendor roadmap dictating your future. In theory this is compelling. In practice it rarely works out.

Building a core insurance system from scratch requires skills that are increasingly hard to find. Developers who understand insurance are rare enough. Developers who understand your specific lines of business, your distribution model, your regulatory environment and modern software architecture at the same time are rarer still.

The timeline is almost always longer than projected. A project scoped at 18 months becomes three years. Budgets double. Key people leave halfway through and institutional knowledge walks out the door with them.

When you finally go live you have created something else. Technical debt. The system you built is now yours to maintain. Every bug is yours to fix, every upgrade your responsibility, every security patch and performance improvement on your plate while competitors launch new features on platforms that someone else is investing in.

McKinsey has estimated that insurers spend around 70% of their IT budgets maintaining legacy systems. Much of that goes on systems they built themselves years ago that now anchor them to the past.

Building made more sense when software changed slowly, when a system built in 2005 could reasonably be expected to last fifteen years without major rework. That world no longer exists. Customer expectations have shifted, regulatory demands have grown, distribution has fragmented and AI is rewriting the rules of what core systems need to do. Building for that level of change demands a level of ongoing investment that few insurers can sustain.

The case against buying

Buying should solve these problems. Let someone else build the platform, let them maintain it, let them invest in R&D, you just use it.

The trade-off is flexibility. Traditional bought systems are rigid. They come with pre-defined workflows and fixed data structures and a way of doing things that reflects how the vendor thinks insurance should work, not necessarily how your business operates.

Implementation becomes an exercise in adaptation. You change your processes to fit the system, build workarounds for the things it cannot do, request features that sit on a roadmap you do not control, behind other clients whose priorities differ from yours. The system works. But it does not fit.

This matters more as insurance becomes more competitive. Speed to market is a real differentiator and launching a new product in weeks rather than months can decide whether you win or lose a distribution partnership. A rigid system that needs vendor involvement for every change becomes the bottleneck.

Then there is lock-in. Once you are on a platform, moving is painful. Your data is structured their way, your integrations are built to their APIs, your team has learned their system. The switching cost creates leverage and the vendor knows it when renewal conversations come around.

Buying solves the maintenance problem and creates a dependency problem in its place.

Configure: the third option

Configuration sits between building and buying. You do not build from scratch because the platform exists, the core functionality is proven and the infrastructure is maintained by someone else. Updates, security and scalability are handled for you.

You do not simply accept a rigid system either. You configure it, shaping the platform to your business without writing code, using the no-code and low-code tools that modern platforms provide.

Product configuration, workflow design, underwriting rules, rating logic, document templates, user interfaces, all adjustable by your team, in your time, without waiting for a development cycle. The platform provides the foundation and you provide the specifics.

This is the middle ground between reliability and agility. You get an enterprise-grade platform that is tested and backed by a vendor investing in its future. You also get the agility to change. Launch a new product, adjust a workflow, respond to a regulatory shift, add a distribution partner, all without raising a change request and joining a queue.

The 95% nobody should want to build

The strongest version of the build argument is that configuration cannot handle the things that genuinely matter. The differentiated parts. The reasons your business is not like everyone else’s.

That argument deserves a closer look.

A core insurance platform handles a lot of things that are not differentiators. Task management. Address fields. Document storage. Basic reporting. User permissions. Audit logs. Workflow state. The plumbing every insurer needs and nobody wins on. Building that from scratch is spending senior engineering time on commodity functionality so you can feel like you own it.

Press most build advocates and the argument narrows quickly. What they want to control is the 5% of what they do that genuinely differentiates them. The rest of the system is just the cost of getting to that 5%.

Configuration answers this directly. You take a platform that resolves the 95% you were always going to need, and you build the differentiating 5% on top of it. Or you ask your vendor to build it for you as an extension.

This is usually where the build case collapses. If that 5% is important enough to justify constructing an entire core system from the ground up, it is surely important enough to pay your vendor a fraction of that cost and time to build it as an extension on a platform that already works. If you are not willing to pay for it as an extension, the harder question is whether it was ever as differentiating as you told yourself it was.

Most of the things used to justify building from scratch turn out, on closer inspection, to be commodity functionality dressed up as special, or genuinely differentiated features that could have been built on top of a working platform in a fraction of the time.

What configuration looks like in practice

Configuration is not a new word, but the depth of what can actually be configured has changed dramatically.

A decade ago, configuration meant adjusting some settings. Changing a label, tweaking a threshold, anything more substantial still required development. Modern platforms work at a different level.

Take product building. A configurable platform lets underwriters or product managers define a new insurance product without developer involvement. They set the risk fields, the rating logic, the rules for referral, the documents generated and the questions asked at quote stage. They test it, refine it and push it live.

Hayes Parsons used this approach to take a new yacht insurance product from specification to market in ten days. The point is not the speed in isolation. It is that the speed came from the product team owning the build directly, without a developer queue sitting between the underwriting decision and the live product.

Arma Karma went further. They stood up an entire policy administration platform with Genasys in seven days. Not a single product inside an existing implementation but the whole system from zero. The difference between that and a traditional implementation is not measured in weeks. It is measured in months and quarters. That is what depth of configuration makes possible when the platform underneath is built for it.

Workflow design works the same way. A configurable platform lets operations teams define how work moves through the business. What triggers a task, who it gets assigned to, what happens when it is completed, what escalates and when. This is not a diagram handed to IT to implement. It is a workflow the business builds and owns.

Integrations sit in the same category. Open APIs let you connect to external systems without custom development. A rating engine, a payment gateway, a third-party enrichment service, your general ledger. The platform handles the plumbing and you decide what connects to what.

Why Buy versus Build versus Configure matters now

A few shifts have moved configuration past the old build-or-buy debate.

The talent shortage is real. The people who built your legacy systems are retiring. Developers who understand COBOL are expensive and getting harder to find. Relying on scarce technical skills for every business change is not sustainable. Configuration moves power to the people who already understand the business: underwriters, product managers and operations leads who know what needs to change and why.

Speed has become a competitive advantage in its own right. The MGA market has grown rapidly and the firms winning are the ones who can launch products quickly, respond to market shifts and onboard new distribution partners without months of lead time. A rigid system cannot keep that pace.

The regulatory environment is tightening at the same time. The FCA has drawn a direct line between legacy infrastructure and operational fragility, and operational resilience is moving from good practice toward compliance requirement. Configuration allows faster response to regulatory change because a new requirement can be reflected in workflows, documents and rules without waiting for a software release.

The questions to ask

If you are evaluating platforms the question is no longer just build or buy. It is how much of the platform you actually control once it is yours.

Ask how much can be configured without code and ignore the marketing answer. Get specific. Can you build a product end to end? Can you change a workflow? Can you add an integration?

Ask who does the configuring. If every change still requires the vendor, you have bought a rigid system with extra steps. Configuration should be in your hands, not theirs.

Ask how deep configuration goes. Surface-level settings are not enough. You need to shape the system to your operating model rather than adjust the cosmetics.

Ask what happens when you need something that cannot be configured. No platform covers every edge case. The question is what the path looks like when you hit the limits. Is there an extension framework? An API layer? A way to add capability without forking the core?

Get straight answers to those four questions and the choice in front of you stops being build versus buy. It becomes a question of how much of the platform will still work the way your business works once the implementation team has gone home. Configuration is what keeps that answer in your hands.

Personalisation is constantly raised as essential if carriers are to remain competitive with emerging service providers. Not just in product development, distrunution channels, Quote & Buy and Mid-Term Adjustments but also throughout insurance claims from simple accidental damage to complex property claims and CAT events.

EY categories nine types of customer.

You can read about these categories in detail via the link at the bottom of this article. They key point is that insurers need to understand the different personas, motivations, requirements if they are to retain customers never mind grow them. 

A recent conversation with Katherine Walker added new insights. Katherine and I have collaborated on insurance claims transformation for a carrier before she  co-founded Startup Sherpa helping the next generation of entrepreneurs and innovators. She has just finished writing this report to be published  October 13th which reveals the motivations of Gen Z and Gen Alpha - your future insurance buyers. 

See the annoucement by Aviva here

With customers having so much choice from traditional annual policiies to UBI products, embedded insurance, subsription services from all kinds of service providers with insurance included personalisation becomes a key differentiator. 

EY goes on to say: -

"To satisfy new demand, engage new customers and retain existing ones, insurers will have to overcome their reputation for delivering sub-par experiences and emphasizing standardized policies and traditional channels over customer needs and preferences. That requires fully operationalizing customer centricity, embedding it deeply in every function and promoting teaming across the organization, as leaders in other sectors have done. We’ve structured our latest NextWave Insurance report around nine key customer types that will define the market on the road to 2030. The report provides insights for insurers looking to seize the growth opportunities these changing expectations and behaviors present, with recommended actions to prepare and optimize operations across the business, including purpose and mission, people, teams and culture, and technology and data. We believe those insurers that take an open-minded, proactive approach to change and remain agile in their innovation efforts will enjoy sustainable growth and se cure market leadership in the decade to come despite challenging economic conditions."

Now, it is one thing to have the vision, strategy, capabilities and people to inniovate and personalise but what about thye technology?

It is hard with the complex systems and platforms whuch have immense depth and breadth of functionality which comes at the cost of less flexibility, low agility and consequently less ability to personalise and iterate. Let's look at core systems and claims platforms. Both are important as it is rare that a carrier, broker or MGA that chooses a core platform soes not find the need to also deploy a claims platform to cater for the wide range and depth of claims from General Inaurance, through Speciality to Commercial. 

Core Systems

These include the old legacy, mainframe driven systems still prevalent across incumbent insurers. Large insurers may have 15, 30, 50 or more technology stacks inherited over years of M&A around the globe. Then there are the more modern legacy core systems like Guidewire and new modern architecture CoreTech like EIS and Genasys.

These core systems are the central computing brain, heart and muscle of insurers.

Old Legacy

Old legacy systems show that mainframes are still relevant whilst at the same time the skills and people able to maintain and upgrade them shrinking. We all have seen cases of bank legacy core systems literally failing during upgrades as one or more links in the high number of workarounds, many times undocumented, fail. Customers without banking for days and even weeks at a time!

Technology partners can create ‘digital wrappers’ around them and integrate at various points of the system. But at the heart of matters you still have an old and vulnerable set of often incompatible mainframes, AS400s and UNIX servers chugging away like steam engines in our current digital worlds.

New Legacy

That gave the opportunity for Guidewire which formed in 2000 and went for IPO in 2012. It underpins over 450 insurers globally and is the gorilla in the market and Gartner Magic Quadrant Leader for North America and Europe. Duck Creek, Sapient, Majesco and others have established themselves in the market since 2000.

Why do I term them new legacy? Because they are rooted in a traditional server platform. They may have deployed to the cloud but no more than stuffing a large, inflexible, and traditional enterprise app which behaves the same. Like the on-premises model it is dependent on armies of Systems Integrators, Consultants and Developers to help scope, spec and deploy them. The result is hard-coded, complex, and generally inflexible platforms that involve expensive and long-winded upgrades every three to five years. There is no dynamic scaling up or down capability by specific products, markets or lines of business as demand changes. It’s an all or nothing deployment on the cloud.

But they work, are comprehensive, have international coverage and cope with high volume transactional models required by Tier One to Tier Three insurers and brokers.

They have partners and marketplaces to help insurers integrate best-of-breed point software like Shift, Tractable. All have cloud versions, but these vary in completeness and Gartner may, for example, warn that

“XYZ does not offer a true SaaS model. The application is not deployed multitenanted, and the vendor’s contract requires commitment to minimum terms and minimum volumes. Insurance CIOs will need to ensure they do not overcommit to volumes and capabilities to ensure they are not overpaying for the solution over the term of the agreement.”

Gartner may question the capabilities to execute well particularly the further from their core home markets e.g., North America.

Size has its advantages and I have included an indicator in the table below i.e., the number of deployments in North America and Europe. The data is supplied to Gartner by vendors for 2021 and where you see N/A the vendor does not appear in the 2022 Gartner Insurance Core Systems (P&C) reports for an insufficient volume of deployments.  

Tellingly, many insurers implement one line of business, e.g. auto, with these core systems but not another like home. The time, cost and shear resourcing requirements can drain ambition, budgets, and people. That’s not to say insurers cannot run all lines of business on them- just that the cost and effort is high.

That opens potential for the cloud-native, serverless, micro-services and API architecture platforms that can be scaled up from one line of business and across all lines. Subscription licensing removes cost as a barrier especially as you can say goodbye to expensive upgrades. Every customer will be on the latest version of the software and that being so can be assured of competent support by the vendor. Deployed on public cloud platforms like Amazon AWS and Azure they are infinitely scalable and their large API libraries make them ideal for integration with 3rd party applications and data sources

Many new legacy vendors will say they have SaaS versions, but they are rarely complete and often a mix of vendor or customer hosted rather than public cloud.

CoreTech

This is a term coined to describe 100% cloud-native core platforms that can deliver the functionality of ‘new legacy platforms’ from serverless platforms like Amazon AWS, Azure, Google.

They can scale up to millions of transactions whilst starting on the initial steps of the "stairway to heaven". They can license specific modules and offer subscription licensing for cost-effective means to transform and move away from legacy and new legacy platforms  at the speed insurers require.

The list below is not exhaustive whilst giving a good indication of the choices available. You can read detailed SWOT reviews in the Gartner Magic Quadrants:

• Magic Quadrant for P&C Core Platforms, North America
• Magic Quadrant for P&C Core Platforms, Europe

Personalising Claims

70% or more of an insurer's costs are incurred in claims operations and payments and as claims inflation hits carrier's profits hard never has there been a more important time to choose the optimal technology partners to help you address these challenges.

Two years ago or more many carriers looked at digital claims vendors to help augment claims adjusters and transform customer experience. Too often, the price was high and the technology complex. Support from the C-Suite patchy at best. Claims a poor second or third to the glamour of online Quote & Bind, Comparison websites and distribution. Those same carriers are refocussing on claims transformation today and even those that made advances in one line of business are painfully aware that others like home, travel, pet and speciality are often woefully stuck in an analogue rut.

When they look again at the technology offered they often f'ind them grounded in older solutions that had never been challenged by the pandemic and work-from-home, supply chain constraints delaying repair and replacement and costs rising by the day for labour, parts and materials. Estimating packages rooted in times of stability and high availability are no use in today's world of uncertainty. Platforms that require major upgrades every few years at high cost in time and money. Platforms that lack the eFNOL. self-service and delightful customer experience that today's customers demand.

No one vendor offers a solution for every need and the fabled "end-to-end" claims solutions remains a fairy tale. So how best to choose the best option for your business? Find answers below

1. An introduction to the technology
2. The range of options on offer
3. Point Solutions essential to integrate with these platforms
4. The data sources that are vital for optimal decisions and outcomes
5. Start with a roadmap
6. Organisation and structure to innovate
7. The evaluation phase

1) The technology

It is telling that whilst all core technology platforms feature a claims module most customers license a separate digital claims platform. With circa 70% of an insurer’s costs tied up in claims, a key determinate of customer satisfaction and retention, this decision is sensible.

Just as with core platforms you have a range of options including Claims Ecosystems Providers like CoreLogic and Verisk and what you might term Claims CoreTech i.e., modern architecture, cloud native, public hosted, micro-services and API architected with low-code/zero-code self-configurability. Examples include RightIndem and Snapsheet.

Some technology partners specialise e.g., CoreLogic and Synergy (UK) with property, home and contents whilst others cover multiple lines of business e.g. -Verisk, 360Globalnet and RightIndem.

You have the same challenges and opportunities we examined looking at core platforms. Do you put all your trust in a cloud-native, micro-services and API driven platform that has a limited number of customers, scaled only to modest claims volumes and may have shown focus in only one or two lines of business?

Or do you choose a proven “new legacy option” that has scaled across many large Tier 1 and Tier 2 insurers but has an amount of technical debt hidden in the various modules and tends to be expensive, more complex to deploy and require major upgrades every three/four-year period?

Fortunately, a few digital claim management platforms have scaled up and offer proven ability to deal with millions of claims per annum. And scale up from just thousands to hundreds of thousands of claims at a rate to match your own capabilities. That make it easier to prove the technology in one line of business and, once the technology and relationship is trusted, expanded over the whole business. That means you can offer customers a similar digital UX and satisfaction level across auto, home, travel, pet and all lines of business.

You will require assurance that each platform can integrate with core third party software to build out the functionality, digital UX and claims journey required for all lines of business, different regional/national compliance and regulation and different levels of claims complexity. Many vendors talk of their API documentation and ability to integrate but some lack the stamina and inhouse resources to fulfil the promise. Supporting an integrated ecosystem of technology partners and software is vital as no one technology partner delivers everything.

The fabled “End-to-End” claims promise is too often a case of “The Emperor without Clothes” and you know how that fairy tale ended don’t you?

You will need a claims platform that already passes data in real-time to and from these market leading applications; each one making a decision automatically for simpler claims or enhancing claims adjuster decisioning when human intuition and skills is necessary e.g. more complex and unusual claims. In each case, the claims platform ensures the evidence and decision is validates and passed to the nest step/stage for the next decision(s) to be made.

There are pros and cons for either choice and key to this is the trust you feel you can place in the people involved and relationships with each vendor. Geoffrey Moore is an outstanding advisor on the technology adoption lifecycle and on technology start-ups achieving scale. He emphasises that founders and managers of start-ups are often not the ones suitable to take innovators beyond the first few customers.

A recent research project by Sonr in partnership with EY rates InsurTech’s by a number of characteristics including the capabilities of the people involved. The result is the Insurtech 100 Report (see Further Reading at end of the article).

2) What range of options do you have?

Note: Listed in alphabetical order- no implied ranking of capabilities

Legacy Ecosystem Claims Management Platforms

• CoreLogic for property
• Verisk for property and auto

New Claimstech Management Platforms

• 360SiteView
• Claims Genius
• Claim Technology
• RightIndem
• Salesforce Industries (Insurance)
• Snapsheet
• Synergy Cloud
• Upptec
• Wilbur

No one platform will have everything an insurer, broker, MGA requires. You will need to add third-party solutions to deliver all the requirements an insurer, broker, MGA will demand. Whilst all vendors claim to have large API libraries and integration capabilities many will lack the resources and commitment to be able to connect the required mix of third-party apps and data sources we examine below

 3) Point Solution Software

Policy Admin, Claims Validation and Triage

• HUGHUB
• Iotatach
• Open GI
• Sprout.ai

SMS Communications Platform

• Hi Marley

Claims Damage and Cost Estimation (often combinations of these)

• Be Valued
• CCC
• Claims Genius
• ClickIns
• LexisNexis
• Mitchell
• SLVRCD
• Solera/Audatex
• Tractable
• Upptec
• Value Checker
• Verisk
• Xtract360

Property Repair & Restoration

• Next Gear
• Westhill

Liability Assessment

• BAIL

Counter Fraud

• 360Retrieve
• BAE NetReveal
• Frisk
• Shift

4) Key Data Sources for claims management

Insurance was founded by leveraging the best of data to price risk, provide protection and manage business. “Data-driven” is a familiar refrain but the question is which data and intelligence is best and how can I integrate it into my systems?

Some platforms are positioned as key data providers e.g., CoreLogic for home and property from selling to protection and Verisk for auto and property. Their offerings are most complete in their home territory, North America, and expanding in Europe especially the UK and DACHS regions.

Claims platforms generate data in real-time and are a prime source of intelligence for decision making, fuelling AI, machine learning and rules engines including counter-fraud.

In the New Legacy platforms AI and ML is generally “on the side” in different database silos as the operational database was not designed to support real-time analytics. Being separate the learnings from the AI/ML cannot be connected to the core claims platform. The newer ClaimsTech vendors deem data, data science and analytics central to their platforms.

There is a frightening amount (circa 80% of unstructured data hidden in data silos, web forms, emails, SMS messages, voice files) that insurers must be able to access, normalise and analyse. Yet that data too often lies hidden and the value unrealised.

By the time the data is presented in dashboards, reporting or alerts it is often too late to take timely action and the costs of that failure are high.

New ClaimsTech platforms help address that issue and whilst New Legacy claims platforms will you must beware of the potential complexity, time and cost involved in connecting all those silos and especially delivering real-time insights.

In addition, insurers need to license external data to feed the AI applications penetrating all parts of insurance with a selection listed below. Again, you will want to ensure that claims platforms and core technology can surface and leverage these.

• Accuweather-weather data
• CoreLogic- manage property data for selling, financing, and protecting property
• Hazard Hub- property risk data
• ICEEYE- global flood earthquake and CAT damage data in near real-time
• KETTLE- house-by-house risk assessment across USA
• LexisNexis- vehicle, ADAS and home data
• McKenzie Intelligence Services Ltd wide range of connected data sources and data management
• Mitchell- Auto data
• SAFEHUB- building specific US earthquake damage
• Synectics identity, financial and fraud data
• Terrafirma property risk data
• Verisk- auto and property data
• WeatherNet- granular and near real-time weather data
• WhenFresh- wide range UK property data

5)  Start with a roadmap- Some advice from Geoffrey Moore.

“Let us assume we have a clear design for our desired future state. It won’t take you long to realize there is little chance that a single intervention can get you from here to there. So, the next major deliverable must be a roadmap organized around a maturity model, or what we like to call, a stairway to heaven. Each step up the stairway should be designed to deliver value upon completion, thereby allowing the organization to pace its change management, funding things as it goes, building its confidence, and reassuring its various stakeholders.

With such a roadmap in place, now you have a current-state/future-state accountability mechanism that can govern each stage of the transformation—the software and systems, the systems integrators, the process owners insider your enterprise, and the people responsible for executing the processes. As we have noted elsewhere, digital transformation is not a restaurant. You cannot simply pay for it and have it delivered to your table. It is a gymnasium. You still have to pay for it, but to get any value out, you have to actually do the transformational work yourself.” 

Geoffrey Moore

 6) Organisation and structure to innovate 

Running a business is a challenge and everyday operational issues can take up 70%-80% of time and attention span.

In February 2022 Russia invades Ukraine, cyber activity increases, and Australia suffers CAT flooding. The West’s financial sanctions against Russia impact capital, financial and insurance markets. There are always events soaking up bandwidth and the ability to make and execute decisions.

Nevertheless, innovation, in general, must be a core strategy, but the approach to it must also change, and it must be viewed with a bit of a different lens. When times are challenging for insurers, innovation is usually the first thing to go due to bigger priorities or limited budgets and resources. Carriers may not be able to afford to focus as much as they’d like on innovation during those times.

To stay relevant, however, they must find ways to keep innovative pursuits going and part of their portfolio. Easier said than done, however!

One way is to establish a transformation unit staffed with a mix of staff from the insurer and digital transformation expertise bought in from outside to avoid tunnel vision. Reporting to the CEO directly the Chief Innovation Officer must be able to anticipate disruption, new products hitting the market, new entrants to the market like NeoBanks, and the viable emerging technologies that business and commerce will adopt and deploy.

This team must also work closely with business units, central and business IT, marketing and sales, finance and counter fraud, procurement and legal. It must persuade, make sound business cases and ensure the insurer is not outflanked by competitors or disrupters.

This will help ensure a viable, world-class stairway to heaven plan that is bought in to by the whole company and driven by the digital transformation team. With that in place the insurer is better positioned and resourced to choose the right mix of technology partners

7) The evaluation phase

Gartner published a very useful illustration of the planning and evaluation to be undertaken when choosing technology partners. Combined with the advice above it will help find the right partners to ascend the "stairway to heaven".

The best MGA platforms in 2026: five options compared

MGA platforms are the single biggest technology decision a Managing General Agent will make, and the wrong choice can cost you a year of premium income before you have written a single policy. The market has doubled in five years. U.S. MGAs wrote $114.1 billion in direct premiums in 2024 according to Conning's annual study¹, up 16% year-over-year. Over 1,150 program administrators are competing for capacity². The UK has 350+ MGAs managing over 10% of its general insurance market³, while Continental Europe's 650+ MGAs wrote approximately €18 billion in GWP with a five-year CAGR of 23%⁴.

Private equity now owns more than 30% of all U.S. MGA entities⁵ and fronting carriers generated roughly $28 billion in GWP in 2024⁶. TMPAA's 2025 study flagged fragmented data and technology infrastructure as a top operational concern for program administrators². MGA founders consistently rank speed to market as their number one priority, followed by total cost of ownership, configuration flexibility, API-first architecture and automated bordereaux reporting⁷.

I evaluated five platforms that come up repeatedly when MGAs talk about technology: Genasys, Guidewire, Duck Creek, Insurity and Majesco. Here is what I found.

Genasys

Founded in 1997 in Cape Town and now headquartered in London, Genasys has grown from a South African insurance admin startup into a credible international platform⁸. The company has around 110 employees and took investment from Frog Capital in 2021⁹. Its latest platform, Genasys Unify, is cloud-native on Microsoft Azure and built on a MACH architecture (microservices, API-first, cloud-native, headless)¹⁰.

What sets Genasys apart for MGAs is the combination of speed and scope. The platform delivers policy administration, claims management and billing in a single unified system¹⁰. That is unusual. Most MGA-focused vendors handle only policy admin, leaving you to stitch together separate systems for claims and billing. Implementation timelines are genuinely fast: Arma Karma, a UK subscription-based MGA, received its foundational platform in one week¹¹. GENRIC Insurance went from concept to market in 50 days with just 10 days of technology rollout¹². King Price replaced legacy tech in six weeks¹³.

The platform has 350+ pre-configured product templates across all lines of business, a no-code product builder that lets business users configure products without engineering support and 486 documented REST API endpoints¹⁰. Pricing follows a GWP-based model with an initial setup cost plus monthly licence fee¹⁴, designed to scale with the MGA's revenue rather than punish it from day one. InsTech's profile of Genasys notes that its approach is aimed at organisations that want to avoid multi-million-pound transformation programmes¹⁴.

The limitations are worth noting. Genasys has limited independent validation outside of Celent's vendor directory¹⁵. Its strongest client base is in the UK and South Africa, with no publicly disclosed major U.S. wins. The team is small, which could constrain capacity for large concurrent implementations. There is no self-service onboarding or transparent pricing page, so you will need to engage the sales team.

If you are an early-to-mid-stage MGA in the UK or London Market and you want a fast, full-stack platform covering policy, claims and billing without enterprise-tier pricing, Genasys should be on your shortlist. It is particularly strong for MGAs that need to launch quickly and want no-code configuration rather than months of developer time.

Guidewire

Guidewire (NYSE: GWRE) is the largest P&C insurance technology vendor by revenue at $1.2 billion annually¹⁶. It has 570+ customers across 42 countries and was named the top Leader in Gartner's inaugural 2024 Magic Quadrant for SaaS P&C Core Platforms¹⁷. Its InsuranceSuite, which covers PolicyCenter, ClaimCenter, BillingCenter and the new PricingCenter and UnderwritingCenter modules launched in the December 2025 "Olos" release¹⁸, is the default choice for large carriers.

For MGAs, the relevant product is InsuranceNow, a separate cloud-native platform aimed at regional insurers and mid-market MGAs¹⁹. Guidewire's GM Zachary Gustafson acknowledged in October 2025 that the MGA space is relatively new territory for the company but noted strong momentum, with two MGAs going live in under four months in recent implementations²⁰. Delos Insurance Solutions, a California wildfire MGA, implemented InsuranceNow in six months²¹. The PartnerConnect ecosystem now has over 110 cloud-native integrations²² and 21,000+ trained partner professionals¹⁹.

The downsides for MGAs are well documented. Full InsuranceSuite implementations typically run 12 to 24 months²³. The platform uses Gosu, a proprietary JVM language, which creates dependency on specialised talent that is expensive and hard to find²⁴. User reviews on Software Advice cite cost, UI complexity and a steep learning curve²⁵. Even InsuranceNow, the lighter option, typically takes four to six months.

Guidewire is the right choice for large, well-capitalised MGAs writing $200M+ in GWP that want carrier-grade infrastructure, audit readiness that impresses capacity providers and access to the broadest partner ecosystem in insurance technology. It is not a good fit for startups or budget-conscious operators.

Duck Creek

Duck Creek Technologies was taken private by Vista Equity Partners in 2023 for $2.6 billion²⁶. Its suite covers policy, rating, billing, claims and the Clarity analytics platform, all running cloud-native on Microsoft Azure via Duck Creek OnDemand²⁷. The company has been a Gartner Magic Quadrant Leader for over a decade²⁸ and processes $200+ billion in annual premiums across 200+ customers²⁷.

The platform's low-code configuration is strong. User reviews confirm that 90%+ of requirements can be met without custom code²⁹. The Active Delivery model, launched in August 2024, pushes bi-weekly automatic updates through feature flags, which eliminates traditional upgrade cycles entirely³⁰. Duck Creek introduced a 90-day guaranteed implementation package in 2025³¹, although this likely applies to limited-scope deployments rather than full-suite transformations. Realistic full-suite timelines remain 12 to 18 months.

The problem for MGAs is architectural. Duck Creek was designed with a single carrier at the operational centre²⁷. MGA-specific workflows such as multi-carrier relationships, bordereaux reporting to capacity providers and delegated authority management are not native to the platform. They must be custom-built on top of carrier-centric defaults³². Independent analyses by Regure note that MGAs implementing Duck Creek spend significant customisation budgets building features that purpose-built MGA platforms provide out of the box³². The platform targets organisations writing $100M+ in GWP, and those under $50M often find the cost and timeline prohibitive³³.

Duck Creek suits large, established MGAs writing $100M+ in GWP with complex operations and the resources to invest in a lengthy implementation. It is particularly relevant for those already in the Duck Creek ecosystem or those that value continuous cloud-native updates. It is not suited for smaller MGAs or those needing native delegated authority workflows.

Insurity

Insurity, backed by GI Partners since 2019 with TA Associates as co-investor³⁴, holds the strongest position in the U.S. MGA market by a wide margin. Seven of the top 10 U.S. MGAs run on Insurity's platform, and Datos Insights named it a "Dominant Provider" of MGA core systems in November 2023³⁵. The company serves 500+ customers with 400+ cloud deployments across AWS and Azure³⁶.

The MGA-specific offering is Insurity Pro Suite (formerly Sure MGA Suite), which was assembled through acquisitions of MGA-focused companies including Epic-Premier, Virtual MGA and Instec³⁷. It covers underwriting, policy administration, billing, claims, trading and distribution, agency management and analytics in a single integrated suite³⁸. The Sure Submission Gateway manages delegated authority, enforces underwriting guidelines and handles moratorium updates for insurer-MGA relationships³⁸. The proprietary Valen Data Consortium, built on $109 billion in premium data, powers predictive models that Insurity claims deliver 3x industry average growth and measurably better loss ratios³⁹.

Under CEO Jeff Clarke, who was appointed in January 2025, Insurity committed $50 million in R&D for AI and product innovation⁴⁰. The Andromeda and Borealis releases delivered AI-powered underwriting, a redesigned UI and no-code ML model workflows⁴¹. The company reported 30+ new customer wins in 2025⁴⁰, and Zurich U.S. extended a 30-year collaboration with Insurity in December 2025⁴².

Implementations are not fast. Plan for several months to 12+ months depending on complexity⁴³. User reviews cite recurring software defects after updates, slow loading times and dated UI in older modules⁴³. The platform is heavily U.S.-focused with limited international capabilities⁴⁴.

Insurity is the platform of choice for U.S.-based mid-to-large MGAs that need the most comprehensive purpose-built MGA technology suite available, strong analytics and bureau content management across all 50 states. It is less suited for international MGAs or those that need ultra-fast deployment.

Majesco

Majesco, owned by Thoma Bravo since its $729 million take-private in 2020⁴⁵, has expanded following its November 2025 acquisition of Vitech Systems Group⁴⁶. The platform serves 375+ customers. Celent named its P&C policy admin system a "Luminary" in 2025, which is the highest classification, and awarded it two XCelent awards⁴⁷. The company was named Best InsurTech Team of 2025 by the Global InsurTech Awards⁴⁸.

The MGA-specific product is P&C CoreConnect, purpose-built for MGAs and MGUs⁴⁹. It manages multiple insurers, reinsurers and distribution partners on a unified platform with built-in London and Lloyd's market capabilities⁴⁹. The January 2024 acquisition of Decision Research Corporation added a market-leading enterprise rating engine and 20+ P&C customers⁵⁰. CoreConnect is cloud-native on Azure with an API-first, microservices-based composable architecture⁴⁹.

The standout MGA development is the MGA Model Office, launched in the autumn of 2025. It is a fully pre-configured, production-ready MGA system available on-demand with third-party integrations and pre-built line-of-business products⁵¹. Majesco's AI investment is the most aggressive in this group, with 13 AI Agents across P&C workflows, the Majesco Copilot GenAI assistant embedded on every screen and plans to quadruple AI investment in 2026⁵². The Digital1st EcoExchange marketplace provides plug-and-play partner integrations with pay-per-use pricing⁵³. Pricing follows a DWP-based usage model aligned to MGA growth⁵⁴.

User reviews on SelectHub note integration challenges and a learning curve with older UI modules⁵⁵. The platform is less proven for the smallest, earliest-stage MGAs despite the Model Office initiative.

Majesco suits mid-market MGAs that want a dedicated, AI-native platform with multi-carrier management, London and Lloyd's market access and growth-aligned pricing. It is particularly compelling for MGAs that view AI-augmented underwriting and claims as a competitive advantage.

How to think about the decision

The market has split into three tiers. Enterprise incumbents like Guidewire and Duck Creek offer unmatched breadth and carrier credibility but come with implementation timelines, costs and complexity that most MGAs under $100M GWP cannot justify. Guidewire's InsuranceNow is its most relevant MGA offering and is improving rapidly. Duck Creek's carrier-centric architecture remains a structural limitation for delegated authority models.

MGA-focused incumbents like Insurity and Majesco are the middle ground. Insurity's market dominance is earned. No other vendor serves as many top-tier U.S. MGAs, and its analytics capabilities are genuinely differentiated. Majesco's CoreConnect and MGA Model Office show the strongest intent to win MGA-specific business, with AI capabilities that outpace the other four and London market support that Guidewire and Duck Creek largely lack.

Agile challengers like Genasys offer the speed and cost profile that early-stage and growth-stage MGAs actually need. Genasys stands out for combining genuine speed, with one-week deployments documented¹¹, with full end-to-end scope across policy, claims and billing. That combination is rare among MGA-specific platforms.

An MGA founder launching with $10M in GWP and needing to go live in weeks should start with Genasys or Majesco's Model Office. A $200M+ MGA consolidating onto an enterprise platform with carrier-grade reporting should evaluate Insurity or Guidewire's InsuranceNow. Any MGA with London or Lloyd's ambitions should shortlist Genasys or Majesco, where that market support is native rather than bolted on.

Every month spent implementing technology is a month of premium you are not writing.

References

1. Conning, 2025 Managing General Agents Study, 2025. https://www.conning.com/about-us/news/ir-pr---mga-2025
2. Insurance Journal, "Growth Momentum Continues for Program Business: TMPAA," Insurance Journal, December 2025. https://www.insurancejournal.com/magazines/mag-features/2025/12/01/848712.htm
3. IDEX Consulting, "MGA Outlook: Is Growth Clashing with Capacity Concerns?," June 2025. https://www.idexconsulting.com/blog/2025/06/mga-outlook-is-growth-clashing-with-capacity-concerns
4. Global Reinsurance, "Europe's MGA Market Rises as Tech-Driven Growth Channel, Says Howden Re," 2025. https://www.globalreinsurance.com/home/europes-mga-market-rises-as-tech-driven-growth-channel-says-howden-re/1455460.article
5. Deloitte, "MGAs as Additional Sources of Growth for Private Equity," Deloitte US, 2025. https://www.deloitte.com/us/en/Industries/financial-services/articles/why-mgas-next-big-opportunity-for-private-equity-investors.html
6. Risk & Insurance, "MGA Business Surges to $100 Billion as Fronting Carriers Spur Growth," 2025. https://riskandinsurance.com/mga-market-surges-to-100-billion-as-fronting-carriers-spur-growth/
7. MGA Insurance Software, MGA Policy Administration Systems Guide 2025, 2025. https://www.mgainsurancesoftware.com/
8. Insurance Edge, "25 Years Stacked Up by Genasys Tech," October 2022. https://insurance-edge.net/2022/10/05/25-years-stacked-up-by-genasys-tech/
9. Genasys Technologies, "Genasys Secures R260M Investment from Frog Capital," 2021. https://www.genasystech.com/genasys-secures-investment-from-frog-capital/
10. Genasys Technologies, MGA Insurance Software Solutions, 2025. https://www.genasystech.com/product/mga-insurance-software-solutions/
11. Genasys Technologies, "Policy Administration System: Rapid Launch Success in 1 Week," 2025. https://www.genasystech.com/policy-administration-system-in-just-1-week/
12. Genasys Technologies, "Rapid Speed to Market," 2025. https://www.genasystech.com/speed-to-market/
13. FAnews, "Insurtech 'Disruptor' Genasys Reflects on 25 Years of Business," 2022. https://www.fanews.co.za/article/company-news-results/1/general/1056/insurtech-disruptor-genasys-reflects-on-25-years-of-business-cut-through-the-hype-and-use-tech-to-solve-genuine-problems/35603
14. InsTech, "Genasys Technologies Member Profile," 2025. https://www.instech.co/member-profiles/genasys-technologies/
15. Celent, "Software Key to Insurance (SKi): Genasys Technologies," 2025. https://www.celent.com/vendormatch/discovery/solutions/189280137
16. Stock Analysis, "Guidewire Software (GWRE) Revenue 2016-2025," 2025. https://stockanalysis.com/stocks/gwre/revenue/
17. Guidewire, "Guidewire Recognized as a Leader in the Inaugural 2024 Gartner Magic Quadrant for SaaS P&C Core Platforms," October 2024. https://www.guidewire.com/about/press-center/press-releases/20241017/guidewire-recognized-leader-2024-gartner-magic-quadrant-saas-pc-core-platforms-na-insurancesuite
18. Guidewire, "Guidewire Olos Release Powers Intelligent Pricing," December 2025. https://www.guidewire.com/about/press-center/press-releases/20251208/guidewire-olos-power-intelligent-pricing-drive-faster-rate-changes-enhance-workers-comp-performance
19. Guidewire, Solutions for Managing General Agents, 2025. https://www.guidewire.com/products/solutions/solutions-for-managing-general-agents
20. Insurance Innovation Reporter, "ITC Briefing: Guidewire's Zachary Gustafson on Momentum within the MGA Market," October 2025. https://iireporter.com/itc-briefing-guidewires-zachary-gustafson-on-momentum-within-the-mga-market/
21. PR Newswire, "Delos Insurance Solutions Partners with Exavalu to Implement Guidewire InsuranceNow," 2023. https://www.prnewswire.com/news-releases/delos-insurance-solutions-partners-with-exavalu-to-implement-guidewire-insurancenow-cloud-platform-successfully-to-deliver-protection-to-wildfire-exposed-homes-in-california-301984207.html
22. Guidewire, "Guidewire PartnerConnect Ecosystem Surpasses 110 Cloud-Native Integrations," January 2025. https://www.guidewire.com/about/press-center/press-releases/20250110/guidewire-partnerconnect-ecosystem-surpasses-110-cloud-native-integrations
23. Guide Wire Masters, "Implementation Strategies for Guidewire Integration," 2025. https://guidewiremasters.in/implementation-strategies-for-guidewire/
24. Guidewire, Gosu Programming Language, 2025. https://www.guidewire.com/developers/developer-tools-and-guides/gosu-programming-language
25. Software Advice, "Guidewire Software Reviews, Demo & Pricing," 2026. https://www.softwareadvice.com/policy-management/insurancesuite-profile/
26. TechCrunch, "Vista Equity Partners to Acquire Insurance Software Company Duck Creek for $2.6B," January 2023. https://techcrunch.com/2023/01/09/vista-equity-partners-to-acquire-insurance-software-company-duck-creek-for-2-6b/
27. Duck Creek Technologies, Policy Management Software, 2025. https://www.duckcreek.com/product/policy-management-software/
28. Gartner, "Duck Creek Reviews, Ratings & Features 2025," 2025. https://www.gartner.com/reviews/market/finance/vendor/duck-creek
29. SelectHub, "Duck Creek Reviews 2026: Pricing, Features & More," 2026. https://www.selecthub.com/p/insurance-software/duck-creek/
30. Duck Creek Technologies, "2025 Partner of the Year Award Winners," 2025. https://www.duckcreek.com/blog/duck-creek-technologies-announces-2025-partner-of-the-year-award-winners/
31. Insurance Business America, "Duck Creek Launches New Policy Administration Solution," 2025. https://www.insurancebusinessmag.com/us/news/technology/duck-creek-launches-new-policy-administration-solution-500195.aspx
32. Regure, "Regure vs Duck Creek Claims: Modern Alternative for MGAs & Brokers," 2025. https://www.getregure.com/blog/regure-vs-duck-creek-claims-comparison/
33. Regure, "Regure vs Duck Creek: Insurance Platform Comparison," 2025. https://www.getregure.com/compare/regure-vs-duck-creek/
34. Business Wire, "Insurity Announces Growth Investment from TA Associates," November 2021. https://www.businesswire.com/news/home/20211109006158/en/Insurity-Announces-Growth-Investment-from-TA-Associates
35. Business Wire, "Datos Insights Recognizes Insurity as a Dominant Provider of MGA Solutions," November 2023. https://www.businesswire.com/news/home/20231129971438/en/Datos-Insights-Recognizes-Insurity-as-a-Dominant-Provider-of-MGA-Solutions
36. Insurity, Insurity Platform, 2025. https://insurity.com/insurity-platform
37. Insurity, "Insurity Expands Commitment to the MGA Market," 2024. https://insurity.com/press-release/insurity-expands-commitment-mga-market-creating-most-comprehensive-mga-product-suite
38. Insurity, Insurity for MGAs, 2025. https://insurity.com/markets/mga
39. Insurity, Insurity Predict: Predictive Analytics in Insurance, 2025. https://insurity.com/insurity-analytics/predictive-analytics
40. Insurity, "Building on 30+ New Logo Wins in 2025," 2025. https://insurity.com/press-release/building-30-new-logo-wins-2025-insurity-showcase-next-phase-50-million-product
41. Insurance Innovation Reporter, "Insurity Andromeda Release Follows $50M Investment in AI Capabilities," 2025. https://iireporter.com/insurity-andromeda-release-follows-50m-investment-in-ai-capabilities/
42. Business Wire, "Zurich U.S. Extend 30-Year Collaboration with Insurity," December 2025. https://www.businesswire.com/news/home/20251204028933/en/Zurich-U.S.-Extend-30-Year-Collaboration-with-Insurity-Advancing-Cloud-based-Policy-Administration-and-Bureau-Managed-Services
43. Nerdisa, "Insurity Review: Streamline Policy Processing & Boost Regulatory Compliance," 2025. https://nerdisa.com/insurity/
44. SelectHub, "Insurity Reviews 2025: Pricing, Features & More," 2025. https://www.selecthub.com/p/policy-administration-systems/insurity/
45. Majesco, "Majesco Enters Into Amended Agreement To Be Acquired by Thoma Bravo," 2020. https://www.majesco.com/press/majesco-enters-into-amended-agreement-to-be-acquired-by-thoma-bravo/
46. Business Wire, "Majesco to Acquire Vitech," November 2025. https://www.businesswire.com/news/home/20251120805721/en/Majesco-to-Acquire-Vitech-Creates-Insurance-Industrys-Premier-Technology-Partner-for-Group-Benefits-and-Retirement-Pension-Markets-with-Advanced-AI-Powered-Intelligent-Solutions
47. Morningstar/Business Wire, "Majesco Intelligent Policy for P&C Named Luminary in Celent Report, Wins Two XCelent Awards," April 2025. https://www.morningstar.com/news/business-wire/20250430189762/
48. Business Wire, "Majesco Named Best InsurTech Team of 2025 by the Global InsurTech Awards," November 2025. https://www.businesswire.com/news/home/20251113848919/en/Majesco-Named-Best-InsurTech-Team-of-2025-by-the-Global-InsurTech-Awards
49. Majesco, P&C CoreConnect: MGA Insurance Software, 2025. https://www.majesco.com/core-software-insurance-solutions/pc-coreconnect/
50. Thoma Bravo, "Majesco Acquires the Decision Research Corporation Business," January 2024. https://www.thomabravo.com/press-releases/majesco-acquires-the-drc-business-bringing-market-leading-enterprise-rating-and-complementary-core-platform-for-the-rapidly-growing-mga-mgu-and-sm-1704489988335
51. Majesco, "Majesco Launches Fall '25 Release with AI Agents," 2025. https://www.majesco.com/press/majesco-launches-fall-25-release-with-ai-agents-to-transform-intelligent-insurance-operations/
52. Reinsurance News, "Majesco to Quadruple AI Investment to Expand, Accelerate P&C Roadmap," 2025. https://www.reinsurancene.ws/majesco-to-quadruple-ai-investment-to-expand-accelerate-pc-roadmap/
53. Majesco, "Ready-To-Use Partner Apps in Majesco Digital1st EcoExchange," 2025. https://www.majesco.com/press/majesco-announces-ready-to-use-partner-apps-in-majesco-digital1st-ecoexchange/
54. Majesco, P&C CoreConnect eGuide, 2025. https://www.majesco.com/eguides/majesco-pc-coreconnect/
55. SelectHub, "Majesco Reviews 2025: Pricing, Features & More," 2025. https://www.selecthub.com/p/insurance-software/majesco/

Guidewire is the default answer when an insurer goes looking for a core platform. It has 739 InsuranceSuite customers, roughly $1.44 billion in annual revenue and a place as a Leader in the 2024 Gartner Magic Quadrant for SaaS P&C Core Platforms.^1,2 For a Tier 1 carrier writing billions in premium, the case is straightforward. For everyone else, the economics fall apart quickly.

Standard InsuranceSuite implementations take 12 to 24 months and require engagement with enterprise systems integrators such as Accenture, PwC or Capgemini, billing at $200 to $400+ per hour.³ Capgemini markets its ability to reduce Guidewire total cost of ownership by up to 40%, which tells you everything you need to know about what the baseline looks like.⁴ SaaS pricing is pegged to direct written premium, so costs escalate automatically as a book grows. Two Guidewire customers will each exceed $20 million in annual recurring revenue during their current contract terms.² User reviews on G2 consistently cite system complexity and cost as top complaints, and one Capterra reviewer described it as the least intuitive software they had ever used.^5,6

Guidewire knows it has a mid-market problem. InsuranceNow, its lighter-weight platform acquired from ISCS, is the explicit answer for regional and super-regional carriers. But InsuranceNow has just 122 customers versus InsuranceSuite’s 739⁷ and the gap between the two products in analyst coverage and customer confidence is wide. Pre-packaged “InsuranceNow GO” implementations and a new Rapid Implementation specialisation requiring partners to go live within six months are welcome, but unproven at scale.⁸

The result is a large and growing market of MGAs, regional carriers, specialty insurers and brokers that need modern policy administration but cannot justify Guidewire’s cost structure or timelines. Five vendors are competing aggressively for this segment. Each has a different sweet spot, and each has weaknesses worth understanding.

Duck Creek: the enterprise alternative with a mid-market ceiling

Duck Creek Technologies is the most direct Guidewire competitor at scale. Taken private by Vista Equity Partners for $2.6 billion in March 2023,⁹ the company reported $302.9 million in total revenue for its final public fiscal year, with SaaS ARR of $169.3 million growing 25% year-over-year.¹⁰ Its customer base of roughly 335 includes Progressive, Liberty Mutual, AIG, The Hartford and Berkshire Hathaway Specialty Insurance.¹¹

The platform runs natively on Microsoft Azure and covers policy, billing, claims, rating, distribution management and reinsurance. Duck Creek’s “OnDemand” SaaS model delivers continuous evergreen updates, eliminating painful major-version upgrades. Speed-to-deployment claims are backed by real examples: Munich Re Specialty went live on the full suite in 90 days, and Australian startup Argyle Insurance deployed end-to-end in under 60 working days.^12,13

But Gartner Peer Insights tells a cautionary story. Duck Creek scores 3.2 out of 5 stars from 17 reviews versus Guidewire’s 4.7 from 99 reviews.¹⁴ Reviewers cite dated developer tooling and code quality issues. Competitor analysis suggests Duck Creek’s cost structure frequently fails a basic ROI test for MGAs writing less than several hundred million in premium,¹⁵ and its workflows remain carrier-centric, lacking native delegated authority and bordereaux features. Vista Equity’s ownership introduces R&D uncertainty; Forrester has noted Vista’s reputation for cost-cutting.¹⁶

Best fit: regional and specialty carriers writing $250 million to $2 billion+ in premium who want cloud-native SaaS without Guidewire’s complexity, and who have the scale to justify the cost.

Majesco: broad platform, strong MGA play, unproven at the top

Majesco, acquired by Thoma Bravo for $729 million in September 2020,¹⁷ has transformed under private equity ownership. It flipped its revenue mix from 70% services to approximately 65% software, acquired four companies including Vitech Systems Group in January 2026, and now claims roughly $500 million in revenue serving 375+ customers processing over $100 billion in DWP.¹⁸

The platform runs a deliberate two-tier strategy. The P&C Intelligent Core Suite targets mid-to-large carriers with full policy, billing, claims and embedded GenAI. P&C CoreConnect is purpose-built for MGAs, MGUs and smaller P&C insurers, and the recently launched MGA Model Office promises production-ready deployments reducing implementation from months to weeks.¹⁹ Concrete results back the claim: AmCap Insurance went from inception to go-live on the full suite in eight months, and MMG Insurance deployed a digital agent portal in five months, achieving a 6% increase in quote volume and a 20% increase in average premium per policy.^20,21

Majesco’s AI investment is a genuine differentiator. It launched 13 AI Agents in its Fall 2025 release and plans to quadruple AI investment in 2026.^22,23 QKS Group ranked it first for AI maturity, and Gartner has named it a Magic Quadrant Leader for P&C six consecutive times.²⁴

Weaknesses centre on integration maturity and scale. Gartner Peer Insights reviewers flag bugs in cross-module communication, with one noting that producer integration between policy and billing did not work as advertised.²⁵ The partner ecosystem is smaller than Guidewire’s, and brand recognition still lags with conservative CIOs.

Best fit: MGAs and mid-market carriers wanting a single vendor for P&C and L&A, rapid MGA-specific deployment via CoreConnect and embedded AI. Particularly strong for organisations that value speed and digital-first distribution.

Insurity: the deepest regulatory bench in P&C

Insurity positions itself as the second-largest P&C core system vendor by revenue. Based in Hartford, Connecticut, and owned by GI Partners and TA Associates, it generates $330 million+ in revenue with EBITDA margins exceeding 35%.²⁶ Its customer base of 500+ carriers, MGAs and brokers includes 22 of the top 25 U.S. P&C carriers and 7 of the top 10 U.S. MGAs.²⁷

The competitive moat is regulatory and bureau content management. Insurity’s Circ service processes 12,000+ regulatory changes annually across all 50 states, handling 3,000+ bureau changes per year. CEO Chris Lafond has identified this as the number one piece of customer feedback.²⁸ For commercial lines carriers dealing with relentless compliance complexity, this is hard to replicate.

The product portfolio reflects aggressive acquisition (12+ completed). Implementation timelines range from 90 days for a single line of business to six months for more complex deployments, with Bridge Specialty templates reducing implementation costs by up to 60%.²⁹ Insurity recorded 20 successful customer go-lives in the first half of 2025 and won 30+ new logos that year. A $50 million AI and R&D investment produced the Andromeda release in November 2025.^30,31

Weaknesses are real. Multiple product lines from acquisitions create confusion. Gartner reviewers note that integration capabilities are adequate but immature compared to competitors.³² The footprint is overwhelmingly U.S.-focused with limited international presence.

Best fit: commercial lines carriers, specialty insurers and MGAs in the U.S. who need deep regulatory compliance, bureau content management and analytics, particularly in workers’ compensation and specialty lines.

BriteCore: lowest cost, smallest footprint

BriteCore occupies a distinct niche: Tier 4 and Tier 5 P&C insurers, typically under $500 million in DWP. The Springfield, Missouri company has approximately 60 to 100 employees, an estimated $12.5 million in annual revenue and has raised $62 to $93 million in total funding led by Warburg Pincus.^33,34 It serves 100+ insurers across North America with $1.1 billion in total DWP on platform.³⁵

The architecture is genuinely API-first, with 924 published APIs allowing carriers to run the platform headlessly with custom front-ends.³⁶ Built natively on AWS, the platform delivers policy administration, billing, claims, portals and analytics as a unified SaaS offering. Pricing follows a metered model at roughly 1% of premium for core access, plus approximately 0.25% for BriteApps and around $500 per month for AWS hosting.³⁷ That makes it radically more affordable than any enterprise alternative.

Customer outcomes are strong for its segment. Baldwin Mutual tripled employee productivity. East Tennessee Mutual tripled direct written premiums. Average client DWP growth on the platform is 20%, rising to 47% for MGA clients.³⁸ BriteCore was included in the 2024 Gartner Magic Quadrant for SaaS P&C Core Insurance Platforms.³⁹

Limitations are straightforward. BriteCore is a small company. Reporting tools are described as restrictive for advanced customisation.⁴⁰ Complex commercial and specialty lines depth lags enterprise platforms. BriteCore is largely unproven above Tier 4 carriers and promotes a “multicore” approach, encouraging large Guidewire customers to deploy it alongside for new lines of business rather than claiming to fully replace enterprise platforms.⁴¹

Best fit: small mutual carriers, regional P&C insurers under $500 million DWP and fast-growing MGAs in personal lines that find Duck Creek and Guidewire prohibitively complex and expensive.

Genasys: the fastest route from idea to live product

Genasys Technologies is a South African-founded, UK-headquartered insurtech with 25 years in the market and approximately 110 employees.⁴² It raised £12.25 million from Frog Capital in December 2021 and operates in a fundamentally different way to the vendors above.⁴³ Where Guidewire, Duck Creek and Majesco compete on breadth of enterprise features, Genasys competes on speed. Where BriteCore and Insurity are primarily North American, Genasys has a genuinely international footprint spanning 23 countries.⁴⁴

The Genasys Unify platform is a true composite system covering P&C, life, health and specialty lines, deployed on Microsoft Azure with 450+ REST API endpoints and a no-code product builder with 350+ pre-configured templates.⁴⁵ The deployment speed claims are not theoretical. UK MGA Arma Karma received a foundational platform in one week and went to market in under six weeks.⁴⁶ South African insurer King Price deployed a new engineering product in six weeks and grew premium from R500 million to R4 billion on the platform.⁴⁷ GENRIC Insurance reduced product speed-to-market from 12 months to 10 days.⁴⁸ Hayes Parsons, a UK broker, launched a new product in 10 days.⁴⁹

That speed is the product of architectural decisions made years ago. The no-code product builder means insurers and MGAs configure products, rating engines, underwriting rules and document templates without writing code and without waiting for the vendor’s development team. The 350+ pre-configured templates cover common product structures across personal lines, commercial, specialty, life and health, giving new clients a running start rather than a blank canvas.⁴⁵

The marquee UK enterprise win is Simplyhealth, a multi-year digital transformation migrating over one million health plans.⁵⁰ The platform transacts over £3 billion in gross written premium across 23 countries and manages 1.5 million+ policies.⁴⁴ Other named clients include King Price, GENRIC Insurance, Guardrisk and SA Home Loans in South Africa, alongside a growing UK portfolio.⁵¹

For an MGA or broker with delegated authority that needs to get a product to market in weeks rather than months, Genasys is the strongest option on this list. The no-code configuration means the business controls product development directly, without queuing behind an SI partner or waiting for a vendor sprint cycle. The composite architecture means a single platform can handle P&C, health and life without bolting on separate systems. And the cost structure, as a modular SaaS offering without DWP-pegged enterprise pricing, makes it accessible to organisations that would never get past the first conversation with Guidewire or Duck Creek.

The honest limitations are about scale and market position. Genasys does not appear in any Gartner Magic Quadrant or Forrester Wave. The majority of named customers and case studies are South African, though the UK client base is growing with Simplyhealth and others. For a Tier 1 U.S. carrier running a $5 billion book of commercial auto, Genasys is not the right answer. For a UK MGA that needs to launch three products in the next quarter, it is hard to see a better one.

Picking the right fight

The decision comes down to what kind of organisation you are and what you need to do next. A U.S. commercial lines carrier with deep regulatory obligations should look at Insurity. A regional carrier writing $250 million to $1 billion that wants an enterprise-grade alternative to Guidewire should evaluate Duck Creek and Majesco. A small mutual or Tier 4 carrier in personal lines should talk to BriteCore.

And an MGA, broker or insurtech startup in the UK that needs to move fast, launch products in days or weeks and avoid the cost and complexity of enterprise platforms should put Genasys at the top of the list. In a market where the biggest vendors measure implementation timelines in years, a platform that can get you live in weeks is not a compromise. It is a competitive advantage.

References

1. Guidewire, “Guidewire Recognized as a Leader in the Inaugural 2024 Gartner Magic Quadrant for SaaS P&C Core Platforms, North America,” Yahoo Finance, 2024. https://finance.yahoo.com/news/guidewire-recognized-leader-inaugural-2024-205500510.html

2. Daily Political, “Guidewire Software Q2 Earnings Call Highlights,” 9 March 2026. https://www.dailypolitical.com/2026/03/09/guidewire-software-q2-earnings-call-highlights.html

3. Guide Wire Masters, “Implementation Strategies for Guidewire Integration,” 2025. https://guidewiremasters.in/implementation-strategies-for-guidewire/

4. Capgemini, “P&C Insurance Transformation with Guidewire Cloud and Capgemini,” 2025. https://www.capgemini.com/us-en/about-us/technology-partners/guidewire/

5. G2, “Guidewire InsuranceSuite Reviews 2025,” 2025. https://www.g2.com/products/guidewire-insurancesuite/reviews

6. Capterra, “Guidewire Software Pricing, Alternatives & More 2026,” 2026. https://www.capterra.com/p/173704/InsuranceNow/

7. 6sense, “Guidewire InsuranceSuite vs Guidewire InsuranceNow: Insurance Administration And Management Comparison,” 2025. https://6sense.com/tech/insurance-administration-and-management/guidewireinsurancesuite-vs-guidewireinsurancenow

8. Guidewire, “Speed of Implementation: Guidewire Delivery Services and InsuranceNow GO,” 2025. https://www.guidewire.com/resources/blog/technology/speed-of-implementation-guidewire-delivery-services-and-insurancenow-go

9. Duck Creek, “Vista Equity Partners Completes Acquisition of Duck Creek Technologies,” 2023. https://www.duckcreek.com/blog/vista-equity-partners-completes-acquisition-of-duck-creek-technologies/

10. SEC Filing, Duck Creek Technologies FY2022 Results, 2022. https://www.sec.gov/Archives/edgar/data/0001160951/000095017022019497/dct-ex99_1.htm

11. Insnerds, “The Insurance Platform Wars: What Guidewire and Duck Creek’s Rivalry Means for the Industry,” 2025. https://insnerds.com/insights/the-insurance-platform-wars-what-guidewire-and-duck-creeks-rivalry-means-for-the-industry

12. Munich Re, “Munich Re Specialty Insurance and Duck Creek Partner To Develop State-of-the-Art Digital Platform,” 2020. https://www.munichre.com/us-non-life/en/company/media-relations/press-releases/2020/

13. Duck Creek, “Argyle Insurance, Built in Less Than 60 Working Days,” 2023. https://www.duckcreek.com/blog/leveraging-the-speed-and-efficiency-of-duck-creek-technologies-cloud-based-platform-australian-start-up-firm-argyle-insurance-built-in-less-than-60-working-days/

14. Gartner Peer Insights, “Duck Creek vs Guidewire 2026,” 2026. https://www.gartner.com/reviews/market/saas-p-and-c-insurance-core-platforms-north-america/compare/duck-creek-vs-guidewire

15. Regure, “Regure vs Duck Creek Claims: Modern Alternative for MGAs & Brokers,” 2025. https://www.getregure.com/blog/regure-vs-duck-creek-claims-comparison/

16. Insurance Innovation Reporter, “News Analysis: Duck Creek is a Private Company Once Again,” 2023. https://iireporter.com/news-analysis-duck-creek-is-a-private-company-once-again/

17. PR Newswire, “Thoma Bravo Completes Acquisition of Majesco,” September 2020. https://www.prnewswire.com/news-releases/thoma-bravo-completes-acquisition-of-majesco-301134776.html

18. Majesco, “Majesco Delivers Record FY25,” 2026. https://www.majesco.com/press/majesco-delivers-record-fy25/

19. FFNews, “Majesco Launches MGA Model Office for P&C CoreConnect,” 2024. https://ffnews.com/newsarticle/insurtech/majesco-launches-mga-model-office-for-pc-coreconnect-delivering-an-innovative-production-ready-on-demand-mga-system/

20. Majesco, “American Capital Assurance Corp Goes Live with Majesco P&C Suite,” 2023. https://www.majesco.com/press/american-capital-assurance-majesco-pc-suite/

21. Business Wire, “Majesco Congratulates MMG Insurance on Inclusion in Datos Insurance Technology Impact Awards,” August 2023. https://www.businesswire.com/news/home/20230801274921/en/

22. Majesco, “Majesco Launches Fall ’25 Release with AI Agents,” 2025. https://www.majesco.com/press/majesco-launches-fall-25-release-with-ai-agents-to-transform-intelligent-insurance-operations/

23. Reinsurance News, “Majesco to Quadruple AI Investment to Expand, Accelerate P&C Roadmap,” 2025. https://www.reinsurancene.ws/majesco-to-quadruple-ai-investment-to-expand-accelerate-pc-roadmap/

24. Business Wire, “Majesco Named in 2025 Gartner Magic Quadrant for SaaS P&C Insurance Core Platforms,” September 2025. https://www.businesswire.com/news/home/20250925322142/en/

25. Gartner Peer Insights, “Majesco Reviews, Ratings & Features 2026,” 2026. https://www.gartner.com/reviews/market/saas-p-and-c-insurance-core-platforms-north-america/vendor/majesco

26. Insurity, “Insurity’s Continued Growth in 2024 from Market Performance,” 2024. https://insurity.com/press-release/insurity-poised-continued-growth-2024-based-achievements-cloud-based-solutions-and

27. Insurance Innovation Reporter, “Insurity CEO on the Company’s Rising Rank Among P&C Core System Providers,” 2025. https://iireporter.com/insurity-ceo-on-the-companys-rising-rank-among-pc-core-system-providers/

28. Insurance Innovation Reporter, “Insurity CEO on the Company’s Rising Rank Among P&C Core System Providers,” 2025. (ibid.)

29. Insurity, “Insurity Advances Modernization for P&C Insurers with 20 Go-Lives Across Core Insurance Solutions in 2025,” 2025. https://insurity.com/press-release/insurity-advances-modernization-pc-insurers-20-go-lives-across-core-insurance

30. Insurity, “Building on 30+ New Logo Wins in 2025,” 2025. https://insurity.com/press-release/building-30-new-logo-wins-2025-insurity-showcase-next-phase-50-million-product

31. Insurity, “Insurity’s Continued Growth in 2024,” 2024. (ibid.)

32. Gartner Peer Insights, “Guidewire vs Insurity 2025,” 2025. https://www.gartner.com/reviews/market/saas-p-and-c-insurance-core-platforms-north-america/compare/guidewire-vs-insurity

33. Tracxn, “BriteCore – 2025 Company Profile, Team, Funding & Competitors,” 2025. https://tracxn.com/d/companies/britecore/

34. Growjo, “BriteCore: Revenue, Competitors, Alternatives,” 2025. https://growjo.com/company/BriteCore

35. BriteCore, “About BriteCore,” 2025. https://www.britecore.com/company/about-us

36. BriteCore, “Guidewire vs BriteCore,” 2025. https://www.britecore.com/promotion/guidewire-vs-britecore

37. GetApp, “BriteCore Pricing Plan & Cost Guide,” 2025. https://www.getapp.com/industries-software/a/britecore/pricing/

38. BriteCore, “Best P&C Insurance Policy Administration Software,” 2025. https://www.britecore.com

39. Gartner, “Gartner Magic Quadrant for SaaS P&C Insurance Core Platforms, North America,” 2024. https://www.gartner.com/en/documents/5827147

40. SelectHub, “BriteCore Reviews 2026: Pricing, Features & More,” 2026. https://www.selecthub.com/p/insurance-software/britecore/

41. BriteCore, “Guidewire vs BriteCore,” 2025. (ibid.)

42. FAnews, “Insurtech ‘Disruptor’ Genasys Reflects on 25 Years of Business,” 2024. https://www.fanews.co.za/article/company-news-results/1/general/1056/insurtech-disruptor-genasys-reflects-on-25-years-of-business/35603

43. InsurTech Digital, “Genasys Secures £12.25M Investment from Frog Capital,” 2021. https://insurtechdigital.com/insurtech/genasys-secures-ps1225m-investment-frog-capital

44. InsTech, “Genasys Technologies Member Profile,” 2025. https://www.instech.co/member-profiles/genasys-technologies/

45. Genasys Technologies, “Modern Policy Administration System for Insurers & MGAs,” 2025. https://www.genasystech.com/policy-administration/

46. Genasys Technologies, “Arma Karma: Launching a Policy Administration System in One Week,” 2024. https://www.genasystech.com/policy-administration-system-in-just-1-week/

47. Genasys Technologies, “Case Studies,” 2025. https://www.genasystech.com/resources/case-studies/

48. Genasys Technologies, “Case Studies,” 2025. (ibid.)

49. Genasys Technologies, “Case Studies,” 2025. (ibid.)

50. Genasys Technologies, “Simplyhealth Teams Up with Genasys on Digital Transformation Programme,” 2024. https://www.genasystech.com/simplyhealth-teams-up-with-genasys-on-digital-transformation-programme/

51. Genasys Technologies, “Genasys & Simplyhealth: New Policy Delivery Milestone,” 2025. https://www.genasystech.com/genasys-and-simplyhealth-hit-new-policy-delivery-milestone/

Despite lazy narrative to the contrary, insurance technology is evolving at an astonishing pace, with a proliferation of innovative solutions emerging across the industry. A recent Insurtech 50 report highlighted 50 cutting-edge companies, underscoring the breadth of technology being used to enhance the insurance customer experience.

With so many opportunities and new tools available, insurers, brokers, and MGAs are recognizing that no single organisation can develop all necessary capabilities in-house. Instead, the ability to orchestrate different technologies to provide unique, seamless experiences such as easy access to personalised products and frictionless digital claims journeys is now seen as key to driving future success in insurance. In fact, more than 75% of global insurance executives view digital ecosystems and partnerships as essential to creating competitive advantage (ey.com).

Embracing an ecosystem approach in insurance technology is increasingly not just an IT strategy, but a business imperative for those seeking a competitive edge.

The Ecosystem Approach in Modern Insurance

An ecosystem approach in insurance involves integrating a network of specialised tech solutions and partners into a cohesive platform, rather than relying on one monolithic system. Advancements in cloud computing and open APIs have made this possible by making technology more open, available, and cost-efficient.

Curating the right mix of technologies into a unified ecosystem can drive far more innovation and differentiation than spending years developing proprietary systems in isolation. Executing this approach well, however, requires more than simple service exchanges; it demands real expertise, disciplined processes, and technology designed for interoperability.

Crucially, the role of the insurance CIO and CTO is evolving in tandem with this trend. Industry experts note that successful technology leaders now act as “curator-orchestrators” who carefully select and integrate the best-in-class components and partners into their IT stack. This means focusing on overall solutions rather than siloed products, identifying technologies that add real value to customer experiences, and placing a premium on compatibility and open standards when choosing vendors.

Existing system capabilities are important, but how a tool works on its own is less important than what it can deliver as part of a larger, connected whole. In other words, success lies in how well these technologies work together.

High-quality APIs, clear integration documentation, and a proven ability to collaborate with other platforms have become critical criteria when evaluating insurtech partners.

This ecosystem mindset represents a strategic shift from the traditional “build or buy” decision toward a “build and link” philosophy. Rather than reinventing every wheel, insurers can rapidly assemble capabilities by linking to specialist providers.

Modern core platforms often serve as the central hub in this model, allowing multiple applications (policy administration, claims, data analytics, customer portals, etc.) to plug in easily. Such a modular architecture facilitates ongoing innovation and agility, as new components can be added or swapped out with minimal disruption.

Notably, innovation thrives when the tech stack is built around a single core platform that everything connects to. This modular, plug-and-play design lets firms introduce new functionalities without having to “switch everything off and do a whole programme reset” on their legacy systems. The result is a more flexible and resilient technology foundation for the business.

It’s important to clarify that plug-and-play does not mean plug-and-forget. Real value comes from deep, intelligent integrations between ecosystem partners, not just surface-level connections.

The combined functionality of the ecosystem must operate as one seamless solution for the end-user. Achieving this requires well-designed integration points and close collaboration with partners during implementation. When done right, however, the ecosystem approach yields a platform that can adapt quickly to change, incorporate emerging technologies, and deliver superior experiences with a clear competitive advantage in a fast-moving market.

Competitive Advantages of the Ecosystem Approach

An ecosystem approach offers several competitive advantages for insurance organisations seeking to modernise and differentiate their offerings. Below we delve into the key benefits that a well-implemented digital ecosystem can provide to insurers, brokers and MGAs.

Faster Innovation and Agility

By assembling solutions from multiple specialist providers, firms can innovate more rapidly. New capabilities (e.g. a telematics scoring engine or an AI underwriting tool) can be plugged into the ecosystem without lengthy development timelines, accelerating time-to-market for new products and features.

Building around a central platform enables a modular strategy where adding or upgrading a component does not require overhauling the entire system. For example, one report noted that a plug-and-play architecture lets insurers introduce new technologies without having to “turn everything off”, avoiding large-scale disruptions to the business.

This agility allows organisations to respond quickly to emerging opportunities and changing customer needs. It also future-proofs the business to some extent: as technology evolves, an insurer can continuously incorporate cutting-edge tools by partnering rather than solely coding from scratch.

The net effect is a more dynamic innovation cycle and the ability to stay ahead of competitors stuck on inflexible legacy systems. (That said, agility goes hand-in-hand with integration depth, truly realising this benefit requires robust APIs and tight integrations so that new tools work seamlessly with existing ones, rather than as isolated add-ons.)

Enhanced Customer Experience and Retention

Digital ecosystems enable insurers and brokers to deliver a more seamless and personalised customer journey by connecting services end-to-end. Rather than a disjointed experience across multiple providers, customers enjoy a unified journey, for instance, getting personalised product recommendations, instant policy issuance, and efficient digital claims all through one integrated platform.

Ecosystems increase the number of customer touchpoints and value-added services an insurance business can offer. Insurers can, for example, integrate chatbots for 24/7 service, mobile apps for policy management, IoT devices for proactive risk mitigation, and partnerships that reward customers (such as wellness programs or smart home integrations).

These additions enrich the customer experience and can significantly boost satisfaction and loyalty. As evidence of the stakes: insurers that are slow to develop ecosystem-based offerings risk losing market share to more tech-savvy competitors that provide these engaging, convenient experiences.

In contrast, those who leverage ecosystems to put customers at the centre, offering ease, personalisation and speed, are more likely to retain clients and expand their share of wallet in the long run.

Operational Efficiency and Cost Reduction

Collaborating in an ecosystem can also improve efficiency and economics. By leveraging external partners for non-core functions, insurers can avoid large capital outlays and reduce their IT development burden. Each partner focuses on what they do best, which can lower overall costs through specialisation.

According to industry research, successful insurance ecosystems unlock new sources of growth while also improving efficiency in core operations (mckinsey.com). They effectively monetize aspects of the insurance value chain such as distribution, data analytics, or claims services by bringing in partners rather than the insurer having to build those capabilities alone. Moreover, once an ecosystem is fully scaled, it can benefit from economies of scale and network effects that drive costs down.

One study notes that mature ecosystems enjoy strong economies of scale and growth by tapping resources the insurer doesn’t necessarily need to own internally. For example, by integrating with a third-party data provider, an insurer gains insight for underwriting across millions of data points without bearing the full cost of data collection.

Likewise, digital distribution ecosystems have been shown to lower customer acquisition costs and boost productivity by reaching customers more efficiently (bcg.com). In short, the ecosystem model can deliver a leaner operating model reducing duplication, spreading costs across partners, and allowing each participant to focus on their comparative advantage.

Scalability and New Revenue Streams

Ecosystems position insurance firms to pursue new market opportunities beyond traditional channels. By plugging into adjacent platforms (for example, offering insurance via a travel booking site or an e-commerce checkout), insurers can access customers they otherwise wouldn’t reach, creating fresh revenue streams.

Similarly, brokers and MGAs that connect with multiple insurers and service providers can scale up their product offerings quickly to serve niche markets or customer segments. The flexibility to partner means an MGA can, for instance, team with an insurtech for cyber insurance products or usage-based insurance, expanding its portfolio without extensive R&D. This strategic expandability gives ecosystem-centric businesses a growth edge.

As McKinsey observes, effective ecosystems help attract and retain customers and make products more viable through added services like prevention and assistance (mckinsey.com). They also enable insurers to participate in non-traditional areas (e.g. partnering with health services or smart home companies) and share in the value created.

In an increasingly interconnected digital economy, those insurers who embed themselves into broader consumer ecosystems (finance, health, mobility, housing, etc.) can capture additional premiums and fee income.

Over time, such ecosystem participation may become a differentiator between stagnant insurers and those continuously growing by following the customer into new contexts.

Data and Analytics Advantages

A well-integrated ecosystem greatly enhances an insurer’s ability to collect and leverage data – a critical source of competitive advantage in the digital age. By connecting to various data sources and InsurTech services, insurers can unlock richer data insights for underwriting, pricing, claims, and customer engagement.

For example, telematics devices in cars, IoT sensors in homes, and wearables in health insurance can feed data into the ecosystem, enabling more accurate risk assessments and personalised pricing.

Auto insurers today can tap into the four terabytes of data produced by connected cars each day to tailor coverage and pricing to driving behavior. Similarly, life insurers are partnering with wellness apps and wearable tech to incorporate health data into their products. By integrating big data analytics platforms and AI tools through the ecosystem, insurers turn this flood of data into actionable intelligence.

Carriers that effectively harness big data via ecosystems are able to deliver more personalised experiences, increase customer retention, cut costs, and generate faster, more accurate quotes. In essence, the ecosystem becomes a data engine, continually fueling improvements in decision-making and service delivery.

Firms that stick to closed, legacy systems often struggle to access such breadth of data, whereas those embracing open ecosystems can achieve a superior information advantage, predicting risks more precisely and responding to customer needs in real time.

No Legacy Constraints (Advantage for New MGAs)

For Managing General Agents and startup insurers, an ecosystem approach offers a particularly strong competitive advantage: the opportunity to build a modern platform unburdened by legacy IT debt.

New MGAs are often setting up their operations and technology from the ground up with cloud-native, API-first solutions with no legacy systems holding them back. This clean-slate approach makes them more nimble and prepared to adopt the latest innovations than many traditional carriers that must contend with outdated core systems.

A young MGA can rapidly assemble an ecosystem of underwriting, policy management, and distribution tools that work in concert, giving it a level of responsiveness that older competitors may struggle to match. This has leveled the playing field and, in many cases, allowed MGAs to outpace incumbents in product development and digital service.

Established insurers, for their part, recognize this dynamic and are increasingly partnering with or investing in MGAs and insurtech startups to infuse their own ecosystems with fresh capabilities. The takeaway is that a flexible ecosystem architecture is now a must-have for competing in today’s market and those starting fresh have the benefit of being able to instill this from day one.

Ecosystem Strategies for MGAs, Brokers, and Insurers

While the ecosystem approach delivers benefits across the insurance value chain, its implementation can differ slightly for MGAs, brokers, and insurers given their roles:

MGAs (Managing General Agents)

As noted, MGAs often have the agility to adopt best-in-class technologies quickly, since many are not tied to legacy core systems. By leveraging ecosystem-friendly platforms (with open APIs and modular services), MGAs can focus on their niche specialties like underwriting or program design, while outsourcing other functions to partners.

This allows even smaller MGAs to offer end-to-end digital experiences by plugging into policy admin systems, claims handlers, data enrichment services, and more via a network of integrations. The result is an “MGA-as-a-service” model that punches above its weight in terms of capabilities.

For example, an MGA can integrate an electronic trading platform to distribute its products widely, or connect with an analytics provider for sophisticated risk modelling, all without building those tools internally. By prioritising ecosystem connectivity in procurement decisions, MGAs ensure they remain highly responsive to market changes and can scale up efficiently.

The lack of legacy constraints means MGAs can serve as industry innovators, proving out new tech-enabled insurance models faster than large insurers in some cases.

Brokers

Insurance brokers sit between customers and insurers, and an ecosystem approach empowers them to deliver greater value to both sides. Digital broker platforms now often integrate directly with insurers’ quote APIs, policy management systems, and third-party data sources to create a one-stop interface for clients.

This connectivity allows brokers to obtain quotes from multiple insurers in real time, compare coverage options, and bind policies more swiftly, enhancing customer service. Brokers are also tapping into value-added services via ecosystems – for instance, integrating premium finance solutions, digital payment platforms, or risk management tools that they can offer to clients as part of a broader service package (insuranceciooutlook.com).

By embracing an ecosystem of insurtech partners, brokers can automate routine processes (reducing manual paperwork and administrative costs) and focus on advisory roles. The competitive advantage for brokers lies in being able to present insurance solutions faster and more tailored to client needs, which strengthens client loyalty.

Additionally, brokers who are digitally savvy can collaborate with insurers on new distribution ecosystems (such as embedded insurance offerings or online marketplaces), thereby expanding their reach. In a market where customers expect quick, online interactions, brokers that invest in ecosystem integration, effectively becoming digital brokers, will have a clear edge in efficiency and client satisfaction.

Insurers (Carriers) 

For insurers, the ecosystem approach can operate on two levels: internally in how they build their IT architecture, and externally in how they position their business in the wider market. Internally, insurers are increasingly transforming their core systems to be ecosystem-ready, adopting modern policy administration platforms that easily connect with third-party applications and data feeds.

This internal tech revamp often involves moving to cloud-based core systems, exposing services via APIs, and embracing microservices, so that the insurer’s own products and services can plug into larger networks. The benefit is improved agility and the ability to incorporate innovations from the insurtech ecosystem (e.g. a new fraud detection AI service) with minimal friction.

Externally, insurers are also choosing what role to play in emerging insurance ecosystems. Some incumbent insurers aim to become ecosystem orchestrators themselves, for example, building a platform where they aggregate services (insurance and beyond) from multiple partners to capture customers in a broader context (like a “mobility ecosystem” offering car insurance alongside car loans, maintenance, etc.).

This orchestrator strategy can unlock new revenue streams and solidify the insurer’s relationship with the end-customer. Other insurers may choose to participate in ecosystems led by other industries or tech firms – for instance, providing insurance products through an e-commerce platform or a travel app. Both strategies require strong API capabilities and partnership management. 

The common theme is that insurers who modernise their core technology and embrace openness will find ecosystem integration significantly easier, and more lucrative, over time (doxa.com).

By contrast, those clinging to closed, legacy systems risk being sidelined as nimble competitors form cross-industry alliances. In summary, insurers that proactively position themselves within ecosystems (either as leaders or valued contributors) stand to gain expanded distribution, richer customer data, and brand relevance in the digital economy.

Key Challenges and Success Factors

Adopting an ecosystem approach is not without its challenges. Interoperability and data security are two major considerations. Opening up systems via APIs and third-party integrations introduces potential vulnerabilities if not managed properly.

CIOs and CTOs must ensure robust cybersecurity measures, compliance with data protection regulations, and governance frameworks for how partners access and use data. Establishing clear protocols and vetting partners for security standards is essential to maintain trust in an open architecture.

Another challenge is the cultural and process shift required. Organisations need to move away from a control-oriented mindset to a more collaborative one. This means developing partnership skills, from legal contracting and revenue-sharing models to joint innovation processes. It also means training internal teams to work with external developers and services.

Not every insurer is used to rapid, API-driven projects with external contributors, so there can be a learning curve. Strong executive sponsorship and a clear ecosystem strategy are needed to align all stakeholders (IT, operations, compliance, underwriting, etc.) around the new model.

Legacy IT constraints remain a practical hurdle as well. Many insurers still operate core systems that were not designed to integrate easily with others. Replacing or modernising these systems can be expensive and time-consuming, which is why some firms hesitate to embrace a fully open ecosystem.

However, incremental steps such as implementing API gateways or using middleware can help bridge old and new systems during a transition period. The risk of not modernising is growing, as staying in a closed system can lead to missed opportunities, declining market share and unhappy customers, while rewarding more open and agile competitors. The pressure from nimble insurtech startups and MGA entrants is forcing legacy players to accelerate their digital transformation roadmaps or risk obsolescence.

To maximise the competitive advantages of an ecosystem approach, insurance organisations should focus on a few success factors:

• Choose the Right Core Platform: A flexible, API-rich core system (for policy, billing, claims, etc.) is the heart of any ecosystem. It should easily connect with external applications and allow data to flow smoothly in and out. Many insurers are investing in next-gen core platforms or digital layers on top of legacy cores to achieve this connectivity.
• Prioritise Integration Capabilities: When evaluating new technology vendors, insurers should weigh integration capabilities as heavily as functionality. This includes assessing the quality of APIs, availability of developer support and documentation, and the vendor’s track record in past integrations. Partners who actively collaborate and have proven plug-in readiness can reduce integration time and cost.
• Modular Architecture and Microservices: Designing systems in modular building blocks (microservices) ensures that each component can be updated or replaced independently. This architecture aligns well with an ecosystem approach because it prevents one component’s issues from bringing down the whole system. It also forces clarity in defining each component’s role, making it easier to spot redundancies or gaps. Companies that adopt a microservice, API-first architecture find it much easier to onboard new services or swap providers when needed, maintaining agility.
• Strong Governance and Partner Management: As ecosystems involve multiple parties, having a clear governance model is crucial. This includes setting standards for data sharing, service levels, and issue resolution among the partners. Regular communication and joint planning with key tech partners help ensure the ecosystem evolves in line with business strategy. Leading “ecosystem insurers” often establish dedicated teams or roles (e.g. Head of Ecosystem Partnerships) to manage these relationships and scout for new collaboration opportunities.
• Customer-Centric Design: Despite the tech complexity behind the scenes, the measure of success is in the customer’s experience. Ecosystem initiatives should be guided by customer-centric metrics, for instance, improvement in Net Promoter Score, reduction in claim processing time, or growth in cross-product adoption rather than internal IT metrics alone (ey.com). Keeping a focus on delivering tangible customer value helps prioritise which integrations or services to pursue and ensures the ecosystem grows in a way that strengthens the firm’s market position.

By addressing these factors, CIOs and CTOs can mitigate the challenges and extract the full value of an ecosystem approach. It transforms IT from a bottleneck into an innovation enabler, allowing the organisation to continuously adapt and improve.

What the future holds

The ecosystem approach to insurance technology offers a compelling competitive advantage for insurers, brokers, and MGAs navigating a rapidly changing digital landscape. It enables organisations to be more agile, innovative, and customer-centric by leveraging a network of specialised partners and technologies rather than going it alone. 

As one industry analysis observed, ecosystems may well represent the single greatest opportunity for insurers to differentiate themselves in the era of digital transformation. Yet, despite this promise, the majority of insurance companies have not fully capitalised on the ecosystem model, as of a few years ago, only about 5% of insurers could be considered “ecosystem masters”. This gap highlights the significant upside for firms willing to embrace open collaboration and modernise their core systems.

The coming years are poised to bring a step-change in insurance modernisation, and those companies that recognise the value of partnership and connectivity will be best positioned to thrive. Embracing an ecosystem approach is ultimately about acknowledging that no single player can excel at everything, but together, a connected network can create superior outcomes for customers and sustainable growth for each participant. 

For CIOs, CTOs, and procurement leaders, the mandate is clear: invest in technologies and relationships that make your business an integral part of the new insurance ecosystem. By doing so, you not only gain short-term efficiencies and new capabilities, but also ensure your organisation remains relevant and competitive in an industry being reshaped by digital innovation and collaboration. In a sector where the experience is as important as the product, those who build the richest ecosystems will secure a lasting advantage.