Latest / The Pricing Marketing Podcast with Fexingo: Price Anchoring, Bundling, and Conversion Pricing / How Bundle Architecture Drives Revenue
Transcript
- Lucas: Let’s talk about the architecture of choice. Most people think of bundling as just throwing two products together and calling it a deal. But if you look at the balance sheets of the biggest software companies today, bundling is actually a structural engineering problem. They aren't just discounting; they are designing friction. Luna: Friction? I would have guessed they were trying to remove friction to make buying easier. Lucas: They want to remove financial friction but add structural friction elsewhere. The goal is lock-in. When you buy one service, you don’t leave because the other five services you rely on are bundled into that same contract. It’s not about the price point anymore. It’s about the exit cost. Luna: So the bundle isn't a gift. It's a cage. Lucas: Exactly. And before we get too deep into the corporate espionage side of things, I want to pause for a second. If these marketing conversations have sparked something you've actually used in your own work or life, consider supporting the show. Listener support is what keeps this network ad-free and allows us to dig into these specifics without rushing. You can find us at buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Luna: Yeah, and honestly, keeping these episodes free makes it easier for me to keep doing the research so we can actually explain the mechanisms instead of just reading press releases. Lucas: Right. So let’s look at a concrete example. Think about the enterprise software market around October twenty twenty six. We see a lot of providers offering a base analytics package, a CRM module, and a customer support tool. Sold separately, each might cost thirty thousand dollars a year. Sold as a suite, the total comes to seventy-five thousand. On paper, that’s a twenty-five percent discount. Luna: That sounds like a genuine saving. Why is that problematic? Lucas: Because you’re likely only using half of those features deeply. You might love the analytics, but the CRM is just okay, and you rarely touch the support tool. By buying the bundle, you’ve paid full price for the features you barely use, just to secure the discount on the ones you do. The net cost per useful feature actually goes up. Luna: So you’re subsidizing the dead weight with your enthusiasm for the core product. Lucas: Precisely. And the vendor knows this. They know that once you’ve migrated your data into their ecosystem, switching costs become astronomical. It’s not just about the money. It’s about the retraining, the integration headaches, the risk of downtime. That structural friction is worth more to them than the twenty-five percent discount ever was. Luna: It feels manipulative, but also incredibly efficient for their retention metrics. Lucas: Efficiency is the right word. Let’s look at the numbers. In many cases, bundled customers have a renewal rate that is fifteen to twenty percentage points higher than single-product subscribers. That gap isn't random. It’s engineered by the complexity of unbundling. Luna: But doesn’t that hurt innovation? If they can just lock people in with bundles, why build better individual tools? Lucas: That’s the paradox. They still innovate, but they innovate within the bundle. They add new modules to the suite rather than improving the standalone core. It’s incremental expansion. It keeps the average revenue per user growing without requiring a massive leap in product quality. It’s safer for their stock price. Luna: So the consumer gets a slightly larger pie, but the slices are smaller and harder to eat alone. Lucas: I like that image. Smaller slices. But here’s where it gets interesting. Some companies are now using asymmetric bundling. They bundle a high-value item with a low-value item that you wouldn’t have bought anyway. This is common in telecommunications. You get unlimited data, but you’re stuck with a streaming service you never watch. Luna: Because the streaming service has zero marginal cost for them, right? Lucas: Zero marginal cost. They already own the content or license it cheaply. Adding it to the bundle increases the perceived value of your phone plan without costing them anything extra. It’s pure margin expansion disguised as customer benefit. Luna: It’s basically clearing inventory with psychology. Lucas: Exactly. And it works because humans are bad at valuing things we don’t use. We anchor on the headline number: unlimited everything. We don’t calculate the opportunity cost of paying for features we ignore. We just feel good about the deal. Luna: So the key is recognizing when the bundle includes things I don’t need. Lucas: The key is asking what happens if I cancel the whole thing. Would I miss the core product enough to pay its standalone price? If the answer is no, then the bundle is just a trap. If the answer is yes, then maybe the discount is real. But most of the time, it’s neither. It’s just confusion. Luna: Confusion is expensive. Especially in B2B contracts where the buyer isn’t the end user. Lucas: Right. In B2B, the person signing the check often doesn’t use the software. The IT manager does. So the bundle is designed to please the IT manager with technical breadth while pleasing the CFO with the headline discount. It’s a dual-appeal mechanism. Luna: So it’s less about the product and more about internal politics. Lucas: Almost entirely. The best bundle is one that solves a political problem for the buyer, not just a functional problem. If buying the suite makes you look strategic to your boss, you’ll buy it even if it’s inefficient. That’s the hidden value. Luna: Strategic appearance over operational efficiency. Lucas: Yes. And companies know this. They sell the narrative of integration. Everything connects. Data flows seamlessly. It sounds wonderful until you realize you’re connecting to a system you didn’t choose. Integration is great if you control the source. It’s a nightmare if you’re forced into it. Luna: So autonomy is the casualty. Lucas: Autonomy is always the casualty in a bundle. You trade flexibility for convenience. The question is whether the convenience is worth the loss of optionality. In my experience, optionality is usually more valuable than it appears until you’re locked out. Luna: Have you seen any counter-trends? Are people pushing back against bundles? Lucas: There is a quiet movement toward modular pricing. Some newer entrants in the SaaS space are refusing to bundle. They say: take what you need. No extras. It’s a bold move because it lowers the initial contract size. But it builds trust. And trust is becoming a premium currency. Luna: Trust as a differentiator. That’s rare. Lucas: It is. And it works because buyers are tired of negotiating every line item. They want transparency. If a company says, here is the price for exactly what you asked for, it cuts through the noise. It’s simpler. Simpler wins in the long run. Luna: But simpler usually means less revenue for the seller initially. Lucas: Short term, yes. Long term, it reduces churn. Bundles churn when users realize they’re paying for junk. Modular pricing churns only when the core need disappears. That’s a much healthier business model. Luna: Healthier for the business, and hopefully for the buyer too. Lucas: Definitely. So as you look at your own subscriptions this month, ask yourself: am I being sold a bundle, or am I being sold a solution? Because most of the time, it’s the former. And knowing the difference is the only leverage you have. Luna: Or simply realizing that the deal wasn’t a deal at all. Lucas: Exactly. The next time you see a bundle, don’t look at the discount. Look at the parts. See which ones you’d never buy alone. That’s where the truth lives.