A first draft while the problem is still warm

Most products do not die from a bad architecture. They die in the months between the meeting where everyone agreed the problem was real and the first day a customer could touch a path that answered it. The question cools. The room moves on. Someone files the notes.

We staff against that clock. A small named crew sits in your repo the week the brief is still sharp. We use the tools of this decade — models, agents, evals — to go from a spike to something a person can keep, while the original pain is still the thing people complain about in Slack.

Warm is a technical constraint

Warm means the operator can still show you the broken screen. The warehouse can still walk you to the bay where the scan fails. The founder can still say, without a deck, which three flows they would bet the company on. That knowledge evaporates. It gets replaced by a spec that is internally consistent and slightly wrong.

So we do not start with a six-month document. We start with access: the repo, the stand-up, the incident channel, a thin slice that can go to production. AI in the loop so we are not waiting on a design phase that never touches the code. Human review on the decisions that will still be there in a year — the nouns, the data, the thing you cannot undo on a Friday.

What “first draft” actually means

A first draft is not a prototype on a laptop. It is a path in production with real data, a way to roll it back, and a name on the pull request. It is ugly in the places that do not matter yet. It is careful in the places that do: auth, money, the record a regulator will ask for, the query that will fall over at 4 p.m.

We have shipped first drafts that were a live operations surface a shift lead could stare at, a catalog a buyer could trust, a booking path that did not feel like a scavenger hunt. None of those started as a forty-page brief. They started as a constraint that was still warm and a crew that would still be in the channel after the slice landed.

Speed without the disappearing act

Shops that move fast often vanish at launch. Shops that stay often move like 2014. We do not accept that trade. The people who write the first slice write the runbook. When the product is live, those names are still on it. That is the engagement, not an extra invoice after the applause.

If you have a problem that is on fire this month, send the messy version. We will have a first draft in the repo while you can still point at the flame.