The 14-day sprint, anatomy of a single day

The most common question after "what does it cost" is "what does a day actually look like." So here is day 7 of the ApplyAI recruiter-finder sprint. The middle of the build. No demo, no kickoff, just the work.

Morning, India

The engineer opens the day reading what the overnight US window left in Slack: a question about the confidence threshold and a screenshot. They answer, then pick up the day’s Linear card. Today is the confidence gate. They write the eval cases first, before the gate exists, so the gate has a target.

Midday overlap

This is the window where Chicago and Bhubaneswar are both awake. Twenty minutes, camera optional. We look at the eval numbers together. The gate is catching too much. We talk it through, decide the threshold, and the engineer goes back to it. Decisions get made in the overlap so neither side is ever blocked waiting.

Afternoon, India

Heads-down. The gate gets built, run against the eval set, tuned, run again. Three commits, each one small and described. The pull request goes up with the eval score in the description. I review it before I sleep, Chicago time.

A sprint day is boring on purpose. Boring days are how you get an exciting day 14.

Evening, US

I review the pull request, leave two comments, approve it. I drop a two-line note in the client Slack: what shipped today, what is next. Twice a week that note is a Loom instead. The founder does not have to ask. The day closes itself.

That is it. No status meeting, no standup theater, no slide. Fourteen of these in a row, with the boring days protected, is the entire method.