Build an MVP in a Weekend

Build an MVP in a Weekend

48 hours. One idea. One working product. Here's how.

What is an MVP?

Minimum Viable Product = The smallest thing you can build that delivers value and tests your hypothesis.

Not an MVP:

• Feature-complete product
• Perfect design
• Scalable architecture

MVP:

• Solves ONE problem
• Works (barely)
• Someone can use it

Before the Weekend

Friday Night (1-2 hours)

• Define the ONE problem you're solving
• Define the ONE user who has this problem
• Define the ONE feature that solves it
• Write it down in one sentence

Example: "Help freelancers track their time so they can bill accurately."

Saturday

Morning (4 hours): Design & Plan

Hour 1: User Flow

• Draw the flow on paper
• What screens are needed?
• What's the core action?

Hour 2-3: Design

• Use a template or component library
• Keep it minimal
• Focus on the core feature only

Hour 4: Plan the Build

• What data do you need?
• What API endpoints?
• What can you skip?

Afternoon (6 hours): Build Core

Using Spawned (recommended)

• Describe your MVP clearly
• Let AI generate the base
• Iterate on the output
• Focus on core functionality

Manual Build

• Next.js + Supabase
• Use component libraries (shadcn/ui)
• Don't build auth—use Supabase Auth
• Don't build from scratch

Hour by Hour

• 1-2: Database schema, basic setup
• 3-4: Core feature (the ONE thing)
• 5-6: Basic UI to use the feature

Evening (4 hours): Polish & Test

• Make sure the core feature works
• Fix obvious bugs
• Add basic error handling
• Test the critical path
• Deploy (Vercel one-click)

Sunday

Morning (4 hours): Landing & Signup

Hour 1-2: Landing Page

• Headline: What is it?
• Subheadline: For whom?
• One screenshot
• One CTA

Hour 3-4: Onboarding

• Simple signup (Google auth is easiest)
• One-screen onboarding
• Get them to the value fast

Afternoon (4 hours): Final Polish

Hour 1-2: Mobile check

• Does it work on phone?
• Fix major issues only

Hour 3: Add Analytics

• Plausible or PostHog
• Track signups and core action

Hour 4: Final Testing

• Use it yourself
• Have one friend test
• Fix critical bugs only

Evening: Launch

• Post on Twitter/X
• Share in relevant communities
• Post on Spawned (if built there)
• Email friends who might use it

What to Skip

Skip These

• Perfect design
• Multiple features
• Admin dashboard
• Complex auth
• Email notifications
• Mobile app
• Tests (for now)
• Error handling for edge cases

Don't Skip These

• The core feature working
• Basic responsive design
• Deploy to real URL
• Simple analytics
• Way to contact you

Tools for Speed

Spawned

• Describe → Generate → Deploy
• Fastest path to MVP
• Built-in discovery

Supabase

• Database in minutes
• Auth built-in
• Real-time if needed

Vercel/Netlify

• Deploy in one click
• Free tier is enough

Component Libraries

• shadcn/ui
• Tailwind CSS
• Copy-paste components

Post-Weekend

Week 1

• Get 10 people to try it
• Collect feedback
• Fix critical issues

Week 2

• Decide: iterate or pivot?
• If iterate: add ONE more feature
• If pivot: new weekend, new MVP

Real Talk

Most MVPs don't become businesses. That's okay.

The goal is to learn:

• Do people want this?
• Will they use it?
• What's missing?

A weekend MVP that fails saves you months of building the wrong thing.

Key Takeaways

1. ONE problem, ONE user, ONE feature
2. Skip everything that's not core
3. Use tools that accelerate (Spawned, Supabase)
4. Ship imperfect, learn fast
5. 48 hours is enough for a real test