Quick answer
A one-week scoping sprint clarifies the problem in two days, shapes the smallest useful release in two more, and ends with a scope, budget range, timeline and the top risks to test.
A six-week discovery phase is usually a sign that nobody wants to make a decision. We compress the same work into one focused week with a clear output: a scope, a budget range and a first release.
Days 1–2: understand the problem
We talk to the people who feel the problem daily — not only the buyer. The goal is a single sentence the whole team agrees on: who is stuck, and what would make their day measurably better?
Days 3–4: shape the smallest useful release
We sketch flows, list the data we need and cut everything that is not required for the first promise. The output is a release map: what ships now, what waits, and why.
Day 5: price the risk
Estimates are not guesses about effort. They are a conversation about uncertainty. We call out the unknown parts explicitly so the budget reflects reality instead of optimism.
- A one-page problem statement
- A first-release scope with a clear cut line
- A budget range and timeline
- The top three risks and how we will test them
A week is enough to decide. It is not enough to be perfect — and it is not supposed to be.