Validate the idea before expanding the build.
Start by identifying the uncertain assumption: who has the problem, whether the proposed workflow helps, or whether the solution is technically feasible. Choose a small experiment that can answer that question. Interviews, an interest test, a prototype or a focused MVP may each be useful at a different stage. A launch is a chance to gather evidence; it does not guarantee demand or paying customers.
Plan your first release
Practical guides to building an MVP.
Work through your budget, timeline, features and platform choice. Then discuss the development requirements for your app or platform.
Building a wide feature set before understanding the customer can make the next decision more expensive. A long specification does not replace evidence that the target user needs the core outcome.
A documented hypothesis, evidence from the chosen experiment and a next decision: refine, test again, build a focused MVP or stop.
How to do it
- 01
Define one question
Name the target user, problem and assumption. Write what evidence would make you change direction.
- 02
Choose the smallest useful experiment
Use interviews for the problem, a prototype for an uncertain interaction, a proof of concept for technical risk, or a working MVP for the complete user task.
- 03
Agree scope and evidence
Define participants, success observations, exclusions, ownership and any spending before running the test. Avoid universal conversion benchmarks.
- 04
Observe actual behaviour
Separate comments, sign-ups, task completion, return visits and payments. Record where people fail and what they need help with.
- 05
Decide the next release
Compare the evidence with your original question. Keep the limitations visible and agree the next experiment or first-release scope.
What we use
FLUIDS helps turn a defined product idea into an MVP scope, a working release and a plan to learn from use. The build and its timeline are agreed in writing.
Start with these
Common questions
Do I need a complete app to validate an idea?
Not always. Start with the uncertainty you need to resolve. A conversation, prototype or focused test may answer the question before you invest in a working product.
What if I have several assumptions to test?
Prioritise the assumption most likely to change the decision to build. Record what each experiment tests so you can interpret the results.
Do I have to buy advertising?
No. Recruiting participants, interviews or a pilot with a known customer may be more appropriate. If paid acquisition is part of the experiment, agree the budget, audience and measurement first.
Does an MVP guarantee paying customers?
No. An MVP creates a way to test a working product with users. Demand and willingness to pay need evidence from the intended audience.