Talk to an Expert

Staged change

Packaging and editions

5 min on the light depth

The frame

Changing packaging on a live customer base is a staged change: made in steps, each leaving every existing customer on terms that still hold. The Foundations module named Customer Groups, the clusters of customers who get value from your product the same way, and the forms packaging can take. This module is about moving the boundaries when customers already live inside the old ones. The decision framework starts from boundaries between customers before boundaries between features: name the groups, read how each one values and uses the capabilities, and the editions and add-ons follow from that reading.

The change in front of you probably begins with the catalog you inherited. A SKU is the construct in the pricebook, your schedule of list prices, that records what a customer buys. A legacy catalog nobody can explain is packaging decided one negotiation at a time. Collapsing it re-derives the packaging from the Customer Groups, and the number of codes left is an output. The installed base, the customers already paying on the old editions, reads every step in its own renewal terms.

The decision framework reads each group’s capabilities on the value they extract against how often they use them. Collapsing a legacy SKU catalog argues that the count of codes is the wrong question and that the legacy base sees a collapse as a change to its own terms. Good-better-best pricing argues that the stacked ladder is one expression, and that the psychology behind it says nothing about what belongs on the menu. Across all of them: packaging’s commercial job is upsell, a richer package, and the value metric’s job is expansion, more of the same unit. Writing the metric into the edition boundaries asks a customer for both at once.

When you redraw your packaging, which boundary between your customers moves first, and which customers on the current editions will feel it?

Three things to say in the room this week

  • Our packaging change starts with where our customers differ, and the feature list comes after that.
  • The catalog we inherited is a record of deals; collapsing it means re-deriving the editions from our Customer Groups.
  • We stage this so nobody on the current editions is broken by the new ones.

Core reading

Go deeper: the heavy depth

Read the core in this order.

  • The software packaging decision framework: boundaries between customers first, the value-in-use and usage-frequency reading, and design before enforcement.
  • Collapsing a legacy SKU catalog: how codes multiply, how a collapse re-derives the catalog from the groups, what the legacy base sees.
  • Good-better-best pricing: why selection evidence says nothing about construction, the symptoms of template-first packaging, and when the ladder genuinely wins.

Then the shelf.

  • Software packaging: the pillar, and the expressions beyond editions.
  • Customer Groups vs buyer personas: the unit the framework runs for.
  • Packaging by workflow: a vertical package that half-fits is amended deal by deal until the amendments are the product.
  • Unify pricing across product lines: coherence across products aligns all three decisions.
  • Freemium SaaS: the free edition is a boundary across all three decisions.
  • Repricing freemium: when a free edition’s serving cost stops rounding to zero, recut, convert or withdraw it in sequence.
  • PLG pricing and monetization: product-led growth is a channel strategy; the three decisions go unowned behind it.

Glossary pages to open: packaging model and Customer Groups.

The research hubs hold peer-reviewed work on bundling and versioning, on nonlinear pricing and package design, and on how edition structures are presented. They are the provenance of the construction evidence.

Where this leads. The Repackaging your pricing page describes the SKU structure that has bloomed over a drifted licensing metric: repackaging treats the surface, and simplicity arrives by fixing the layer below. It names the signals of a lost licensing anchor and the choice between full rebuild and targeted evolution. The Observatory’s packaging page collects the moves where what ships together changed, and asks of each: what moved, and who decided?

The next module is Licensing: the unit and the grant.

The shelf

Terms

Where this leads

Which depth did you take?