Ship Your First Product in 3 Days: The Weekend Sprint

You’ve been thinking about building something for months. Maybe years.

You have the idea. You have the skills. But you haven’t shipped anything.

Here’s the uncomfortable truth: planning feels like progress. Research feels productive. “Getting ready” feels like movement.

It’s not. Shipping is the only thing that counts.

Not a perfect product. Not a complete product. A live, functional product that solves one problem for one person.

Why 3 Days, Not 30

The math is brutal: projects that take longer than a week to ship fail at dramatically higher rates. Not because the product is worse, but because momentum dies.

A weekend sprint creates artificial pressure. You have to make decisions. You can’t add features. You must ship.

The Only Three Rules

The 3-Day Plan

Day 1: Friday Evening (4 hours)

6:00 PM - Define (30 min)

Write one sentence: “My product helps [specific person] do [specific thing].”

Bad: “My product helps everyone manage their life” Good: “My product helps freelancers send invoices in 30 seconds”

6:30 PM - Stack Setup (1 hour)

# Create project
npx sv create my-product
cd my-product

# Add Supabase
npx supabase init

# First deploy
git init && git add . && git commit -m "init"
vercel

Your “Hello World” is now live on the internet. URL in hand. Momentum started.

7:30 PM - Database Schema (30 min)

Design one table. Maybe two. No more.

create table invoices (
  id uuid primary key default gen_random_uuid(),
  user_id uuid references auth.users,
  client_email text not null,
  amount numeric not null,
  sent_at timestamp,
  created_at timestamp default now()
);

8:00 PM - Auth (30 min)

Supabase auth is one line. Magic link or email/password. Done.

<button onclick={() => supabase.auth.signInWithOtp({ email })}>
  Sign In
</button>

8:30 PM - Core UI Scaffold (1.5 hours)

Build the skeleton:

• Landing page (headline + sign up)
• Dashboard (empty state)
• Main action page (the one thing your product does)

No styling. Ugly HTML. Working routes.

10:00 PM - Deploy & Sleep

git add . && git commit -m "day 1: scaffold" && git push

Your product is live. It doesn’t do anything yet, but it exists on the internet. Go to sleep.

Day 2: Saturday (10 hours)

8:00 AM - Core Feature (4 hours)

This is the marathon session. Build the ONE thing your product does, end-to-end.

For an invoice app:

• Form to enter client email + amount
• Save to database
• Send email via Resend/Brevo
• Show “sent” confirmation

12:00 PM - Lunch Break (1 hour)

Step away. Your brain needs processing time.

1:00 PM - Landing Page (2 hours)

Now make it sellable:

• Headline: What it does (5 words)
• Subheadline: Who it’s for (10 words)
• One screenshot
• Sign up button
• Price (or “Free”)

<h1>Send Invoices in 30 Seconds</h1>
<p>For freelancers who hate paperwork.</p>
<img src="/screenshot.png" alt="Invoice form" />
<a href="/signup">Start Free →</a>

3:00 PM - Payment (2 hours, if charging)

Stripe Checkout is the fastest path:

const session = await stripe.checkout.sessions.create({
  mode: 'payment',
  line_items: [{ price: 'price_xxx', quantity: 1 }],
  success_url: `${origin}/success`,
  cancel_url: `${origin}/pricing`,
});

Skip subscriptions. One-time payment or “pay what you want” for v1.

5:00 PM - Bug Bash (1 hour)

Use your product. Every path. Every button. Make a list of what’s broken.

Fix only what prevents the core action from working. Everything else is v1.1.

6:00 PM - Deploy

git add . && git commit -m "day 2: core feature + landing" && git push

Your product now does something. A real person could use it.

Day 3: Sunday (8 hours)

9:00 AM - User Test (1 hour)

Find ONE person. Watch them use it. Don’t explain anything.

You’ll discover:

• What’s confusing (they hesitate)
• What’s broken (they get stuck)
• What’s unnecessary (they ignore it)

10:00 AM - Critical Fixes (2 hours)

From your user test, fix what prevents value delivery. Ignore “the button should be blue.”

12:00 PM - Lunch

1:00 PM - Polish Pass (2 hours)

One hour on UI (spacing, colors, fonts). One hour on copy (headlines, buttons, errors).

This isn’t about perfection. It’s about not looking broken.

3:00 PM - Launch Prep (1 hour)

Write your launch post:

• 2-sentence description
• One screenshot
• Link

Pick your channel: | Audience | Platform | |----------|----------| | Developers | Hacker News, Reddit | | Indie makers | Indie Hackers, Twitter/X | | General | Product Hunt |

4:00 PM - Launch

Post it. Share it. Tell 10 people directly.

5:00 PM - Engage (2 hours)

Respond to every comment. Answer every question. Thank everyone who tries it.

7:00 PM - Done

You shipped.

The Stack (Opinionated)

Already know React? Use Next.js. Know Python? Use FastAPI + HTMX. The best stack is the one you can ship with.

Common Objections (And Why They’re Wrong)

What Happens Monday

You shipped. Now what?

Talk to every user. Everyone who signs up, reach out:

• How did you find this?
• What were you trying to do?
• Did it work?

Fix what’s broken. Users find bugs. Fix them fast. Fast response builds trust.

Ignore most feature requests. The first week brings “you should add…” Ignore 90%. Only build what multiple users independently request.

That last point matters. You’re no longer someone who wants to build. You’re someone who ships.

The first product is the hardest. The second is easier. By the third, shipping becomes a habit.

Start This Friday

Pick your idea. Clear your weekend. Ship.