💰Pricing & Packaging — Masterclass
Pricing is product. The single highest-impact decision most companies make and re-make wrong.
A 10% pricing change typically moves revenue 10-20%. Most teams underprice for years. PMs who own pricing well unlock outsized value with no engineering cost.
Pricing has four components: structure (per-seat, usage, tier), positioning (premium vs commodity), specific numbers (the $99 question), and packaging (what's bundled). Get the structure right first; numbers and packaging tune around it. Re-evaluate annually.
The four pricing decisions
1. Structure. How the customer pays. Per-seat, usage-based, flat tier, hybrid. Structure should fit the value metric — what the customer cares about scaling.
2. Positioning. Premium or commodity? Set by your brand, target segment, and competitive context. Both can win; the in-between often loses.
3. Numbers. The actual prices. Run willingness-to-pay research (Van Westendorp), competitive benchmarking, internal testing.
4. Packaging. What's in which tier. Good/Better/Best is the default; the magic is the contents of each tier.
Picking the right structure
- Per-seat: when each user creates value (Slack, Notion).
- Usage-based: when value scales with consumption (Twilio, Stripe).
- Flat tier: when value is binary or hard to meter (Netflix).
- Hybrid (per-seat + usage): mature SaaS where both matter (Snowflake, Datadog).
The wrong structure caps your ceiling. Most B2B SaaS uses per-seat by default; in 2026, usage-based is gaining as AI products produce huge usage variance.
Tier design
Three tiers (Good/Better/Best) is the default because it works. The middle tier should be the one you want most customers on. The high tier is the anchor that makes the middle look reasonable. The low tier is the upsell vehicle.
What to put in each tier:
- Low: features that hook users and drive trial. Restrict on usage, not feature.
- Middle: the core value prop. The 'this is the real product' tier.
- High: premium features (SSO, advanced security, dedicated support), volume discounts, custom integrations.
Common pricing mistakes
- Underpricing. The most common. Almost every B2B SaaS could raise prices 20-30% without losing customers — and often gain perceived value.
- Free tier too generous. Power users get all the value for free; conversion to paid is low.
- Hidden gotchas. Annual contracts that auto-renew, usage charges customers don't see coming. Damages trust.
- Same price for every segment. SMB and Enterprise have different willingness-to-pay; structure should differentiate.
Pricing changes
Annual re-evaluation. Test before announcing. Communicate to existing customers transparently. Grandfather active customers for a period (6-12 months).
Most pricing changes that go wrong are communication failures, not pricing failures.
Real-world examples
Notion's free tier was deliberately generous — full feature set for individuals, just limited team features. The viral effect (individuals using Notion → bringing it to work → upgrading the team) was the engine. Once at scale, they tightened the free tier strategically.
Snowflake's consumption-based pricing aligned vendor and customer incentives — Snowflake wins when customers query more. The structure was a competitive advantage against per-seat alternatives and unlocked massive expansion revenue.
Go deeper — recommended reading
Interview questions (1)
Q1Your company has flat per-seat pricing. Should you move to usage-based? How would you decide?strategysenior▼
Three-question diagnostic:
- Does value scale with usage? If a customer using your product 10x more gets 10x the value, usage-based aligns price to value. If usage doesn't track value (e.g., a seat-of-truth feature where one seat per company is enough), per-seat is fine.
- What's the variance across customers? If your top 10% of customers use 10-100x more than the median, per-seat leaves money on the table — they're paying the same as the median. Usage-based captures more.
- Will customers resist? Usage-based pricing creates anxiety ('what will my bill be next month?'). For finance teams, this is a real friction point. Often hybrid (base subscription + usage above threshold) resolves it.
If yes/yes/manageable, usage-based is worth modeling. Roll out: new customers first, grandfathering existing customers for 12 months. Communicate transparently. Expect 20-40% revenue uplift if the structure fits.