Latest / The Pricing Marketing Podcast with Fexingo: Price Anchoring, Bundling, and Conversion Pricing / How Unit Economics Breaks Your Bundle Strategy
Transcript
- Lucas: So last week I finally caved and signed up for a video editing tool, and I went with the bundle — the whole creative suite — because the per-product prices looked ridiculous on their own. Luna: Right, that classic move: the standalone price makes the bundle feel like a steal. Lucas: Exactly. But then I started digging into the numbers behind that bundle, and I realized something: some of those individual products are almost certainly losing money, or at best breaking even. And the bundle as a whole is only profitable because of the high-margin ones. Luna: So you're saying the bundle works for me as a customer, but for the company, it might be masking a weak product? Lucas: That's exactly the angle I want to explore today. Because bundling is one of the most powerful pricing tools we have, but it can also hide terrible unit economics. And when those hidden losses get big enough, the whole strategy can unravel. Luna: Before we get deep into that, I want to mention something that's come up a few times from listeners. People have said they enjoy these pricing deep dives and find them useful in their own work. If that sounds like you, and you want to help keep these conversations ad-free, there's a simple way to support the show. You can buy me a coffee dot com slash fexingo. No pressure at all — just a low-key way to say this content matters to you. Lucas: Yeah, and it genuinely helps. We don't run ads, so listener support is what keeps the lights on. Okay, back to bundles and unit economics. Let me give you a concrete example from a company everyone knows: Adobe. Luna: Adobe? I thought their whole model is the Creative Cloud bundle — Photoshop, Illustrator, Premiere, all together. Lucas: It is — or it was. But in late 2025, Adobe quietly started offering more granular single-app subscriptions and even introduced a stripped-down 'Essentials' tier for a couple of their apps. Why? Because they realized the bundle was masking which products were actually driving profit. Luna: So they unbundled to expose the unit economics? Lucas: Partly. Think about it: Photoshop has enormous margins — it's mature, the R&D is mostly done, it's a cash cow. But a product like Adobe XD, their design tool, is still investing heavily in features to compete with Figma. Its unit cost per subscriber is much higher. In a bundle, you can't see that. The bundle just has one combined profit number. Luna: And if you're Adobe's CFO, you'd want to know which products are dragging the bundle down. Lucas: Exactly. There's a well-known framework for this: you calculate the unit margin per product — revenue minus the direct cost of serving that customer — and then see what happens to the bundle's overall margin when you mix them. Let's say product A has a 90% margin, product B has a 20% margin. If you bundle them at a discount, you might think you're doing great, but the mix actually lowers your blended margin. Luna: And that's the hidden risk of bundling: you can't optimize what you can't measure. Lucas: Right. So let's put some numbers on it. Suppose you have a high-margin product at $50 per month with a $5 cost to serve — that's 90% margin. And a low-margin product at $10 per month with an $8 cost to serve — only 20% margin. If you bundle them at $55, the customer saves $5, but your combined cost is $13, so your margin is $42, or 76%. That's still good, but lower than the 90% you had before. Luna: So the bundle is profitable, but you're leaving money on the table compared to selling the high-margin product alone. Lucas: And that's the best-case scenario. The worst case is when the low-margin product has a high fixed cost that's shared — like server infrastructure or customer support. Then the bundle can actually become unprofitable at scale, because every new subscriber costs more to serve than the bundle revenue brings in. Luna: That sounds like a recipe for a death spiral. More customers, more losses. Lucas: Exactly. And I think that's what happened with some of the all-you-can-eat SaaS bundles from a few years ago. Companies like Microsoft and Google offered huge suites — Office 365, G Suite — but some of the included apps had very low adoption and high support costs. They were essentially subsidizing features nobody used. Luna: So what's the fix? Should companies just not bundle? Lucas: No, bundling is still powerful for customer acquisition and retention. The fix is to do the unit economics analysis before you set the bundle price. And to track it continuously. You need to know the margin per user, per product, per bundle — and you need to be willing to unbundle or reprice when the math stops working. Luna: I remember reading that Spotify's audiobook bundling was a mess for exactly this reason. They added audiobooks to premium subscriptions, but the per-audiobook cost was much higher than per-song streaming cost, and it eroded margins. Lucas: Great example. Spotify's music streaming has a marginal cost that's tiny — they pay labels a percentage of revenue. But audiobooks have a per-unit cost that's much higher, especially for new releases. When they bundled audiobooks into the $10.99 premium plan, they essentially gave away a high-cost service for free. It took them about a year to realize they needed a separate audiobook tier. Luna: So the lesson is: if you're going to bundle, make sure the unit economics of each component are healthy, or at least that the bundle as a whole still meets your margin targets. Lucas: Exactly. And there's a second lesson: sometimes the best bundle decision is not to bundle at all. I've seen startups waste months trying to create the perfect bundle when they should have been fixing the unit economics of their weakest product first. Luna: That's a good point. If product B is a money loser, no amount of bundling with product A will fix that — it just hides it. Lucas: Right. And the customer eventually figures it out. If the bundle feels too good to be true, they might suspect you're cutting corners somewhere. Or they'll churn because the low-margin product has poor support or bugs, and that taints their perception of the whole bundle. Luna: So transparency in pricing can actually be a competitive advantage. If you show customers the standalone prices and let them build their own bundle, you signal confidence in each product's value. Lucas: And that's exactly what Adobe is moving toward. Their new single-app subscriptions are more expensive per app than the bundle, but they're still profitable. And customers who only need one tool don't feel like they're overpaying for stuff they don't use. Luna: I wonder if we'll see more of that in the enterprise space. Like, Microsoft already offers some modularity in Office 365 — you can choose plans with or without Teams, for example. Lucas: Yeah, that's another good data point. Microsoft realized that Teams had high adoption but also high support costs, so unbundling it into the enterprise plans allowed them to price it appropriately. The key is that the unit economics drove the decision, not the marketing team's desire for a simple one-price pitch. Luna: So for our listeners who are building pricing strategies, what's the one thing they should take away? Lucas: Run the math before you bundle. Calculate the margin per product, per user, per bundle. And if the numbers show that one product is dragging the whole thing down, either fix that product's unit cost or don't include it in the bundle. A great bundle is built on strong individual units, not hidden subsidies. Luna: And the corollary: a bundle that looks amazing to customers might be a ticking time bomb for your bottom line. Lucas: Exactly. So next time you see a bundle that seems too good to be true, ask yourself: what's the unit economics story behind it? Chances are, someone's math is about to break.