Latest / Sales Leadership with Fexingo: Quota Carriers, Sales Managers, and Revenue Teams / How to Structure Multi-Threat Enterprise Deals
Transcript
- Lucas: So you're in a competitive deal, and the buyer tells you, 'We're also looking at Vendor A and Vendor B.' That's standard. But what about when they say, 'We could also just do nothing, or we could build it ourselves, or we could buy Vendor C and then swap out a different piece of our stack in six months'? Luna: The multi-threat buyer. I've seen that freeze reps. They try to counter each option separately and end up muddying their own message. Lucas: Exactly. And the instinct is to play defense — discount, add features, promise the moon. But there's a better way: structure your offer so that it only makes sense compared to the full set of alternatives, not any single one. Luna: Like Amazon did with those enterprise agreements at re:Invent a few years back. They basically said, 'Take our bundle of compute, storage, and AI credits, and we'll give you a volume discount that no individual cloud provider can match.' Lucas: Right. Amazon wasn't just competing against Microsoft for compute. They were competing against the buyer's option to use a mix of three different vendors, plus an on-premise fallback. So they created a package that made the multi-threat comparison harder — because now the buyer had to compare a bundle against a fragmented alternative. Luna: And that's what we're going to unpack today. How a mid-market SaaS company can borrow that logic without having Amazon's leverage. Lucas: Let's start with a concrete example. Say you sell a CRM platform, and you also offer an analytics module. Separately, each costs $50,000 a year. Your prospect is evaluating you against a best of breed CRM competitor at $45,000 and a separate analytics tool at $40,000. Luna: So the multi-threat buyer could mix and match and get a total of $85,000 if they go with the two competitors. But if they buy both from you, it's $100,000 — you're more expensive. Lucas: Exactly. So the reflex is to cut the price of the CRM to $45,000 to match. But then you're still $5,000 over if they take the analytics separately. Better move: bundle the CRM and analytics together at $85,000 — matching the combined competitor price — but structure it as a single contract with a minimum two-year commitment. Luna: Now the buyer's multi-threat comparison shifts. They're not comparing individual line items anymore. They're comparing a unified bundle with a single vendor relationship against a patchwork of two contracts, two support teams, two renewal dates. Lucas: And that's the core insight. You're not trying to win on price per feature. You're restructuring the decision so that integration and simplicity become the deciding factors. The multi-threat buyer has to evaluate your offer as a system, not a list of parts. Luna: But what if the buyer is sophisticated and says, 'I'll just take the analytics piece from you and buy the CRM elsewhere'? Then you're back to single-threat. Lucas: That's why the bundle has to be priced aggressively enough that it's irrational to unbundle. In our example, $85,000 for both — but if they want only CRM, it's $55,000. Only analytics? $45,000. The bundle is $15,000 cheaper than buying separately from you. Luna: So the disincentive to unbundle is baked into the pricing. The buyer would have to be really committed to a different CRM to pay that premium. Lucas: Right. And you can take it further with what I call 'credits for commitment.' Say your deal size is $100,000 annually. Offer the buyer $120,000 in platform credits if they sign a three-year deal. Those credits can be used for future modules, additional users, or even training services. Luna: That's interesting because it ties the buyer's future decisions to you. The credits feel like found money, but they lock the buyer into your ecosystem. Lucas: Exactly. And it blunts the multi-threat because now the buyer has a pool of value that they can only access if they stick with you. If they go with a competitor, they forfeit the credits. So the comparison becomes: take our $100,000 deal with $20,000 of future credits, versus a competitor's $85,000 deal with no future value. Luna: The multi-threat buyer has to weigh that future value against the immediate savings. And future value is harder to compare. Lucas: Let me give you a real case. A few years ago, a mid-market HR tech company I worked with had a deal with a manufacturer. The manufacturer was looking at three different payroll providers and considering building an in-house solution. Classic multi-threat. Luna: What did they do? Lucas: They offered a bundle that included payroll, time tracking, and benefits administration — three products they sold separately — at a 20% discount for a three-year term. But the kicker was they included a 'migration credit' worth $15,000 that could be used for any of their other products in year two. Luna: So the buyer couldn't easily compare that to the alternative of building in-house or buying two separate payroll systems. Lucas: Exactly. The buyer's internal team had a spreadsheet comparing three options. But ours was the only one that included a credit that expanded the relationship over time. They won the deal, and two years later, the buyer used those credits to add an analytics module. Luna: There's also a psychological layer here. The multi-threat buyer is often trying to reduce risk. They think having multiple options insulates them. But a well-structured bundle actually reduces risk more — one vendor, one contract, one support line. Lucas: And that's where the sales rep's framing matters. You don't say, 'Here's our bundle.' You say, 'Here's how we simplify your vendor landscape and give you predictable costs for the next three years.' You're repositioning the multi-threat as a source of complexity that you can solve. Luna: Which leads to a practical tip: map out all the buyer's alternatives upfront. Don't just ask who else they're talking to. Ask, 'If you don't go with any of us, what's your fallback?' That reveals the full set of threats. Lucas: And then use that map to design your bundle. If their fallback is building in-house, your bundle should emphasize speed to value and lower total cost of ownership. If it's mixing two vendors, your bundle should emphasize integration and single-vendor accountability. Luna: One risk I've seen: reps create a bundle that's too complex. They try to include every possible product and end up with a Frankenstein offer that confuses the buyer. Lucas: Good point. The bundle should have no more than three components. Two is ideal. And each component should be something the buyer already values. Don't throw in a module they haven't asked for just to pad the value. Luna: Also, make sure the pricing is transparent. If the buyer feels like you're hiding costs, the multi-threat comparison gets easier for them, not harder. Lucas: Let's talk about how to introduce the bundle in a conversation. You don't lead with it. First, you establish that you understand their full set of alternatives. Then you say something like, 'Given everything you're considering, we think the most effective path is a single agreement that covers X and Y, with a structure that aligns with your goals.' Luna: That frames the bundle as a solution to their multi-threat dilemma, not as an upsell. Lucas: And then you walk through the economics. Show them the standalone prices, then the bundle price, then the credits or discounts. Make it visual. A simple table can work wonders. Luna: I want to touch on one more thing: the multi-threat buyer who is also a committee. Different stakeholders have different priorities. The CFO cares about total cost, the CTO cares about integration, the VP of Sales cares about features. How do you handle that? Lucas: That's where you need to have a version of the bundle that speaks to each stakeholder. For the CFO, highlight the total cost over three years versus the fragmented alternative. For the CTO, emphasize the single API, single data model. For the VP of Sales, show the features that are exclusive to the bundle. Luna: So it's not one pitch — it's a coordinated set of messages, all pointing to the same bundle. Lucas: Exactly. And that requires prep. Before the meeting, map out who the stakeholders are and what they care about. Then tailor your bundle's positioning for each. Luna: Before we wrap, I want to step back. We've talked a lot about tactics, but the underlying principle is that a multi-threat buyer is making a complex decision. Your job is to simplify it in your favor. And that's a real skill. Lucas: It is. And the best reps I've seen don't just react to the threats — they anticipate them. They walk into the first meeting already thinking, 'What are all the ways this buyer could say no, and how can I structure my offer to make those paths less attractive?' Luna: That kind of preparation is why this show exists — to help reps think that way. And speaking of that, a quick honest thing: a handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many episodes. It keeps the show ad-free and focused on real tactics. Lucas: Yeah, it's a small group, but it makes a big difference. If these conversations have moved your work forward in some small way, that's where you can help keep them coming. Luna: Alright, back to it. So let's say you've structured your bundle, you've mapped the stakeholders, and you're in the final negotiation. The buyer says, 'We like the bundle, but we want a 10% discount on top.' Lucas: Classic. Don't just give the discount. Instead, say, 'We can do that if we extend the term to four years' or 'If you prepay the first year.' You maintain the bundle's integrity while giving them a win. Luna: And you avoid unraveling the multi-threat structure. Because if you start discounting components, you're back to line-item comparisons. Lucas: Right. The bundle is a fortress. Defend it. Make any concession tied to something that strengthens the overall relationship. Luna: So to sum up: map the full threat set, design a simple bundle that beats the combined alternatives, price it to disincentivize unbundling, and frame it as a risk-reduction move. Then defend the bundle in negotiation. Lucas: That's the framework. Next time you're facing a buyer who says, 'We have options,' don't panic. Structure your offer so those options look worse by comparison.