Pricing wiki · Category

Product, Packaging & Bundling

Strategic product packaging, bundling, and offer design that maximizes value capture while maintaining customer clarity and choice.

Published concepts
5
Updated
Jul 2026

Editorial guide

Use this category

These notes preserve the category’s recommended sequence, decision rules, and practical applications.

Which page do you need right now?

Your symptomLikely causeStart here
"Every new feature goes into the same plan and nobody upgrades"Kitchen-sink packagingPackaging architecture
"We argue feature-by-feature about what goes in which tier"No classification systemLeader/Filler/Killer Features
">50% of signups pick the cheapest plan"Entry tier too rich, weak fencesGood–Better–Best tiers
"High-value niche features are bloating our core plans"Missing modular layerAdd-ons & modular packaging
"We have multiple products and buyers cherry-pick one"Uncaptured cross-product surplusBundling

Insights

Blueprint Insight

Start with Packaging architecture to define your offer structure (plans, modules, limits, upgrade paths) independent of the price numbers—because packaging precedes pricing. A good architecture reduces decision friction, prevents feature giveaways, and sets you up for clean upgrades as customers hit natural "success triggers."

Tier design Insight

Next, use Leader/Filler/Killer Features to decide what belongs where. Leaders are the few capabilities that actually drive someone to buy; fillers are expected "completeness" items; killers are the clutter or cost drivers that lower willingness to pay for some segments and should be removed—or sold separately. With those classifications in hand, design Good–Better–Best tiers so each plan targets a real segment: make "Better" the obvious default, fence premium value drivers so Good doesn't cannibalize upgrades, and make the Best tier meaningfully different (not just a longer checklist).

Expansion Insight

Once your core ladder is clear, expand your revenue capture without bloating the base plans. Use add‑ons & modular packaging when value is high but not universal: add‑ons work best as "power/scale" top‑ups, while modules work best when they map to distinct roles or use cases that can't fit neatly into one tier ladder. Use bundling when you have multiple products (or distinct offers) and customers value the combination: mixed bundling is often a safer default because it preserves choice while encouraging larger purchases—bundle for workflow value (and sometimes charge a premium), not just for volume discounts.

How to use this

The Packaging Workflow

Package first, price second. A quarterly packaging check-in to keep tiers clean, upgrades obvious, and new features monetized.

Steps

  • 01 | Define Architecture | Plans & Upgrade Paths
  • 02 | Classify Features | Leader/Filler/Killer
  • 03 | Set Tiers | Good–Better–Best
  • 04 | Expand | Add-ons & Bundling

Continue through the library

Related categories

Move to the adjacent pricing decision without losing context.

Open license

Reuse with attribution

This content is available for reuse. When referencing or republishing it, please credit Dr. Sarah Zou and link back to the original source.

Licensed under Creative Commons Attribution 4.0 International. You may share and adapt the material with appropriate credit.