Does Your Subscription App Need a Family Plan? Price to the Payer, Not the User

The short answer: segment before you discount

Does your subscription app need a family plan? If your headline price is too high for your core demographic but you don't want to cut it for everyone, yes, and pair it with a verified student discount. The mistake is treating a blanket price cut as the only lever. Two segment moves capture the demand your price excludes while holding the price for users who would pay it.

First, price to the payer, not the user. Second, add a verified-segment discount that reaches the willingness-to-pay tail. Feynman AI is the worked example: it charges EUR 52.50 per year, and every review that mentions price calls it too high for students, its entire user base.

Price to the payer: the family plan reframe

A family plan changes who is making the decision. The student who balks at EUR 52.50 per year for themselves is one price-sensitive person. The parent paying for tutors, revision guides, and online courses at EUR 79.99 per year for 2 to 4 learners is a different conversation, judged against a basket they already fund.

Duolingo's family plan is a significant revenue contributor for exactly this reason, and the student demographic is precisely the one where parents often control the subscription budget. Feynman AI's proposed EUR 79.99 per year family plan reframes the buyer from the student to the parent. Same product, different payer, a price that reads as reasonable against what that payer already spends.

Capture the tail: a verified student discount

The second move is a verified student discount, EUR 29.99 per year with an .edu email or a student ID. The users who would pay EUR 29.99 and would not pay EUR 52.50 are the majority of the people sitting on the free tier. Capturing them at a lower price is better than not capturing them at all.

Verification is what makes this safe. It ring-fences the discount to the segment that needs it, so you hold the EUR 52.50 headline price for everyone else while still converting the tail. A blanket price cut would hand that discount to users who were already willing to pay full price, which is money left on the table in the other direction.

The opposite diagnosis: are you actually underpriced?

Before you discount anything, check which problem you have. The mirror image of too-high-for-the-segment is genuine underpricing, and the fix there is the reverse. Fishing Points charges around $10 per year while comparable apps charge $8 per month, roughly $96 per year, and its own users express surprise at how cheap it is. That surprise is a price signal, not a compliment. The floor is set below the willingness-to-pay ceiling.

The read is simple. If reviews say the price is too high for a specific segment that is your whole base, segment it. If users are pleasantly surprised how cheap it is, raise it toward the competitor anchor. Same symptom on the surface (people talking about price), opposite prescription underneath.

Why this beats cutting the price for everyone

Higher prices tend to win on both conversion and lifetime value, so a blanket cut usually costs more than it recovers. In RevenueCat's data, higher-priced apps convert better than mid-priced ones, and one app, Jurney, tripled its revenue moving from $0.99 to $14.99. Cutting your headline price walks away from that.

Segment pricing keeps the high headline number and its LTV while still capturing the users that number excludes. It's the same instinct as showing the right number of plans: structure captures more than a raw price change does. You are not lowering the price. You are adding a payer the old price could not reach and a tier the old price shut out.

How to decide

• Read your price reviews. If a single segment that is most of your base calls it too expensive, segment. If users are surprised it's so cheap, raise the price instead
• Add a family plan when your buyer and your user can be different people (kids, students, households). Price it against the basket the payer already funds, the way Duolingo does
• Add a verified student or segment discount to capture the WTP tail. Gate it with .edu or an ID so you hold the headline price for everyone else
• Don't cut the headline price for everyone to fix a segment problem. Higher prices win on conversion and LTV; a blanket cut walks away from both
• Treat these as structure, not a discount war. You're adding a payer and a tier, not starting a race to the bottom