Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / How Price Objections Signal Deal Breakdowns
Transcript
- Lucas: There is a specific moment in almost every enterprise deal where the temperature drops. The prospect leans back, crosses their arms, and says the three words that make every salesperson’s heart skip a beat: that seems high. Luna: Right, and immediately everyone starts reaching for their discount calculator or preparing a feature comparison sheet to justify the number. Lucas: Exactly. We spend years training reps to handle price objections by building stronger value props or offering concessions. But I have been looking at some recent data on deal velocity, and the pattern is frustratingly consistent. The deals that survive price shocks are not the ones where the seller gave the best discount. They are the ones where the seller stopped talking about price entirely and started talking about the buyer’s internal pain. Luna: So you are suggesting that when a buyer flags the price, they are not actually negotiating a rate, but rather expressing anxiety about the return on investment? Lucas: Precisely. And here is the concrete thing I want us to drill into today. There was a mid-market software provider I spoke with last month, let us call them Vertex Analytics. They were stuck in a two-month stall on a four hundred thousand dollar contract because the procurement team kept citing budget constraints. Their standard play was to offer a five percent discount if the deal closed within ten days. Luna: Which usually just trains the buyer to wait until the end of the quarter to push harder. Lucas: It does. But their new account executive, Sarah, decided to try something different. When procurement pushed back on the four hundred thousand figure, she did not offer a discount. She did not even defend the price. She asked one question: tell me exactly how this number sits inside your current fiscal year budget line item. Is this capital expenditure or operational expense? And more importantly, who else needs to sign off on this specific line item? Luna: That is a sharp pivot. Instead of fighting the number, she is trying to map the political landscape around it. Lucas: She is mapping the bureaucracy. And what happened next is the part that matters. Procurement admitted that the finance director was blocking the deal not because of the vendor cost, but because the implementation team had no dedicated project manager assigned to the rollout. The price tag was just the convenient excuse to hide the resource gap. Luna: Oh wow. So the objection wasn't about the product cost at all. It was about the hidden labor cost of making the product work. Lucas: Exactly. Once Sarah realized that, she shifted the entire conversation. She offered to include a dedicated implementation specialist for the first ninety days as part of the package, which effectively neutralized the finance director's concern about internal resource drain. The deal closed two weeks later at full price. No discount. Just a better alignment of risk. Luna: That is a classic example of confusing symptom with cause. Most teams treat the price complaint as a math problem when it is actually a management problem. Lucas: And this brings us to the core argument I want to make today. We need to stop viewing price objections as a barrier to be overcome and start viewing them as a diagnostic signal. When a buyer says the price is too high, they are usually saying one of three things. First, they do not understand the unique value enough to justify the cost. Second, they lack the internal mandate to approve the spend without a concession. Third, they are hiding a different objection behind the money shield. Luna: The third one is the most dangerous because it means you are solving the wrong problem. If you discount because you think they can't afford it, but they actually just don't trust you, you have just destroyed your credibility. Lucas: Spot on. And that is why the Vertex case works so well. Sarah used the price objection to uncover the trust deficit regarding implementation. By addressing the implementation risk, she solved the underlying trust issue, which made the price acceptable again. It is a loop. You cannot fix the price without fixing the context. Luna: But how do you teach a rep to ask those deeper questions without sounding interrogative? It feels like walking a tightrope between curiosity and interrogation. Lucas: You frame it around their success, not your margin. The script isn't 'why is this too expensive?' The script is 'help me understand what needs to happen internally for you to feel confident moving forward at this level.' It shifts the burden of proof from the seller to the buyer's internal process. It invites them to share the roadmap rather than demanding justification. Luna: I like that framing. It makes the buyer an ally in figuring out the logistics rather than an adversary in a haggling match. Lucas: It does. And there is a second layer to this that many leaders miss. We often talk about the buyer's perspective, but we forget to look at our own commission structures. If your reps are incentivized solely on revenue booked, they will always default to discounting to close the deal quickly. They are acting rationally within their own incentive model. Luna: So you are saying the price objection culture is actually a reflection of bad internal compensation design, not just bad sales skills. Lucas: Absolutely. If a rep loses twenty percent of their quota for closing a deal at full price versus closing a larger deal at a discount, they will choose the discount every single time. Until you change the incentive to reward margin retention or long-term customer health, you will never change the behavior at the table. Luna: That is a structural insight. It explains why training sessions fail. You can teach someone to diagnose risk, but if their paycheck depends on speed, they will ignore the diagnosis. Lucas: Right. So we have the diagnostic shift, and we have the incentive alignment. But there is a practical tactic that helps reps execute this in the heat of the moment. It is called the silence pause. When a buyer throws the price bomb, the natural instinct is to fill the void with more features or a counter-offer. Luna: Because we are afraid that if we stop talking, the deal dies. Lucas: We are afraid of the silence. But in reality, silence forces the buyer to elaborate. If you say, 'I hear you. That is a significant investment,' and then you stop, the buyer will often volunteer the real reason. They might say, 'Well, we also haven't defined the use case yet,' or 'My boss is pushing back on this.' Silence extracts the truth. Luna: It feels uncomfortable in the moment, but it is probably the highest leverage move in the entire playbook. Lucas: It is. And this ties back to the Vertex story. Sarah didn't jump in with a discount. She paused. She let the procurement officer sit with the rejection of her initial stance. That discomfort forced the officer to dig deeper and reveal the resource gap. It was the silence that did the heavy lifting. Luna: So the takeaway is really about patience. Patience to listen, patience to diagnose, and patience to align incentives rather than rushing to the bottom line. Lucas: Patience and precision. Rushing to a discount is easy. It is low effort and it creates long term problems. Diagnosing the root cause is hard work, but it builds a relationship that survives beyond the signature. Luna: I think a lot of operators would agree that treating price as a conversation starter rather than a conversation stopper is a mindset shift we could all use. Lucas: Definitely. And if these conversations have moved your work forward in some small way, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Luna: Yeah, it really helps keep the research sharp and the guests prepared for these deep dives. Lucas: Back to the tactical side though. Let us look at the documentation aspect. How many companies actually document these value discussions in their CRM, or do they just note the final negotiated price? Luna: Most just note the price. They capture the transaction, not the transformation. Which means they lose the institutional knowledge of why the deal actually closed. Lucas: That is a massive blind spot. If you do not record the diagnostic questions and the answers, your next rep walks into the same room blind. They will repeat the mistakes of the previous quarter because the data doesn't exist. You need to capture the story, not just the number. Luna: So the CRM becomes a library of objections and resolutions, not just a ledger of revenue. Lucas: Exactly. It turns your sales process into a learning organization. Every objection handled well becomes a playbook entry for the next rep. It scales the intuition that Sarah showed in that Vertex deal. Luna: It makes sense. You cannot scale what you do not document, and you cannot document what you do not prioritize. Lucas: Right. And that prioritization starts with leadership valuing the quality of the interaction over the speed of the close. It sounds obvious, but in practice, it is incredibly rare to see companies rewarding the diagnostic approach consistently. Luna: Unless you measure it. If you only measure days to close, you kill the diagnostic behavior before it starts. Lucas: You have to add metrics that reflect the depth of the engagement. Maybe it is the percentage of deals where the buyer explicitly validated the ROI in writing. Or the number of stakeholder interviews completed before the proposal stage. These are leading indicators that predict whether the price objection will even arise. Luna: If you have done the homework, the price is just a formality. If you haven't, the price is a wall. Lucas: Perfect summary. It really comes down to preparation. The buyers who walk away angry about price are usually the ones who felt sold to, not sold with. They feel like the vendor saw a wallet, not a problem. Luna: And the ones who pay full price are the ones who feel like partners in solving their internal challenges. Lucas: That partnership is what you are actually selling. The software is just the tool. The relief from the internal friction is the product. Luna: So next time a rep hears 'that seems high,' they should remember that it is an invitation to help, not a demand to lower the bar. Lucas: An invitation to clarify the value. To diagnose the risk. To build the business case together. It changes the entire tone of the rest of the negotiation. Luna: It transforms a conflict into a collaboration. I think that is the key distinction most teams miss. Lucas: It is. And once you make that shift, you stop fearing the objection and start welcoming it as the moment the real work begins. Luna: A much more sustainable way to run a sales floor than chasing discounts all day. Lucas: Exactly. It keeps the margins healthy and the relationships intact. Which, in the end, is what actually drives long term revenue growth. Luna: Do you think buyers appreciate the transparency of that approach, or do they prefer the ambiguity of a quick discount? Lucas: Smart buyers appreciate the transparency. They know that a discounted deal often comes with reduced service levels or hidden fees later. They would rather pay full price for full value than get a stripped-down version that fails later. Trust is the ultimate currency. Luna: Then the question is really just about execution. Can the sellers actually deliver on that promise of value once the deal is signed? Lucas: That is the ultimate test. Because if the implementation fails, the whole house of cards collapses. The diagnosis was correct, but the delivery was wrong. That is why customer success cannot be siloed from sales anymore. Luna: They have to be the same team. From the first conversation to the hundredth renewal. Lucas: Without that handoff integrity, the best negotiation tactics in the world are just temporary fixes for a broken system. Luna: So we circle back to structure. Incentives, documentation, and shared goals between sales and success. Lucas: All of it. You cannot negotiate your way out of a structural flaw. You have to build the structure to support the negotiation. Luna: It is a holistic view of the revenue engine. Not just the front door, but the whole foundation. Lucas: Exactly. And that is how you turn a price objection from a threat into a catalyst for a better deal. Luna: A catalyst for clarity. I like that. Lucas: Clarity wins. Always. It just takes a little more courage to pursue it than to settle for the easy discount.