Decisions made before the money is spent
Research earns its keep when it stops a bad build. We do the smallest study that can change your mind, and we tell you when the answer is not to proceed.
Three reasons clients bring us in early
Frame the real question
Most briefs arrive as a solution. We work back to the decision underneath it, because that is what the research has to serve.
→The decision written down, with its owner→What evidence would change that decision→The cheapest study that could produce it→An explicit not-doing list→A deadline the decision actually hasLearn the domain properly
We have lost money building for a business we did not understand. We do not repeat it — the domain comes before the roadmap.
→Interviews with operators, not just sponsors→Time spent watching the work as it is done today→Constraints from finance, legal and operations→Competitor behaviour, not competitor marketing→The unknowns listed as unknownsRecommend, then commit
A research deck that recommends nothing has wasted everyone. We put a recommendation in writing and we are accountable to it.
→One recommendation, with the case against it→Costs and risks stated in plain numbers→A first phase small enough to test the thesis→Kill criteria agreed before the build starts→Four pages, not fortyBook a call →The honest answer is sometimes do not build it
Two of our own products failed because we committed before we understood the market. That experience is why our recommendation is sometimes to stop — and why we say it before the invoice, not after.
What we work with
A short, deliberate list — each in production on a system we maintain. See the full partner stack.
Clients we work with
Strategy case studies
What we will not do
Most strategy briefs ask us to validate a decision already made. These are the ones we hand back.
$./scoping-call→