#157 — The art and science of bundle pricing

Start by mapping every product or feature into 'atoms' and tagging which customers are SuperFans (heavy users) vs CasualFans (light users) of each. Bundling works best when each bundle can be justified by being a SuperFan of just one component and merely a CasualFan of the rest. This approach follows Shishir Mehrotra’s 'SuperFan' framework, which shows that bundles with minimal SuperFan overlap and maximum CasualFan overlap reach far more customers at attractive price points.

Microsoft’s strategy of bundling Teams into Microsoft 365 is a classic example: Teams rode on the existing distribution of Office, email, and identity, making it much harder for Slack to compete on a standalone basis. The bundle gave buyers a default collaboration stack at no obvious incremental cost, even if Teams was not initially the best-of-breed point solution. This illustrates how bundling can use an existing product’s footprint to quickly scale a new product inside enterprises.

Treat each product or service as something a segment is either a SuperFan of (they would buy it alone) or a CasualFan of (they only want it if it’s effectively 'free' in a bundle). The best bundles are structured so a customer only needs to be a SuperFan of one component to feel they are 'paying for that and getting everything else for free.' Shishir’s math shows that requiring customers to be SuperFans of multiple components shrinks your effective market and makes the bundle feel like a bad deal.

A practical rule is that for any given segment, the bundle price should be less than or equal to what a SuperFan would rationally pay for their single favorite product alone. When you anchor the bundle around that SuperFan price and then add other components that many users are CasualFans of, the perceived value becomes 'I’m paying for the thing I truly love, and everything else is a bonus.' This aligns with the SuperFan test described in the 'Four Myths of Bundling' framework and later expanded in SaaS pricing breakdowns.

Usage-based allocation often feels intuitive but is usually wrong for bundles, because light-use components can be the reason customers do not churn. The better approach is Marginal Churn Contribution (MCC): measure how much each product reduces the probability that a customer cancels the overall bundle. Shishir’s second myth shows that when revenue is distributed by MCC, providers that drive retention—even with low usage—get rewarded fairly, which encourages partners to participate in bundles.

Yes—bundling is often even more powerful in service-heavy B2B categories because buyers crave simplicity and fewer vendors. For example, facilities providers increasingly bundle cleaning, maintenance, security, and basic IT setup into a single 'workplace operations' contract rather than forcing companies to manage four separate vendors. In professional services, agencies frequently bundle strategy, execution, and analytics into one retainer, lowering friction for clients and smoothing revenue for the firm.

The primary risks are overcomplicating your packaging with too many bundles, underpricing in a way that strains margins, and creating a bundle that only appeals to a tiny set of multi-product SuperFans. The 'Four Myths' framework highlights how founders can accidentally design bundles that require customers to love two or three products just to break even, effectively shrinking the addressable audience. Early-stage teams should keep the menu to a small number of bundles, test willingness to pay, and ensure each bundle passes the 'SuperFan of one thing' test.

Unbundling tends to work when a specific component of your suite has significantly higher product-market fit, usage, or willingness to pay than the rest, and buyers are being blocked by the requirement to purchase the whole package. In B2B SaaS, many companies have successfully spun out high-demand modules—like analytics, automation, or API access—into separate add-ons or products to capture value from customers who do not need the full bundle. The rebundling cycle in SaaS shows that markets often move between specialty point solutions and integrated bundles as segments mature.

Telecom and cloud providers offer strong examples: many bundle connectivity, collaboration tools, security, and support into one contract, making it difficult for a competitor offering just one of those components to displace them. Similarly, platforms like Amazon combine infrastructure, marketplace distribution, advertising, and logistics into a bundle of capabilities that makes switching extremely costly for merchants who rely on several of those services at once. These ecosystems demonstrate how bundling creates multi-dimensional lock-in that pure point solutions struggle to match.

Start with a clearly defined test group—such as a segment in one geography, industry, or size band—and offer them the new bundles alongside your existing packaging. Track conversion, ARPU, attach rate, and churn versus a control group, and pay close attention to whether customers can explain the bundle back to you in their own words. Shishir’s discussions on bundling emphasize iterative experimentation: use small, controlled tests to calibrate price points and composition rather than betting the entire business on a single, untested bundle.

Product bundling is a strategy where multiple products or services are packaged and sold together as a single offer, often at a perceived discount or with added convenience. For founders, bundling matters because it can increase average revenue per customer, improve retention by making the offer harder to switch away from, and unlock value from CasualFans who would never buy each component separately. When done well, bundling produces value for both providers and customers by expanding access and simplifying decisions.

Start by analyzing buying patterns to see which products are frequently purchased together or used in the same workflow, then group those into logical, outcome-based bundles. In B2B, this often looks like industry- or job-based bundles, such as an 'office operations' package that includes supplies, maintenance coordination, and basic IT support. Research shows that bundles perform best when they solve a coherent problem for a specific segment, rather than combining unrelated items just to raise ticket size.

Common bundling strategies include pure bundling (items only sold as a bundle), mixed bundling (sold individually or as a bundle), cross-sell bundles (complementary products from different categories), tiered bundles, and subscription bundles. B2B companies frequently use mixed and tiered bundles to serve different segments without overwhelming buyers, such as offering 'Basic', 'Standard', and 'Premium' packages with increasing scope. Choosing the right type depends on your goals—whether you want to drive adoption of a new product, clear underused capacity, or raise overall ARPU.

A practical approach is to anchor bundle pricing around the value of the hero product—the one your SuperFans care most about—then ensure the total bundle price feels like a clear win compared to buying that single item plus key alternatives. Pricing research in B2B bundling recommends testing multiple price points, modeling how different bundles affect willingness to pay, and validating that the bundle passes the 'no-brainer' test for your target segment. Tools like Van Westendorp analysis and conjoint studies are often used to quantify whether a bundle is undervalued or overpriced.

Instead of allocating revenue purely by usage, which often under-rewards components that drive retention, use Marginal Churn Contribution (MCC) as your guiding metric. MCC asks how many customers would cancel the entire bundle if a specific component were removed, and allocates revenue proportionally to that retention impact. Shishir Mehrotra’s bundling framework highlights MCC as a fairer, more strategic way to split bundle economics—especially when multiple internal teams or external partners are involved.

In telecom and cloud, providers bundle connectivity, collaboration tools, security, and support into one contract, making it difficult for a point solution to displace them without replacing the entire stack. In B2B commerce, platforms that combine storefront, payments, inventory, and logistics into a single subscription create a bundle that locks in merchants across multiple jobs-to-be-done, not just one feature. These examples show how bundling can turn a product into a multi-dimensional platform that competitors struggle to unseat.

Bundling can backfire when items are unrelated, when the package becomes too complex, or when high-end, highly personalized offerings are forced into a generic bundle. In these cases, buyers feel manipulated or overwhelmed, and the perceived value of premium items can actually drop. Studies on bundling mistakes emphasize that every bundle should feel natural and relevant, with a clear, simple story about why these components belong together.

Well-designed bundles reduce decision fatigue by simplifying choices and presenting a clear 'best fit' option for each segment, which tends to lift conversion rates. In ecommerce and B2B portals, bundles that are surfaced contextually—such as 'frequently bought together' or industry-themed packages—help customers discover complementary products and increase average order value. Dedicated landing pages for bundles, optimized around specific use cases and keywords, also create targeted entry points that convert better than generic product pages.

Create dedicated bundle pages that target high-intent, long-tail keywords like 'B2B product bundle for [industry]', '[use case] package', or '[problem] solution bundle'. Optimize each page with clear descriptions, benefit-focused headings, FAQs, and internal links from individual product pages so search engines understand the bundle’s relevance and structure. Including schema markup for FAQs and product offers, plus acquiring backlinks to your best-performing bundle pages, can significantly improve visibility in search results.

Start with small, controlled experiments: introduce new bundles to a specific segment, region, or channel while keeping your existing packaging live as a control. Track conversion rate, ARPU, attach rate, and churn to see whether the bundle improves customer economics and whether customers can clearly articulate its value. Experts like Shishir Mehrotra recommend treating bundling as an ongoing, iterative motion—continuously refining composition, pricing, and messaging based on measured impact and customer feedback.