Budget Conversation Swipe File

Raising Budget Early + Handling "We Don't Have Budget"

Budget conversations feel pushy only when they're disconnected from pain. Every script below is built to follow a stated problem — never lead with money before the buyer has said, in their own words, that the problem is worth solving.

---

Part A — Raising Budget Early (First Discovery Call)

The universal bridge line (use this before any of the scripts below):

"This sounds like a real problem worth solving — so I don't waste your time later, can I ask a couple of practical questions about how something like this would actually get funded at [Company]?"

A1. Inbound lead (they came to you)

"You reached out, so I'm guessing this is already a priority somewhere internally. Has budget already been set aside for solving this, or is this still at the 'building the case' stage?"

A2. Outbound call that turned into discovery

"Before we go further — I want to be respectful of your time and mine. If we get to the end of this and it's a fit, is there a realistic path to funding it this year, or would this be more of a 'let's build the case for next year' conversation? Either is fine, I just want to pace this right."

A3. Referral / warm intro

"[Referrer] mentioned this has been a pain point for a while. Has anyone put a number on what it's costing you today? That usually tells us pretty quickly whether budget is the easy part or the hard part here."

A4. After the pain is quantified in-call

"You said this is costing you roughly [$X / Y hours] a month — has that number been shared with whoever controls budget, or is that new information?"

---

Part B — Responses to "We Don't Have Budget"

B1. "There's no line item for this yet."

"That's normal at this stage — most of the deals I work on don't start with a line item, they start with a business case that creates one. If I put together a one-pager tying this to the cost you just described, would that be useful for you to bring to whoever approves new spend?"

B2. "Budget's frozen this quarter."

"Got it — quarters end, freezes lift. Two questions: when does the freeze typically ease, and is this something that would need to compete with other requests once it does, or would it move quickly given the impact you described? I'd rather build a plan around the real timeline than pretend it's urgent when it isn't."

B3. "That's not my budget, it's [other team]'s."

"Makes sense. Given what you've told me about the impact, would it be worth the two of us putting together something for [other team's owner] together, or would you rather make that intro and let me walk them through it directly?"

B4. The soft stall — "Let's revisit next quarter."

"Happy to. Two things so I plan around it properly: is 'next quarter' a real budget cycle event, or a way of saying 'not a priority right now'? Either answer is useful to me — I just don't want to chase a date that isn't real."

B5. Genuine no-budget-this-fiscal-year

"Appreciate the honesty — that's actually useful. A few options: we could scope something smaller that fits what does exist today, we could build the business case now so it's ready the moment next year's budget opens, or we park it and I check back at [specific month]. Which of those is most useful to you?"

---

The Value-Objection Reframe

If "no budget" comes up before any pain has been established, it's very often a value objection wearing a budget costume. Use this:

"Totally fair — and to be honest, if I haven't shown you why this is worth funding yet, 'no budget' is the right answer. Can I ask two questions about what this is costing you today before we talk about cost of fixing it?"

Then return to Situation & Problem Discovery before raising budget again.