/saas-builder
Agent 34: Custom SaaS on Vercel (S7 Builders, any industry)
Designs and, on explicit approval, ships a bespoke custom SaaS web application (real accounts, a database, optional billing) for a business's own product idea, hosted on the user's own GitHub/Vercel rather than GHL's SaaS mode. Defaults to the program's own stack (Next.js + tRPC on Vercel, Postgres/Neon + Drizzle, Clerk auth) unless overridden. No repo or deployment is created until the user names the product and says yes.
verified (fixture) 2026-09-08 · manual-fallback: repo/deployment creation held pending the user's explicit approvalv0.1.0
Its status above is the registry's own, with the date of the run that produced it.
What it is for
Contract A
- #34 — Custom SaaS (Vercel etc.)
Example requests
- “build us a custom SaaS app”
- “we want a client portal beyond what GHL gives us”
- “build a real web app for this idea”
- “saas builder”
What it needs, and what it hands back
Needs connected
- github
- vercel
Better with: stripe.
Uses create_repository, create_git_project, list_deployments, get_deployment, get_deployment_build_logs, web_fetch_vercel_url, which exist in Claude Code. In the platform those steps come back as something for you to do, with the exact clicks.
Hands back
- clients/<business-slug>/plans/saas/saas-builder-<date>.md (spec, approval record, and once built: repo URL, live URL, deployment read-back)
Stops and asks
- creating the GitHub repo and Vercel project for a named product
- enabling a billing provider at a quoted price
Steps it cannot do through an API, and hands you instead: linking the Vercel project when create_git_project is unavailable or denied -- the exact Add New -> Import Git Repository click path.
How it runs
These are the headings of its own written instructions — 241 lines you can read and change.
- Step 0 — Environment, connection, and profile
- Step 1 — Design the application
- Step 2 — Approval gate (real infrastructure is next)
- Step 3 — Scaffold, push, and deploy (only after Step 2's yes)