Product · MVP · Experiments

MVP in 6 Weeks: From Idea to Validation with Money

A step-by-step plan, checklists, and a mini-calculator for quickly launching a minimal product and testing demand.

In Brief

An MVP in 6 weeks is not about a beautiful interface. It's about quickly validating value: are real users willing to pay for your solution now, not “someday”.

Below is a week-by-week plan, frameworks, checklists, and a mini-calculator to help soberly assess if there's a chance to grow.

Week 0: Preparation (Days Before Start)

Your goal is to assemble a minimal kit for experiments.

  • Assemble a team: PM/Product → manages hypotheses Designer/UX → creates the right flow without the polish Engineer or no-code maker → builds the prototype Sales/Customer → talks to real users
  • One value proposition sentence: “For whom → what problem → what result”. If it doesn't fit in one sentence, you're not ready.
  • Define one validation metric: conversion to payment / sign-up / ARPU 7/30.
  • Readiness checklist:
    • [ ] The problem is real and confirmed by 3–5 interviews
    • [ ] The audience is known (narrowly!)
    • [ ] A minimal value scenario is formulated
    • [ ] You have a source for the first 50 users

Weeks 1–2: Quick Prototype and First Test

The goal is to show value in 1–2 clicks.

  • Landing page + lead collection / pre-payments. Webflow / Tilda / Carrd / Notion + Stripe. Important: the payment button must work.
  • Simple value demonstration: one flow, one result. Replace everything you can with manual processing: “Wizard of Oz”.
  • Mini-sales script: 5–7 phrases explaining the problem and the result.
  • Sources for first users:
    • personal contacts
    • thematic communities
    • narrow targeting (minimal budget)
  • Goal: get the first money, not the first likes.

Weeks 3–4: First Users and Feedback

Now you need to understand why people pay or don't pay.

  • Sell the MVP → record every payment and refusal.
  • Conduct short CustDev interviews (10–15 minutes). Key questions:
    • “What are you currently using instead of this?”
    • “Why did you choose us?”
    • “What would you remove or add first?”
  • Track metrics:
    • lead → payment conversion
    • 7-day retention
    • ARPU 7/30
    • % of refunds / cancellations
  • Run a simple A/B test on the landing page: change one thing: price, promise, CTA.

Weeks 5–6: Iteration and Decision

This is the main fork in the road for the entire project.

  • Scale if:
    • they pay without constant persuasion
    • LTV is predictably > CAC (see mini-calculator below)
    • repeatable scenarios are visible
  • Revisit the hypothesis if:
    • payments are small and irregular
    • users say “interesting” but don't buy
  • Shut down if:
    • CAC is consistently higher than LTV
    • there's no demand even with a lower price
    • 10+ interviews revealed no clear pain
  • Document:
    • insights about user behavior
    • what turned out to be a false assumption
    • which scenario brought in money

Practical Tips

  • Do it manually until you start drowning in manual operations—then automate.
  • Don't build a “platform.” Build one use case, as narrowly as possible.
  • Maintain direct contact with every paying customer. This saves months of development.
  • Calculate CAC “on a napkin”: if a channel brings a lead for X, and the conversion to payment is Y%, then CAC = X / Y%.
  • An MVP is complete when a user can:
    1. understand the value → 2) try it → 3) pay for it.

Mini Unit Economics Calculator (Quick)

Калькулятор LTV / CAC

Введите свои параметры, чтобы оценить LTV, LTV/CAC и примерный срок окупаемости CAC.

LTV (чистая прибыль)
8 400 ₽
LTV / CAC
2,1
Окупаемость CAC (периодов)
5,71
OK, но без запаса
Для комфортного роста LTV/CAC обычно стремятся к диапазону от 3 и выше. Но контекст бизнеса важнее, чем «магическое» число.

Quality MVP Checklist

  • [ ] It costs money (and people pay for it)
  • [ ] It solves one specific scenario
  • [ ] There are 5+ paying customers in the first weeks
  • [ ] The first value is delivered within 1 day
  • [ ] Acquisition channels are clear
  • [ ] Manual processes don't hinder hypothesis testing

Common Mistakes (and How to Avoid Them)

  • Mistake: Doing everything at once. Correct: Choose one flow.
  • Mistake: Focusing on UI. Correct: Focus on “wow-value” for the user.
  • Mistake: Interviewing friends. Correct: Only take those who have the pain.
  • Mistake: Counting leads as success. Correct: Count the money.

Simple Experiment Template (2 days)

  1. Hypothesis: If we offer X to segment Y, they will pay/sign up
  2. Success criterion: one number (e.g., “3 sales”).
  3. Landing page + payment/sign-up form.
  4. Drive traffic (organic/community/targeted).
  5. Collect 5–20 paying responses.
  6. Short interviews.
  7. Decision: continue / change approach.

Conclusion

Six weeks is an honest timeframe to understand the main thing: is there a product that customers are willing to pay for right now.

Don't waste energy on “perfection.” Spend it on validating value, manual processes, and talking to real people.