Build a SaaS
Write a spec, design the database, build one user action at a time, and use established providers for login and billing.
-
How Do You Build a SaaS With Claude, One Slice at a Time? Build one user action at a time, end to end, from database to screen, and test it before starting the next. Level 4: Multi-tool systemsBy layernothing runs until the end
- all the tables
- all the endpoints
- all the screens
By slicesomething works each day- one user action
- database to screen
- tested, then committed
-
How Do You Design a SaaS Database With Claude? Before any screens, have Claude draft the schema from your spec, including who owns each row. Level 4: Multi-tool systemsCheap to change laterCostly to change later
- A screen
- An empty table
- A table with live data
-
Should Claude Write Your SaaS Login and Billing Code? Claude shouldn't write them from scratch. Level 4: Multi-tool systemsWritten from scratchyour liability
- password hashing
- session handling
- card and retry logic
Provider plus Claudereviewable- hosted auth and checkout
- webhook signature checks
- tests for failure paths
-
How Do You Write a SaaS Spec With Claude Before Coding? Have Claude interview you until it can write a one-page spec to SPEC.md, and cut that spec down yourself. Level 4: Multi-tool systems
- 1Claude interviews you
- 2It writes SPEC.md
- 3Build in a fresh session
- 4Review the diff against SPEC.md
The order that keeps a build under control
Work in this order: a one-page spec, then the database design, then one user action at a time, then login and billing with established providers. Claude Code can do most of the typing at each stage, but each stage produces something you can review before the next one depends on it. Most of these steps assume Claude Code, since it can read your repo and run your tests.
What Claude won't do for you
Claude stops when work looks done, so it needs a check it can run, such as a test or a build. It also can't know what you decided last week unless it's written down. Keep a spec and a progress file in the repo, and start a fresh session for each piece of work. Budget your own review time for the schema and for anything touching identity or payments, because that's where a working demo tells you least.
Can I build a SaaS with Claude if I can't code?
You can get a working prototype, and Claude Code can write most of the code. But someone with experience should review login, billing and data isolation before real customers use it, because those can run fine while being unsafe.
Should I use Claude Code or the Claude chat app to build an app?
Use Claude Code for the real build, since it can read your repo, edit files and run tests. Use the chat app and Artifacts for early ideas and clickable prototypes. Claude Code is included with paid plans, not the Free plan.
What should a SaaS spec include?
The primary user and their one problem, 3 to 5 must-have features with a testable line for each, what's out of scope, the main data entities, and how you'll know version one is done. Keep it to one page.
How do I stop Claude reading my API keys?
In Claude Code, add deny rules to the project's settings file, such as Read(./.env). The docs say deny rules hold in every permission mode. Instructions in CLAUDE.md are context rather than enforcement, so don't rely on those for secrets.