Plan your product before you build.

#Why start with scope

Every founder begins with more ideas than a first version can hold. The work of scoping is choosing: which users, which problems and which few flows have to be excellent on day one, and what can wait until real users tell you what they want.

The Scope Sprint gives that choice a week of focused attention. At the end, the product exists clearly on paper, the risks are known, and you hold a quote based on a real specification rather than a guess. This is what makes fixed-price MVP development possible.

#How the week runs

• Session 1: the problem and the users. Who the product is for, what they are trying to do, how they manage today, and what success looks like for you in the first six months.
• Between sessions. We draft the user flows and rough wireframes, and research any integrations or AI features for feasibility and running cost.
• Session 2: flows and screens. We walk through the draft together and adjust it. This is where most of the important decisions are made.
• Between sessions. We design the data model, settle the technical approach, and draft the version-one feature list.
• Session 3: scope and plan. We agree what is in version one and what is parked, then go through the quote and the week-by-week build plan.

Each session is 60 to 90 minutes. In total you spend about five hours across the week.

#What is in the specification

• Users and goals. Who uses the product and what each type of user needs to achieve.
• Core flows. Each flow described step by step, from the user's point of view.
• Wireframes. Simple layouts of the key screens, enough to see how the product fits together.
• Data model. What information the product stores and how it relates.
• Technical approach. The stack, the third-party services, and how any AI features will work, including an estimate of what they cost to run.
• Version-one feature list. What is in, clearly separated from what is parked for later.
• Risks and open questions. Anything that could affect cost or timeline, stated plainly.
• Quote and plan. One fixed price and a week-by-week schedule.

#Deciding what waits for version two

This is often the most valuable part of the week. A smaller first version launches sooner, costs less and teaches you more, because real usage replaces assumptions.

We help you sort every idea into one of three groups: needed for launch, valuable soon after, and worth revisiting once you have users. Nothing is lost. The later ideas are recorded in the specification, ready for when you need them.

#After the sprint

You decide what happens next. You can go ahead with an MVP build at the quoted price, take the specification to your own developers, use it to raise funding first, or pause. For a rough idea of budget before you start, the MVP cost calculator takes about two minutes.

#Guides for founders

• MVP vs prototype vs proof of concept: which one you need first.
• Fixed price vs time and materials: why a defined scope makes a fixed price possible.