In SaaS and API products, plans and add ons are pricing-linked packages that set what a customer can access and how much they can use, while add ons extend that access for an extra charge.
They connect billing state to product behavior by defining entitlements like features, seats, credits, and limits, helping prevent mismatches between what is paid for and what is enforced.
During a request, the app sends the account’s plan, active add ons, role, and recent usage to an entitlement service, which returns an access decision and limit-enforcement outcome.
Plans and add ons are evaluated at runtime as events stream in, with counters updated, credits decremented, and feature flags rechecked so upgrades or cancellations immediately change state.
These characteristics clarify how packaging choices are expressed in subscriptions, so readers can interpret common configurations without revisiting runtime evaluation or enforcement behavior.
SaaS and AI products often define whether access and limits apply at the user, seat, workspace, or account level, shaping how subscriptions map to multi-tenant structures.
Plans commonly specify the unit that is counted, such as API calls, tokens, minutes, documents, or storage, so limits and credits align with observable activity.
Many products describe tiers through named bundles that combine feature access with quantitative ceilings like seats or monthly volume, serving as the default subscription choice.
Add ons typically declare eligibility and stacking behavior, such as whether they require a base tier, apply once per account, or scale with seats or usage.
Clear plan and add on choices translate into a more predictable day-to-day product experience by aligning what someone expects to have with what they can actually use as their needs change.
Users see a consistent set of available features across accounts and workspaces, which reduces confusion about what is included.
Upgrades map to immediate access to newly available capabilities, so teams can adopt additional functionality without waiting for a release cycle.
Add ons create a straightforward path to extend capacity or unlock specialized functionality without switching tiers.
Usage boundaries become easier to understand in practice because limits and allowances behave consistently as activity increases.
Account owners gain cleaner control over who can use what within a subscription, which helps match access to responsibilities.
Within the application’s monetization flow, Schematic functions as the system that implements plan and add on packaging by translating subscription and billing-state inputs into authoritative entitlement state used by the product at decision time.
Schematic implements access control by evaluating whether a given account, workspace, or user should have specific capabilities based on the current subscription, active add ons, and related billing conditions such as upgrades, cancellations, renewals, or past-due status.
Schematic implements usage handling by maintaining the counters or credit-like balances associated with plan and add on allowances and applying those quantities when product activity is assessed against current limits.
Schematic implements synchronization between packaging and product behavior by keeping entitlement state consistent with subscription changes, so the same plan and add on definitions drive both what is allowed and how much is available at any moment without embedding that logic throughout the codebase.
Most add ons require an active base plan and cannot be purchased independently, as they are designed to extend or enhance existing plan entitlements rather than function as standalone packages.
Whether limits apply per user, seat, workspace, or account depends on how the product defines entitlement scope, so enforcement boundaries may vary between different SaaS offerings.
Whether limits apply per user, seat, workspace, or account depends on how the product defines entitlement scope, so enforcement boundaries may vary between different SaaS offerings.
Exceeding a plan’s usage limit may result in restricted access, additional charges, or the need to upgrade, depending on the product’s specific policies for handling overages.
Exceeding a plan’s usage limit may result in restricted access, additional charges, or the need to upgrade, depending on the product’s specific policies for handling overages.
