Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / How a Rep Won a Deal by Asking for a Detailed Budget Breakdown
Transcript
- Lucas: There's a moment in almost every enterprise deal where the buyer says something like, 'We just don't have the budget for that right now.' And most reps either discount or walk away. But one rep I know did something different — he asked the buyer to pull up their actual budget spreadsheet and walk him through every line item. Luna: Wait — the buyer actually showed them the budget? I've heard of asking about budget range, but line-by-line? That feels almost invasive. Lucas: It does, until you frame it right. This was a seven-figure SaaS deal with a mid-market manufacturing firm. The rep, let's call him Dan, had been stuck for three months. The procurement lead kept saying the budget was 'frozen.' Dan didn't push on price. He said, 'I understand. Could you help me understand what's already allocated — not to change your numbers, but so I can see if there's a way our solution fits within your current structure?' Luna: And the buyer actually shared it? Lucas: Yeah, because Dan made it about helping the buyer, not about squeezing more money out of them. The buyer shared a spreadsheet with twelve line items. Dan noticed that line six was a legacy software subscription that was expiring in two months — and it cost about 60 percent of what Dan's solution would. So he said, 'What if we time your implementation to start right after that subscription ends, and you redirect that line item to us?' The buyer hadn't even considered it. Luna: So the budget wasn't frozen — it was just allocated in a way that didn't leave room for something new. The rep basically found a reallocation opportunity. Lucas: Exactly. The buyer's default position was 'no new spend.' But once Dan saw the actual numbers, he could position his solution as a swap, not an add-on. That deal closed two weeks later. And the buyer actually thanked Dan for helping them optimize their tech stack. Luna: I love that. But — and I have to ask — doesn't this only work if the buyer trusts you enough to share that level of detail? I've had buyers who get defensive if you even ask for a rough range. Lucas: That's a fair point. Trust is the prerequisite. Dan had built that over several calls — he'd given them a free audit of their current workflow, no strings attached. So by the time he asked for the budget, he had credibility. But even without that, there's a less invasive way to do it. Luna: What's that? Lucas: Instead of asking for the spreadsheet, you ask: 'If you had to prioritize, which budget line items are most flexible? Which are locked?' That still gives you a map of where the money can move. Most buyers will answer that without feeling exposed. Luna: So the goal isn't to get the exact numbers — it's to understand the constraints. Where's the slack, where's the friction. Lucas: Right. And once you know that, you can shape your proposal to fit into the slack. In Dan's case, the slack was the expiring subscription. In another deal I saw, the slack was a training budget that was underutilized, and the rep positioned their onboarding as 'professional development.' Luna: That's clever. But I want to push back a little — what about commoditized markets where the buyer has a fixed pool of dollars and three vendors competing for it? Does this tactic still hold? Lucas: It actually works even better there, because the budget is often more transparent. In those situations, the buyer might share the total allocated amount — say, $500,000 — and you're competing against two other vendors. The question then becomes: 'What criteria will you use to split that pool?' If the buyer says 'best value,' you can ask what 'value' means to them specifically. That's where you differentiate without discounting. Luna: So you're using the budget detail to understand the scoring system. That's smart. But I've also seen the opposite — a deal where the rep asked for a budget breakdown, the buyer shared it, then the rep realized the buyer had massively inflated one line item to create negotiating room. Lucas: Oh, that happens. Budgets are often political artifacts. A line item might include a buffer for 'unforeseen costs' that's really just a slush fund. If you see a line that seems out of proportion — like 'consulting fees' that are as big as the software line — you can ask gently: 'Help me understand what's driving that number. Is that a fixed contract, or is there flexibility?' Luna: And if they get defensive? Lucas: Then you back off. The goal isn't to audit them — it's to find alignment. If they clam up, the budget detail approach probably won't work, and you need to shift to value-based selling. But in my experience, if you've earned trust, most buyers are willing to be transparent because they want to find a way to say yes. Luna: That's a good note to end on. But before we wrap, I want to come back to something you said earlier about Dan's approach — he asked for the budget breakdown after giving a free audit. That feels like a pattern: give value first, then ask for transparency. Lucas: Absolutely. You can't ask for their budget if you haven't shown you understand their business. The audit wasn't a gimmick — it saved them money on another vendor. So when Dan asked for the budget, it felt like a natural next step in solving their problems together. Luna: I think that's the real takeaway. The budget conversation isn't about squeezing — it's about collaborating to find a path forward. And if these kinds of conversations have helped you think differently about your own sales process, you know, a couple of dollars a month is genuinely what keeps this show going — buy me a coffee dot com slash fexingo, if you've gotten something out of it. Lucas: Yeah, it's a small thing that makes a big difference. Keeps us ad-free and focused on real tactics. Anyway — back to the budget. One more angle I want to touch on: what about when the buyer gives you a number that's way below your price? Do you still ask for the breakdown? Luna: Interesting — because if they say 'we only have $50,000' and you're at $100,000, the breakdown might reveal they're not really the decision-maker. Lucas: Exactly. In one case, a rep was told the budget was $30,000 for a solution that typically cost $80,000. He asked for the breakdown, and it turned out the $30,000 was just the department's discretionary fund — the real budget was controlled by a VP who hadn't been in the meetings. The rep then asked for a meeting with the VP, reframed the conversation around ROI, and closed at $75,000. Luna: So the budget breakdown didn't just uncover reallocation — it uncovered a stakeholder gap. That's a double win. Lucas: Right. The breakdown tells you not just where the money is, but who controls it. If the line items are all operational, the buyer might be a cost-center manager. If there's a line for 'strategic initiatives,' that's a different conversation. Luna: I think that's the most underrated part of this tactic. It's not about the numbers — it's about the story the numbers tell. Who's involved, what's prioritized, what's flexible. Lucas: Yeah. And the best part is, it's a repeatable move. You don't need a special personality or a silver tongue. You just need the curiosity to ask, and the trust to have earned the answer. Luna: Alright, I'm convinced. Next time I hit a budget wall, I'm trying the breakdown approach. Lucas: Let us know how it goes. For now, that's it for Closing the Deal. We'll be back next time with another tactic that turns stalled conversations into closed business.