Starter Overview
This starter kit is built for teams launching a B2B2C SaaS product that needs three distinct surfaces without splitting into multiple apps too early.
It gives you one repo with a clear separation between:
- the org-facing product surface
- the tenant-facing portal surface
- the platform-operator surface
- the public marketing site
- the shared backend and typed packages behind them
What It Is Good For
- products with both staff and customer-facing experiences
- teams that want one app shell but explicit surface boundaries
- builders who want Convex, Next.js, and typed shared packages already wired together
- teams who expect to customize auth, billing, permissions, and product workflows quickly
What It Is Not Trying To Be
- a one-page marketing template
- a generic CRUD boilerplate with no product shape
- a finished vertical product with your business rules already chosen
Evaluation Checklist
- Does the org, portal, platform split match your product?
- Does the repo structure match how your team wants to work?
- Are the backend and package boundaries clear enough to extend safely?
- Does the starter remove enough setup cost to justify adopting it?