Combined Ratio Solutions Offers an Alternative Path for Core Systems

Michael Jones, Co-Owner and CEO, Combined Ratio Solutions
Luke Magnan, Co-Owner and Chief Insurance Officer, Combined Ratio Solutions

For most insurance carriers, replacing a core system remains one of the most expensive and structurally consequential technology decisions they will ever make. The dominant market options are well known. They are also built on a shared economic foundation: recurring license revenue, platform roadmaps governed by vendor priorities, and delivery models that often separate software ownership from implementation accountability.

Combined Ratio Solutions (CRS) takes a materially different approach. Headquartered in Hartford, Conn., the company provides a full policy administration foundation— but without software licensing fees. Instead, CRS monetizes its business entirely through implementation, managed services and ongoing operational support. The result is a structure that places ownership, control and long-term alignment directly in the hands of the carrier.

Michael Jones, CEO, Combined Ratio Solutions, describes the company’s position not as oppositional to traditional vendors, but as a structurally distinct option for a specific segment of the market.

Michael Jones, CEO, Combined Ratio Solutions.

“We compete on business model,” Jones comments. “The traditional software market is built on recurring license revenue because that’s what drives valuation. That structure limits flexibility. We built CRS so that ownership and control sit with the customer, not with investors.”

A Foundation Without Rent

At the center of CRS’s model is OS Policy, its open-source policy administration system. The platform is available without licensing fees and is governed by CRS as a community project. Clients own their deployed code base, retain control over its evolution, and are not bound to mandated upgrades, forced platform migrations, or pricing structures tied to premium volume.

Jones says the implications of that ownership model are practical, not ideological.

“Open source means the carrier owns the code. They’re not beholden to a vendor’s acquisition strategy, pricing adjustments or product sunsets. They dictate their roadmap. That changes the entire power dynamic.”

CRS derives revenue from the work that follows: configuring the platform to carrier requirements, implementing new lines of business, managing infrastructure, and supporting production environments over time. The company also supports clients that choose to build internal engineering capabilities alongside CRS engagement.

“We sell the project and the managed services,” Jones notes. “And we’ll teach you to fish if you want that level of autonomy. We hope to keep earning the work, but we’re not holding anyone hostage with licensing.”

Why This Structure Resonates with Tier Two and Specialty Carriers

CRS focuses on tier two and tier three insurers, MGAs and specialty organizations—companies that often sit between homegrown legacy environments and the capital intensity of full enterprise platforms.

These organizations typically face overlapping constraints:

  • Legacy systems that cannot support modern underwriting tools
  • Limited tolerance for multi-year, high-eight-figure platform programs
  • A growing need to integrate data-driven and AI-based decision support
  • Pressure to launch and iterate product lines quickly

For these carriers, Jones says the value proposition is not about chasing vendor feature releases, but about establishing a stable, cost-controlled foundation.

“If you’re not spending millions on license fees, you can invest that capital in the tools that actually make you different—your underwriting intelligence, your analytics, your automation,” he says.

CRS works with clients across commercial property, specialty programs and managing general agency operations, where speed, product experimentation and operational control are central to competitiveness.

AI as a Capability Layer, Not a Marketing Label

While much of the current market discussion centers on agentic AI and workflow automation, CRS positions itself as foundational infrastructure rather than as a direct AI vendor.

Jones says the distinction matters.

“AI doesn’t replace the core. It feeds the core. You still need a stable policy system underneath everything. You can’t just bolt agentic AI on top of a broken foundation and expect real operational leverage.”

By maintaining an open, controllable core, CRS positions clients to integrate emerging underwriting, hazard and data-enrichment platforms without waiting on vendor release cycles.

A Services-First Culture Shaped by Early Failure

CRS’s operating philosophy was shaped less by theory than by lived experience.

Jones and Luke Magnan, CRS’s Chief Insurance Officer, previously held leadership roles at Xchanging and Xuber before the businesses were absorbed into CSC and later DXC. Both founders recount that period as formative—not only because of commercial success, but because of what followed.

.

Plans to launch a venture-backed software company collapsed days before closing. With families to support and no investor safety net, the founders pivoted immediately into a services-driven survival model. That decision remains central to CRS’s identity today.

Magnan says that early experience permanently shaped their view of vendor economics.

“We learned how fragile investor-dependent models really are,” he comments. “Services revenue created discipline. It forced us to stay aligned with customer outcomes year after year. There’s no ‘lock-in’ with us. We have to stay relevant.”

Magnan, a 26-year veteran of property/casualty core systems architecture, previously served as an enterprise architect at The Hartford. His career has focused on the full lifecycle of policy, claims, billing and reinsurance platforms.

He argues that much of the market’s structural friction stems from how software monetization evolved after major vendors exited services delivery.

“Once vendors decided they only cared about recurring revenue, services shifted to large SIs. That separation changed everything. Customers now buy software from one party and delivery from another. Accountability gets diluted. Outcomes become harder to enforce.”

One Throat to Choke—By Design

CRS deliberately retains responsibility across software, implementation and managed operations. The company declines RFP-driven multi-vendor delivery models and routinely walks away from programs it believes cannot succeed under real-world constraints.

“We don’t preside over failures,” Jones says. “If we believe a project will end up late, over budget, or structurally misaligned, we won’t take it on.”

That posture stands in contrast to the traditional ecosystem model, where vendor, SI and hosting providers often operate within contractually insulated roles.

Client Validation Without Headline Logos

While CRS avoids publicizing individual carrier names, the company points to long-standing production relationships across specialty commercial insurers and program administrators, including multi-year engagements within the Fairfax Group of companies.

These organizations share common traits:

  • High underwriting autonomy
  • Frequent product and program introductions
  • The need for architectural flexibility rather than vendor lock-step

CRS’s model, Jones says, aligns more naturally with that operating reality.

A Competitive Alternative Built on Structure, Not Scale

CRS does not present itself as a replacement for traditional platform vendors across the entire market. Large carriers pursuing global platform consolidation and massive IT transformation programs will continue to gravitate toward large-scale providers.

But for smaller and mid-sized organizations operating under tighter capital and faster execution cycles, CRS represents a genuinely competitive alternative—one defined less by features than by ownership, economics and delivery alignment.

In a market where most core systems evolve under the pressure of valuation metrics and investor exits, CRS occupies a rarer position: an owner-operated company built to sustain long-term client alignment through services economics rather than software rent.

GOT A TECH CHALLENGE?

We’ve got the experts—whether it’s seamless implementation, no-drama integrations, custom builds that actually work, or support that doesn’t ghost you.

Let’s make your tech better.

DEVELOPER RESOURCES

Source Code (GitHub)

Knowledge Base

Open-Source Forum

Start Your Rebellion

To gain access to the open source code, submit your information, and a Rebel leader will be in touch.

    Contact your Rebel

    Please use a business email address or email us directly at rebels@combinedratio.com

    RSVP to secure your spot!