Sample blueprint (pre-generated — no API calls)
Invoice SaaS
Recurring invoices, dunning automation, and audit-grade payment reconciliation.
Demonstrates finance-safe engineering: exact money math, guarded invoice state machine, and replayable webhook reconciliation for low billing risk.
Advanced outputs (CLAUDE.md, .cursorrules, Master Prompt)
Recommended Tech Stack
Primary stack: - Next.js 16 App Router + TypeScript strict. Reason: strong full-stack DX and secure server-side rendering for billing data. Alternative: Rails + Hotwire if your team is Ruby-heavy. - UI: Tailwind + shadcn/ui + TanStack Table. Reason: fast dashboards and robust data table patterns. Alternative: MUI DataGrid for built-in enterprise controls. - Auth/tenancy: Clerk organizations. Reason: clean org membership + role management. Alternative: Auth.js + custom org model when cost sensitivity is critical. - DB: Postgres + Prisma. Reason: transactional integrity and mature indexing/performance tooling. - Money math: decimal.js on server + integer cents in DB. Reason: precision and deterministic totals. - Payments: Stripe Payment Links + Checkout + webhooks. Reason: quick go-live, no PCI burden. - Jobs: Trigger.dev or QStash. Reason: reliable recurring invoice and reminder scheduling. - PDF: React-PDF server rendering with versioned template snapshots. Reason: reproducible invoice artifacts for audits. Stack choice rationale: - Optimizes for correctness and supportability, not novelty. - Preserves clear handoff artifacts (OpenAPI, state-machine docs, SQL schema).
Quick FAQ for this example
What makes this example production-ready?
Tenant isolation, immutable audit events, deterministic totals, and webhook idempotency are built in.
Is this only for big teams?
No. The stack and phases are optimized for small teams shipping paid beta quickly.
Can I adapt it for subscriptions instead of invoices?
Yes. Keep the same event/audit backbone and swap invoice lifecycle with subscription lifecycle.
Copy this URL to share the sample blueprint.