Build my first legal SaaS.

An overview of the track. The technologies used (Next.js, Supabase, Stripe), their respective roles, how they fit together. You don't need to master these tools. You need to understand what they do.

The step everyone wants to skip. And the most important one.

What problem does your tool solve? For whom? What is the user workflow from the first click to the last? Which features are essential at launch, and which can wait?

This exercise turns your idea into a spec that AI can convert into code. A failed SaaS rarely fails for technical reasons. It fails because the problem was poorly defined.

Your spec becomes an application. Claude Code generates the first working version from your description: user interface, navigation, core business logic. You guide, you validate, you adjust. The result runs locally on your machine.

Your code is saved on GitHub. Every change is versioned. If something breaks, you roll back. Syncing takes a few seconds and becomes second nature.

A SaaS stores data: users, content, transactions. Supabase provides a hosted PostgreSQL database, with a visual interface to manage it. This step connects your application to its database and structures the data it needs.

Users need to be able to create an account, log in, and resume their session. Supabase Auth handles authentication (email/password, Google sign-in, magic link). You integrate the system into your application in a few exchanges with Claude Code.

The V1 works. Users log in. What's left is adding the features that make your tool useful: dashboards, exports, notifications, business logic specific to your use case. You work with Claude Code to add, test and refine each feature.

Going solo. You pick a feature you want to add and you build it yourself with Claude Code.

The goal: confirm that you've mastered the full process (describe the need, generate the code, test, fix, deploy) without following a step-by-step guide.