Second site from the same stack — and the reason they look related is that one lives inside the other. The first one is a compliance product. EZ is the infrastructure it sits in.

That's a specific design problem. The platform can't look like a competitor to its own component, and it can't look like a louder version of it either. EZ took the wider frame — four modular layers, three entry points, regulators in the trust section — while the component kept the close-up.

Same toolkit both times: Figma, a Unicorn Studio shader in the hero, the reel in Jitter. Designed with my wife, who owned the product and the content side.

Wider frame versus close-up is such a clean way to keep two related products from stepping on each other. Curious how the regulators reacted to seeing their section live in the trust page versus a static doc.

Supplement Tracker manages insurance supplements for roofing contractors. Contractors create and track supplements through workflow stages from draft to sent, in review, and approved or denied, organized by insurance carrier and claim job. Supplement letters go to adjusters by email, with inbound replies received via webhook and kept in message threads, and AI provides supplement review, message classification, and draft replies. Automated follow-up sequences, escalation triggers, and homeowner notifications keep claims moving, and the app supports supplement images with annotations, a building code requirements library by jurisdiction, templates, CSV and PDF export, an analytics dashboard, two-factor authentication, and audit logging for compliance.