Direct answer
The pricing model field accepts four values — Free, Paid, Freemium, and Subscription — and it changes the angle generated copy takes on value and commitment, not just whether a price appears in the text. A freemium app needs copy that earns the download without overselling what's behind the paywall, while a subscription app needs copy that justifies ongoing value rather than a one-time purchase decision. Picking the wrong model produces copy that sets the wrong expectation before a user ever opens the app.
What each model shifts in tone
| Pricing model | What the copy tends to emphasize |
|---|---|
| Free | Immediate value, no friction to try |
| Paid | Confidence in the one-time value proposition, less hedging |
| Freemium | What's free vs. what's gated, without overselling the gated part |
| Subscription | Ongoing value and ongoing use, not a single feature moment |
Freemium is the easiest one to get wrong
Freemium copy that oversells the paid tier sets up disappointed free users; freemium copy that undersells it gives users no reason to upgrade. The pricing model field alone won't calibrate that balance — the project's description and feature framing still need to make clear what's actually included at the free tier the copy is describing.
Subscription copy needs a different kind of proof
A one-time purchase only needs to justify itself once. A subscription needs to justify itself continuously, so copy tends to lean on ongoing use cases and recurring value rather than a single killer feature — a subtle but consistent difference from paid or free copy that the pricing model field helps the generation account for.
Update this field when pricing changes
If an app's actual pricing model changes — moving from paid to freemium, for instance — the project's pricing model field should be updated before the next generation, not left on the old value. Stale pricing model input produces copy with the wrong value framing even if every other field is accurate.
Common mistakes
- Leaving the pricing model on its default value after the app's actual pricing changed.
- Selecting Freemium without updating the description to clarify what's actually free, leaving the copy to guess.
- Treating Paid and Subscription as interchangeable when the value framing they need is different.
Checklist
- Confirm the pricing model field matches the app's current, real pricing structure.
- For Freemium, make sure the description clarifies what's free vs. gated.
- For Subscription, check that generated copy leans on ongoing value rather than a single-use pitch.
Operating rule
Pricing model is not a label for the store listing page — it's an input that shapes the value argument the copy makes, so it needs to match reality before generation, not after.