Product capability map

The founder MVP template ships with the hard parts already shaped.

Each capability is designed to be customized without breaking the workspace, authorization, billing, or operator model that keeps the MVP production-ready.

Acquisition surface

Landing, pricing, feature, legal, changelog, and contact pages are separated from the authenticated shell so public copy can change without touching app logic.

  • Metadata per route
  • Sitemap and robots coverage
  • Central marketing content module

Authentication and workspace model

Firebase Auth, custom claims, workspace documents, member records, and invite callables are the default pattern for every customer fork.

  • Email verification gate
  • Owner/admin/member roles
  • Platform admin claim

Billing and plan gates

Stripe checkout and customer portal calls live in Cloud Functions, while the UI reads plan metadata from one customer-editable module.

  • Free, Pro, Enterprise
  • Server-side Stripe only
  • Idempotent webhook event storage

Operator controls

The admin shell is scoped to platform operators and intentionally excluded from public indexing and public navigation discovery.

  • Workspace overview
  • User lookup
  • Audit feed
  • Feature flags