How we scope a whole project in one week
Our discovery sprint, step by step, how we turn a vague idea into a fixed scope, a fixed price and a plan everyone trusts.
Most projects don’t run over because the team is slow. They run over because nobody agreed what “done” meant. Our discovery sprint exists to kill that ambiguity in a week, and turn a vague idea into a fixed scope, a fixed price and a plan everyone trusts.
Day 1 to 2: the real problem
We start with the problem, not the feature list. Who is this for, what are they trying to do, and what happens if we do nothing? We map the riskiest assumptions, the ones that, if wrong, sink the project, and decide how to test them early.
Day 3 to 4: shape the solution
Now we sketch. Flows, rough screens, the spine of the data model. The goal isn’t polish, it’s alignment. By the end you can see the product in your head, and so can we, which means we’re estimating something real instead of a wish.
Day 5: the plan
We hand over a clear scope, a fixed price, a timeline and a prioritised build order, what ships first, what can wait, what we’ll deliberately leave out. No surprises later, because we did the thinking now.