SaaS Entitlements and Plan Gating

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.

Use When

Designing the runtime that answers "what is this tenant allowed to do?" — every gated feature, every limit-checked action, every plan-tied capability.
Replacing scattered if tenant.plan == 'pro' checks with a single entitlements service.
Designing the data model for plans, features, limits, overrides, and add-ons.
Supporting enterprise custom-contract overrides without forking the codebase.
Pairing in-product upgrade prompts (PLG) with the gate runtime so users hit a wall and see the path forward.
Coordinating entitlements with feature flags (distinct concerns; they overlap dangerously if confused).

The task is Stripe Billing primitives (Plan / Price / Subscription / Trial) — use subscription-billing. This skill consumes those primitives.
The task is experimentation feature flags (A/B tests, gradual rollout) — feature flags ≠ entitlements; see §3.
The task is per-tenant data isolation — use multi-tenant-saas-architecture.
The task is enterprise SSO/SCIM — use saas-sso-scim-enterprise-auth.