Skip to content
AppDues
Log in
Contact salesSign up

Using customer interviews to improve pricing decisions

Pricing changes can compound over time, but frequent changes can harm trust and leaving a price unchanged can leave growth on the table. Conversations with customers can reveal how value is perceived, provided the questions are designed to limit bias and are checked against behavioural evidence.

Watch out for bias before asking about price

Two risks recur in pricing interviews. First, people may try to please the interviewer, so praise can be a warning sign rather than evidence. Second, people often overestimate what they will do in future, especially when asked whether they would pay. Treat compliments and hypothetical yes answers as weak signals. Ground questions in past behaviour, current spending and specific decisions, and combine interviews with quantitative analysis, user testing and, where possible, A/B testing before making permanent changes. Record whether each participant uses Android or iOS and analyse platform learnings separately, because pricing behaviour can differ between them.

Interview potential customers around current behaviour

Choose potential customers by relevant behaviour and need, not only by demographics. Avoid screening questions that reveal the desired answer. For a meditation app for sleep, instead of asking directly whether someone meditates several times a week and has sleep problems, offer several activities and several reasons for meditating so relevant people can identify themselves without being led. Then ask what solutions they currently use, why they use them, how long they have used them, what they pay, and what makes that price worthwhile. Current spending is more informative than asking whether they would pay a hypothetical amount. To explore packages, present attribute combinations through conjoint analysis and follow up on why a package was chosen, what was unclear, what features are missing, what information would create confidence, and what would hold them back.

Interview existing customers about the journey to paying

Prioritise actively engaged customers with high lifetime value who are not so new that they have forgotten their first experience. A useful starting point is around six months after onboarding, adjusted to the normal customer lifespan. Reconstruct the journey: what prompted trial, how long the problem had existed, how the problem was recognised, which alternatives were tried, what was liked or disliked, why they switched, and their first impression. This explores jobs to be done — the change the customer wants, not simply the features supplied. Then ask when they decided to pay, or what made them stay after a trial, which factors influenced the decision, which attributes provide most value, what would increase perceived value, and what they would use instead if the product disappeared.

Interview churned customers without assuming price is the whole story

A claim that price caused churn does not automatically mean the price is too high. It may indicate the wrong audience, a gap between expectations and delivery, or weak communication of valuable features. Start with what led the person to use the app, then ask what led them to stop. Compare their original problem with the problem faced by high-spending customers and check whether they reached the most valuable parts of the product. If price still appears central, ask whether something expected was missing, when value felt insufficient for the price, and how that realisation developed. Stay neutral, do not argue for a return, and ask what would have made the price worthwhile. Finally, ask whether they switched to another solution, what led them there, what it costs, and how the experience compares. For recruitment, keep sessions to at most 30 minutes, offer a reward other than a subscription, use a personal plain-text message, follow up, and make booking easy with a calendar tool and ample slots.

Turn interview themes into behavioural experiments

Use interviews to form hypotheses, then test behaviour. A practical sequence is: collect evidence from each customer group, identify the value or expectation gap, translate it into a specific experiment, and test it through a lower-risk surface such as email or advertising before changing the app itself. Checklist: separate Android and iOS findings; replace future hypotheticals with past behaviour; ask about current alternatives and spending; probe package choices and blockers; compare light and heavy users or different tiers; and verify interview themes with behavioural data. This keeps pricing work focused on strong hypotheses rather than unsupported assumptions.

What to learn from each customer group
Customer groupBest starting focusPricing signal to seek
Potential customersCurrent solutions, spending and package trade-offsWhat they already pay for and what makes it worthwhile
Existing customersOriginal problem, alternatives, switch trigger and purchase decisionAttributes and outcomes that justify paying
Churned customersReason for starting, reason for stopping and replacement solutionExpectation, value or audience mismatch behind a price objection

Use as interview planning guidance; validate themes with behavioural data before changing prices.

Frequently asked questions

What additional information would you need to feel confident about purchasing it?

It is a fine line because you do not want to sound too salesy, but you want to understand if they are actually willing to pay that price. You will get a better answer than a simple affirmative.

When did you feel that [app name] was not providing enough value for the price?

This helps you better understand what is essentially the opposite of the aha moment, which we will call the oh no moment. Sometimes this is not a specific moment but several individual moments.