Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / How to Close Deals Using Value Stacking
Transcript
- Lucas: Welcome to Episode Two Hundred of Closing the Deal with Fexingo. That is a number that feels heavy enough to require a cake, but since we are in a business podcast, I suppose a well-structured proposal will have to suffice. Luna: I think the cake would just get lost in the pile of RFPs on everyone’s desk anyway. So what is the angle for two hundred? Lucas: We are looking at value stacking. Most operators treat price as the final boss of any negotiation, but the real leverage comes from how you bundle the things that matter to the buyer after the signature. It is not about lowering the sticker price; it is about increasing the weight of the offer. Luna: So you are saying the deal dies when you only talk about dollars and cents? Because I see too many sales reps who think they have to defend every line item on the invoice. Lucas: Exactly. When you defend the price, you are admitting that the price is the only thing there. If you stack value, you shift the conversation to outcomes. Let me give you a concrete example from a mid-market SaaS provider I tracked last quarter. They were losing deals to cheaper competitors because their base license was ten percent higher. Luna: Ten percent is a big gap in enterprise procurement. How did they bridge it without discounting? Lucas: They stopped selling software and started selling an outcome package. Instead of just the platform, they bundled three years of premium customer success management, which included quarterly business reviews and dedicated onboarding engineers. The cost to them was low, but the perceived value to the buyer was massive because it removed internal friction. Luna: That makes sense. The buyer isn't paying for code; they are paying for peace of mind. But does that actually change the bottom line for the seller? Lucas: It changed their close rate by twenty percent in six months. The key is that the additional services are marginal cost for the seller but high value for the buyer. You are trading something you already have for something they desperately want. Luna: Right, because the engineering team is already there. Why not add the onboarding as part of the premium tier? Lucas: Precisely. And this brings us to the first rule of value stacking: identify the pain points that money cannot easily solve. Time is the biggest one. If your competitor is slower to implement, you can stack speed as a value item. Security is another. If you have SOC two compliance and they don't, that is a stackable asset. Luna: But what if the buyer is still focused on the total cost of ownership? Can't they just strip out those services and ask for a lower price? Lucas: That is the risk. You have to make the services sticky. You frame them not as add-ons, but as prerequisites for success. You say, 'This isn't an extra cost; it is the insurance policy that ensures you get the ROI you asked for.' It changes the narrative from expense to investment. Luna: I like that framing. It puts the onus on the seller to prove the value, which forces them to be more confident. Lucas: Confidence is contagious. If you hesitate on the value, they will hesitate on the price. But let's look at the mechanics. How do you actually present this without confusing the CFO? Luna: You have to keep the numbers clear. If you bury everything in jargon, the finance team will just reject the whole proposal. Clarity is king. Lucas: Clarity is essential. I recommend using a simple table. Column one is the core product. Column two is the implementation. Column three is the ongoing success program. You list the standalone value of each column, then show the total package price. The visual contrast between the sum of parts and the package deal creates a psychological anchor. Luna: So you are essentially using the decoy effect? Making the package look like the obvious choice because it has so much more in it? Lucas: It is similar, but it is more about completeness. Buyers hate buying incomplete solutions. If they buy just the software, they worry about adoption. If they buy the stack, they feel secure. You are selling certainty. Luna: Certainty is expensive. I wonder how many deals are lost because the seller was too cheap to provide that certainty? Lucas: A lot. Especially in complex B2B environments. Let's talk about a second layer: exclusivity. This is where value stacking gets really powerful. What if you offer early access to new features or direct lines to your product team? Luna: That sounds risky. Won't that create technical debt or scope creep for the product team? Lucas: It can, if you are not careful. But if you limit it to a small cohort of strategic partners, it works. You are selling influence. For a large enterprise, having a voice in the roadmap is often worth more than a five percent discount. It gives them political capital internally. Luna: Political capital. That is a very accurate way to put it. The buyer needs to win their own internal battle to justify the purchase. Lucas: Exactly. If you help them win that battle, you become indispensable. But here is the trap. Do not stack value that the buyer does not care about. I see sellers all the time adding white papers or webinars to proposals. Nobody wants those. Luna: Please tell me you are joking. White papers are the lowest form of currency in sales. Lucas: I am serious. It looks like padding. It signals that you are trying to inflate the perceived value with garbage. Only stack what solves a real problem. Implementation, training, security, access, community. Those are the four pillars. Luna: Four pillars. That is a clean framework. I can see how a sales director could train a team on that quickly. Lucas: It is scalable. But let's address the elephant in the room. What happens when the buyer says, 'I love the stack, but I only have budget for the base product'? Luna: Then you have to be ready to walk away or restructure. You cannot just unwrap the stack and drop the price. That destroys the value model. Lucas: Correct. If they only have budget for the base, you sell the base. But you do not apologize for it. You say, 'Fair enough. Here is the core solution. You can always add the success program later once you have proven the ROI.' You leave the door open, but you do not discount the current deal. Luna: That requires discipline. Most reps would rather give up the margin than lose the deal. Lucas: And that is why they stay junior. You protect the integrity of your pricing by protecting the structure of your offer. If you start chopping up the stack to fit every budget, you end up with no stack at all. Luna: So the lesson is: build the stack, defend the stack, and only remove pieces if the buyer explicitly asks for them, and even then, charge for the removal. Lucas: Charge for the removal. Or rather, acknowledge that removing value costs money. If they want to drop the implementation support, they need to accept the risk of longer ramp times. Make them feel the weight of what they are leaving behind. Luna: That is a subtle psychological lever. Risk aversion is a powerful motivator. Lucas: It is. And it keeps the conversation focused on what they gain, not what they lose. Now, before we go further, I want to take a quick moment to acknowledge our listeners. Luna: Yeah, we hit episode two hundred, which is a big milestone for the network. Lucas: If these conversations have moved your work forward in some small way, the way these stay ad-free is listener support. You can buy me a coffee dot com slash fexingo. It helps keep the research sharp and the episodes consistent. Luna: We appreciate it. It allows us to dig deeper into cases like this one instead of just skimming the surface. Lucas: Thank you. Now, back to the deal. Let's talk about timing. When should you introduce the stack? Luna: Not in the first call. You need to know their pain points first. Otherwise, you are just throwing spaghetti at the wall. Lucas: Agreed. Introduce it in the proposal phase, after you have validated the problems. If you lead with the stack, you look like you are trying to oversell. If you lead with their problems and then offer the stack as the solution, you look like a partner. Luna: Partner vs vendor. That is the distinction that wins enterprise deals. Lucas: It is. And one last thing. Document the value. When you send the proposal, include a section that explains why each component matters. Don't just list the items. Explain the benefit. 'Quarterly Business Reviews' sounds boring. 'Ensuring Year-One Adoption' sounds critical. Luna: Language matters. You are translating features into outcomes for the reader. Lucas: Always. Because the person signing the check might not be the person using the product. You need to give the signer the ammo to sell it internally. Luna: That is a smart tactical move. Empowering the champion. Lucas: Exactly. If you make their job easier, they will pick you. Value stacking is not just about the deal; it is about the relationship. It shows you are invested in their success, not just their wallet. Luna: And that is a long-term play. Short-term players just want the signature. Long-term players want the partnership. Lucas: Well said. So, as we wrap up episode two hundred, think about your next proposal. Are you selling a commodity, or are you selling a stack of value? Luna: I hope everyone listening goes back and adds one thing to their deck that proves they care about the outcome, not just the transaction. Lucas: Do that. And if you find yourself struggling to define that value, remember the four pillars: implementation, training, security, and access. Build on those. Thanks for listening.