For early-stage products
Give your first release a clear job to do.
A minimum viable product, or MVP, is a focused first version that lets real users try the essential idea. We help you define what that version needs to do, shape the experience, and turn the agreed scope into a development plan.
Discuss your projectName the user, the problem, and the first useful outcome
An early product becomes easier to scope when the intended user and task are specific. Instead of beginning with a long feature list, describe the situation that brings someone to the product and what they should be able to accomplish.
We use that outcome to identify a complete first workflow. Features that support it belong in the initial discussion; ideas for other audiences or use cases can be recorded for later. This creates a clear basis for deciding what the first release includes.
- A defined initial audience and problem statement
- One or more essential journeys with a clear completion point
- An explicit list of later ideas and unresolved assumptions
Use the right level of build to answer the next question
Sometimes the next question is whether users understand a proposed flow. A prototype may be enough to explore that. Other questions require working software, such as how a real integration behaves or whether people can complete the task with their own data.
We discuss which uncertainty matters most and scope the work accordingly. For an application build, the plan also identifies account access, administration, integrations, and the basic states required to make the selected workflow usable.
- Prototype or development scope matched to the next decision
- Required user and administration features
- Technical dependencies reviewed before committing to features
Prepare to learn from the first release
Before development is complete, decide who will try the product, how they will be supported, and what feedback will be useful. These choices can shape onboarding, administration, and any measurement included in the scope.
We review the built workflows against the proposal and hand over the agreed materials. Early usage can then inform the next set of improvements. The first release gives you something concrete to evaluate; the response from users determines what you learn.
- Review criteria for the initial workflows
- A plan for onboarding and gathering early feedback
- A prioritised next-release discussion based on what emerges
Questions, answered
A few useful answers.
How do we decide what belongs in an MVP?
Start with the task the first users must complete and include the features required for that journey to work. Consider necessary administration and failure states too. Additional audiences, automation, and secondary workflows can be evaluated separately rather than assumed to belong in the first release.
Should I build a prototype before an MVP?
A prototype is useful when you need to review an idea's structure or interaction before building working software. An MVP is more appropriate when the next question depends on real functionality or use. The initial discussion helps identify which output serves your next decision.
What should I prepare before discussing my startup idea?
Describe the intended user, the problem, the current way they solve it, and the outcome your product would offer. Share any interviews, sketches, existing code, or integration requirements you have. A clear problem description is more useful than a polished pitch deck.
Tell us what you want to make possible.
Tell us what you’re building, who it’s for, and where you want to go next.