Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / How The CFO's Third Question Closes Enterprise Deals
Transcript
- Lucas: We have spent the last few weeks dissecting the first two questions a CFO throws at you when the deal is on the line. The first is about value, the second is about ROI timelines. But there is a third question that kills more deals than anything else, and it usually comes out of left field, right before the signature page is printed. Luna: I love this angle because it feels like the trap door opening. What is the question? Lucas: It is: What happens if this fails? Not what are the risks, but what happens if this actually fails. And I want to look at a specific moment from late August here in New York, where a mid-market software vendor was stuck on a fifty million dollar contract because their sales leader tried to argue against the possibility of failure. Luna: That is a classic mistake. Telling a CFO that something won't fail sounds like ignorance, not confidence. Lucas: Exactly. The vendor rep said, well, our implementation success rate is ninety nine percent, so it will work. The CFO just stared at him and asked, so you are betting my entire department's quarterly targets on a number you pulled from your marketing deck. That is the moment the deal started dying. Luna: So how do you pivot from that defensive posture into something that actually closes the deal? Lucas: You stop talking about probability and start talking about structure. You shift the conversation from whether failure might happen to how the architecture of the deal protects them if it does. Let me walk you through the framework we call the Safety Net Close. Luna: I am curious if this works for services too, or if it is mostly product plays. Lucas: It works better for services, honestly. Because with software, you can point to uptime metrics. With services, the fear is human error, scope creep, or cultural mismatch. The CFO knows people leave, projects drift, and plans change. So you have to acknowledge that reality immediately. Luna: Right, because ignoring the messiness of execution makes you look naive. What does the first step of the Safety Net look like? Lucas: Step one is the admission of partial control. You say something like, we cannot guarantee the outcome of every individual stakeholder interaction, but we can guarantee the governance process. It is a subtle linguistic shift, but it moves you from a promise of perfection to a promise of discipline. Luna: I think I have heard that phrasing before in high stakes consulting pitches. It feels less like a sales pitch and more like a legal disclaimer. Lucas: That is the point. A legal disclaimer is boring, but it is safe. Your job is to make the governance process sound exciting. You show them the dashboard, the weekly check-ins, the escalation paths. You are selling visibility, not just results. Luna: So you are selling the ability to catch problems early, rather than preventing them entirely. That is a very different value prop. Lucas: Precisely. And this leads us to the second part of the framework, which is the kill switch. Every good enterprise deal needs a defined off-ramp. If things go sideways, how do they exit without losing everything? Luna: Most salespeople hate talking about killing the deal. It feels like admitting defeat before you even start. Lucas: They are wrong to feel that way. Offering a clear, fair kill switch increases trust. It tells the CFO that you are confident enough in your delivery to let them walk away if the value isn't there. It removes the feeling of being trapped in a bad contract. Luna: That is interesting. It flips the script from vendor lock-in to vendor accountability. Do you have a concrete example of how that looks in a clause? Lucas: Sure. In that August deal, the vendor added a milestone-based termination clause. If the first phase misses its key performance indicators by more than ten percent, the client can terminate for cause with full refund of unearned fees. It sounds scary to the seller, but it actually accelerated the close by three weeks. Luna: Because it gave the CFO the permission slip she needed to get internal approval. She could take that clause back to her board and say, see, they are putting their money where their mouth is. Lucas: Exactly. It turns a liability into a credibility signal. But here is where most operators trip up. They offer the kill switch too broadly. They give away the whole dog. Luna: So you have to be surgical with it. Specific metrics, specific timelines. You don't just say 'if it fails,' you say 'if Phase One doesn't hit X by Y date.' Lucas: Yes. Vague triggers are useless. The CFO needs to know exactly what the alarm bell looks like. When you define the trigger clearly, you also define the success criteria clearly. It aligns both sides on what winning actually looks like. Luna: This feels like it requires a lot more upfront work in the proposal stage. You can't just wing this in the final negotiation meeting. Lucas: You absolutely cannot. If you bring up the kill switch at the eleventh hour, it looks like a concession. If it is built into the draft from day one, it looks like standard operating procedure. It signals maturity. Luna: I wonder if this changes how we price these deals. Does offering a strong exit clause force you to charge less? Lucas: It should not. In fact, it allows you to charge more. Because you are reducing the perceived risk for the buyer, you are increasing the value of your service. Risk reduction is a tangible benefit. You can monetize peace of mind. Luna: That is a hard sell to traditional procurement teams who only look at bottom line cost. How do you translate risk reduction into dollars for them? Lucas: You calculate the cost of delay. If this project fails, how many months of lost revenue does the company incur? If your safety net prevents a three month delay, that is millions in value. You frame your fee as insurance against that larger loss. Luna: So you are positioning yourself as the insurer, not just the vendor. That is a powerful mental model shift. Lucas: It is. And it gets easier when you talk about the fourth component, which is the post-mortem commitment. Most contracts end when the work is done. Ours includes a mandatory review session thirty days after launch. Luna: Why is that necessary? Isn't that extra work for no immediate return? Lucas: It builds the long-term relationship, yes, but more importantly, it proves you care about the outcome, not just the invoice. It shows that you are invested in the success of the implementation, even after the handoff. It closes the loop. Luna: I like that. It stops the silence after the sale. We talked about post-sale silence before, but this is active engagement. Lucas: Right. It keeps the channel open for upsell later, but for now, it serves as a final reassurance. The CFO sees that you are thinking about the future state, not just the present transaction. Luna: Let's pause here for a moment. If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. Lucas: Yeah, if these conversations have moved your work forward in some small way, consider supporting the network directly. It keeps the research deep and the ads non-existent. Luna: And it helps us keep digging into these specific mechanics instead of just skimming the surface. Lucas: Back to the deal. There is one final layer to the Safety Net Close, and it is about the communication protocol during a crisis. What happens when things go wrong? Luna: This is huge. Usually, vendors hide when things go wrong. They wait for the monthly report. That creates panic. Lucas: Correct. You need a rapid response protocol. Within four hours of a critical issue, the account team initiates a call. No emails, no tickets. A live conversation. It shows respect for the urgency. Luna: That requires a really disciplined internal culture. You can't expect sales reps to enforce that if operations is slow. Lucas: It has to be baked into the service level agreement. If you promise a four hour response, you must deliver it. Otherwise, you are just adding another layer of risk. But when you can deliver it, it is a massive competitive advantage. Luna: It turns your operational excellence into a sales asset. Most companies try to sell features, but you are selling reliability under pressure. Lucas: Exactly. And it ties back to that third question. What happens if this fails? Well, if it starts to fail, here is exactly how we will handle it, here is who will call you, and here is the timeline for resolution. Luna: It transforms the unknown into a known quantity. And for a CFO, a known quantity is infinitely preferable to a shiny promise. Lucas: It is. Because shiny promises evaporate when the market turns. Governance structures remain. They provide stability in a volatile environment. Luna: Do you think this approach scales down to smaller deals? Or is it overkill for sub ten million contracts? Lucas: The principles scale. The clauses might be simpler. You might not need a formal kill switch, but you definitely need the admission of partial control and the clear success metrics. Every buyer wants to know they aren't walking blind. Luna: So it is really about transparency. Giving the buyer enough rope to feel safe, without tying them up in red tape. Lucas: Transparency with structure. That is the sweet spot. You give them the map, but you also build the guardrails. Luna: I think the hardest part will be getting sales teams to adopt this. They are trained to be optimistic, not analytical. Lucas: They need to understand that optimism without structure is just noise. Analytical optimism is what wins enterprise deals. It shows you have thought through the worst case and you are still willing to bet on the partnership. Luna: It shifts the dynamic from vendor-client to partner-partner. Because partners share the risk, not just the reward. Lucas: Precisely. And when you share the risk, you earn the right to share the upside. It changes the entire tone of the negotiation. Luna: One last question. If you had to pick one element of the Safety Net Close to implement next week, what would it be? Lucas: The admission of partial control. Just change your language in the first meeting. Stop promising perfection. Start promising discipline. It sets the stage for everything that follows. Luna: Simple, honest, and effective. I will try that in my next round of proposals. Lucas: See what happens when you trade certainty for credibility. It might just be the closer you have been missing.