Step 1: One user, one journey
Write: ‘For [user] who needs [job], the app lets them [action] so that [outcome].’ Every feature must serve that sentence.
Step 2: MoSCoW
| Class | Meaning | Example for a booking app |
|---|---|---|
| Must | Without it the journey fails | Choose service, pick time, confirm, reminder |
| Should | Important but workarounds exist | Reschedule, simple admin view |
| Could | Nice to have | Loyalty points, referral codes |
| Won’t (yet) | Explicitly postponed | Multi-language, advanced analytics, marketplace |
Step 3: Value vs effort
- High value, low effort: do first
- High value, high effort: plan carefully or split
- Low value, low effort: only if free
- Low value, high effort: drop
Step 4: Plan six weeks
- Week 1: design, data model, sign-in
- Weeks 2–3: build the core journey
- Week 4: admin, notifications, analytics
- Week 5: testing and security review
- Week 6: launch to 10–50 users and collect feedback
Measure
- Activation: share of users who complete the core journey
- Retention at day 7 and day 30
- One qualitative insight per user interview
See our MVP guide.
Plan your app Quote in 24 hours
Tell us the problem and users. We reply with scope, timeline and price.
Frequently asked questions
How many features should an MVP have?
As few as make the core journey work, often 3–5 main capabilities.
What if investors want more features?
Show traction and a roadmap; evidence from real users beats a long feature list.
Can you help scope my MVP?
Yes, in a short free scoping call.
Get a free quote in 24 hours
Tell us what you need. We reply with scope, timeline and a fixed price.