saas-mvp-launcher

Use Next.js 15 with TypeScript, Tailwind, and shadcn/ui for the frontend, Supabase PostgreSQL with Prisma for data, Clerk for auth, and Stripe for payments. Follow a structured roadmap: validate the idea, scaffold the project structure, implement auth and billing, then run a pre-launch checklist.

A recommended stack is Next.js 15 with TypeScript, Tailwind CSS with shadcn/ui, PostgreSQL via Supabase, Prisma or Drizzle as ORM, Clerk or NextAuth.js for auth, Stripe for payments, Resend for email, and Vercel plus Railway for deployment.

Clerk provides managed social login and session management with middleware-based route protection, while NextAuth.js is a self-hosted alternative. The Skill recommends either over building custom auth, which adds unnecessary risk and development time.

Use the Stripe CLI to forward webhook events to your local server. Run 'stripe listen --forward-to localhost:3000/api/webhooks/stripe' so subscription events reach your Next.js API route during development.

Production failures usually happen when running 'prisma migrate dev', which is meant for local development. Always use 'prisma migrate deploy' in production environments to apply migrations safely without prompts or schema drift checks.

Do not build if you cannot get at least three potential customers to pre-pay or sign a letter of intent. Validate the problem, target customer, and willingness to pay before writing any code.