What MVP Actually Is

Minimum: as little as possible.

Viable: solves core problem.

Product: ships and gets used.

Not: half-baked half of full product.

Pre-MVP Work

Problem interviews: confirm need.

Solution interviews: validate approach.

Landing page: measure interest.

This is not the 4 weeks.

The 4-Week Constraint

Force decisions.

Prevent scope creep.

Get to market.

Learn from real users.

Not lower quality – just less scope.

Week 1: Design

User flow: 5-10 screens max.

Wireframes: no visual design yet.

Data model: what to store.

API endpoints: what backend needs.

Focus: core flow only.

Week 2: Foundation

Auth: signup/login.

Data layer: models and DB.

Basic UI: not polished.

Deploy infrastructure.

Focus: works end-to-end.

Week 3: Core Feature

The one thing that solves the problem.

Not: bells and whistles.

Not: 10 features.

One feature done well.

Focus: value delivery.

Week 4: Polish and Launch

Bug fixes.

Design pass.

Onboarding flow.

Analytics setup.

Payment (if paid MVP).

Launch preparation.

Ruthless Scope Cuts

Admin panel: no (use DB directly).

Multi-tenant: usually no.

Complex permissions: no.

Integrations: only critical one.

Beautiful design: no (functional is enough).

Tech Stack for Speed

Familiar > new: no learning curve.

Full-stack framework: Next.js, Rails.

Managed services: Vercel, Supabase.

No microservices.

Not: greenfield architecture.

Design for Speed

Component library: Tailwind, shadcn.

Copy paste templates.

Not: custom design system.

Focus on flow, not aesthetics.

Testing Discipline

Not: TDD.

Not: 100% coverage.

Manual testing.

Critical paths only.

Fix real issues, not theoretical.

Launch Plan

Not big launch.

Small user group.

Feedback loop tight.

Iterate based on usage.

Grow gradually.

Common Mistakes

Trying to launch ‘complete’ product.

Perfecting design.

Adding ‘just one more’ feature.

Complex architecture.

Delaying launch.

Handling Feedback Post-Launch

Fast response.

Fix critical bugs.

Learn what matters.

Not: build everything requested.

Iterate on core hypothesis.

When 4 Weeks Isn’t Enough

Regulated industries.

Hardware.

Highly technical products (marketplaces, exchanges).

Different playbook needed.

Accept the constraint.

What Comes After

MVP is start.

Weeks 5-12: iterate based on feedback.

Grow features that matter.

Kill features that don’t.

This is where product wins.

The Mindset

Speed > perfection.

Learning > shipping features.

Real users > imagined users.

Feedback > assumptions.

Ship early, ship often.

Our Track Record

10+ MVPs built in 4-6 weeks.

Some became successful products.

Some got killed – and that was fine.

Better to know fast.

Based on Real Projects

This guide is based on our work with:

• Podd
• Platforma365

Further Reading

If this guide helped you, you might also want to read our comprehensive guide on Custom SaaS Development.