Closing the Deal with Fexingo · 2026-07-09 · 8 min
Key moments - from our scoring
Substance score
49 / 100
Five dimensions, 20 points each
This episode dissects a counterintuitive negotiation move that succeeded because it was built on strategy rather than desperation. Lucas and Luna examine how a rep used a substantial price reduction as a diagnostic tool to uncover hidden objections rather than as a concession. The buyer's reaction to the 20% offer revealed the true constraint: implementation costs were the budget killer, not the software fee itself. By learning this, the rep pivoted from discounting to a phased rollout structure that spread costs over two quarters, ultimately growing the deal size. The conversation explores when this tactic works - strong relationship, vague budget objections, credible alternatives to discounting - and when it fails catastrophically (pure price shoppers, weak negotiating position, lack of strategic backup). The hosts emphasize that anchoring and social psychology principles like door-in-the-face can actually reinforce value perception when executed correctly, but only if the rep has genuine leverage and a prepared alternative.
Only when you have a strong buyer relationship, the buyer has given vague budget objections without a specific number, and you have a credible structural alternative (like payment terms or phased implementation) ready to deploy based on what you learn from their reaction.
Instead of cutting price to win the deal, you propose a significant cut (15-25%) to see whether the buyer accepts it or reveals the actual constraint; if they resist the cut and explain why, you've uncovered the real problem (like implementation costs) that discounting alone won't solve.
The discount forced the buyer to admit they actually needed 30% off and, more importantly, revealed that implementation costs were the real budget issue, allowing the rep to restructure the deal with phased rollout that increased total contract value instead of just cutting margin.
Strategic discounts are tied to a hypothesis about hidden constraints and have a prepared alternative ready; fear-based discounts are offered to prevent losing the deal and leave you negotiating against yourself with no backup plan.
Proposing a 20% cut actually anchors the base price higher because it implicitly signals your full price is the real value and you're making an exception, similar to the door-in-the-face social psychology technique where the smaller ask seems reasonable after an extreme one.
Our reviewer’s read on each dimension, with quotes from the episode.
The episode presents a genuine tactical insight - using a discount offer as a diagnostic tool rather than a concession - along with useful contextual framework (green lights, margin considerations, anchoring dynamics). However, it recycles some psychology concepts (door-in-the-face) without deep novelty, and the core idea, while sound, is relatively contained. The back-half discussion of when to apply the tactic adds substance but includes some rehashing.
By suggesting the cut himself, he forced the buyer to either accept - which would signal that price really was the issue - or push back and reveal what they actually needed.
before you ever propose a lower price, ask yourself what you're trying to learn. If the answer is 'maybe they'll just buy faster,' that's not a good enough reason.
The framing of a discount as a hypothesis test is pragmatic and somewhat fresh for sales podcast discourse, but the underlying mechanics (door-in-the-face, anchoring, diagnostic questioning) are established psychology and negotiation concepts. The episode applies these competently to a specific scenario but doesn't break genuinely new theoretical ground or challenge conventional wisdom in a surprising way.
the discount was a hypothesis test.
He anchored high on a different dimension. By offering a twenty percent cut, he implicitly said 'my full price is the real value, I'm just making an exception.'
No guest is present. This is a two-host conversation between Lucas and Luna discussing a second-hand anecdote ('this rep,' unnamed and unverified). Neither host establishes direct operational credibility for having executed similar deals, and the rep whose story is told is never identified or brought on. The episode relies entirely on narrative retelling rather than first-person practitioner insight.
So there's this story I keep coming back to - a B2B software rep who was stuck in a deal
The buyer didn't take the deal.
The single case study provides some concrete details (20% discount, 30% needed, implementation costs, phased rollout, deal value increased) but lacks hard metrics: no company name, industry context beyond 'B2B software,' actual dollar figures, or verifiable outcomes. The discussion of margin thresholds (15-25% in software, 10% in low-margin) is sensible but generic. The episode would be significantly stronger with 2-3 named examples and actual deal sizes.
The rep offered twenty percent. Is there something magic about that number?
In software, profit margins are high, so a twenty percent cut is painful but survivable.
The hosts maintain good pacing and Luna asks clarifying follow-ups ('And what happened?', 'There's also the risk...', 'What about the anchoring effect?'). However, the conversation rarely pushes back or challenges; it's largely confirmatory. Neither host introduces skepticism, tests the rep's logic rigorously, or explores failure modes in depth. The dialogue feels cooperative rather than investigative, and lacks the sharp back-and-forth that would elevate the episode.
That's counterintuitive. So the discount actually reinforced the value of the full-price offering.
But only if you're genuinely prepared to walk away if the buyer just takes the cut and you can't make the economics work.
Computed from the transcript - who did the talking, and the words that came up most.
In this episode of Closing the Deal with Fexingo, Lucas and Luna explore a counterintuitive sales strategy: asking the buyer for a 20 percent price cut - and winning. They break down the true story of a B2B software rep who, facing a stalled deal, proposed a steep discount that forced the buyer to reveal their actual budget and decision criteria. Lucas explains the psychology of anchoring downward, the difference between price negotiation and value negotiation, and why asking for less can sometimes land a bigger commitment. Luna pushes back on when this tactic backfires, and they discuss the specific signals that make it worth trying. A concrete case with actionable lessons for any sales operator who's tired of the same old discount dance. #SalesStrategy #NegotiationTactics #B2BSales #PriceCut #DiscountPsychology #ValueSelling #SalesPsychology #BusinessPodcast #Business #SalesTechniques #ClosingTheDealWithFexingo #FexingoBusiness #Podcast #LucasAndLuna #WinningDeals #SalesMindset #RevenueGrowth #SalesTips Keep every episode free: buymeacoffee.com/fexingo
Transcribed and scored by The B2B Podcast Index.
Lucas: So there's this story I keep coming back to - a B2B software rep who was stuck in a deal that had been dragging for months. Luna: Classic stall. What was the blocker? Lucas: Price, supposedly.
The buyer kept saying the budget was too tight, but they wouldn't give a number. So the rep did something most sales training would tell you never to do: he proposed a twenty percent price cut. Luna: Wait - he offered a discount before they even asked? That goes against everything about anchoring high.
Lucas: Exactly. But his reasoning was clever. By suggesting the cut himself, he forced the buyer to either accept - which would signal that price really was the issue - or push back and reveal what they actually needed. Luna: And what happened?
Lucas: The buyer didn't take the deal. Instead, they admitted that a twenty percent cut wasn't enough - they needed at least thirty percent, but more importantly, they needed the rep to understand the real problem: implementation costs were eating their budget. Luna: So the discount was a Trojan horse. It got the buyer to open up about the actual constraint.
Lucas: Right. Once the rep knew the real issue, he restructured the deal - not a discount on software, but a phased rollout that spread the implementation cost over two quarters. The total contract value actually went up. Luna: Interesting.
He used a price cut as a diagnostic tool, not a concession. Lucas: And I think that's the key insight here: sometimes asking for less - or appearing to - gets you more information than defending your price ever would. Luna: If these conversations are shifting how you think about your own deals, that's exactly what we hope for. A quick note - listener support is what keeps this show ad-free and independent.
If you've gotten value from episodes like this, you can help us keep going at buy me a coffee dot com slash fexingo. No pressure, just an option if the show's been useful to you. Lucas: Yeah, and we really mean that - every bit helps us keep the conversations honest and practical. Alright, back to the story.
So the rep's move worked in that case, but it's not a universal play. Let's talk about when this works and when it backfires. Luna: Let me guess: it depends on how much leverage you have? Lucas: Partly.
In this case, the rep had a strong relationship with the buyer - they'd been talking for months. He knew the buyer respected his opinion. If it had been a cold deal or a purely transactional relationship, proposing a discount might've just trained the buyer to ask for more. Luna: There's also the risk that the buyer takes the cut and walks away happy - but then you've left money on the table.
Lucas: Absolutely. That's why I think the tactic only works when you have a specific hypothesis about the buyer's hidden constraint. The rep in this case suspected it wasn't just price - he'd heard hints about implementation costs in earlier conversations. Luna: So the discount was a hypothesis test.
Lucas: Exactly. And that's the frame I'd recommend: before you ever propose a lower price, ask yourself what you're trying to learn. If the answer is 'maybe they'll just buy faster,' that's not a good enough reason. Luna: What about the anchoring effect?
Doesn't proposing a low number reset the negotiation floor? Lucas: It can. But here's the twist - the rep didn't anchor low. He anchored high on a different dimension.
By offering a twenty percent cut, he implicitly said 'my full price is the real value, I'm just making an exception.' The buyer actually perceived the base value as higher, not lower. Luna: That's counterintuitive. So the discount actually reinforced the value of the full-price offering.
Lucas: Right. It's similar to the 'door-in-the-face' technique from social psychology: if you ask for something extreme first, the smaller request seems reasonable. But here, the extreme ask was the discount itself. Luna: I can think of a scenario where this would fail badly: if the buyer is purely price-driven and has no other constraints.
Then they just take the cut, and you're stuck. Lucas: That's the danger. You need to be confident that the buyer cares about something beyond the upfront cost - maybe implementation time, maybe a specific feature, maybe the relationship itself. If they're a pure price shopper, don't try this.
Luna: So what signals should a rep look for before trying this move? Lucas: First, the buyer has engaged deeply - they've asked detailed questions, involved multiple stakeholders. Second, they've given a vague budget objection without a number. Third, you have a credible alternative to discounting, like a different payment structure or scope adjustment.
Luna: Those three together seem like a green light. Lucas: I'd say if you have two out of three, it's worth considering. But only if you're genuinely prepared to walk away if the buyer just takes the cut and you can't make the economics work. Luna: That's a good point - this strategy requires the rep to have a strong alternative, otherwise they're just negotiating against themselves.
Lucas: Right. And that's where a lot of reps get into trouble. They offer a discount because they're afraid of losing the deal, not because they have a strategic reason. The difference is night and day.
Luna: Let's talk about the actual numbers in the story. The rep offered twenty percent. Is there something magic about that number? Lucas: I don't think so, but it has to be significant enough to be noticed.
If he'd offered five percent, the buyer might have just said 'that's not enough' without revealing anything. Twenty percent is large enough to feel real, but not so large that it destroys credibility. Luna: So the threshold is around fifteen to twenty-five percent. Lucas: Roughly.
It also depends on the industry. In software, profit margins are high, so a twenty percent cut is painful but survivable. In a low-margin business, even ten percent might be too much. Luna: Good to keep in mind.
So the rep's move was essentially a calculated gamble that paid off because he understood the buyer's real situation. Lucas: Exactly. And that's the through line of this whole episode: the most effective negotiation tactics aren't about pressure or tricks. They're about information.
The rep asked for less to learn more, and then used that information to create a better deal for both sides. Luna: I think our listeners can take away a concrete question: 'If I offered a significant discount, what would I learn?' If the answer is nothing useful, don't offer it. Lucas: Perfectly put.
And if you do try it, make sure you have a plan for what comes next. The rep in our story didn't just cut the price - he used the buyer's reaction to restructure the entire deal. Luna: Alright, let's end with a practical challenge for listeners: the next time a buyer says 'your price is too high,' instead of defending or discounting, try asking 'what if I could lower it by twenty percent - would that change anything?' See what they say.
Lucas: I love that. It's a low-risk probe that could unlock the real conversation. Thanks for listening, and we'll be back next time with another deal story.
Other episodes covering the same guests and topics, from across The B2B Podcast Index.
How Idempotency-Key Design Prevents Payment DisastersThe Developer Tools Podcast with Fexingo · features Luna98 / 100
How Kubernetes Topology Spread Constraints Create Scheduling HotspotsDevOps Daily with Fexingo · features Luna95 / 100
Why Pipeline Velocity Trumps Deal Size Every TimeThe Growth Operator with Fexingo · features Luna95 / 100
Why Enterprise Software Deals Now Include a Vendor AI Model Explainability MandateB2B SaaS Talks with Fexingo · features Luna94 / 100
How B2B Brands Wreck Pipeline with Unsyncroned CRM DataThe Marketing Operator Podcast with Fexingo · features Luna92 / 100
Why Marketing Attribution Misses the Seasonality PatternMarketing Analytics with Fexingo · features Luna91 / 100
How a Rep Won by Negotiating Against Their Own Offer86 / 100How One Rep Closed by Asking the Buyer for a Competitor Comparison81 / 100The Sales Rep Who Won by Telling the Buyer He Was Wrong72 / 100How One Rep Closed by Asking the Buyer to Fire Their Vendor80 / 100The One Question That Won a Deal by Paying the Buyer70 / 100