"No Budget Until Next Fiscal" — Real Stall, Real Answer, and How to Tell Which You Got

The objection everybody accepts too fast

Here is how it usually goes. You have run a decent discovery call, the champion is nodding, you ask about next steps, and you get this:

"Look, I like this. But we have no budget until next fiscal."

And the rep says, "Totally understand. Let's reconnect in Q3." Deal gets pushed, then pushed again, then quietly marked Closed Lost — No Budget. Nobody argues with it in pipeline review, because "no budget" sounds like weather. It is not something a rep did wrong. It just happened.

That is exactly why it is the most useful objection in the business to get good at. It is the one nobody inspects. A good chunk of the deals sitting in your CRM under that label were never budget problems at all. They were value problems that the buyer was too polite to name.

The skill is not having a clever comeback. The skill is telling the two apart in under two minutes, on the call, before you build a follow-up plan for the wrong one.

Two different objections wearing the same coat

When someone tells you the money is gone until the new fiscal year, one of two things is true.

It is a capital calendar constraint. The organisation genuinely allocates money once a year, the allocation happened, your line item was not in it, and the person you are talking to cannot conjure funds no matter how much they want to. This is real. I have sold into environments where it is absolutely real, and where trying to argue your way around it makes you look like you have never worked inside a company with a finance function.

Or it is a soft no. The buyer does not want to say "I am not convinced this is worth doing" or "I do not think I can win this internally" or "my boss will ask me why and I do not have a good answer." So they reach for the one objection that cannot be argued with and is nobody's fault. Budget is the polite exit. It ends the conversation without either of you losing face.

The worst outcome is not getting the objection. The worst outcome is treating path two like path one — building a beautiful nurture sequence, a calendar reminder for July, and a follow-up that starts "Hi, checking in as discussed, has budget freed up?" for a deal that was dead on the call and would have told you so if you had asked one more question.

The two-question test

Two questions. Ask them in this order, in the same breath, without a pause for reflection in between. You are not interrogating. You are being helpfully practical, which is what a good seller sounds like anyway.

Question one: the calendar question

"That makes sense — when does your fiscal year actually start, and when do budget requests for it have to be submitted?"

Notice the second half. Anyone can tell you their fiscal year starts in July. That is public information at most companies and it is the answer a person gives when they are reaching for a shield. The submission deadline is different. That is operational detail, and it lives inside the head of someone who actually participates in planning.

A buyer facing a genuine constraint answers this fast and boring. "Fiscal starts July 1, but submissions go to finance in early April, and my director wants everything from us by the middle of March." That is a person describing their real life. Nobody invents that.

A buyer using budget as a shield gets vague. "Uh, next year sometime. I'd have to check." Or they answer the first half and skip the second half entirely. That is your tell.

Question two: the isolation question

"Okay, that's helpful. Let me put the money completely to one side for a second. If the funding were already sitting in your budget today — signed off, no approval needed — is this something you'd move forward with, or would you still want to see something else first?"

This is an old question and it works because it is fair. You are not pressuring anyone. You are giving them a clean, consequence-free way to tell you the truth.

The real-constraint buyer says yes, and then keeps talking. "Yeah, honestly, if I had the money I'd do it now, the problem is I've got two other things ahead of it in the queue and I already spent my discretionary on the migration." More detail than you asked for. That is what conviction sounds like.

The soft-no buyer hedges. "I mean... probably. I'd want to see how it fits with what we already have." Or, "I'd need to get the team's input." Or the flat, cheerful "Yeah, definitely" with nothing after it — no detail, no complication, no queue. When someone genuinely wants a thing, they tell you what is in the way of it. When they do not, they just agree with you so the call can end.

The third tell, which you get for free

Listen for whether they name a person. Real budget constraints come attached to a name and a process. "Priya owns the capital plan." "It goes to the ops committee, they meet monthly." A soft no is populated entirely by pronouns. They. Us. The business. Finance. If nobody in the story has a name, there is no story.

One more thing worth separating out: "we have no budget" and "we have budget but it's allocated" are not the same sentence. Allocated money can be reallocated. That is not a calendar fight, it is a priority fight, and priority fights you can win this quarter. Ask which one it is.

Path one: the constraint is real, so build the pre-commit

Good. You are not blocked, you are just early. Now the job changes from selling to positioning, and positioning has a deadline that is much sooner than you think.

The rookie mistake is to aim at the fiscal start date. If their year starts July 1 and you circle back in June, you have missed it by three months. Budget requests get written, argued over, cut and finalised long before the money appears. The date that matters is the submission deadline you asked about in question one. Everything you do now works backwards from that.

Here is what I want in place before that date.

A written business case they can carry. Not a proposal. Not a deck with your logo on every page. One page, in their language, that your champion can paste into their own submission without editing it. What problem it solves, what it costs, what it saves or unlocks, what happens if it is not done. The numbers on it must be their numbers, gathered from them in discovery, phrased the way their finance team phrases things. Your champion is going to have to defend this document in a room you will never enter. Write it for that room.

A scoped, staged start. "What I'd like to do is get us to a point where, on the first day of your new fiscal, this is a signature and not a conversation." Then define exactly what that signature covers — scope, start date, term, price — and put it in writing now, while you have their attention and before the requirements drift.

Something small that does not need the big budget. This is where a lot of these deals actually get unlocked. A scoped pilot, a limited-seat deployment, a paid assessment, sometimes just the security review and procurement onboarding done in advance. Ask directly: "Is there any discretionary spend at your level, or anything under an existing renewal envelope, that could cover a limited pilot before the new year?" Sometimes the answer is yes and you have a deal this quarter. When the answer is no, you have still learned that the constraint is genuine, because someone with a real budget and a real problem would have found the money.

Something in exchange for the wait. You are agreeing to hold scope and price for months. That is worth something. Ask for the exec sponsor introduction, the security questionnaire completed now, agreement on pilot success criteria, or a date in the diary to review the business case before submission. If your buyer will not trade anything for the wait, you may be back in path two after all.

The buyers where "next fiscal" genuinely means something

Some sectors are structurally incapable of buying off-cycle, and reps who came up selling software to mid-market tech companies do not always believe this until they have lost a year to it.

Regulated utilities. Spend has to fit inside approved plans, and in some cases inside what the regulator has agreed can be recovered. When a utility buyer tells you the capital plan is closed, they are not negotiating. The line to use is: "Understood — is this something that sits in the approved plan, or is it small enough to live in operating spend?" That single question sorts a two-year wait from a two-month one. When the deal does land and the technical evaluation goes your way, the pressure moves straight to price, which is why I wrote the energy and utilities pricing negotiation script for holding your number after the technical win — the budget conversation and the discount conversation are the same conversation, separated by a few months.

Public sector and local government. Financial years, committee meeting dates, procurement thresholds and framework agreements all constrain when money can move, and none of them care about your quarter end. The useful thing about council buyers is that the calendar is usually published, so you can do the homework before you ever dial. If you are working these accounts cold, the approach in the government and public sector cold call script for getting a council officer to book twenty minutes is built around exactly that — respecting the process instead of pushing against it.

Hospitals and health systems. Capital committees meet on a schedule, clinical priorities outrank almost everything, and the person who loves your product is frequently not the person who releases funds. Ask: "Does this go through capital or can it be handled operationally? And when does the committee next meet?"

Manufacturing. Capex is often tied to plant schedules and shutdown windows, so the constraint is not only financial, it is physical. "When's your next planned shutdown?" is a budget question in disguise. And when the plant engineers have already picked you, procurement will still come at your price hard, which is the situation the manufacturing pricing negotiation script is written for.

In all four, saying "I understand, that's how the capital cycle works, let's plan around it" buys you more credibility than any amount of urgency-creation. You sound like someone who has sold in their world before.

Path two: the value case is weak, so go back to consequence

If the isolation question got you a hedge, do not build a nurture plan. Build a case, right now, on this call.

And do not re-pitch. Re-pitching is what everyone does and it confirms the buyer's suspicion that you were never listening. Instead, go back to consequence, and make them do the arithmetic out loud.

"Can I ask you something before we park this? You told me earlier that the team is spending most of Monday rebuilding that report by hand. If we wait until the new fiscal year, that is what — three quarters of Mondays? What does that actually cost you, in people and in the decisions you're making late?"

Then stop talking. This is the whole technique. The number has to come out of their mouth, because a number you supply is a number they can dismiss, and a number they supply is a number they have to live with. I will not put an invented figure in a business case and neither should you — the only credible cost of waiting is the one the buyer calculated themselves.

If they produce something — headcount, overtime, churned customers, a compliance exposure, a delayed launch — you now have the raw material for path one, and the business case writes itself. "Right. So the question isn't really whether you have budget in July. It's whether it's worth carrying that cost for nine months when there might be a smaller way to start sooner."

If they cannot produce anything, you have your answer, and it is a genuinely valuable answer. There is no deal here. There is a pleasant conversation with someone who found your product interesting. Say thank you, ask who in the organisation feels this problem expensively, and go spend your week on someone whose pain has a price tag.

When they offer to sign today for a big discount

Watch for this one, because it is the most revealing move a buyer makes.

You have accepted the fiscal constraint, you are politely building for next year, and suddenly: "Actually — if you could come down significantly on price, I think I could find something this quarter."

Read what just happened. The money exists. The calendar was never the real constraint, or at least not an absolute one. What they were telling you all along was that at your price, it was not worth the internal fight. Now they are offering to have the fight for a fee.

So do not celebrate and do not fold. The line I would use:

"I appreciate you looking for a way to make it work. Before I take that anywhere — help me understand what changed. Earlier the issue was that the money wasn't there until July. If it can be found now, is it a budget question or a price question? Because those get solved differently."

Then hold. A discount that large does not buy you a deal, it resets your price permanently, tells the buyer your list number was decoration, and guarantees that every renewal and expansion starts from the discounted floor. If the value case is strong enough that they want it now, it is strong enough to be paid for. If you must move on price, move on term, scope or payment timing in exchange — never on price alone, and never without getting something back. That principle holds identically in clinical buying, where the pressure arrives after the technical decision is already made, which is the exact scenario the healthcare pricing negotiation script for holding your number after the CMIO has chosen you walks through.

Staying alive between now and then

One last thing, for the deals that legitimately go into the drawer until the new year.

Do not "check in." Nobody has ever been glad to receive a check-in. Instead, agree a specific reason to talk on a specific date: the business case review, the pilot scoping session, the internal readout before submission. Put it in both calendars before you hang up. Then between those touchpoints, send things that make your champion look informed inside their own building — how a similar team structured their rollout, what their peers asked in procurement, what changed in your product that affects their scope.

And re-qualify every single time. Champions move roles. Priorities shift. The fiscal year that was going to fund you gets cut before it starts. A deal parked for nine months is not a deal, it is a hypothesis, and you should be testing it on every call rather than assuming it survived the winter.

If you want to get sharp at this, the fix is repetition under a bit of pressure, not more reading. Run the two-question test out loud until it comes out sounding curious instead of forensic, because the difference between those two tones decides whether you get the truth. That is what I would practise next in DrillCall — take the budget stall, run it against a buyer who genuinely cannot spend and then against one who is being polite, and learn to hear which one you are talking to before you decide what to say.

The reps who beat this objection are not the ones with a slicker rebuttal. They are the ones who found out, in the first two minutes, which conversation they were actually in.