Skip to content

Know which customers receive which terms

When your plans change, some customers should move and others should keep their agreement. Entitler lets finance review each change, release it and approve its rollout to production, and control when existing customers receive the new terms.

Early access. We invite teams in small groups.

Explore the example
Example preview
Faster Pro supportPro, version 3 · based on Team launchIn review

Sam Taylor sent this change for review yesterday and asked you to approve it.

Support SLA24 hours12 hours
OK. No features are removed.
Warning. Support SLA drops from 24 hours to 12 hours.
Approve and releaseSend back to Sam

Review a change to Pro’s customer terms

A plan change is easy to announce. Before you release it and roll it out to production, decide whether existing subscribers receive it too.

Step 1 of 5: A change arrives

Step 1 of 5: A change arrives
Nina Brooks · Finance · Faster Pro support · Review

Sam sends the Faster Pro support change for review. It opens Pro version 3, cutting Pro's support response time from 24 to 12 hours.

Service commitmentPro support reply: 24 → 12 hours.
Default move for existing Pro customersKeep their current version. All customers keeps its current release until rollout. Individual cohort choices at rollout override this default.
Search

Editing Faster Pro support

ProproEverything for one person.ActiveMonthlyYearly
Version 3 is open in Faster Pro support, waiting for reviewSam Taylor sent it to Nina Brooks: Support SLA from 24 to 12 hours. Every track keeps its release, and customers keep version 2, until it is released and rolled out.
  1. v3Open, in reviewSupport SLA from 24 to 12 hours
  2. v2Released in More AI credits on ProAI credits from 300 to 500
  3. v1LegacyFirst version, still held by 1,204 customers

Version 3 is waiting for review. Every track keeps running its release, so customers keep version 2 until you release the change, roll it out and choose how they move.

Clear rules when customers change plans

Set when upgrades, downgrades and switches take effect. With Stripe connected, Entitler charges each change to the price its listing names, as these rules say.

Upgrades

A customer on Pro basic asks to move to Pro halfway through their billing period.
  • They move to Pro today.
  • Their renewal date stays the same.
  • Stripe charges for the remaining period on a prorated invoice.

Owners and admins set project defaults in Settings. You can override them for any one move between plans, such as an immediate downgrade that credits unused time.

Releasing a change and rolling it out

Team roles decide the editing and releasing of changes. Each environment’s protection decides the roles allowed to roll out releases to its tracks.

  • Approve and release

    • OwnerFull access, including member and project management.
    • AdminManage plans, customers, API keys, members and project settings.
    • FinanceReview and release changes, and roll out and approve releases in production.

  • Edit changes and send them for review

    • DeveloperEdit changes, send them for review and manage API keys. Changes customers in test environments only.
    • MarketingEdit changes, send them for review and change customers.

  • Read plans but not change them

    • SupportManage customer subscriptions, grants and usage. Read the catalogue without editing it.
    • ViewerView project data without making changes.

Other roles can view the review but cannot approve or release it. By default only owners roll out to Production; list Finance in its protection so finance can roll out too. A live environment can also require a second person to approve each rollout.

When packaging changes an agreement

Review each change and choose when existing customers receive it.

  • A plan is about to lose a feature

    Someone takes Export to PDF out of a plan to make room for a new tier. The review warns that the change removes Export to PDF. Let customers on older versions stay where they are, so only new subscribers on each track receive the change.

  • Some customers were promised their terms

    Your first customers signed contracts that name their plan’s allowances. Start a cohort for them as they join. When a later release changes the plan, keep that cohort on its version while every other cohort moves at renewal.

  • Several plans change at once

    A pricing update touches Pro, Pro basic and Team together. All three change in one change, so you review them together, choose how existing customers move for each new version and release them as one release.

    How product builds the changes

  • A plan is being retired

    Starter has been replaced by Pro, but existing subscribers still need a managed transition. Mark Starter as legacy in a change. Once a track runs that release, Starter closes to new subscriptions there; existing customers keep access until you move them to Pro.

    More on retiring a plan

  • A customer needs a custom plan

    Sales has agreed a bundle that is not on the pricing page. Create a custom plan based on Team or Pro in a change. Review its features and limits before releasing it and rolling out the release.

    Explore custom plans

Questions finance teams ask

Any role that can release, such as owner, admin or a finance role you add, can release a change. With reviews on, others send changes for review instead. Rollouts to a live environment need an owner until you list the roles that may roll out there.

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.