Best for
- Subscription tool
- B2B dashboard
- Multi-tenant app
Avoid if
- Landing page only
- No defined pricing
You need before starting
- Pricing tiers
- User roles
- Core workflow diagram
- Legal pages
● Skill pack
- 01-start-here.md
- 02-business-brief.md
- agent-instructions.md
- deploy-checklist.md
● STACK
Recommended stack
Next.jsVercelSupabaseStripe
● Build phases
SaaS product
01
MVP scope
One paid workflow, one role, one integration.
Done when: Written MVP fits one page
02
Auth and data model
Define users, orgs, roles, core tables and access rules before screens.
Done when: A user can sign in and see only their own workspace
03
Billing path
Connect Stripe subscriptions, customer portal, webhook sync and plan gates.
Done when: Test subscription changes access without manual database edits
04
Usage and support
Add onboarding, usage limits, empty states, logs and support contact.
Done when: First customer can complete the paid workflow end to end
Risks
- Scope creep
- Auth bugs
- Billing edge cases
Usually wrong choice
- Astro for authenticated SaaS
- No staging environment
When to call rescue
- Subscription webhooks fail
- Users locked out
- Data leak risk