Insurance communication at carrier scale
Carriers run on regulated, high-volume communication: adjusters juggling dozens of active claims, policyholders who expect text-message immediacy, and compliance teams who need every word auditable. The product has to feel as light as a consumer messaging app while carrying enterprise weight underneath: permissions, privacy, AI assistance, and carrier-specific branding.
The inbox above is a working recreation of the application I design in. Try sending a message, or open it on a phone to see the mobile patterns. Each workstream below has its own write-up.
Hi Marley Design System
Every feature was designed twice: once in Figma, then again in code. Specs drifted as engineers re-interpreted spacing, color, and states, and each team re-solved the same patterns. Rework was the tax on every release.
Read the Hi Marley Design System write-up. production React components, tokens, and patterns that scale across the product.
Brand Agent
Carriers stake their reputation on every message a policyholder receives, but out of the box, conversations carried the platform's voice, not the carrier's. Brand teams had no self-service way to control how they showed up.
Read the Brand Agent write-up. brand-aligned experiences and tooling for a consistent customer-facing voice.
FNAL AI
Claims intake is a flood of unstructured detail: descriptions, photos, follow-up questions, all arriving while adjusters juggle dozens of active cases. Important signals get buried in the thread.
Read the FNAL AI write-up. aI-assisted workflows and interfaces for carrier teams.
Outreach
Most carrier communication is reactive. Customers chase status updates, and silence reads as neglect. Carriers needed a way to reach policyholders proactively, at scale, without spamming them during off-hours.
Read the Outreach write-up. proactive messaging flows for claims and service teams.
Image and text redaction
Claims conversations are full of regulated data: license plates, documents, faces, account numbers, shared as freely as a text to a friend. Exposure isn't a UX bug; it's a compliance incident.
Read the Image and text redaction write-up. privacy-safe handling of sensitive content in communications.
Mobile
Claims don't happen at desks. Policyholders message from roadsides and adjusters work from the field, but core workflows assumed a wide screen and a mouse.
Read the Mobile write-up. mobile experiences for policyholders and adjusters on the move.
Application Redesign
The platform had grown feature by feature, and it showed: inconsistent navigation, duplicated patterns, and a UI that made a modern product feel older than it was.
Read the Application Redesign write-up. end-to-end application UX modernization across core journeys.
Impact
Reduced design-to-dev rework by 50% by building the design system as production React components instead of static specs.
Shipped self-service brand and configuration features that eliminated recurring IT requests for common carrier workflows.
Established shared patterns now used across AI, outreach, privacy, mobile, and core application surfaces.