Product Packaging & Pricing Tiers

Three packaging archetypes dominate SaaS: (1) Feature-based tiers — each plan tier unlocks progressively more features (Starter → Growth → Enterprise). Advantages: simple to understand for buyers; disadvantages: risk of "value stuffing" that obscures the actual differentiating features. (2) Usage-based packaging — price scales with consumption (API calls, seats, storage, events). Aligns commercial model with value delivery but requires metering infrastructure and creates revenue unpredictability. (3) User-based (per seat) — price scales with the number of users. Simple and predictable but may limit adoption by incentivizing customers to keep seat counts low. Many SaaS companies use a hybrid: base seat-priced plans with usage-based add-ons for variable consumption dimensions.

Packaging changes are pricing decisions that have significant revenue implications — they require rigorous research before implementation. Product Ops facilitates packaging research through a combination of: conjoint analysis (survey-based research that reveals customer preferences across feature/price combinations), Van Westendorp Price Sensitivity Meter (identifies acceptable price ranges), and customer interviews (qualitative exploration of which features customers consider essential vs. differentiating vs. unnecessary). A/B testing packaging and pricing in acquisition flows provides behavioral validation beyond stated preferences. All research findings are documented in a Pricing Research Archive maintained by Product Ops, informing packaging decisions for years after the original study.

Packaging complexity directly increases support volume. When customers are confused about which features are in their plan, they contact support to ask. An ideal packaging structure is self-explanatory: customers should be able to understand what they get at a glance. Product Ops should audit support ticket themes for packaging confusion — a high volume of "is Feature X included in my plan?" tickets signals packaging clarity issues. Documentation should include a clear feature comparison table. Automated in-app messaging (showing an upgrade upsell when a user clicks a locked feature) reduces support contact by explaining the restriction in context, with a clear upgrade path, rather than leaving users frustrated and confused.