Mar 27, 2026 · 3 min read
Why we measure first value in days, not slides
Discovery decks are a coping mechanism for engagements that are afraid to ship. Here is the engagement shape we use instead, and what it costs to run it well.
- engagements
- method
We do not run discovery phases. We run a 60-minute consultation, then a 14-day window in which the only output that counts is something the client can actually use. If we cannot define that something at the end of the consultation, we say so and we do not start.
What 14 days buys
It is not a prototype. A prototype is a slide that runs. What we ship in the first window is a thin slice of the production system — one channel, one agent, one tool, deployed against the client's real data, with the eval harness already running on it. The slice is small. The substrate underneath is not.
- The retrieval layer is real, against the client's documents, with the chunking strategy we will keep.
- The eval harness is real, with the metrics the client will read off in week ten.
- The deployment is real — the same runtime, the same secrets boundary, the same observability.
What it costs to run this way
The cost is that we cannot take engagements where the brief is not yet a brief. We will not write your brief for you in the form of a six-week discovery. If you do not know what shipping looks like, the consultation is the right place for us to find out together — and the right place for either of us to walk away.
The benefit is that by the time most agencies are presenting their architecture deck, your team is already reading metrics off the same dashboard your operators will be reading in production.