Skip to main content

Vertical Fit and Use Cases

This starter is strongest when the product has a real separation between internal operators, organization staff, and customer-facing portal users.

Strong Fit

These are the clearest fits for the starter as it exists today.

B2B2C SaaS platforms

If your product has a company-facing workspace, a customer-facing portal, and a platform-level operator layer, this starter matches that shape directly.

Service businesses with customer portals

If staff need operational tooling while customers need a separate login and self-service surface, the org plus portal split is useful immediately.

Multi-tenant products with billing and gated features

If your roadmap includes plan tiers, permissions, and tenant-specific workflows, the current billing and capability model gives you a real starting point.

Moderate Fit

These cases can still work, but they usually require a more opinionated fork.

Partner or vendor platforms

If your "portal" users are vendors, suppliers, or partners instead of end customers, the host model still works, but your domain workflows will diverge quickly.

Internal-plus-external operations products

If you have a strong internal ops layer and one external customer surface, the starter can still fit well even if one of the product surfaces stays relatively thin.

Likely Overkill

These are the cases where the starter may be more structure than you need.

Single-surface SaaS apps

If you only need one authenticated product surface with no real tenant portal split, this starter may feel heavier than necessary.

Pure marketing or content sites

If the product is mostly public pages with minimal authenticated product behavior, this is not the right starting point.

Simple internal dashboards

If there is no external customer experience and no meaningful host or tenant boundary, a smaller template is often a better fit.

Buyer Questions

  • Do you truly need separate staff and customer surfaces?
  • Will platform-level operations remain distinct from tenant operations?
  • Do you expect permissions, billing, and capability gating to matter early?
  • Is tenant routing part of the product, not just a future maybe?