They just chose to pay you more
Testimonial Request After a Plan Upgrade
An upgrade is a decision made with a budget, so the customer has just weighed your product against the money and said yes. That reasoning is exactly what a hesitant prospect on a lower tier wants to hear. Build an email that asks why they moved up, sent once the new features have had a few weeks of real use.
- Asks what tipped the decision to pay more
- Separate wording for free to paid, a higher tier or an add on
- Timed after the new features have been used
Template builder
Write the upgrade request
Pick the kind of upgrade, then fill in the plan they moved to and the feature that came with it. Each question asks about the decision to pay more, which only an upgrader can answer.
- From free user to paying customer
Subject: What made [Ledgerly] worth paying for, [Priya]?
Hi [Priya], It has been [three] weeks since you moved onto the [Team plan]. Thank you for backing us with a budget. Plenty of people are still on the free version, wondering whether paying is worth it. You made that call. What finally tipped it, and what has [approval workflows] done for you since? Type a few lines, record a short video or leave a voice note here: [your StoryProof link] We read every answer before anything is shared. [Tomas]
Templates fill in inside your browser. Nothing is stored or sent from this page.
The problem, solved
Why upgrade asks go unsent, and how StoryProof helps
Your billing system records every upgrade. Turning that event into a published quote is where it stalls.
- Problem 1
Upgrades only show up in billing
The finance team sees the new invoice line. Marketing never hears that a customer chose to pay more.
How StoryProof solves it
Add each week’s upgraders as contacts and keep them in a smart list for the ask, so the request goes to that group and nobody else. Contacts and smart lists are on every plan.
- Problem 2
Asking the same day gets nothing
On the day of the upgrade the customer has not touched the new features, so the best you hear is that it looks good so far.
How StoryProof solves it
Send the email by hand on the date you choose, a few weeks in, with one collection link that takes text, video or an audio note.
- Problem 3
The person who paid is busy
Budget holders get a lot of email, and a single request slips past them.
How StoryProof solves it
From Pro, reminders go out three days and then four more days after the request, stop once they respond, and stay inside your quiet hours.
- Problem 4
Every tier needs its own proof
A quote about the add on is no help on the page for the top tier, and the reverse.
How StoryProof solves it
Tag each answer with the plan or add on the customer moved to, then choose which approved quotes each widget shows.
- Problem 5
They mention a discount we gave
If the upgrade came with a special price, the quote may praise a deal other buyers will never see.
How StoryProof solves it
Nothing goes public until you approve it, so a quote about a one off price can stay private.
When to send it, by kind of upgrade
The right wait is however long it takes to use the thing they paid for, not a fixed number of days.
In StoryProof
Run upgrade requests with StoryProof
Step 1 of 5
Pull last month’s upgraders
Export the customers who moved up and add them as contacts, noting the plan or add on they chose.
Step 2 of 5
Wait until the new features are in use
Use the table above to pick the send date for each kind of upgrade. Skip anyone mid setup.
Step 3 of 5
Email the request
Paste the template for their upgrade type and send it with your collection link.
Step 4 of 5
Approve and tag by plan
Read each answer, keep anything about a private price out of public view, and tag the rest by plan.
Step 5 of 5
Show it to people on the tier below
Place the quotes where lower tier customers decide, such as your pricing page or upgrade screen.
Before you start
Honest limits
StoryProof cannot see your billing
It does not know when a customer changes plan. You pull the list of upgraders and add them.
No upgrade trigger
There is no automation that fires on a plan change. You send the first request yourself; reminders can follow on a plan with automations.
Email only
Requests go out by email. A prompt inside your own product is something you build there.
One upgrade, one ask
A customer who moves up twice in a year should not hear from you twice. Check their tag before you send.
FAQ
Questions people ask
Short answers to what usually comes up next.
How long after an upgrade should I ask for a testimonial?
Long enough for the customer to use what they paid for, often a few weeks. Asking on the day of the upgrade gets a guess about the future rather than an account of what changed.
Should I ask the user or the person who approved the spend?
Both can work. The daily user can describe the feature; the budget holder can say whether the money was worth it. Use the short template for the second.
Where do upgrade testimonials work best?
In front of customers facing the same choice: the pricing page, the upgrade screen and emails that promote the higher tier.
What if they upgraded because they hit a limit?
Ask anyway, but frame it around what they can do now. If the reply is mostly about the limit, keep it as feedback rather than publishing it.
Still have a question? Ask the StoryProof team or book a demo.
Hear why customers paid more
Create a collection link and send your first upgrade request this week. No credit card needed to start.
Last updated 2026-11-12.