I once had a prospect tell me "we don't have budget" while sitting in a brand new office with a catered lunch being delivered in the background.
They had budget. They just didn't have budget for me.
That's the thing about "we don't have budget" - it's almost never literally true.
What "No Budget" Actually Means
In my experience, budget objections fall into three categories:
1. "I don't see enough value to justify the price"
This is the most common. They have money, but they're not convinced your solution is worth it. This is a value problem, not a budget problem.
2. "We have budget, but it's allocated to other priorities"
Every company has finite resources. They might genuinely see value but have already committed funds to other projects. This is a timing and priority problem.
3. "I'm not interested and this is an easy way to end the conversation"
Similar to "I'm not interested," budget can be a polite brush-off. They don't want to say no directly.
Each of these requires a completely different response. Offering a discount only addresses scenario 1, and even then it's usually the wrong move.
If budget is an excuse rather than the real objection, see our guide on handling "I'm not interested", which covers similar dynamics.
Why Discounting Is Almost Always Wrong
When you immediately discount, you:
- Confirm that your original price was inflated
- Train the prospect to always ask for discounts
- Start the relationship with them having power over you
- Reduce your commission for no reason
- Attract price-sensitive customers who will churn
I've seen reps cut 30% off their price at the first mention of budget. That deal still took three months to close and the customer churned after one year. The discount didn't solve their real objection, it just made them feel like they "won" something.
Research on pricing conversations shows that successful sellers hold price significantly longer than average performers before discussing discounts.
How to Diagnose the Real Problem
When someone says "we don't have budget," I ask one of these questions:
"When you say no budget, do you mean it's not in this year's plan, or that this isn't a priority you'd allocate funds to?" This separates timing from interest. If it's timing, you can work with that. If it's priority, you need to do more value-building.
"If budget weren't a factor, is this something you'd want to move forward with?" If they say yes, budget really is the issue. If they hesitate or give a vague answer, budget isn't the real objection.
"How are decisions like this typically budgeted at [Company]? Is it discretionary or does it need to be planned in advance?" This gets them talking about their buying process, which tells you a lot about how to navigate the deal. Good questions reveal what's really going on beneath the surface objection, moving the conversation from "no" to "not yet."
If It's a Value Problem
When the real issue is that they don't see enough value, more features and more slides won't help. You need to connect your solution to a problem they actually care about.
Ask: "What would solving [problem] be worth to you?"
If they can't quantify the problem, they won't be able to justify any budget. Your job is to help them see the cost of inaction.
I once had a prospect tell me $50k was "way outside their budget." Then I asked how much a single bad hire cost them (they'd had two recently). When they calculated $150k+ in wasted salary, recruiting fees, and lost productivity, suddenly $50k for better hiring tools seemed reasonable.
Nothing about my price changed. Their perception of value changed.
If It's a Priority Problem
Sometimes the value is clear but the timing is wrong. Maybe they just signed a contract with a competitor. Maybe their Q4 budget is locked. Maybe they're mid-acquisition.
These are real constraints. The right response:
"That makes sense. When does your next planning cycle start? I want to make sure we're on your radar for when budget does open up."
Stay in touch. Provide value in the meantime. Don't be pushy. Some of my best deals came from prospects who said "no budget" six months before signing.
The key is staying in touch without becoming annoying: add value with each touchpoint and respect their timeline. Long sales cycles test your patience, but handling the inevitable rejection along the way gets easier with practice.
If It's a Brush-Off
When "no budget" is really "not interested," no amount of objection handling will help. You're better off qualifying out cleanly.
"I hear that a lot, and sometimes it means we're not the right fit. Is this genuinely a budget timing issue, or is this just not a priority for you right now?"
Give them permission to say no. You'll save time and they'll respect you more for it.
The One Time To Discuss Price
If budget is genuinely the blocker - they see value, they want to buy, they just can't afford your standard pricing - then you can have a pricing conversation.
But never discount without getting something:
- Longer contract term
- Case study rights
- Referral introduction
- Reduced scope
- Payment upfront instead of monthly
"Our pricing reflects the full implementation. If budget is tight, we could look at a phased approach - start with [core feature] and add [additional features] when budget opens up. Would something like that work?"
You've preserved your pricing integrity while giving them a path forward.
What I Learned From Tracking Budget Objections
I analysed 200 deals where "budget" was cited as an objection. Here's what happened:
- 42% eventually closed at full price (it was a timing/priority issue)
- 31% were actually just not interested (budget was an excuse)
- 18% closed with some modified scope or terms
- 9% genuinely couldn't afford it and never closed
The majority were never really about budget. The deals that closed at full price just took longer because I had to build more value or wait for better timing.
The lesson: assume budget is a symptom until you've proven it's the disease.
HubSpot's sales research confirms that most deals stall for reasons other than price. Budget is often the easiest excuse, not the real blocker.