Thirty days is enough to put a paying product in front of real users — if you've already validated the idea and you're disciplined about scope. The MVP's only job is to answer one question with real money: will people pay for this core promise? Everything that doesn't serve that question is a distraction.
Before day 1: earn the right to build
Don't start here unless you've done the groundwork — a validated wedge with at least one money-or-scarce-resource commitment (see validation) and a clear teardown of the model you're improving (reverse-engineering). The 30 days are for building, not deciding.
Week 1 — Scope to the core
Write the single sentence: “This product helps [specific user] achieve [specific outcome].” Then list every feature you imagine, and cut everything that isn't required to deliver that outcome once. Ruthlessly. Your MVP should do one job well. Pick your stack for speed and familiarity, not resume points.
Week 2 — Build the core loop
Build the shortest path from “user arrives” to “user gets the outcome.” Ignore settings pages, edge cases, admin panels, and polish. Use off-the-shelf for auth, payments, and email so you spend your hours only on the part that is your product. If you can fake a backend step manually (concierge-style) to ship faster, do it.
Week 3 — Payments, polish the critical path
Wire up real payments early — an MVP without a way to charge isn't testing willingness to pay. Then polish only the critical path: onboarding, the core action, and the moment of value. A rough edge on a settings screen is fine; a rough edge on the main job is fatal.
Week 4 — Launch to a warm audience
Do not “launch to the internet” and hope. Go back to the people and communities you validated with. Hand-win the first ten customers through direct outreach, the communities your niche lives in, and any audience you already have. Ten paying users who give you feedback are worth more than a thousand anonymous visitors.
After launch: let customers drive
Now the real product design begins — with data. Watch where users drop off, what they ask for, and what they'll pay more for. Resist the urge to build everything on your original list; build what paying customers pull from you. Version two should be written by your users' behavior, not your pre-launch imagination.
The discipline that makes it work
Every day, ask: “Does this bring me closer to a paying user experiencing the core value?” If not, it waits. That single filter is what separates founders who ship in 30 days from those who polish for a year and launch to silence.