Fit and scope
Charles reviews the context, the decision timeline, the current assumptions, and whether the question is specific enough for a useful sprint.
How It Works
This page is the practical walkthrough: what to expect, what to prepare, what Charles returns, and where the work stops.
Working rhythm
The first job is not to create a report. It is to define the decision tightly enough that research, evidence, and judgment can change the next move.
Charles reviews the context, the decision timeline, the current assumptions, and whether the question is specific enough for a useful sprint.
The work translates the broad concern into a decision statement, the evidence needed, and the tradeoffs that must be surfaced.
Market signals, customer context, competitive pressure, AI or automation opportunities, and available source material are organized around the decision.
The final output names what to do, what to defer, what still needs proof, and the practical next action for the next 30 to 90 days.
Before the sprint
You do not need a perfect brief. You do need enough context to make the decision real.
Useful context can be messy: notes, links, sales calls, customer comments, founder instincts, decks, spreadsheets, or a plain-language explanation of what feels unclear.
During the work
The deliverable separates the strength of each claim so the final recommendation does not pretend every signal is equally proven.
What you get back
The output should help you act with clearer judgment, even when the risk is not gone.
If the question is still too broad, Charles will help narrow it before recommending a sprint. If the work points toward implementation, that path can be discussed after the decision is clearer.
Compare intelligence sprints or share the decision you need to make.