How long does a strategy engagement take?

Most run two to four weeks depending on how much research is needed. Longer than that usually means the problem needs splitting.

Do we have to build with you afterwards?

No. The output is deliberately written so another team can pick it up. Plenty of clients do continue with us, but the work stands alone.

We already have a spec. Is this still useful?

Often more so. A second read on an existing spec tends to surface scope that has crept in, and assumptions nobody has tested yet.

Can you work with our existing team?

Yes. Strategy work frequently runs alongside an in-house team who will do the building.

01 — Services

Product strategy that decides what to build, and what to leave out.

Most products fail on scope before they fail on execution. Strategy work is where the idea in your head becomes a thing that can actually be built — small enough to ship, clear enough to explain, and pointed at a problem someone genuinely has.

We work in short, decisive engagements. You end up with a shape for the product, an order to build it in, and a written case for why the first release contains what it contains.

Who this is for

Founders with an idea and no clear first release
Teams whose roadmap has grown faster than their capacity
Businesses digitising a process that currently runs on spreadsheets
Anyone who has been quoted for a build and isn't sure it's the right one

Problems this solves

A scope that has quietly doubled since the first conversation
No agreed definition of what the first version must do
Features chosen by opinion rather than by the problem they solve
A product that can't be described in one sentence
Building for an audience nobody has spoken to

What you get

Product definition and scope for a first release
Prioritised roadmap with an explicit build order
Positioning and messaging foundations
Technical approach and platform recommendation
Launch plan and success measures

How the work runs

01
Understand
Sessions with you and, where possible, the people you're building for. We map the problem before touching a solution.
02
Define
We cut the idea down to a first release that can ship, and write down what was deferred and why.
03
Sequence
A build order that puts the riskiest assumptions first, so what's uncertain gets tested early rather than at launch.
04
Hand over
A document you can hand to any team — including ours — and a conversation about what happens next.