Skip to content

Decide each plan’s features and limits

Your plans will change many times. Build tiers, limits and add-ons in Entitler, edit them in a change, and release new versions without losing track of the terms earlier customers were promised.

Early access. We invite teams in small groups.

Explore the example
Example preview
TeamInherits from Pro · 6 featuresv1
ProMonthly · Yearly · 4 featuresv2
Pro basicInherits from Pro · 3 featuresv1
Pro plusInherits from Pro · 5 featuresUpgrade path from Pro added

Q4 pricing sent to Priya Shah for review.

Add a higher tier above Pro

Pro needs a higher tier, but its existing customers should keep their terms. Build Pro plus from it in a change, adjust the package and decide how both versions reach customers, track by track.

Step 1 of 6: Build on Pro

Step 1 of 6: Build on Pro

In the Q4 pricing change, Ana creates Pro plus for customers needing more AI credits, starting with Pro's features.

Requested packagePro plus inherits Pro, with more AI credits and shared folders.
Customer termsPro version 2: 500 → 300 credits in version 3. Choose how existing customers move before release.
Ana Silva, head of product
Pro is doing two jobs

Pro serves customers with very different usage needs. In the Q4 pricing change, create Pro plus with 2,000 AI credits and shared folders, and set Pro's new allowance to 300 credits.

Search

Editing Q4 pricing

New planNew plans start in Q4 pricing, the change you are editing. Customers can subscribe once it is released and rolled out to their track.
PlanOne active plan per customer
Add-onAdditional features for an existing plan
Name · Prepared valuePro plus
Key · Prepared valuepro_plusUse this key in your code. It is locked once the change is released.
Inherits from · Prepared valuePro
Billing periods
WeeklyMonthlyQuarterlyEvery six monthsYearlyEvery two years
Preview: Cancel

The rules behind inheritance

Pro plus stays linked to Pro. Features you leave alone update when Pro does. Anything you change, remove or add stays as you set it.

  1. 1

    From Pro

    Export to PDFOn or off, from ProIncluded
    When Pro changes

    Inherits from Pro. A change to Pro also opens a Pro plus version with the inherited update, released together.

    Set your own value to stop following.

  2. 2

    Changed from Pro

    AI creditsMetered, changed from Pro2,000 creditsPro has 500
    When Pro changes

    Stays as you set it, regardless of changes to Pro.

    Use Pro’s value to follow Pro again.

  3. 3

    Removed from Pro

    Priority supportRemoved from ProRestore
    When Pro changes

    Stays out, even if Pro changes it.

    Restore puts it back, following Pro.

  4. 4

    Added in Pro plus

    Shared foldersOn or off, added in Pro plusIncluded
    When Pro changes

    Belongs to Pro plus alone. Pro never touches it.

    Remove it like any other feature.

More ways to reshape the plans you sell

Use the canvas, the feature matrix and a review of each change to manage common packaging updates.

  • A cheaper tier without the extras

    Some customers need Pro's core features at a lower price, without premium support. Create a plan based on Pro, remove priority support and set a longer support response time. The sample Pro basic plan uses this approach.

  • Three products back into one

    You want to combine three separate products into one set of tiers. Build the replacement tiers in one change and mark the old plans as legacy, which closes them to new subscriptions on each track that runs the release. Existing customers keep their access until they move through a plan change or an upgrade prompt.

    More on retiring a plan

  • Change Pro's features for new customers

    Shared folders cost more to support than expected, so you want to move them from Pro to Team. Update both plans in the matrix in one change and release them together. Pro’s new version can keep existing customers on their version, or keep only the cohorts you promised shared folders to, while upgrade recommendations point to Team.

    More on upgrade prompts

  • A large customer wants a custom bundle

    An enterprise customer needs Team with single sign-on and a four-hour support response time. Create a plan based on Team and override the requested features or limits. Other features continue to inherit from Team.

    Explore custom plans

Questions product teams ask

Only when you choose. Each new plan version says how customers on older versions move: they stay, move at renewal or move now. When you roll out the release to a track, you can choose differently for any cohort, such as keeping a sale’s customers on their version while the rest move. The move runs on each track when the release is rolled out to it, so customers on Beta can move before those on All customers. New subscribers join the version their track runs.

More solutions

Explore all solutions, organised by team, company size, industry and use case.

See how this would work for your product.

Try your plans in Entitler

Start with sample plans and customers. Then try a change you expect to make, such as a new tier, a usage allowance or an exception for an early customer. Request an invite to try it with your team.

Early access. We invite teams in small groups.