Skip to content
PixelformBuy the $500 audit

For insurtech

A claim is a form someone abandons.

A claim is the longest form your customer will ever fill in, and they fill it in on a phone, on a bad connection, in the worst week of their year. Partial save, resume where they stopped, and an evidence upload that survives a dropped signal are the product.

What ships

Claim intake
Partial save, resume later, evidence upload
Uploads
A dropped connection retries; it doesn't lose the form
Adjuster queue
Assignment states and an SLA clock you can see
Decisions
Reason codes, and a path to appeal one
Shipped as
Production components and a documented system

Three surfaces, and the constraint each is under

The three surfaces an insurtech interface needs, and their constraintsClaim intake: Partial save, Evidence upload, Resume later. Adjuster queue: Assignment states, SLA clock visible. Decision record: Reason codes, Appealable.Claim intakePartial saveEvidence uploadResume laterAdjuster queueAssignment statesSLA clock visibleDecision recordReason codesAppealable
Three surfaces, and the constraint each one is under.

What the studio is not

Not your compliance advisor. The studio builds the interface that makes your policy visible and enforceable; a lawyer or a compliance officer decides what the policy is. It doesn't write your controls, and it won't tell you what your regulator will accept.

What there is to show

No published insurtech work yet. The nearest real thing is Roast My Website: a live product that takes payments from strangers and runs a multi-step intake, the same abandonment problem at a tenth of the length.

Start by finding out what’s wrong.

$500, five business days, a recorded walkthrough, a written action plan and a competitor table, and it comes off the project if you book one.