A useful subscription plan makes it clear what customers receive, which limits apply and how the service continues. If you offer several tiers, each should meet a recognisable need. The goal is to help buyers choose and enable your team to deliver exactly what they purchased.
For a business in Andorra, define the features and rules first, then connect the catalogue, payment and access. At AndorPay, we review that journey with your banking setup and platform so that the plan shown in the offer is the plan collected and delivered.
Start with genuinely different buying situations
Tiers make sense when they meet different needs. Someone working alone may need individual access; a team may need multiple users and shared management. That distinction is more useful than inventing “Pro” and “Premium” names without explaining what changes.
Write down what each buyer wants to do, what they need on day one and what might become useful later. Do not turn every future possibility into a current plan. Each option adds rules, messages, checks and support questions.
A single plan can be a good starting point if it meets the main need. Separate offers may also make sense when they deliver genuinely different services. The number of columns does not determine offer quality; buyers need to recognise their situation without interpreting your internal organisation.
Create an operational description of each plan
Before designing the comparison table, write a description that both sales and the application team can use. Cover the service, period, limits, access and continuation rules.
| Item | What needs defining | Example decision |
|---|---|---|
| Intended buyer | Who needs this option | Individual or team use |
| Service | What they receive during the period | Library, sessions or application |
| Limit | Included quantity or scope | Users or available actions |
| Period | Start and end | Signup date or common date |
| Renewal | How the service continues | Next period and communication |
| Change | When another option takes effect | End of the current period |
| Cancellation | What happens to current access | End date communicated to the user |
Add the relevant commercial terms and documentation requirements. The internal description needs precision even if the website presents a simpler explanation. If your team cannot describe what happens when a customer changes plans, a decision remains unresolved before configuration.
Compare plans using the same criteria
Organise all tiers around common categories. If one column talks about users and another about abstract benefits, readers cannot compare them. Keep the same order: intended customer, main features, limits and support.
Baymard's plan matrix research describes the role of these tables in comparing features and finding an appropriate option. In practice, show the differences that affect the decision and make it easy to check whether a needed feature is included.
Avoid filling the table with identical rows simply to make it look substantial. Group common features and reserve comparison space for meaningful differences. Technical detail can have a separate explanation; the table should support a clear initial choice.
Use names that help people navigate
A name can guide buyers, but it does not replace a description. Add a line such as “For individual work” or “For teams sharing the service”. This identifies the intended user before they read every limit.
If you highlight an option, explain who it suits. Do not call a plan popular without supporting data. The recommendation should make sense because of its features and the buyer's circumstances, rather than an unsupported label.
Read the comparison aloud as though explaining it to a prospect. If you keep needing qualifications outside the table, incorporate the important ones into the plan description. The aim is a decision the customer can make without an extra translation by your sales team.
Define limits you can explain and measure
A limit needs an operational meaning. “Five users” should establish whether pending invitations, active people or all created members count. “Included sessions” should explain what happens to a cancelled booking. These details prevent differences between the offer and application behaviour.
Decide what happens at the limit. The service might stop new actions, offer another plan or apply another agreed rule. Users should know the next step before encountering an error they do not understand.
Variable consumption also requires unit records and a calculation rule. Our usage-based billing guide develops that part. Adding a counter to the commercial table does not establish that measurement and collection are ready.
Monthly and annual: explain the actual period
Two frequencies can provide the same features while changing the purchase and renewal calendar. Buyers must understand the period they are purchasing and when another payment occurs. An informational monthly equivalent should not obscure the payment they are actually accepting.
Define cancellation effects for each frequency. The end date should match the service terms and recorded period. Do not infer annual behaviour by simply multiplying monthly settings; review dates, messages and subsequent management.
When an offer changes during a period, distinguish new purchases from existing ones. Retaining each version's identity and terms lets you explain why two customers may have different service periods or entitlements.
This also matters to support. A current website description does not necessarily describe an earlier purchase. Keep enough history for your team to answer using the customer's actual plan rather than the latest marketing page.
Prepare plan changes before offering them
Changing a plan has at least three dimensions: when access changes, what happens to the existing period and when the next payment changes. Write the whole rule. A “change plan” button does not answer those questions on its own.
For an initial offer, applying changes at the next renewal may be straightforward when it fits the service. The rule still needs implementing and testing. Immediate changes or financial adjustments require a specific review of integration support.
Do not promise automatic prorating merely because a tool offers multiple plans. Do not assume that changing a payment amount updates your application's permissions. Collection and delivery need an explicit connection for customers to receive the correct option.
Example: moving from individual to team access
Imagine a service with an individual plan and a multi-user plan. When requesting the change, the buyer needs to know when they can invite colleagues and which period the new option covers. The system retains the request and applies the agreed rule at the right time.
When the change takes effect, the application updates permissions. The next payment should correspond to the plan valid for that period. If payment encounters a problem, the established policy applies rather than an improvised mixture of old and new access rights.
If the amount also changes according to business data or rules, read how to plan dynamic subscription pricing to distinguish it from a straightforward plan change.
Align the offer, checkout and service
Plan name, frequency and features need to stay together. If the sales page describes one option and checkout shows another name, the buyer may stop to check what they are purchasing. A consistent catalogue removes that avoidable doubt.
After payment, welcome instructions should explain how to use what is included. For sessions, explain the booking step. For multiple users, describe how access is managed through the available integration. Do not advertise interface actions that your product does not yet provide.
Our payment lifecycle documentation separates financial confirmation from subscription events. That distinction supports activation of the right period without treating creation of a subscription as proof of collection.
Promotions and trials need rules too
If you offer an introductory condition, define who qualifies, how long it lasts and what happens afterwards. Customers should recognise when the ordinary arrangement begins. The commercial explanation and payment configuration need to agree.
A trial requires rules for start, end, access and transition to payment. A discount needs duration and eligibility. These are more than messages added beside a price: they affect signup and ongoing management.
To define the promotion, read how to set subscription coupon rules and duration, including what happens when the discount ends or the customer changes plans.
Before enabling them, review what your installation supports. Our API documentation describes available contracts and restrictions. Support for a particular condition needs verification within your project's scope.
Keep the original plan understandable without its introductory condition. If a customer cannot explain what continues after the trial, the offer still needs clarification. The end of an introduction should feel like the stated next step, rather than an unexpected change of product.
Use real questions to improve the offer
Sales questions show where plan differences are unclear. If people repeatedly ask which option they need, the intended customers may be poorly described. If buyers soon discover a limit, examine how and when that information was presented.
Observe use after signup too. An included feature nobody can find may need better onboarding. A plan requiring constant manual adjustments may have rules that are too complicated for the current stage of the business. These are signals for specific improvements to content and operations.
Avoid changing several dimensions at once without keeping context. If names, limits and scheduling change together, it becomes harder to identify what resolved the buyer's question. Keep a simple record of the offer version and the confusion you intended to address.
Test every plan before opening sales
Complete a test purchase for each option. Verify the selected plan, payment, period and access. Add a reached limit, a plan change and a cancellation. Check the customer's messages and confirm that your team can identify the purchased version.
Test a repeated notification too: the same payment must not extend the period twice. When an outcome is pending, access should follow the defined policy without accidentally creating another charge. The comparison table is ready when its advertised journey can be verified.
To prepare the connection, send us your plans and how you want them to work. We can review catalogue, calendar and access with AndorPay and prepare a private proposal. If the choice between purchase and recurrence is still open, begin with our guide to one-off payments, instalments and subscriptions.
Frequently asked questions
Should I create three plans?
There is no required number. Use options that meet distinct needs and that you can operate properly. One clear plan may be more useful at launch than several options whose differences are difficult to explain.
Can I change the limits of an existing plan?
Define which purchases the change affects and its effective date. Retain earlier terms so current periods remain explainable. The application and messages should reflect that decision.
Do multiple plans mean customers can switch automatically?
No. A catalogue and plan-change management are separate capabilities. Verify when payment, period and access update, and what happens if one of those actions fails.
