Service
MVP development and prototyping: test the idea before the costly build
The most expensive mistake with a new product is months of building features nobody uses. A prototype shows cheaply whether people understand the product, and an MVP tests it with real users. FUTURIO takes you through both steps without paying for scope you do not need yet.
A prototype and an MVP are different things
A prototype is a clickable model of the screens. It looks and behaves like the product, but it stores no data and takes no payments. You use it to check whether someone can complete the main flow without help, and to show the idea to partners or investors.
An MVP is the first working release, with real accounts, data and payments, limited to the features the product cannot make sense without. In most cases we recommend this order: prototype first, then an MVP that contains only what the tests confirmed.
What you get from prototyping
- A role map: who uses the product and what each of them wants to achieve
- Key flows from first sign-in to the outcome
- An interactive prototype of the core screens that opens on a phone and a laptop
- A visual interface style instead of grey wireframes
- The feature list for the first release, and what was deliberately postponed
- An MVP estimate based on the prototype rather than on assumptions
When to start with a prototype
- You need to show the product to an investor, partner or team before paying for development
- The flow is complex and everyone describes it differently
- You need a firm development estimate, not a wide range
- You are not sure which features the first release really needs
- The idea is new to the market and you do not know how people will react
6GOALS: a first release without the extras
6GOALS is a visual goal manager for people with ADHD. For this audience every unnecessary screen becomes a reason to put the plan off, so the product keeps only what helps people move: goals with milestones, a budget, a timeline and concrete weekly actions. 6GOALS runs on the web and on iOS.
How we work: 15 business days
- A free task review and Zoom call: the idea, the audience, the constraints
- We fix the roles, flows and boundaries of the first release
- We design the screen structure and walk through the key flows with you
- We build an interactive prototype in the product’s visual style
- You receive the prototype, the first-release scope and the MVP estimate
How to test a prototype with people
A first round does not need a large study. Find five to seven people from your audience, give each of them a concrete task such as “book a consultation for Thursday”, and watch without prompting. Every place where someone pauses, asks a question or taps the wrong thing is a change to make. After about the fifth session new problems rarely appear.
Do not ask “do you like it?”. Almost everyone says yes to be polite. A better question is “what did you expect to happen after that tap?”.
How much does MVP development cost?
FUTURIO public formats: a prototype from $1,990 in 15 business days, a finished product from $3,990 in 25 business days with a year of support, and a system that adds team automation from $6,990 in 35 business days. An MVP price depends on the number of roles, flows, integrations and platforms. We fix it after a free task review, before any work starts.
Do I need a technical specification?
No. Tell us what problem the product solves, who it is for and how people deal with that problem today. We write the technical description of the first release, and it is part of what you receive.
Can another team build the MVP?
Yes. The prototype and the first-release scope are yours, and any development team can work from them. If we build the MVP, the estimate is already done and nobody has to learn the product from scratch.
What if the prototype shows the idea does not work?
That is a result too, and it costs $1,990 rather than months of development. From there we change the flow and test again, or stop honestly while the losses are still small.