Who hurts
Frontend and mobile engineers blocked by a flaky or rate-limited upstream API.
The problem
Hand-written mocks encode the happy path from the spec. Production returns nulls in 'required' fields, 300ms of jitter, and a 429 every fortieth call — so code passes locally and breaks live.
What you build
Record a session against staging, learn the real response shapes, latency distribution and error rate, then replay a local server that reproduces the mess. One binary, no cloud.
Why now
Contract testing never crossed into small teams because the setup cost was too high. Recording is a five-minute setup.
Validate it this week
Ship the CLI free, watch whether anyone records a second session. One session is curiosity; two is a workflow.
Why you'd keep winning
None, honestly. This is a good first product to get known, not a good company.
The honest risk
Developer tools that solve a one-afternoon problem get cloned into an open-source package within a month. Price it as a one-time purchase and don't build a roadmap.
The prompt is written to make an AI argue with you before it writes code — that first round of pushback is worth more than the scaffold.