An upgrade is a conversion with its own funnel
The guide to designing a pricing page names the existing customer considering an upgrade as a visitor of their own. What they need to know is different from what a new buyer needs: the step up described in their terms, and how an upgrade is billed part-way through a period. That guide sends them to upgrade from inside the account and reports their visits apart from new buyers, and the pricing page layout experiment leaves upgraders out of its sample because their route to a plan is not the one a new buyer takes. That route is what this guide designs.
Like any conversion, the upgrade has steps, and each one can lose the customer.
| Step | What the customer needs | Common failure |
|---|---|---|
| The need arises | To notice that the plan, not the product, is what stands in the way | A limit reached in silence, or a feature that simply fails to appear |
| The prompt | To understand what the next plan allows and roughly what it costs | A block that says "upgrade" and nothing else |
| The upgrade screen | The new price, today's charge, the next billing date and what changes | A link to the public pricing page, written for strangers |
| Confirmation | Proof of what changed and what they will pay | A charge on the next invoice that nobody explained |
| The opening session on the new plan | The task that started all this, now possible | Being dropped on a dashboard to find it again |
| Later | A way back down if the plan stops fitting | A downgrade hidden behind a support request |
Several neighbouring moments belong to other pages. The move from a free trial to a first payment is diagnosed in free trial users not converting to paid and set up in the sign-up and trial-start flows guide; the trial-to-paid rateShare of free trials that became paying subscriptions. measures that moment, not this one. Expansion of business accounts led by sellers and account managers, across teams and sites, is expansion and renewal marketing. Onboarding sequences are built in the software onboarding emails tutorial. And the rules on price-change notice, auto-renewal and contract terms are outside this guide; nothing here is legal advice. The funnel and checkout section places the upgrade beside the other journeys it covers.
Where the need to upgrade shows itself
Upgrades start with a need, not a message. The guide to product-qualified leads reads hitting the limits of a free plan or a trial as a sign of a need that a paid plan would meet, and asks of every such signal whether it led to purchase or to leaving. It also points out that some accounts would rather buy without talking to anyone, and that what may help them most is a clear self-serve route to the paid plan plus an onboarding message, not a call from a seller. The same reading works between paid plans.
The moments fall into a few kinds, and each suggests where the path should begin.
- A limit reached. Seats, locations, projects, records, storage or volume: whatever the plans are fenced by. The customer meets the limit while trying to do something, which is exactly when the prompt is relevant.
- A feature reached for. The customer opens a menu, a report or a setting that belongs to a higher tier. The interest is real, but the need may be passing, so the prompt explains rather than insists. Which tier a new feature belongs to in the first place is a packaging decision, and the guide to deciding which plans get a new feature covers it.
- A change in the customer's situation. A second member of staff, a new site, a busier season. These often show up first as a limit, but sometimes in the account settings or in a support question.
- A billing choice. A move between monthly and annual billing is a plan change in billing terms, recorded as one even though nothing in the product changes.
Which moments matter depends on how the plans are built. The pricing and packaging guide separates good fences, which follow value, such as limits that only heavy users reach, from bad ones, which withhold something every buyer needs and so feel like a punishment instead of a reason to move up. Good-better-best tiering adds that in self-serve software the default tier also frames how each upgrade prompt reads. If most customers hit a fence in their first weeks, the fix is the packaging, not the prompt.
To find the moments in practice, look at what accounts did shortly before upgrading and shortly before leaving: which limits were reached, which higher-tier features were opened, which support questions were asked. Support contacts asking how to do something the plan does not include are upgrade moments the product is currently sending to the support queue.
Prompts that inform rather than pressure
A good prompt appears at the moment of need and answers the questions the customer has at that moment: what they were trying to do, which plan allows it, what that plan costs, and how to move to it. Where the product can let the customer carry on within the current plan, the prompt says how. Where it cannot, it says so plainly and still gives the price.
Three habits keep prompts useful rather than irritating. Trigger them from behaviour, at the moment of need, rather than on a timetable. Cap them, so that a customer who has said no is not asked again on every visit. And keep them out of the way of the task: the guide to push notifications and in-app messaging warns that messages which get in the way of a task, cover the screen or come back every time the app opens teach people to close them without reading, and it regards an in-app message as a piece of the product's interface. Messaging tools and their settings are outside this guide.
The guide to honest persuasion tests every device against three questions: whether it is true, whether the customer would pick it for themselves, and whether the test captures any harm. For upgrade prompts that rules out deadlines that are not real, a higher plan pre-selected on the upgrade screen, and paid extras added unless the customer notices. Its rule on plan defaults applies here too: the plan that fits the customer, not the one with the highest margin.
Decide, too, what happens when a limit is reached. The pricing guide wants its answers section to say which it is: whether the customer is prompted, moved up automatically, charged extra or stopped. Any of them can be fair if the customer knew in advance. An automatic move to a dearer plan that the customer learns about from an invoice is a cost revealed late, whatever the terms said.
Upgrade prompts sent by email follow the rules for marketing. The SaaS industry guide counts trial onboarding, nurture sequences and upgrade prompts as commercial email whenever they promote the product, and keeps purely transactional messages in a stream of their own. The sign-up flows guide, drawing on the list building guide, summarises the Information Commissioner's Office guidance on direct marketing in the UK: when consent is required, and the opt-out each marketing message has to carry. The onboarding emails tutorial classes an upgrade offer as marketing even when it is sent to someone already using the product. So an upgrade email goes only to customers who may receive marketing, carries an opt-out, and never travels inside an account notice.
What the upgrade screen has to show
The upgrade happens inside the account, on a screen that knows who the customer is. Sending an existing customer to the public pricing pageThe page where buyers compare plans and prices, treated as a conversion step that shows who each plan is for, the complete cost and the next step. asks them to work out their own situation from a page written for strangers. The upgrade screen does that work for them.
| Element | What it shows | Why it matters |
|---|---|---|
| Current plan and usage | The customer's own figures against the current limits | The step up in their terms, as the pricing guide asks |
| The proposed plan | What it adds that this customer would use, led by the need that brought them here | A list of every feature reads as a brochure |
| The new recurring price | Per period, with any tax treatment the customer will see on the invoice | Nothing on the invoice should be new |
| Today's charge | What is charged now for the rest of the current period, or that nothing is charged until renewal | The mid-period question every upgrader has |
| The next billing date | When the new price first applies in full | Avoids a surprise on the next statement |
| What changes and when | Whether the new limits apply at once | The customer can finish their task straight away |
| The way back | How to move down again and what that would mean | Lowers the risk of saying yes |
Costs belong on this screen in full before the customer confirms. The pricing guide notes that the UK's Competition and Markets Authority acts on misleading pricing under consumer protection law, fees that surface late in a purchase among them, and an existing customer deserves the same treatment as a new one. How the business bills a change part-way through a period is its own decision; the pricing guide asks only that the answer is published, and this screen shows its result for this customer.
Where the plans follow good-better-best, the natural step is usually the next tier, not the top one. Offer the plan that meets the need that started the journey, with the others available to compare, rather than leading with the tier that carries the best margin.
The button names the action and the price, such as moving to the named plan for the stated amount, rather than a neutral "continue". If payment details are already held, the customer is not asked for them again; if a payment fails, the screen says so plainly and the account stays on its current plan, with nothing half-changed.
Billing, confirmation and the opening session on the new plan
What the upgrade screen promised is what billing must deliver. Charge what the screen said, on the date it said, and make sure the next invoice shows the change in the same terms. Billing support contacts after an upgrade are the clearest sign that the screen and the invoice disagree.
The guide to confirmation pages sets the pattern for the confirmation: say what happened and what happens next before anything else. For a subscription that means the plan and its price, when billing happens, when the plan renews and how to cancel. Send the same facts by account email, as a service message with no promotion in it. The guide to communicating a price change notes that a message mixing a notice with a promotion counts as marketing when it comes to consent and unsubscribing, which is reason enough to keep them apart.
Count the conversion once. The confirmation pages guide warns that a tag firing on every load of a confirmation page counts repeats; record the upgrade from the plan change itself, not from a page view. The subscription measurement guide records plan changes, upgrades, downgrades and switches between monthly and annual billing, as billing events, with billing as the source of truth and the warehouse and CRM fed from it. Send the upgrade to analytics as a Key EventA GA4 event marked as important to the business, the property's measure of success. from the same source, once per plan change.
Then finish the job. The customer upgraded to do something, and the first screen on the new plan should take them back to it with the new capacity in place: the second location added, the extra seat ready for its user, the report open. A short note on what else the new plan includes can follow, but the task that triggered the upgrade comes first. Wider onboarding into the plan's other features belongs to the onboarding sequences, not to this screen.
Moving down or out as easily as moving up
The guide to designing the cancellation experience sets the standard for the other direction: leaving should take no more effort than joining did, and a pause or a smaller plan sits next to the cancel option, not in the way of it. It records that the CMA and other regulators regard easy cancellation of subscriptions as a matter of consumer protection, and the honest persuasion guide asks that a no be as easy as a yes.
For upgrade paths that means three things, as general practice. The downgrade sits where the upgrade sits, in the account's plan settings, not behind a support form. It says plainly what the customer would lose and when, which is the pricing guide's question of whether a downgrade loses anything. And a customer who upgraded by mistake can reverse it without an argument. A visible way back is also part of the case for the upgrade: the customer who can see how to undo the step has less to fear from taking it.
Price changes are a separate journey. When the business changes what plans cost, the price change guide covers grouping customers, notice, reasons and options; this guide does not set notice periods or describe renewal rules, which depend on contracts and local law.
Measuring upgrades apart from new sales
Report upgrades on their own line, apart from new customers, as the pricing guide asks. Mixing them hides both: a rise in upgrades can mask weaker acquisition, and a drop in upgrades disappears inside a good month for new sales.
The rate that tells you whether the path works has a precise denominator: accounts that reached the moment the path serves, such as the limit or the higher-tier feature, in a given period. The numerator is those accounts that upgraded within a fixed window after reaching it. The conversion rate calculator turns those counts into a rate. A rate over all customers mixes those who never needed more with those who did.
Read the rate by CohortA group of customers who share a starting event and period, tracked together over time., grouping accounts by the month they reached the moment, and beside the Churn RateShare of customers at the start of a period who left during it. for the same cohorts. The subscription measurement guide joins billing, analytics and the CRM through a shared customer identifier, which is what lets an upgrade be followed by whatever happened next. An upgrade followed by a downgrade, a refund or a cancellation was not a win.
| Measure | What it shows | Role |
|---|---|---|
| Upgrades per eligible account, within a fixed window | Whether the path converts the customers it serves | Primary outcome |
| Rate at each step: prompt seen, upgrade screen opened, confirmed | Where customers stop | Diagnosis |
| Support contacts about billing or plans after an upgrade | Whether the screen and the invoice agree | Guardrail |
| Downgrades and refunds among upgraders | Whether customers were rushed into a plan that did not fit | Guardrail |
| Churn among upgraders' cohorts | Whether upgrades lasted | Guardrail |
Test prompt changes as the A/B testing guide describes: the primary metric, the guardrails and the sample fixed before launch, and the result read once. Each Guardrail MetricA metric an experiment must not worsen beyond an agreed bound, watched beside the primary metric that decides the test. is a measure that must not get worse, and for upgrade prompts the natural ones are downgrades, refunds, cancellations and support contacts. A variant that wins on upgrades and breaches one of them is not shipped without a deliberate decision. The upgrade prompt test sets out that comparison for a prompt at a plan limit, with each account assigned when it first reaches the limit and every assigned account counted.
A salon booking app redraws its upgrade path (illustrative)
Xyrallon Booking redraws its upgrade path
Xyrallon Booking, an invented appointment-booking app for hair salons, sells a Solo plan at £19 a month for one stylist and a Team plan at £45 a month for up to 8. When a Solo salon tries to add a second stylist, the app blocks the action with "Upgrade to add more staff" and a link to the public pricing page. Over one quarter, 640 Solo salons try to add a stylist; 115 upgrade within 14 days, about 18%. Support logs 95 contacts from those salons asking what the Team plan costs or why their bill changed, and many owners simply keep the second stylist off the system.
The team moves the prompt to the "add stylist" screen itself. It explains that Team adds diaries for each stylist and staff rotas, shows the new price of £45 a month, and states the charge for the rest of the current period before confirmation, for example £17.33 for the remaining 20 days of a 30-day period. The button reads "Move to Team for £45 a month". After the upgrade, the owner lands back on the stylist form with the second diary ready, and the change is confirmed on screen and by an account email that carries no offers. The "Change plan" page shows moving back to Solo as plainly as moving up.
In the following quarter, 610 Solo salons try to add a stylist and 190 upgrade within 14 days, about 31%. Billing contacts from those salons fall to 38. Downgrades within 60 days of upgrading stay near 6% in both quarters, refunds near 2%, and cancellations among the upgraders' cohorts stay level. With no controlled test behind it, the team treats the quarter-on-quarter rise as directional rather than proven: it records that prices, plans and acquisition did not change across the two quarters, reads the flat guardrails as a sign that salons were not rushed into a plan they did not want, and runs the next change to the prompt as a test.
Common mistakes
- Sending existing customers to the public pricing page. It cannot show their usage, their charge today or their next bill.
- A block with no explanation. Say what the customer tried, which plan allows it and what it costs.
- Prompts on a timetable. Trigger them from the moment of need, and cap them.
- Leading with the top tier. Offer the plan that meets the need, not the one with the best margin.
- A charge the screen never mentioned. Show today's charge, the new price and the next billing date before confirmation.
- Automatic upgrades customers learn about from an invoice. Say in advance what happens at a limit.
- Upgrade offers inside account notices. Keep service messages free of promotion, and send upgrade emails only where marketing is allowed.
- Counting upgrades with new sales. Report them apart, by cohort, beside churn.
- Counting the upgrade on page loads. Record it once, from the plan change.
- A downgrade only support can do. Put the way down beside the way up.
- Judging a prompt on upgrades alone. Read downgrades, refunds, cancellations and billing contacts with it.
