Foundations
Customer Groups and editions
The frame
A Customer Group is a cluster of customers who get value from your product the same way, whatever their size or industry, and who therefore buy it the same way. That is the unit packaging is built for. Personas describe who the buyer is; size and vertical describe the org chart; neither predicts how anyone uses the product. Packaging, the second of the three decisions after licensing and before pricing, decides what goes together for whom. Editions are its most common expression, and only one of several: modular add-ons a customer assembles, a platform with apps on top, an all-in-one, or bundles. The right expression comes from how each Customer Group extracts value. A good-better-best ladder built on features alone is a ladder with no groups under it, and a sales team quoting around the grid is the visible sign.
The edition grid you inherited probably records that mistake. Every custom configuration and discount exception was a deal desk working around editions that matched no real group. Price points cannot be fixed until the editions are coherent, and editions cannot be fixed until you know which groups they serve. Under a mandate to grow without adding staff, this is the decision every later price move depends on.
Customer Groups versus buyer personas: packaging built on personas sprawls, and grouping by shared value lets the editions consolidate. Packaging by workflow: industry is a label on the buyer, and the work customers do is where Customer Groups become visible. Software packaging: editions are one archetype among several, and the edition count is derived from how the groups extract value. Packaging’s job is upsell, a richer edition; the value metric’s job is expansion, more of the same. Good-better-best pricing: the case for the stacked ladder rests on how buyers choose from a menu; the evidence on what belongs on the menu points back to the Customer Groups.
Which clusters of customers get value from your product in different ways, and does each edition you sell answer to one of them?
Three things to say in the room this week
- Before we argue about which features go in which edition, let's name the customers who value this product differently.
- Our packages should follow how customers use and value the product; company size and industry say little about that.
- If every deal closes on a configuration we never published, the editions were drawn around the wrong customers.
Core reading
Go deeper: the heavy depth
Read the core in this order.
- Customer Groups vs buyer personas: the unit itself, why a persona cannot be the packaging unit, and the signature a packaging mess leaves when it was.
- Packaging by workflow: the axis on which groups become visible, why a vertical package half-fits everybody, and when industry is the right axis after all.
- Software packaging: packaging’s place as the second of the three decisions, the archetypes beyond editions, and why designing a boundary and enforcing it are different jobs.
- Good-better-best pricing: what the prevalence and psychology case for the stacked ladder proves, and what the construction evidence asks of your Customer Groups.
Then the shelf.
- Three more B2B SaaS pricing errors: the early statement that a pricing tier is a purchase amount and says nothing about who the customer is.
- Differential pricing in B2B software: different prices are legitimate when they trace to Customer Groups, editions and the value metric, and punished when they are accidental.
- The software packaging decision framework: boundaries between customers come before boundaries between features; SPP’s own method for reading how each group values and uses capabilities.
- Collapsing a legacy SKU catalog: a sprawling pricebook is packaging decided one negotiation at a time; a collapse re-derives it from the groups.
- Freemium SaaS: the free edition is a packaging boundary that touches all three decisions at once.
Glossary terms to open: Customer Groups, the unit; packaging model, the decision; and tiered pricing, a price break by volume, which is why this path says editions when it means packages.
The research hubs behind the module are peer-reviewed work on bundling and versioning, on price differences across customer groups and self-selection, and on how pricing pages and edition structures are presented. They are the provenance of the versioning claim the core pieces lean on.
The shelf
- Three more B2B SaaS Pricing Errors - and how to avoid them
- Is It Fair to Charge Different Customers Different Prices for B2B Software?
- Software Packaging Framework: How to Decide Edition Boundaries
- How Many SKUs Should a Software Company Have?
- Freemium SaaS: When It Works, When It Doesn't, and What Most Companies Get Wrong
Terms
Pages read from your company
Start Here
Save my place
Your checkmarks follow your email, on any device. We send a link; no password.
Check your inbox
Open the link on any device; this page will sign itself in.
If you open the link on another device, type this code there:
Never type a code that someone sent you. Only use the code shown on your own other screen.
The link was opened on another device. Type the code above there to sign in here too.
