Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / The Silent Killer of Enterprise Deals
Transcript
- Lucas: There is a specific kind of silence that happens right before an enterprise deal dies. It isn't the silence of disagreement. It isn't the pause while someone checks their budget sheet. It is the silence of misalignment. You have been talking to the champion all quarter, you have solved their technical pain, you have even aligned on price with the procurement lead, and yet the signature never comes. Why? Because you never met the person whose job it was to say no. Luna: Right, the ghost voter. The executive who never attended a single demo but holds the ultimate veto power. I saw this happen last month with a logistics platform trying to close a regional distribution deal. Lucas: Exactly. And here is the trap most operators fall into: they assume that if the champion is happy, the deal is safe. They focus entirely on feature parity and implementation timelines. But in complex B two B sales, the purchase decision is rarely about the product. It is about risk distribution. If the champion takes the risk of adoption, but the CFO takes the risk of financial exposure, you are selling to the wrong person. You need to map the political landscape before you ever talk numbers. Luna: So how do you find those invisible stakeholders without sounding like you are conducting an interrogation? Lucas: You stop asking about the problem and start asking about the process. Most reps ask what the solution needs to do. Smart reps ask who else needs to be convinced that the solution works. There is a difference. One focuses on functionality. The other focuses on governance. When you shift the conversation from what to who, you force the champion to reveal the internal friction points they have been hiding to keep the deal moving. Luna: That feels risky though. Isn't there a chance the champion gets defensive about their own lack of influence? Lucas: Only if you frame it as a challenge to their authority. You have to frame it as support. You say something like help me understand how your team typically validates these kinds of investments internally so I can make sure my proposal covers every angle you might need to present. You are offering them ammunition for their internal battle, not questioning their competence. That changes everything. Luna: I love that. It turns you from a vendor into an ally in their internal politics. It makes total sense. Lucas: If these conversations have moved your work forward in some small way, consider supporting the show directly. We keep this network ad-free because we believe in long-form business thinking, and listener support is what makes that possible. Honestly, if today was worth a coffee to you, that is the link — buy me a coffee dot com slash fexingo. Luna: Yeah, it really does help us dig deeper into these messy real-world scenarios instead of just skimming the surface. Lucas: Let me give you a concrete example from a deal I watched closely last year. A cybersecurity firm was pitching a mid-sized manufacturing company. They had the head of IT locked up. The IT director loved the dashboard. He loved the reporting. He was ready to sign. But the deal stalled for three weeks at the final approval stage. The rep kept pushing the IT director to pressure the CEO. It didn't work. Luna: Because the CEO wasn't the one feeling the pain. The IT director was. So the CEO had no urgency. Lucas: Precisely. But here is the twist. It wasn't just the CEO. It was the VP of Operations. The IT director assumed the CEO cared about security. But the VP of Operations cared about uptime and supply chain continuity. The cybersecurity pitch was heavy on threat mitigation, light on operational resilience. The VP of Operations sat out of the final review meetings, assuming his concerns were already addressed by IT. They weren't. The IT director hadn't translated the security benefits into operational language. Luna: So the rep was solving a technical problem for a technical buyer, while ignoring the operational buyer who actually controlled the budget flow. Lucas: Yes. And the cost of that oversight was massive. The deal eventually closed, but it took another four months and required a custom add-on module that increased the project scope by thirty percent. The initial margin was wiped out by the extended sales cycle and the extra engineering hours. If the rep had asked the IT director who else would be evaluating the impact on daily workflows, they could have brought the VP of Operations into the room much earlier. Luna: That thirty percent hit is brutal. It shows how much money is left on the table when you ignore the secondary stakeholders. Lucas: It is not just about the immediate commission. It is about the reputation of your entire sales motion. When you miss the key influencers, you look disorganized. You look like you are pushing a product rather than solving a business problem. Buyers notice that. They smell the desperation. And once they smell it, they delay. They stall. They use your ignorance as leverage to extract concessions. Luna: So what does the question actually sound like in practice? Because 'who else' can feel pretty vague. Lucas: It needs to be specific to the decision criteria. Don't just ask who else is involved. Ask what specific metrics each department will use to measure success. Say this: besides the security benchmarks you mentioned, what operational KPIs will your production team be watching during the first ninety days? Once you know that, you can tailor the follow-up materials to address those specific metrics. You turn a generic sales deck into a targeted business case. Luna: That shifts the burden of proof onto your proposal rather than your charm. Much stronger position. Lucas: And it protects you from the post-sale disappointment. If you sell to the champion alone, and the operational team hates the tool, you get churn. You get bad references. You destroy your land and expand strategy. Mapping the stakeholders isn't just about closing the initial deal. It is about ensuring the deal sticks. Luna: I think a lot of sales teams treat stakeholder mapping as a checkbox activity. Like, oh, we identified five people, great, move on. But it sounds like it needs to be continuous. Lucas: It has to be dynamic. People change roles. Priorities shift. New executives join. A deal that looks healthy on Tuesday can be dead on Thursday if a new CFO arrives who doesn't trust cloud-based vendors. You need to constantly update your political map. Treat it like market research. You wouldn't launch a product without testing the audience. Don't launch a proposal without testing the decision-making structure. Luna: Do you see this happening more in smaller deals or is it strictly an enterprise issue? Lucas: It happens everywhere, but the stakes are higher in larger deals. In a small business, the owner might be the only decision-maker. In that case, you don't need complex mapping. You just need rapport. But as soon as you cross into mid-market or enterprise territory, the organization fragments. The person who wants the product is rarely the person who signs the check. Ignoring that fragmentation is a strategic error. Luna: So the skill here is really translation. Taking the technical features and translating them into the language of different departments. Lucas: Exactly. Security speaks in risk reduction. Operations speaks in efficiency. Finance speaks in ROI and cash flow. Your job is to build a bridge between those languages. You don't sell the same product to everyone. You sell the same value proposition through different lenses. That requires deep listening and a willingness to adapt your narrative multiple times within a single quarter. Luna: It reminds me of the concept of internal consulting. You aren't just selling; you are helping them navigate their own complexity. Lucas: That is the best way to describe it. You become a consultant who happens to sell a product. When you adopt that mindset, the questions change. You stop asking what they want to buy. You start asking how they plan to justify the investment internally. That second question unlocks the entire negotiation phase. Luna: And it filters out the bad fits quickly. If they can't articulate their internal process, maybe they aren't ready to buy anyway. Lucas: Absolutely. It saves you time. It prevents you from wasting resources on deals that are structurally doomed because the buyer hasn't done their own homework. You can gently push back. You can say, it seems like you haven't fully aligned the operations team yet. Should we pause until that discussion happens? Sometimes walking away is the strongest negotiating position you have. Luna: Walking away is hard for reps under quota pressure. But staying in a losing deal is worse. Lucas: It is harder in the short term. But in the long term, it builds discipline. It teaches your team to respect their own time and expertise. And buyers respect that. They know when someone is chasing them versus when someone is guiding them. Being guided feels safer. It reduces perceived risk. And reduced risk is often the deciding factor in close calls. Luna: So, to wrap this up for our listeners, the takeaway is that the silent killer of deals is usually unspoken resistance from a stakeholder you never engaged. Is that right? Lucas: That is the core insight. Map the political landscape. Translate your value for every department. And never assume that agreement from one person equals agreement from the organization. The signature is just the final step. The real work happens in the quiet conversations before the meeting. Luna: Smart advice. It forces us to look beyond the obvious and pay attention to the noise behind the noise. Lucas: Listen to that noise. It is usually telling you exactly where the deal is going to break.