Work through this checklist before you talk to any developer. A clear scope does more than anything else to decide how fast and how cheaply your MVP gets built.
1. The problem
- I can describe the problem in one sentence.
- I know who has this problem, by role, industry or situation.
- I know how they solve it today, even if badly.
- I've spoken to at least 5 people who have this problem.
2. The one thing to prove
- I've written down the one thing the MVP must prove, for example "Clinics will pay to automate appointment reminders."
- I know which number tells me it worked: sign-ups, paid users, retention, time saved.
3. Users and journeys
- I've listed every type of user, such as customer, admin or partner.
- For the main user, I can describe the journey from sign-up to the "aha" moment in 5 steps or fewer.
4. Features
- I've listed every feature I can think of.
- I've marked each one as "must have" (it proves the idea) or "later".
- I have 3 to 5 must-haves and no more.
- Login, payments and admin are only on the list if the MVP truly needs them.
5. What to skip in version 1
- Custom design polish beyond the core screens
- Every edge case and setting
- Multiple languages, unless your first market needs them
- Native iOS and Android apps, if a web app or cross-platform app will do
6. Practical details
- Platform: web, mobile, or both
- Integrations needed (payments, email, CRM, SAP, other APIs)
- Any data or content the product needs at launch
- Budget range and the date I need it live
- One person on my side who makes decisions quickly
7. Ownership
- The code will live in my repository.
- Cloud and tool accounts will be in my name.
- The contract assigns all IP to me.
If you can tick these, you're ready for a scoping call. Book a free one with Ryo Forge, or estimate your timeline first.
