About claimOS

Built inside a public adjusting firm.

claimOS didn't start at a whiteboard. It started on a claim. Andy Rouhafzai — the founder — is a public adjuster who built the software he wanted for his own firm, Insurance Claim Hero, because nothing on the market was actually built for public adjusters.

Why claimOS exists.

The insurance industry has quietly armed itself. Carriers invested a decade into AI-driven estimating, automated denials, and claims triage software that recognizes patterns and pushes back at scale. Public adjusters — the one profession that exists to hold carriers accountable for homeowners — were still working out of spreadsheets, shared drives, DocuSign subscriptions, and six different CRMs stitched together by Zapier.

If that asymmetry stays, the people who need representation most — homeowners after a loss — lose. That's the gap claimOS fills.

Insurance was supposed to be America's reliable safety net. When it stops being one, public adjusters are the backstop. The point of this company is to make sure they're armed as well as the carriers they go up against.

How we build.

Insurance Claim Hero runs every claim through claimOS. Every intake, every inspection, every weather pull, every demand letter. If an ICH adjuster can't use a new feature on a live claim, it doesn't ship.

This means a slower roadmap than a lot of SaaS companies. It also means the software you see is software that's already in use, today, on real claims against real carriers. The feedback loop between adjuster and product is the same day. No committee. No roadmap roulette.

When we scale the team, it will be with people who have actually run claims — adjusters, ops leads, claim directors — and with engineers who want to build alongside them. Not the other way around.

How we got here.

claimOS didn't show up fully formed. Six beats from a homeowner dealing with a frozen pipe to a platform that now runs every claim at a working public adjusting firm.

  1. The moment

    Three frozen-pipe claims.

    Andy's first real encounter with insurance came not as a professional but as a homeowner — three frozen-pipe claims in a row. He watched how carriers approached them: politely, procedurally, and in a way that consistently moved money in the wrong direction. The industry had quietly turned a safety net into a P&L optimization problem.

  2. The profession

    Became a public adjuster.

    Instead of hiring a PA, Andy became one. Getting licensed was the cheapest education in how the other side actually operates: how estimates are written, how denials are framed, how pressure is applied, how documentation wins or loses claims. It was also how he found out how bad the software was.

  3. The firm

    Founded Insurance Claim Hero.

    ICH was built around one promise to policyholders: your fight is our fight. Every claim gets a real advocate, not a procedural pass. Within months the firm was running more claims than any single adjuster's head could hold — and the operational stack underneath it was spreadsheets, shared drives, DocuSign, an estimating app, a CRM, and a photo app, stitched together and drifting apart.

  4. The build

    Started building claimOS.

    No off-the-shelf product was going to fix it. The industry's existing claims software was either built for carriers (wrong incentive structure) or for other trades (roofers, field services) with a thin PA skin. So ICH started building its own — one module at a time, each one replacing a tool ICH was already paying for.

  5. The platform

    Every ICH claim runs on it.

    From intake through settlement, every active claim at Insurance Claim Hero now lives on claimOS. Every photo, every weather pull, every demand letter, every e-sign, every client portal login. No parallel system, no fallback. If a feature breaks, the firm feels it the same day — and so does the product team, because it's the same people.

  6. The opening

    Now we open it to other PA firms.

    claimOS isn't leaving ICH behind. ICH is still the proving ground — every new feature has to ship there first. But the tools are now stable enough to run other firms' claims too. That's why this page exists.

What we believe.

  1. Public adjusters deserve the same caliber of tools carriers have.

    Carriers spent the last decade arming themselves with AI-driven estimating, automated denials, and claims triage at scale. If PAs are still working out of spreadsheets, DocuSign, and six stitched-together apps, the fight isn't fair — and the homeowner is the one who loses.

  2. Software built by operators beats software built about operators.

    Every feature in claimOS ships because it had to work on a real Insurance Claim Hero claim first. If an adjuster can't use it on the roof, in the driveway, or with a carrier on the phone, it doesn't ship. No pitch-deck features — only things a working public adjuster uses every day.

  3. One claim, one record.

    If your software makes you re-enter the same information in five places, it's not software — it's a filing cabinet with a login screen. claimOS is built around a single live claim record that every module reads from and writes to. No sync jobs, no integrations, no drift.

What claimOS will never be.

A few commitments we make out loud so you can hold us to them. These aren't slogans — they're hard stops on product decisions.

  • Not a generic CRM with claims bolt-ons.

    Contact-centric data models don't work for claim-centric work. We will not ship a HubSpot clone.

  • Not a data broker.

    We do not sell, rent, or train general-purpose AI on your claim data. Your files are yours; our AI runs on your files for your benefit, full stop.

  • Not a walled garden.

    Export your claims, documents, and photos as CSV and PDF any day you want. Cancellation doesn't hold your data hostage.

  • Not built by people who've never run a claim.

    No engineer, designer, or PM here ships a claims feature without shadowing an ICH adjuster using it. That's a hard rule, not a slogan.

Andy Rouhafzai

Founder

Andy Rouhafzai

Founder, claimOS · Public Adjuster & Owner, Insurance Claim Hero

Andy became a public adjuster after personally dealing with three frozen-pipe claims that exposed how insurers prioritize profit over policyholder support. He founded Insurance Claim Hero to give homeowners real representation, and then he founded claimOS because the software his adjusters were stuck with couldn't keep up.

LinkedIn

Want to see what we've built?

15 minutes, your actual workflow, no sales theater. Or read the full story of how Insurance Claim Hero runs its entire operation on claimOS.

Book a demo →Read the ICH story