Thirty days to an MVP sounds impossible. It's not. It's actually the sweet spot—long enough to build something real, short enough to force ruthless prioritization. The magic isn't in working faster; it's in knowing what to cut and what to protect.

Week 1: Ruthless Scoping

Your entire first week goes to defining the core loop. What is the single interaction that proves your idea works? For a marketplace, it's a successful transaction. For a note-taking app, it's capturing and retrieving a note. Not sharing, not collaboration, not advanced search—the absolute minimum that demonstrates value.

Write this down. Share it with your team. Everything else is scope creep. Every feature request gets measured against the core loop: "Does this make the core loop better?" If not, it waits for v1.1.

What to cut in week 1: Authentication (use magic links), payment processing (mock it), analytics (you'll do it live), social features (post-launch), admin dashboards (post-launch).

Week 2: Build the Core

By day 8, you're writing code. Your database schema is rough but functional. Your API endpoints map directly to the core loop. Your UI is wireframes and basic CSS—you're optimizing for speed, not aesthetics. Figma can wait. Build in the browser.

Aim to have the core loop working end-to-end by day 10. Janky, unpolished, possibly buggy—but functional. You sign up, you create a thing, you see your thing. Every subsequent day refines this loop.

Week 3: Polish the Critical Path

The core loop works. Now you optimizing the friction out of it. Confusing error messages get clarified. Slow queries get indexed. Mobile experiences get stress-tested. The design goes from "bare minimum" to "people won't hate this."

But only on the critical path. You don't polish the settings page. You don't optimize the FAQ. The 80% of the product that 20% of users touch in month one—that gets refined. Everything else stays rough.

Week 4: Launch Preparation

Monday through Wednesday: bug fixes and monitoring setup. You deploy to production. You set up error tracking and basic metrics. You write a README for early users.

Thursday and Friday: you launch. To your immediate network first. Fifty users who will tolerate jankiness and give honest feedback. Get them using the product. Take notes. Fix the most egregious bugs over the weekend.

Your MVP is shipped. Your job now is listening, not building.