Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / How a Rep Won by Never Mentioning Price
Transcript
- Lucas: So there's this story I keep coming back to. A B2B software rep — sells workflow automation to mid-market manufacturing firms — closes a four hundred and seventy five thousand dollar contract. And the buyer never asked about price until the very last meeting. Luna: That's insane. I've been on the buyer side of that kind of deal. Procurement is literally trained to ask about price in the first email. Lucas: Right. But this rep — let's call her Dani — she structured the entire process so that price was essentially the last variable introduced. And it wasn't an accident. She had a three-part system: value scaffolding, budget anchoring through competitor benchmarks, and what she calls a "pricing conversation postponement" script. Luna: Okay, I need to hear the script. But first — how did she get away with not naming a number in the first call? Most buyers won't let you off the hook. Lucas: That's the key. She didn't deflect. She acknowledged the question directly. The buyer said, 'What does this cost?' and she replied, 'I can give you a range right now, but I've learned that if I quote a number before I understand your exact workflow and the downtime cost you're trying to fix, I'll either lowball myself or scare you off. Could we spend fifteen minutes mapping your current process, and then I'll give you a number that's actually relevant to your situation?' Luna: And the buyer said yes? I would have pushed back. Lucas: She had data on her side. She said, 'In my experience, deals where I quote price in the first call end up being thirty percent smaller on average, because I'm guessing. I don't want to guess with your budget.' The buyer later told her that line — 'I don't want to guess with your budget' — was what made him trust her. Luna: So she's framing it as protecting the buyer, not hiding the ball. That's smart. Lucas: Exactly. And then she moves to step two: value scaffolding. She doesn't just ask about pain points. She asks for specific numbers. 'How many hours per week does your team spend manually reconciling orders?' 'What's the fully loaded cost of that headcount?' 'How many errors slip through in a quarter, and what's the average cost to fix one?' Luna: So she's building a dollar figure for the problem before she ever mentions her price. Lucas: Right. By the third meeting, the buyer himself had calculated that the problem cost his company roughly six hundred thousand dollars a year. So when Dani finally said, 'Our solution is four seventy-five,' it wasn't a cost — it was a discount compared to the problem. Luna: But what about the budget anchoring through competitors? How does that work? Lucas: She researched three competitors the buyer was known to be evaluating. In the second meeting, she said, 'Some of our clients come to us after looking at Competitor A and Competitor B. If you've seen their pricing, you've probably seen numbers in the five hundred to seven hundred range for a deployment like yours.' She never stated her own price. She just set an anchor that made her eventual number look reasonable. Luna: So she's using the competitors' pricing to frame the range, without ever committing to a number herself. That's a great move. Lucas: It is. And she did it in a way that felt transparent. She said, 'I don't know exactly what they quoted you, but based on what I've seen, that's the ballpark. We come in a bit lower because we have a different deployment model.' That's vague enough to be true, but specific enough to create an anchor. Luna: Okay, but what about the third part — the pricing conversation postponement script? Is that just the line she used in the first call? Lucas: That's part of it. But she also had a script for when the buyer brought up price in later meetings. For example, in meeting two, the buyer said, 'I need a number to take to my CFO.' She responded: 'I can give you a budget range, but I want to be fair to you. If I give you a precise number now, it might change after we scope the implementation properly. What if I send you a ballpark by email within twenty-four hours, and we schedule a thirty-minute call to walk through it?' She bought herself another day. Luna: And the buyer went along with that? What's the ballpark she sent? Lucas: She sent a range: four hundred to five hundred fifty thousand. That's wide enough to cover her actual price but narrow enough to feel credible. And she included a one-page value summary with the six hundred thousand dollar problem number front and center. Luna: So the CFO sees: 'Problem costs six hundred K. Solution costs four to five fifty.' The math is obvious. Lucas: Exactly. The CFO didn't push back. In fact, the buyer told Dani later that the CFO said, 'That's less than I expected.' Because the anchor was already set at five to seven hundred from the competitor benchmark. Luna: I love that. But I have to ask — when does this strategy backfire? I can think of a few scenarios. Lucas: It definitely backfires if you're selling a commodity. If the buyer can compare your product feature for feature with three other vendors and price is the only differentiator, you can't delay price. They'll just move on. Luna: Right. Or if you're in a regulated procurement process where price has to be submitted by a certain date. You can't postpone. Lucas: Exactly. Dani's deal worked because the solution was complex and the buyer was already frustrated with status quo. She also had a strong referral from a similar company, which gave her credibility to ask for time. Luna: So the referral was part of the trust-building too. That's a good reminder. Lucas: Yeah. One more thing — she never used the word 'price' after the first meeting. She used 'investment' and 'budget' and 'range'. That subtle language shift kept the conversation focused on value. Luna: That's a classic negotiation technique. 'Price' is a cost. 'Investment' is a return. Lucas: Right. So the takeaway: if you're selling something complex and you can build value before you name a number, you can often close a larger deal because the buyer's reference point is the problem, not your competitor's price list. Luna: I think a lot of reps are afraid to delay price because they think the buyer will walk. But Dani's example shows that if you frame it right, the buyer actually respects you more. Lucas: Absolutely. And honestly, if these conversations have moved your work forward in some small way, we'd love to keep them coming. Listener support is what keeps the show ad-free and independent. You can find us at buy me a coffee dot com slash fexingo. Luna: Yeah, every bit helps us keep digging up stories like Dani's. And we really appreciate it. Lucas: So to wrap up — the next time you're in a complex deal, try pushing the price conversation to after you've built the value case. You might be surprised at how much it changes the dynamic. Luna: And if anyone tries Dani's script, let us know how it goes. We'd love to hear your story. Lucas: Exactly. That's all for this episode. Thanks for listening.