Identify the customer task served by the bundle
A bundle should have a reason to exist from the customer’s point of view. List the tasks its components support and whether the same buyer needs them at a similar time. A shared company logo is not enough to establish a coherent package.
For an unbundling proposal, identify the component customers value independently. Ask whether it still delivers a complete outcome or requires other components that the separate price obscures.
Compare purchasing overlap and operational coupling
Research which customers already buy several components, which use only one and why. Keep observed behavior separate from an assumption that everyone wants a simpler bill. Different segments may prefer different structures.
Check delivery dependencies such as shared onboarding, support, infrastructure and integration. A separately priced feature may still incur joint costs. Record the basis used to allocate those costs rather than treating an arbitrary allocation as a fact.
Use cases to examine trade-offs
Compare cases where bundling improved convenience with cases where it created unwanted complexity. Record product maturity, customer type and switching costs. The same package structure may work differently when customers already own substitutes.
Look beyond headline revenue. Ask whether the reported result includes discounts, a migration from existing plans or changes in service scope. Without those details, label the commercial effect as uncertain.
Pilot a comprehensible offer
An illustrative software team could compare one clear bundle with its existing offer for a defined eligible group. Ask customers to explain what they receive and what they would stop buying elsewhere. Confusion is evidence worth recording.
Track purchase, component use, support burden and cancellation reasons over a suitable window. Decide in advance how existing customers will be treated and how the test can end without trapping them in an unclear arrangement.
Use this worksheet for your decision
Copy this into your notes. Leave unknowns visible instead of filling gaps with guesses.
Customer task: Components and dependencies: Segments with overlapping demand: Independent value of each component: Shared costs: Comparable cases and differences: Offer comprehension test: Use and support measures: Migration and exit plan:Download the text worksheet ↓
Find evidence in the archives
Choose a supporting case and a counterexample with a different outcome. Read their sources and check whether their conditions match yours.
Cases to practice with (read and check the underlying sources):
Bring your question to the cases
Search a company or topic in the app, read the cases and ask follow-up questions to compare approaches.