From idea to product: how we decide what to build
Scoping is a research question, not a guess. How a design-led studio turns a big idea into the smallest thing worth shipping.
Kumar Gaurav
Founder
Turning an idea into a product starts by narrowing it, not expanding it. We research who it's for and the job they're hiring it to do, then cut until what's left is the smallest version that proves the point. Scope is the first and most important design decision.
Why start by cutting the idea down?
Every feature you add is a feature you have to design, build, explain and maintain. The teams that ship are the ones that found the core and defended it against everything that merely sounded nice.
How do you decide what makes the first cut?
By the job, not the wish list.
- Name the one person and the one job the product is for.
- Keep only what that job can't happen without.
- Defer anything that's a preference, not a requirement.
- Write down what you're deliberately not building, and why.
What does research actually change?
It replaces opinion with evidence about real behaviour, so the roadmap survives the first disagreement. The point isn't a sixty-page report; it's a decision you can defend.
How we use it
We scope from research and ruthless editing, then hand you a plan you could build with anyone — because a clear decision is worth more than a long document.
Let's build
Have something worth making well?
Tell us what you're working on. We'll come back with how we'd approach it — and whether we're the right studio for it.