Phidea
ai-native · conversational-ai · insurance

Hi Marley

AI-powered texting platform purpose-built for insurance: FNOL, claims status, repair coordination, and policyholder messaging. Embedded in carrier and service-provider workflows via the Hi Marley Insurance Cloud.

www.himarley.com

Score

10/20
50%
Traction (named carrier deployments)
5 carrier deployment(s) with public source.
2/5
Maturity (years since founding)
9 years since founding (2017).
3/5
Coverage (insurance lines supported)
3 line(s) supported: auto, home, life.
3/5
Analyst recognition (Celent / Gartner / Forrester / Everest / ISG)
2 mention(s).
2/5

What it does

Hi Marley is a Boston-based AI communication platform built specifically for insurance. Founded in 2017 by Mike Greene, Mitesh Suchak, and John Miller, the product replaces fragmented email-and-phone communication during claims with a single texting thread that ties together policyholder, carrier, and service providers.

Funding and scale. $41.7M raised across seed, Series A, and Series B (the 2021 Series B was $25M, led by Emergence Capital with True Ventures and Underscore VC). At the time of the Series B announcement, Hi Marley had 40+ carriers in production with a 4× user-base increase year-on-year.

Public carrier footprint. American Family, MetLife, Auto-Owners, Erie, and MAPFRE are the carriers named in public materials. All five are real US (or US-adjacent) volume carriers, not pilot customers. Beyond these five, vendor communications reference "40+ customers" in aggregate.

Analyst coverage. Coverage is limited to trade press and regional tech media (TechCrunch, Built In Boston). No Celent or Gartner analyst mention surfaced in our search; the recognition score reflects that honestly.

Where it sits in the old → new → AI map. The legacy FNOL flow is a phone call to a call-centre and a paper form. The "modern" rung is a carrier portal. Hi Marley compresses that to SMS with AI-driven triage and routing, and sits at the AI-native rung for FNOL intake and claimant communication in the Claims stack.

Named deployments

Covers which actions

Last verified 2026-04-21.