Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / The Rep Who Won by Asking for a Budget Reset
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 this right now.' Most reps hear that and either discount, or walk away, or try to squeeze into whatever tiny pool of money exists. But I came across a story recently about a rep who did the exact opposite — he asked the buyer to forget their existing budget entirely and build a new one from scratch. Luna: Wait — he asked them to ignore the budget they had? That sounds like a good way to get shown the door, not to close a deal. Lucas: That's exactly what I thought when I first heard it. The rep was selling a mid-market SaaS platform — think project management plus analytics — into a company with about five hundred employees. The buyer was a VP of operations, and she told him straight up: 'We have zero budget allocated for new software this fiscal year. It's not happening.' Luna: Classic hard no. Most reps would start talking about payment terms or a smaller pilot. Lucas: Right. And this rep had done that before, and it usually led to a tiny deal that barely covered his time. So this time he tried something different. He said: 'I hear you on the budget. But if we could start from a clean sheet — if you had no existing constraints — how much would solving this problem actually be worth to your organization?' Luna: That's a big ask. Most buyers don't want to do that kind of math in a sales conversation. Lucas: And this buyer almost didn't. But the rep had a framework ready. He walked her through three numbers: the cost of the current workflow in hours per week, the error rate that caused rework, and the opportunity cost of delayed projects. She started doing the math out loud. By the end of that call, she had estimated the problem was costing her team roughly eight hundred thousand dollars a year. Luna: Okay, so she realized the cost of doing nothing was almost a million dollars. That changes the conversation. Lucas: Exactly. And the rep didn't even bring up his own price yet. He just helped her build a business case from scratch. Then he asked: 'If you could capture even half of that eight hundred thousand, what would a reasonable investment look like?' She said maybe two hundred fifty thousand. The rep's platform was priced at one eighty. He closed it two weeks later. Luna: So by resetting the budget, he got her to anchor on the value of the solution, not the limitation of her existing line items. That's smart. Lucas: It's a completely different frame. Most buyers come in with a number that's based on what they spent last year, or what's left in a cost center. That number is almost always too small. But if you help them build a fresh case from the ground up, based on the specific value you can deliver, you often end up with a much bigger number — and a much easier close. Luna: There's a psychological principle at play here too — anchoring. If the buyer says 'we have fifty thousand,' you're fighting uphill to get to one fifty. But if you reset the anchor to the value of the problem, you're starting from a much higher point. Lucas: That's exactly it. And the key is that you're not manipulating them — you're genuinely helping them see the full cost of inaction. In this case, the VP later told the rep that no other vendor had ever done that. They all just tried to fit into her existing budget box. Luna: But I can see this backfiring. If the buyer does the math and realizes the problem isn't that big, you've just talked yourself out of a deal. Lucas: Absolutely. That's the risk. If the value you uncover is less than your price, you're done. But if you've done your qualification work upfront — if you know the problem is real and painful — the math usually works in your favor. The rep in this story had already spent three calls understanding their workflow. He knew the numbers would be big. Luna: So this isn't a cold-call opener. You need to have enough context to guide the buyer to the right numbers. Lucas: Right. You can't just walk in and say 'what's your problem worth?' You need to know their operations well enough to ask specific questions. In this case, the rep knew they were using spreadsheets and email for project tracking, and that projects were routinely delayed by three to four weeks. He had those details ready before he ever asked for the budget reset. Luna: It reminds me of the 'puppy dog close' in a weird way — you're letting them experience the logic of owning the solution before they've paid for it. Lucas: Yeah, except here you're letting them experience the logic of the investment. And it works in part because it's so rare. Buyers are conditioned to defend their budget. When a rep says 'forget your budget, let's figure out what this is really worth,' it disarms them. They stop defending and start building. Luna: I want to talk about when NOT to do this. If the buyer has a very rigid procurement process — like a government agency or a highly regulated industry — does this still work? Lucas: That's a great question. It works best in organizations where budget is somewhat fluid — mid-market companies, divisions of larger firms, places where a VP or director has some discretion. In heavily regulated procurement, the budget is often locked by fiscal year and category code. You can still do the value exercise, but it's more about building justification for next year's budget, not immediate reallocation. Luna: So the tactic is really about shifting the conversation from 'can we afford this?' to 'can we afford not to do this?' Lucas: Exactly. And the best part is, once the buyer has written that business case themselves, they become your internal champion. They're not just defending your product — they're defending their own analysis. That's a much stronger position. Luna: And I imagine this works especially well when the buyer is early in their evaluation. If they've already been through three vendor demos and have a number in their head, it's harder to reset. Lucas: Yes. Timing matters. The rep in our story did this on the very first call where budget came up — it was their fourth conversation overall, but the first time she mentioned money. He jumped on it immediately. If he had waited until she had already gotten approval for a smaller amount, the window would have closed. Luna: So the lesson is: when you hear 'no budget,' don't shrink. Get curious. Ask what the problem is worth. Help them build a case. Lucas: Exactly. And I'd add one more thing: after you help them build that case, don't immediately present your price. Let them sit with the number they came up with. In this story, the VP said two fifty. The rep said nothing for a few seconds. Then she said 'well, maybe two fifty is too high — but even two hundred would make sense.' The rep's price was one eighty. He just let her talk herself into a budget that exceeded his price. Luna: Silence really is a sales tool. She was negotiating against herself. Lucas: Exactly. So the whole sequence is: uncover the real cost of the problem. Help the buyer quantify it. Ask what a reasonable investment would be. Then shut up. If you've done the math right, they'll land above your number. Luna: I love this because it's not about tricks. It's about helping someone make a better decision. And it builds trust. Lucas: It does. And it's one of those moves that works because most reps don't do it. It requires confidence and preparation. But for the rep who's willing to ask the hard question, it can turn a 'no budget' into a seven-figure deal. Luna: Alright, so what's the one takeaway for someone listening right now who's about to have a budget conversation? Lucas: Prepare a simple three-question framework before you ever get on the call: What does the problem cost in time? What does it cost in errors or rework? What is the opportunity cost of delay? If you can answer those three things with the buyer's help, you don't need their budget. You'll build a new one. Luna: And if they still say no after that? Lucas: Then it's probably not a budget problem. It's a priority problem. And that's a different conversation. But at least you'll know.