iOS subscription tier structure: how to design good-better-best plans that increase LTV

A practical guide to structuring iOS subscription tiers — how many tiers to offer, which features go where, how to set price gaps, and the allocation mistakes that silently hurt lifetime value.

Most iOS apps launch with a single subscription price. It's the path of least resistance: one tier, one call-to-action, one question for the user to answer. But once you have meaningful subscriber counts, single-tier pricing almost always leaves money on the table — both at the top (high-value users who would pay more for more) and at the bottom (price-sensitive users who churn rather than convert).

Designing a good-better-best tier structure forces you to think clearly about your product's value drivers, your users' willingness to pay, and how much friction your onboarding can sustain. This post walks through the decisions that actually move the needle: how many tiers to offer, which features belong in each, how to set the price gaps between them, and the allocation mistakes that quietly hurt lifetime value for months before they show up in your data.

Why three tiers outperform one (and why four is usually too many)

The fundamental purpose of multiple pricing tiers is to match your price to each segment's willingness to pay. A market of potential subscribers is never homogeneous — some users will pay $2.99/month without hesitation, others won't flinch at $29.99, and the majority sit somewhere in between. A single price necessarily under-charges the high-value segment and loses the price-sensitive segment entirely.

Analysis in RevenueCat's subscription benchmark reports has consistently found a directional relationship between multiple subscription tiers and higher average revenue per user (ARPU) — primarily because apps with tiered offerings can capture incremental revenue from subscribers who self-select into premium plans. The exact lift varies significantly by app category, but the pattern holds broadly across utilities, productivity tools, and health apps.

The specific case for three tiers over two is the decoy effect: a middle tier makes the relative value of the adjacent options clearer, and it anchors perception. When a user sees $4.99 / $12.99 / $19.99, the step from $4.99 to $12.99 feels significant, but $12.99 to $19.99 looks like a reasonable premium — which tends to push a share of "best" candidates toward the middle, and push "good" candidates toward "better." This dynamic is weaker with only two options because there is no middle reference point to anchor against.

Four tiers are where most teams create problems. Research on subscription paywall optimization — summarized in frameworks such as Phiture's Mobile Growth Stack — consistently finds that beyond three meaningful options, decision paralysis increases and overall conversion rates fall. A fourth tier either cannibalizes the third or confuses the comparison. If you genuinely have four distinct value levels to offer, consider presenting them as three paywall cards with a visible "compare all plans" table rather than four equal-weight choices.

Feature allocation: what belongs in each tier

Feature allocation is where tier design gets genuinely hard, because it requires deciding which parts of your product are "core" versus "premium" — a question most product teams have never needed to answer cleanly.

A useful starting heuristic: the Good tier should solve the primary use case for a majority of your users. If someone subscribes to Good and finds it does not do the thing they downloaded the app for, you have a positioning problem, not just a pricing problem. Churn from Good-tier subscribers who feel undersold is expensive and recoverable only through costly re-engagement work.

The most common allocation mistake is front-loading too many features into the Good tier. Teams do this to improve trial conversion — more features means more perceived value, which should mean more subscriptions. In practice, a Good tier that is nearly as capable as Better reduces voluntary upgrade rates substantially. Research from Phiture on subscription funnel dynamics suggests that the most reliable path to voluntary tier upgrades is the "upgrade prompt moment" — the specific instant a user actively wants to do something they cannot yet do. If your Good tier removes too many of those moments, upgrade revenue falls even as Good-tier subscriber counts rise.

The inverse mistake is gating the primary use case behind Better or Best. This lowers the Good-tier churn rate in a misleading way: users who feel the app does not work simply do not renew. They do not upgrade; they leave.

Setting price gaps between tiers

Once you have settled on feature allocation, you need to price each tier. Two principles govern this: absolute willingness to pay (how much is each tier worth to its target user?) and relative distance (are the gaps between tiers large enough to make tier selection feel meaningful?).

On absolute pricing, start from the value the tier delivers, not from what competitors charge. In a sea of $9.99/month productivity apps, a pure competitor analysis will not tell you whether $9.99 is the right price for your Good tier or your Better tier. Even rough value triangulation — time saved per week multiplied by an imputed hourly rate, or the cost of the closest manual alternative — gives you a floor to pressure-test against before you look at the competition.

On relative distance, the 2x–3x ratio between adjacent tiers is a common thumb rule that has held up across categories. If your Good tier is $4.99/month, your Better tier should be in the $9.99–$14.99 range and your Best in the $19.99–$29.99 range. Ratios below 1.5x make tiers feel like rounding errors; ratios above 4x make the upper tier feel inaccessible and frequently create a "skip the middle" dynamic where most subscribers choose either the cheapest or the most expensive option, and the middle tier ends up pulling subscribers down from Best rather than up from Good.

Annual billing adds complexity. If you offer annual plans at each tier, you now have six prices to set rather than three. A common approach is to price annual plans at 8–10 months of the monthly equivalent — giving subscribers roughly a 17–33% discount for paying up front. If your annual discount percentages vary across tiers, make sure the difference is legible to a user who compares paywall cards side by side. Inconsistent discount rates create confusion and tend to suppress annual take rates on the tiers where the deal looks relatively worse. For the detailed math on monthly-versus-annual trade-offs and what conversion rates to expect by discount depth, see the post on subscription pricing on iOS: monthly vs yearly conversion math.

Mistakes that quietly hurt LTV

Tier design errors rarely announce themselves immediately. They surface over three to six months as subtle shifts in upgrade rates, churn by cohort, or ARPU trends. Here are the patterns most teams encounter:

Naming tiers by rank rather than by audience. "Basic / Standard / Pro" tells users the hierarchy but not the benefit or who the tier is for. Names like "Personal / Team / Business" or "Starter / Growth / Pro" communicate who belongs in each tier, which makes self-selection faster and reduces the support load from users who picked the wrong plan and feel frustrated by it.

Visually emphasising the middle tier regardless of margin. Highlighting the middle option is standard paywall design advice, and it works — because most users will choose the highlighted card. That only helps if the middle tier is the one you actually want them to choose. If Better is your lowest-margin SKU and Best is where subscriber LTV is highest, the visual emphasis is working against your revenue goals. Highlight the tier that benefits your business, not the one that sits in the geometric centre of the paywall.

Adding tiers without revisiting introductory offer eligibility. Apple's introductory offer eligibility operates at the subscription-group level. If a user has already claimed a free trial on any product in your subscription group, they are ineligible for another introductory offer on a new tier you add later. Teams that add a higher tier and want to offer a trial specifically to new subscribers on that tier may need to restructure their subscription group or shift to promotional offers for re-engagement. The post on iOS subscription introductory offers covers the full eligibility rules.

Tracking subscriber count instead of tier mix over time. Once you have multiple tiers, total subscriber count is a misleading headline metric. If your subscriber base is growing but the tier mix is steadily shifting from Best toward Good, your MRR per subscriber is declining even though the top-line subscriber number looks healthy. App Store Connect's subscription summary and cohort views can surface this shift; the post on iOS subscription analytics: MRR, churn rate, and LTV explained walks through which reports to check.

Applying USD tier ratios that collapse in non-USD markets. If you use Apple's globally equivalent pricing or set prices manually by territory, check that your tier price ratios hold across your major markets. In territories where purchasing power parity diverges significantly from USD, the Good-tier price in local currency may already sit at the upper bound of what most users will consider paying — which effectively collapses your three-tier structure to a single viable option. The territories reference on AppsOps and the tools on the pricing page can help you audit this market by market before you expand.

Sources and further reading

• Apple: App Store subscriptions overview and developer best practices
• Apple Developer Documentation: StoreKit reference
• RevenueCat blog: subscription growth, benchmark data, and monetization guides
• Phiture Mobile Growth Stack: frameworks for subscription paywall and funnel optimization
• Apple Human Interface Guidelines: in-app purchase design patterns