Internal tools die when login is embarrassing or tables cannot be trusted. They also die when a kit's demo CRM becomes the product by accident. Use kits for the shell; invent the workflows that match how your company actually operates.
Good fits
- Staff login with roles before you expose sensitive ops data.
- An admin shell you can hang approval queues and audit tables on.
- A billing entitlement viewer for support when customers say “I paid.”
Bad fits
- Replacing a mature ERP with a starter dashboard.
- Anything requiring on-prem constraints the kit never designed for.
- Tools that need fine-grained SSO tomorrow when the kit only has passwords today - unless you budget the IdP work.
Name environments clearly (tools-staging, tools-prod). Internal apps still leak when cookies and webhooks point at the wrong host.
Operating rules
- Delete demo entities on day one so nobody “uses the sample tenant.”
- Map roles to real job functions, not kit defaults.
- Log admin mutations; internal abuse is still abuse.
- Back up the database on the same cadence as customer data if it holds PII.
Billing kits inside internal tools
Support teams often need read-only entitlement views. A billing module can supply the schema even when Checkout is customer-facing elsewhere. Do not run a second source of truth for “who paid.”
Browse Admin Dashboards and Auth Systems, then strip every sample table before the first real CSV import.