Ten hours obsessing over your business before we say a word about ours.

Most discovery work is pitching in disguise.

You've sat through the process before. A consulting firm arrives for a two-week "diagnostic." They interview a handful of your executives, map your tech stack, and produce a deck that — somehow, incredibly — recommends exactly the kind of engagement they happen to sell. The framework is generic. The insights are industry-average. The recommendation was written before the first interview.

A sprint is the inversion of that. We spend the time before an engagement actually working on your business — not pitching the next one. What we produce is a signal intelligence brief: a written, specific, defensible view on the question you asked, with evidence, with counter-argument, and with a recommendation that may or may not involve us.

What the sprint produces.

A signal intelligence brief is not a deck. It's a written document, thirty to sixty pages depending on the question, structured for leaders who need to make a decision — not for a boardroom presentation that leaves you no better informed than before.

Every brief contains three things. First, a precise reframing of the question — because most sprints begin with a question that, once examined, turns out to be the wrong one. Second, the evidence: what we found, what we verified, what competing readings exist, what we concluded. Third, the recommendation, and the reasoning behind it in enough depth that you could defend it without us in the room.

If the answer is "don't do this," we say so. If the answer is "do this, but not with us," we say that too. The integrity of the brief is the product. Anything that compromises it also compromises every future conversation you might have with us — and we need that conversation to be worth having.

The shape of the engagement.

Sprints run two to three weeks, start to finish. One senior lead, often Thomas, supported by the research and engineering capacity needed for the specific question. Focused. Single-signal. We do not run parallel sprint teams or stack multiple questions into one engagement — if you have three questions, we run three sprints, sequenced, so each one earns the clarity of the next.

Typical sprint questions look like: "Where is AI changing the economics of our category, and what's our exposure?" Or: "What parts of our operation could be reshaped by AI in the next twenty-four months, and which of them would most reshape our market position?" Or: "Our board has asked us to have an AI strategy by the end of Q3 — what would one look like that is actually worth having?"

Bad sprint questions, which we'll reframe before we start, tend to sound like: "Can you build us a chatbot?" or "Can you implement [specific vendor product]?" Those are execution questions. Sprints exist for the layer above — the layer where the real decision lives.

Who it's for.

CEOs, executive teams, and boards who want proof of thinking before proof of fit. Leaders who have been pitched enough AI transformation decks to know that the deck is the problem. Buyers who would rather spend the cost of one sprint to get the question right than spend ten times that amount on an engagement built to answer the wrong one.

If you are at the beginning of your AI journey and want to understand the landscape, a briefing is the better entry point. If you are ready to commit to a pod, a sprint is the prerequisite — we will not begin a pod without one. And if you are somewhere between those two — interested, serious, but not yet certain — a sprint is exactly the engagement we've designed for you.

What happens after.

The brief is the deliverable. What you do with it is your decision. Some sprints graduate into pods, because the brief surfaces work that warrants a twelve-month embedded engagement. Some sprints graduate into a smaller piece of work we scope together. Some sprints end with the brief, a clear recommendation, and an introduction to a firm better suited to the execution than we are.

No obligation attaches to the sprint. No follow-on engagement is assumed. The quality of the brief is the only promise we make, and the only one worth measuring us against.