Insurance
Claims intake for an insurance broker
A customer files a claim with photos and a description. The broker tracks it through assessment and settlement, asks for missing documents through the same thread, and the customer always sees what is needed from them next.
Automatically generated draft
Written by machine against our own engineering playbook. The company is invented; the decisions are the ones we would make on a real build. A reviewed blueprint goes further — nine sections, agreed line by line, and it is what the build is tested against.
Section 01 · What has to work
A customer files an insurance claim with photos and description, and the broker tracks it through assessment and settlement via an interactive thread.
Section 03 · Screens
Every screen, and what it is for.
- ›Claim Intake — Customer files claim and uploads photos, instant submission confirmation.
- ›Broker Dashboard — Broker views all active claims by status, instant filter response.
- ›Claim Thread — Customer and broker exchange messages and documents, instant message append.
- ›Document Request — Broker flags missing items for customer action, instant state update.
Anything not on this list is not in version one. That is what keeps a fixed price fixed.
Section 04 · The data model
What it stores, and who can read a row.
claim
id uuid, customer_id uuid, broker_id uuid, description text, status enum(submitted, assessing, pending_info, settling, closed), created_at timestamptz
Access · Customer reads own claims; assigned broker reads broker_id claims.
message
id uuid, claim_id uuid, sender_id uuid, body text, created_at timestamptz
Access · Participants assigned to the parent claim can read.
attachment
id uuid, claim_id uuid, uploader_id uuid, file_url text, file_type text, created_at timestamptz
Access · Participants assigned to the parent claim can read.
document_request
id uuid, claim_id uuid, requested_by uuid, description text, status enum(pending, fulfilled), due_date date
Access · Customer and assigned broker can read requests for the claim.
Those access rules belong in the database, not in the screens. Someone who edits the address bar still cannot read a row that is not theirs — and the test that proves it blocks delivery if it fails.
Section 05 · States
submitted → assessing → pending_info → settling → closed
Most scope arguments three weeks into a build are really arguments about a state nobody named at the start.
Section 06 · Where this breaks
What bites products like this one.
Large mobile photo uploads failing on poor cellular connections during filing.
Client-side image compression and chunked direct-to-storage uploads with retry logic.
Brokers and customers sending conflicting updates simultaneously in the same claim thread.
Optimistic UI updates with server-side monotonic timestamp ordering for all messages.
Section 08 · Deliberately left out
What version one does not do.
- ×Automated email notifications for message updates — build manual in-app polling first to save two days.
- ×Multi-currency settlement tracking — stick to a single base currency to avoid exchange rate API failures.
This is the section that protects the date, and the only place in the document where somebody says no. It is also why clients trust the rest of it.
Still open
What we would ask before quoting.
- Does the broker assign claims manually from a shared pool, or do they route automatically upon submission?
- Should customers be required to authenticate with a password, or use secure magic links sent via email/SMS?
Half of this already exists
Doc Intake
The paperwork half of this is a solved problem: documents read on arrival, validated against your rules, and a person asked only about what does not add up.
It is one of our pre-built products: the code is handed over to you, adapted to your own wording and rules, and the rest of the specification above is built on top of it rather than from scratch.
Your product, not this one
Get this written for what you are actually building.
Describe it in a sentence and the generator returns the same sections for your own product. Free, no email, nothing saved to a list.
Next step
Find out if your idea fits in 10 working days.
Tell us what you want to build. We reply the same day with a straight yes, no, or here is what we would cut.