Septim AI — Vibe-Coding Scaffolds
Build Your SaaS.
A Next.js starter pre-wired to Stripe, Supabase, and Clerk — with a CLAUDE.md tuned for non-developers and 5 agent files that guide Claude Code through auth, database, payments, page generation, and deploy. Ship your first SaaS in two weeks without knowing how to code.
$99
Pay once · You keep it · No subscription
What's inside
A working Next.js app and 5 agents that know how to build it.
The starter directory runs on first npm install && npm run dev. The agents live in .claude/agents/ and handle the parts of a SaaS that trip up non-developers: auth, database schema, Stripe webhooks, new pages, and pre-deploy checks.
package.json ← Next.js + Clerk + Supabase + Stripe
CLAUDE.md ← operating manual for Claude Code
middleware.ts ← Clerk auth guard, pre-wired
app/
page.tsx ← public landing page
dashboard/page.tsx ← protected dashboard
api/webhooks/stripe/ ← Stripe event handler
lib/
supabase.ts ← database client helpers
stripe.ts ← payment helpers + PRICES object
auth-helper.md
db-schema-reviewer.md
stripe-webhook-helper.md
page-generator.md
deploy-reviewer.md
5 agents
One for each part that usually breaks.
Auth, database, payments, new pages, and pre-deploy checks are where most non-developer SaaS projects stall. Each agent handles one of those and outputs working code with an explanation written for someone who doesn't know TypeScript.
01
Auth Helper
Adds protected routes, reads the current user's ID, and sets up user roles. Outputs the complete file — not a snippet — with comments explaining what each line does.
02
DB Schema Reviewer
Reviews a proposed table design, spots problems before you build on a bad foundation, and returns a corrected schema with Row Level Security policies and instructions for running it in Supabase.
03
Stripe Webhook Helper
Wires new Stripe events to database updates and walks through local testing with the Stripe CLI. The scaffold's webhook handler is pre-stubbed — this agent fills it in for your use case.
04
Page Generator
Generates a complete new page from a plain-English description — layout, data fetching from Supabase, and styling. Outputs the full file with a one-sentence instruction for where to save it.
05
Deploy Reviewer
Runs a pre-deploy checklist before you push to Vercel — missing env vars, exposed secrets, Stripe webhook endpoint, Supabase URL config, and .gitignore. Catches the things that break a live deploy.
Who buys this
The non-developer who has a SaaS idea and Claude Code.
This scaffold is for the person with a SaaS idea who is using Claude Code as their engineer. Without a pre-wired starter, you spend the first two weeks setting up auth, configuring Supabase, wiring Stripe, and trying to get a webhook working — before writing a single line of your actual product. This scaffold skips that. The CLAUDE.md tells Claude Code exactly how the project is structured, which means every conversation about adding a new feature starts from context, not from scratch.
How it works
Buy, install, describe your feature, deploy.
01 — Buy
Get the scaffold
Click the buy button. You'll receive a zip file with the starter directory and the 5 agent files. Set up your Clerk, Supabase, and Stripe accounts — the README walks through exactly where to get each key.
02 — Open
Run it in Claude Code
Open the folder in Claude Code. The CLAUDE.md tells Claude what the project is and how to work on it. Type: "Set up the environment variables and get the app running locally." Follow the steps.
03 — Build
Describe what you're building
Tell Claude Code what your SaaS does. Use the page-generator agent to add new pages. Use the db-schema-reviewer before creating tables. Deploy to Vercel when you're ready — the deploy-reviewer agent runs the pre-flight check.
FAQ
Straight answers.
Does this actually run without any code knowledge?
Yes — with Claude Code as your engineer. You describe what you want in plain English; Claude Code writes the code. The scaffold and CLAUDE.md are structured so Claude Code has the context it needs to produce working code on the first try, rather than generic snippets that require debugging. You'll still need to follow the README setup steps, which involve creating three accounts and copying API keys.
What's the ongoing cost to run a SaaS on this stack?
Clerk: free up to 10,000 monthly active users. Supabase: free up to 500MB database. Vercel: free for hobby projects. Stripe: no monthly fee — 2.9% + 30¢ per transaction. For a new SaaS with under 100 users, the total monthly infrastructure cost is approximately $0 until you scale.
Can I change the stack — replace Clerk or Supabase?
You can, but you'd be working against the scaffold rather than with it. The CLAUDE.md and agents are specifically written for the Clerk + Supabase + Stripe combination. If you want a different auth provider or database, the files are editable — but the fastest path to a working SaaS is to start with the stack as shipped.
What's the refund policy?
14-day refund if the scaffold doesn't work for your use case. Email Ethan@septimlabs.com — no form. The only thing we ask is that you attempted the setup and can describe what didn't work.
Ready to build
The wiring is done. Your idea is next.
Auth, database, payments, and agents ready to go. Pay once, keep the files.
Pay once · You keep it · No subscription · Ethan@septimlabs.com