How to ask users why they didn’t upgrade (questions and timing)
The questions, timing and wording that get honest answers from people who tried your product and didn’t pay, without sounding like a sales follow-up.
Short answer: ask soon, ask a single open question, and make it clear you want to learn, not to sell. The best moments are while they’re still in the product (near the end of a trial, after they decline an upgrade) and within a day or two of a trial ending. Use plain text from a real person, and reply to every answer.
In the founder posts we read, the most common reaction to trials that didn’t convert was to change something: the price, the ads, the trial. The founders who learned fastest asked first. One emailed users who had left, got a single reply, and rebuilt their offer around it.
Good questions
- “What would have made {product} worth paying for?”
- “What were you hoping {product} would do?”
- “Was anything confusing, missing or broken?”
- “What are you using instead?”
Questions to avoid
- “Can we offer you a discount?” as the first message. It tells them you want the sale, not the reason.
- “On a scale of 1 to 10…” Scores tell you little at small scale.
- Several questions at once. Pick the one you most need answered.
- “Why didn’t you buy?” It can feel accusatory. Ask what would have helped instead.
When to ask
| Moment | Channel | Example |
|---|---|---|
| They decline an upgrade prompt | Inside the product | “No problem. Anything missing that would change your mind?” |
| Last days of the trial | Inside the product or email | “Is anything stopping you from continuing?” |
| Trial just ended | Plain email | “What would have made it worth paying for?” |
| They cancelled a paid plan | Plain email, same day | “If there was one thing that would have kept you, what was it?” |
Template: trial ended without upgrading
Subject: One question about {product}
Hi {first name},
Your {product} trial ended yesterday. No pressure at all, but I’d love
to know: what would have made it worth paying for?
A one-line reply helps me a lot. I read every answer.
{your name}What to do with the answers
- Write each answer down in their words.
- After ten or so, group them. Usually two or three themes cover most answers.
- Fix the biggest theme first, then tell the people who mentioned it.
- Some of them will come back. Many won’t, but the next trial users will convert better.
In-product prompts that work
- After declining an upgrade: “No problem. Is something missing?” with a free text box, and nothing else.
- On the pricing page: a small “Questions about plans?” link that opens a way to ask.
- When someone hits a limit: explain the limit, offer the upgrade, and offer a way to ask if the plan doesn’t fit.
- After a downgrade: “What made you switch plans?” One line, optional.
Sorting the answers
| What they say | What it usually means | What to try |
|---|---|---|
| “Too expensive” | Didn’t see enough value, or the plan doesn’t fit their size | Ask what they’d use it for; consider a smaller plan |
| “Didn’t have time to try it” | Trial too short or setup too long | Extend for them; shorten setup |
| “Missing X” | A real gap, or a feature they didn’t find | Check whether it exists; show them or note the request |
| “Using something else” | Competitor or workaround | Ask what it does better |
| “Didn’t need it after all” | Wrong audience or one-off need | Check targeting; consider one-time pricing |
Following up after a fix
When you fix the thing someone said stopped them, tell them personally. A short note (“you mentioned X was missing; it’s there now”) is one of the few follow-ups people appreciate, and some of them come back. Keep a simple list of who asked for what so you can do this.
How many answers you need
Fewer than you think. With a small product, five to ten honest answers usually show the main reason. You’re not measuring percentages; you’re looking for the problem that comes up again and again. When the same reason appears three times, it’s worth acting on.
Keeping track
| Date | Who | Their words | Group | Followed up |
|---|---|---|---|---|
| Nov 3 | Trial user, design agency | “Needed it for two client sites, plan only had one” | Plan limits | Yes, offered the larger plan |
| Nov 5 | Trial user, solo founder | “Didn’t get time to set it up” | Time | Extended trial |
| Nov 9 | Trial user, SaaS | “Couldn’t connect it to our tracker” | Missing integration | Noted, will tell them when it ships |
A simple table like this (with real customers instead of these examples) is enough. Review it monthly.
Let them tell you before they decide
The best answers come while people are still trying your product. Bopmigo puts a Feedback option inside your web app or app so trial users can tell you what’s missing in a sentence, with the screen included. You can reply where they asked, and you can start a conversation with a specific user yourself, for example near the end of their trial.