Company File Origami Risk • 1,000+ clients • Founded 2009 • Chicago • Risk, safety and insurance on one cloud platform •

Enterprise software / The operating-system bet

Origami Risk Built a 1,000-Client Business by Fixing Insurance’s Unglamorous Plumbing

The Chicago software company won by treating claims, safety reports and policy records as one connected data problem. Now its bet is that the same platform can carry insurers from first incident to final invoice - with AI tucked into the paperwork.

Risk management has a paperwork problem disguised as a technology problem. An employee slips. A supervisor writes a report. A claim adjuster opens a file. A safety manager hunts for a pattern. Finance wants the total cost, legal wants the documents, and an insurer wants clean exposure data. In a large organization, those requests can ricochet through email, spreadsheets, paper forms and old databases. Origami Risk built its company around one blunt observation: the incident, the claim, the policy and the audit are not separate stories. They are chapters of the same one.

The Chicago company sells a configurable cloud platform for collecting those chapters and making them usable. Risk managers get a risk management information system, or RMIS. Insurers, managing general agents and third-party administrators can run claims, policies and billing. Healthcare organizations can track patient safety and professional liability. Corporate teams can add governance, compliance, environmental health and safety, business continuity, mobile reporting and analytics. It is not software people buy for delight. They buy it because a missing form or late claim can become very expensive.

1,000+client organizations reported by investor Spectrum Equity
900+employees serving a specialized enterprise market
2009founded, nine years before its first institutional investment

A veteran came back to compete with the category he helped build

Robert Petrie was not guessing at the needs of risk departments. Before co-founding Origami Risk in 2009, he had founded CS STARS, the RMIS business that became Marsh ClearSight, and later ran global operations and client technology for Marsh. He knew the incumbents, the buyers and the data migrations. Origami’s opening move was a single-version, cloud-based RMIS that could be configured for different organizations without turning every customer into a separate software branch.

That distinction sounds technical, but it shaped the business. One current platform means releases can flow to customers without years of version drift. Configuration lets a school insurance pool and a multinational retailer use the same foundation while seeing different forms, permissions and workflows. Experienced service teams handle migration and setup. Origami was selling software, but it was also selling the confidence that decades of claims history would survive the move.

“Almost all of the successes at Origami are team events.”Robert Petrie, co-founder and CEO, describing the company’s operating culture
Employees working inside Origami Risk's Chicago office
THE GLASS MENAGERIE: Origami Risk’s Chicago office contains fewer paper files than the industry it set out to modernize.

Paper broke before the algorithms mattered

The cleanest proof comes from a customer that insured 72 South Carolina school districts. Before adopting Origami Risk, incidents arrived on paper and could take three weeks to become claims. After districts began entering incidents directly into a client portal, adjusters could create a claim within two days. Nineteen days disappeared. That meant earlier contact with injured employees and more control over treatment, while districts could see their own claim status instead of calling for updates.

Banner Health had a different first failure: fragmentation at scale. Its home-grown claims system depended on two outside consultants. Origami helped migrate more than 100,000 claims and document attachments in six months, even as Banner acquired another health network. The platform then replaced a scanned-and-emailed post-injury form with an online report that triggered a supervisor investigation, fed a dashboard and gave the safety team structured data.

Rentokil Initial’s headache was annual exposure collection across a moving map of locations, vehicles and employees. What changed its team’s mind during selection was not an extravagant AI demonstration. It was the platform’s agility and usability. The team moved historical data, built forms, ran one collection cycle, then revised the questions, tips, reassignment options and validation rules from what users had learned. “Moving to a new system encourages new conversations,” its risk manager observed. That is the real product loop: migrate, use, notice friction, configure again.

The repeatable implementation loop
01Move history and normalize fields
02Configure forms, roles and workflows
03Run a real operating cycle
04Refine rules from user behavior

One painful workflow became a platform

Origami added P&C claims administration in 2012, healthcare and policy administration in 2015, GRC in 2019 and EHS in 2020. It acquired Dais Technology in 2023 to deepen its tools for MGAs and insurers launching new lines. The menu now runs from incident intake and total-cost-of-risk analytics to underwriting, billing, compliance, internal audit and occupational health. A mobile app catches data near the scene; APIs and marketplace partners connect outside systems.

This breadth is its competitive argument against RMIS rivals such as Riskonnect and Ventiv, GRC platforms such as SAI360 and MetricStream, and insurance-core vendors such as Guidewire and Duck Creek. Origami wants the buyer to see fewer handoffs: the safety observation can become an incident, the incident can become a claim, the claim can change a risk score, and the same data can inform renewal. Competitors may go deeper in an individual category. Origami’s proposition is that connection and configurability are more valuable than a collection of point tools.

The business model follows enterprise SaaS convention: recurring subscriptions plus implementation, configuration, integration and support. There is no public price card because the scope varies by users, modules, records, storage and service hours. Public procurement provides boundaries, not a universal quote. Jacksonville listed annual fees of $355,369 for a deployment that included dozens of users, up to 300,000 claims and other records, integrations, added storage and 20 monthly support hours. A Tucson agreement was reported at $750,000 across five years. An Idaho renewal was listed at $107,555 over five years.

$355,369Jacksonville annual fees after discounts for a substantial RMIS deployment
$750,000Reported value of Tucson’s five-year SaaS, implementation, maintenance and support agreement

The cost buyers rarely put in the headline is commitment. Clean migration requires decisions about codes, fields, permissions and ownership. A configurable platform cannot fix a process nobody agrees on. Small teams with a simple incident log may be better served by a lighter product. Organizations unwilling to assign internal owners, clean historical data or change workflows can end up recreating their old mess in a newer database. And customers that need the deepest specialist feature in only one domain may prefer a focused vendor.

AI arrives after the data earns the right

Origami’s newer AI features are deliberately clerical: summarize a claim, help draft an email, answer questions against platform data, automate a workflow step and support risk assessment. The 2026 product releases also emphasized an administration portal, billing automation, deeper risk modeling, integrations and translation across 15 languages. This is less “replace the adjuster” than “remove the blank page and the second search.” In regulated work, that modesty is a feature.

The sequence matters. Generative tools are useful only after records share definitions, access controls and enough history. Origami spent years building the plumbing before adding the assistant. Its vision is to become the trusted data platform for the entire risk and insurance ecosystem, and its partner program now advertises more than 120 active partners and access to 2,200-plus customer relationships. The ambition is larger than the verified count of direct clients, but the direction is clear: become the layer through which risk data moves.

The moat is the moment a customer stops asking, “Where is that file?” and starts asking, “What does the pattern mean?”

Sell the reduced delay, not the giant dashboard

Origami’s customer stories rarely turn on the elegance of a screen. They turn on a supervisor receiving an automatic investigation email, a district reporting an injury directly, a risk team escaping annual form-chasing or an insurer launching new lines without another core system. Those are legible wins. They save days, remove duplicate entry and make the next decision arrive with better context.

What another vertical SaaS company can copy

  1. Start with a workflow where delay has a visible operational cost.
  2. Hire domain operators who understand the records before hiring for novelty.
  3. Treat migration, configuration and training as part of the product experience.
  4. Expand along shared data, not into categories that merely share a buyer.
  5. Add AI only where permissions, definitions and human review already exist.

Origami took its first institutional investment from Spectrum Equity in 2018, nine years after launch; the minority deal’s amount was not disclosed. That patient path is another clue. This was not a land-grab consumer market. Trust accumulated one implementation at a time. By 2024, the company had passed 1,000 clients. In 2026, it had roughly 900 employees and was still led by Petrie.

The folded-bird logo is almost too tidy a metaphor. Origami Risk takes one stubborn sheet - claims, policy, safety and compliance data - and keeps adding creases until it can hold a useful shape. The trick works when the sheet is sound, the folds are agreed upon and people keep using what was built. Otherwise, it is still just paperwork.