ClaimRite

Insurance Claims Done Right. Prepare before a loss, then run your claim the right way after a loss — deadlines, evidence, FNOL, and letters. Home & auto. Not a replacement for a lawyer.

Comment 2

Inspiration

After a loss, policyholders lose leverage: missed deadlines, thin evidence, forgotten adjuster calls, and a first offer taken in a fog of paperwork. Many only download a claims app after the loss with zero prep.

DIRITEPROPERTY is a real estate company. We kept seeing this pattern on the property side, so we built ClaimRite: prepare the household before day one, then run the claim with a desk and during the development, the idea to extend this opportunity to the Auto Industry side came up since the problems and processes are both similar, we extended the opportunity to both worlds.

What it does

ClaimRite is a Before, During and After claim desk for home/property and auto claims.

Before a loss (Free): multi-policy vault, readiness checklist + score, “if this happens” playbooks, and short warm-up games (all work and no play, not bueno!)

During a loss (Free) when/if safe take pictures, names of parties involved before evidences are cleared up and memories fade away, enter info into ClaimRite

After a loss (Free): claims, photos/docs, deadlines, FNOL packet, evidence, adjuster log, settlement comparison, letters and PDF export.

Standard ($9.99/mo or $99.99/yr): Claim AI and FNOL polish, gated by RevenueCat entitlement standard. Cancel anytime your Free Access and claim data still stays unless you delete you account.

How we built it

  • App: Expo SDK 57, React Native, TypeScript
  • Purchases: RevenueCat (standard` entitlement; monthly + annual on Play and App Store)
  • Backend: Supabase (auth, claim sync, storage) + edge functions (Claim AI, RC webhook, entitlements)
  • Ship: EAS Build + EAS Update (OTA for JS-only changes)

Challenges we ran into

  • Creating something unique from the tons of insurance apps already available on the app stores was interesting.
  • Then came all the rejections from App store which has been harder so far than building the app itself..
  • Fixing rejections over OTA is not advisable, IOS testers usually will not have time to reload app for your OTA updates.
  • Keeping store builds on production RevenueCat keys so the paywall is real, not demo unlock.

Accomplishments that we're proud of

  • A Free tier that is actually very useful: unlimited claims, vault, playbooks (AI is the paid unlock)
  • The freedom to stay free, subscribe and still come back to free anytime is one feature we're very proud of.
  • Real RevenueCat purchases on production (monthly + annual).

What we learned

Store review is a big part of the product. Subscriptions have to ride with the first iOS version. Account deletion has to live in the app. And a claims tool people install after a disaster still needs a before-the-loss story: very handy for first time home buyers and young drivers - or day one is already lost on your claims.

What's next for ClaimRite

Finish the Shipaton video/screenshot pack, then readiness v2 (inventory + renewal reminders) and household share. Maybe also adding some other areas of insurance claims e.g Medical etc.

Built With

Share this project:

Updates

Submission history