Building in public, week 1: I shipped a SaaS MVP in about 20 hours

Non-technical founder · building in public

Committing to building in public with a 30-day goal: launch a working SaaS MVP. Week 1 — landing page, Stripe checkout, onboarding, and v0.1 of the core feature.

~20 hrs
Time
$0
Cost
MVP in 30 days
Goal

Getting Stripe + Supabase + email to talk to each other used to block me for months. ChatAPI made it a 2-hour afternoon task.

I'm committing to building in public. I'm a non-technical founder, and my goal is simple: launch a working SaaS MVP in 30 days. This is my week 1 update.

By the end of the week I had four things live: a working landing page, a Stripe checkout flow, a user onboarding sequence, and v0.1 of the core product feature.

Here's the full tool breakdown. Design and front-end: Framer. API connections: ChatAPI — this is what connected everything together without me writing backend code; I described the logic I needed in plain English. Email: Loops. Payments: Stripe. Database: Supabase. Auth: Clerk. Deploy: Vercel.

The biggest win was getting Stripe, Supabase and email to actually talk to each other. That used to be the thing that blocked me for months. With ChatAPI it was a two-hour afternoon task.

The biggest challenge wasn't technical at all — it was deciding what not to build in week 1.

Total cost this week: $0, all on free tiers. Total time: about 20 hours. Week 2 update coming next Monday.

The stack

Front-end
Framer
API layer
ChatAPI
Email
Loops
Payments
Stripe
Database
Supabase
Auth
Clerk
Deploy
Vercel

Build what they built

APIs mentioned

  • Stripe

    Recommended. Recurring + one-time payments. Use your own Stripe account — your end-users see your brand on checkout.

  • Supabase

    Postgres, storage, auth.

  • Clerk

    Drop-in auth, user management, organizations.

  • Vercel

    Deploy your MVP.

Build it yourself

Your turn

Describe what you want to build. ChatAPI wires the APIs and writes the glue code — start free.

Start building free