A budget is a box someone drew before they met you. The objection says your number doesn't fit the box; it says nothing about whether they think the thing is worth it. Often the value case has already landed, and what's left is logistics.

It's the sibling of “it's too expensive,” and the diagnosis matters: expensive is value, budget is allocation. Budgets move, split, and roll over for things organizations want; value objections don't respond to payment terms at all.

If what they actually said was closer to “it's too expensive”, that's the value objection, a different conversation with a different counter. That page is here.

Test the constraint before solving it: “If budget were the only thing in the way, what would we do about that together?” Then listen to the shape of the answer. A fake constraint comes back with a new objection, which was the real one all along. A real constraint comes back with logistics: names, cycles, approval steps. Logistics you can plan around.

If it's real, negotiate the shape, not the size: timing across quarters, a phased start, scope that fits this year's box with the rest committed for next. Structure concessions hold their shape. A price cut just resets the starting point.

Find out whose box it is. The person quoting the budget often didn't draw it, and “who would we talk to about the exception?” recruits them into the workaround instead of leaving them defending the wall.

“We only have so much set aside for this.” A real number is progress. Build the version that fits it, and price what got cut so the gap has a name.

“Maybe next fiscal year.” Budget plus calendar. Book the planning-cycle date and ask what they need from you before it.

“Can you do it for half?” That's not a budget, that's an anchor. Different objection, different counter: ask what's behind their number.