MVP development

• Product analysis.
  Hypothesis, audience, flows: we decide what belongs in the core and what waits for version two.
• Prototype.
  Clickable screens within days — testable with users and usable in a pitch before a line of code exists.
• Building the core.
  Only the features that test the hypothesis, on a proven stack — no architecture built for a scale you haven't reached.
• Metrics from day one.
  Event tracking, funnels, retention — the MVP answers in numbers, not impressions.
• Launch and first users.
  Deployment, onboarding and feedback collection — the product meets the market.
• The plan for version two.
  Based on what the MVP measured: what to double down on, what to drop, when to scale — a roadmap built on facts.

What moves the price: the platform (web, mobile, bot), the number of integrations and how complex the core is.

1. Hypothesis review — 2–3 days.
   What we're testing and with which metric; we cut the scope to the minimum that answers it. If the hypothesis can be tested before any development, start with customer interviews.
2. Prototype — 3–5 days.
   Clickable screens: testable with people and usable with investors — before development starts.
3. Building the core — 3 weeks.
   Only the features without which the hypothesis can't be tested.
4. Launch and metrics.
   Deployment, tracking, first users: the product collects data instead of opinions.
5. The decision, on data.
   Grow it, pivot or stop — decided by what the MVP measured.