I read your DeltaClaim prototype and its wiki, then rebuilt what it's really about, the Delta engine that chases carriers, and the Xactimate-writer marketplace you sparked, in my own design system, not a copy of yours. Everything here is clickable.
Closed across 6 enforcement files this year.
Adjust the metrics below based on a contractor's claim volume. Clovix automates Florida building code (§627.70131) checks and supplement demands to recover missing overhead, profit, and line items.
Δ Three core surfaces, rebuilt
Track what the carrier owes vs offered, toggle estimate discrepancies that recompute the demand, with the statute-cited AI non-compliance letter.
Your “random-ass inspiration”, built: hire a vetted writer, retain to your bench for free, assign to a claim with the 90/10 escrow split and the four anti-disintermediation rules.
The legal calendar with the AI “next best move”, and the human-vs-AI-agent choice on every enforcement deadline.
Also covers your JD must-haves
Live call shape: ticking timer, animated transcription, dialpad, mute/hold/transfer.
Lead-score gauge, sentiment timeline, action items, and a follow-up email that streams in.
The rep's pocket version in an interactive phone frame, sharing the web's data layer.
What I found in the prototype
The marketplace I built holds the fee in escrow at assignment, then stops. There's no “Accept & release” payout, exactly as your wiki flags. First thing I'd build.
Everything runs on window.* + localStorage today. Clean path to TanStack Query over a typed FastAPI, your exact stack.
Every AI action drafts then waits for human approval. For a legal/financial product that's the right call. I'd keep it.
Why me, against your task list
Co-founded Folderly (React Native / Expo, 1M+ users, both stores via EAS).
Founding engineer: multi-stage LLM orchestration wired straight into product UIs.
Daily stack. This whole demo is built in it, in my own design system.
Comfortable reading, debugging, and extending Python/FastAPI services.
On Twilio Voice, straight with you: I haven't shipped Twilio Voice specifically, it's a JD nice-to-have. But I've wired streaming AI output into UIs, and the VoIP screen here proves the call shape. I'd be productive on it fast.
Scope & estimate
Drawn from your wiki's open questions and the brief. Ranges lean high on purpose. I'd rather overestimate and beat it than miss a date.
Payout state machine, escrow release to the writer, 10% platform capture, ledger entries, both-party notifications. Closes the loop your wiki flags as open.
Typed REST client, query and mutation hooks, Zod-validated forms, optimistic updates, real loading and error states across every screen.
Build the new vertical against the scope and designs you provide, on top of the claims workspace shown here.
Threshold on the carrier offer vs our scope, a prompt in the claim plus a push, deep-linked into Assign.
Claim-stage rules, hidden on settled files, plus many assignments per claim with escrow held per writer.
Design system, WCAG AA accessibility, empty / error / loading states, responsive, dark mode, Framer Motion micro-interactions. The polish the brief is hiring for.
The analytics surfaces tied to your backend, with live updates and tabular, scannable data.
Voice SDK, in-call UI, recording, wired into the AI summary. Estimated high since it is new to me.
Call summaries, scores, and dynamic content, all human-in-the-loop before anything sends.
Read, debug, and make small changes to the FastAPI services and backend performance; comfortable around AWS and Docker Compose deploys.
Everything here was built in a night, in my own design system. Let's get me onboarded and pointed at the real DeltaClaim.