"Call Me Back in Six Months" — The Calendar Stall and What's Underneath It

A no that arrives with a date on it

There is a specific sound a rep makes after a call that ended with "call me back in six months." It's relief. Nobody hung up. Nobody said the deal was dead. There's an action to take, a task to log, a date to put in the CRM. It feels like progress because it has a shape.

It is almost never progress.

The calendar stall is the most comfortable objection in the business, and that is exactly what makes it dangerous. A flat "we're not interested" gets worked. A rep hears that and either pushes back or moves on, and either way the pipeline stays honest. But a date-shaped brush-off slides straight past the part of your brain that checks whether something is real. You write down the month. You feel like you did your job. Six months later you call back and the person has moved roles, or doesn't remember you, or says "actually, now isn't great either."

I have watched this happen on more calls than I can count, in my own selling and in the calls I listen back to. The rep gets a date, thanks them, and hangs up. Nobody asked the only question that mattered.

Why it's always six months

Notice that it is rarely five months. Rarely seven. It is six, or it is "the new year," or it is "next quarter." These are round numbers, and round numbers are a tell. Real timelines are lumpy. Real timelines sound like "we're locked in until the substation work finishes in March" or "budget resets in April but the spec has to be in by February."

Six months is the length of time that feels long enough to make you go away and short enough to feel polite. It's a socially acceptable way of ending a conversation without the friction of saying no. Most of the people who say it are not lying to you. They just don't want the discomfort of a refusal, and they have learned that a date makes the discomfort disappear.

Which means the phrase carries almost no information on its own. It could be a genuine capital cycle. It could be a fiscal reset with a real gate on it. It could be a person who decided in the first thirty seconds that they didn't want this and has been looking for an exit ramp ever since. Three completely different situations, one identical sentence. Your job is to tell them apart before you hang up, because after you hang up you never will.

The one question

Here it is:

"Makes sense — what changes in six months that isn't true today?"

That's it. Delivered flat, curious, no edge on it. You are not challenging them. You are asking them to describe the future, and the future is very hard to describe if you made it up ten seconds ago.

The question works because it does not attack the timeline. If you say "why six months?" it sounds like you don't believe them, and people defend positions they are challenged on even when they don't hold them. "What changes" assumes the timeline is real and asks them to fill in the mechanism. A person with a real mechanism will hand it to you immediately and in detail. A person without one will stumble, generalise, or repeat the date back at you.

Ask it and then stop talking. This is the part reps get wrong. The silence after that question is where the whole thing gets decided, and if you fill it with "...because I know budgets can be tricky this time of year," you have just handed them a reason and they will take it.

What real sounds like

A real timeline has nouns in it. Specific ones.

"The asset management plan submission closes in the autumn, and we can't commit spend against anything that isn't in it."

"We're mid-way through an ERP migration and IT has frozen every new integration until it's done."

"The line is running flat out until the summer shutdown. I physically cannot take equipment down before then."

"Our capital committee meets twice a year. The next one is in November and the paper has to be with them six weeks prior."

Every one of those has a named event, a named constraint, and usually a named person or body. You could draw it. That's a real timeline, and it deserves a completely different treatment from a stall — I'll come to that.

What a soft no sounds like

"Just, you know, things are busy right now."

"We'll be in a better place then."

"Let's see where we are."

"I'd have a better idea of where we're at after the summer."

No nouns. No mechanism. The sentence is made entirely of atmosphere. When you hear this, the six months is not a timeline, it is a door closing gently so nobody has to hear the slam.

And that is genuinely useful information — as long as you find it out now. A soft no you have identified is worth more than a fake yes you're carrying, because you can go and spend that time on someone else.

What to do when it's a soft no

Don't argue with it. You will not talk someone out of a feeling they can't articulate. What you can do is make it cheap for them to be honest, and then either recover the conversation or release it cleanly.

The line I like:

"Totally fair. Can I ask a slightly awkward question — is six months a real thing in your world, or is it more that this isn't a priority right now? Either is fine, I'd just rather know than chase you."

People answer this honestly far more often than reps expect, and the reason is that you gave them permission. You named the second option yourself and you told them it was acceptable. Most of the discomfort in saying no to a salesperson is the fear of the follow-up fight. Remove the fight and you get the truth.

One of two things happens. They say "honestly, it's not a priority," and now you have a clean answer and a decision to make about whether to nurture or drop. Or — and this happens more than you'd think — they tell you the real objection. It's price. It's a bad experience with a competitor. It's that their boss already picked someone. That is the objection you actually needed, and you would never have got it from a task in the CRM dated six months out.

If they give you the real objection, you are back in a live conversation and you handle it like any other. If they confirm it's a soft no, thank them and mean it. Then ask one last thing: "Who in the business would this be a priority for, if not you?" You lose nothing and occasionally you get a name.

Three responses, ranked by what they actually produce

Say the timeline holds up. It's real, or real enough. You now have three options and reps almost always pick the worst one.

Third: the CRM task

"Great, I'll set a reminder and reach out in six months."

This is what most people do and it produces almost nothing. You are relying on a future version of yourself to run a cold call into a warm-ish contact who has forgotten the conversation. Between now and then the person may change role, the project may get pulled forward or killed, and a competitor with a live meeting in the diary may have already written the spec.

The deeper problem is that a reminder puts all the effort on you and none on them. A commitment that costs the buyer nothing is not a commitment. It's a wish.

If this is genuinely all you can get, take it. But recognise what it is: you converted a conversation into a lottery ticket.

Second: the trade

Better is to leave with something that keeps you present without requiring a meeting.

"Happy to come back then. Two things while I'm here — first, when the plan goes in, who else touches it besides you? And second, is it useful if I send you the way three other network operators structured the business case for this? Not a brochure, just the shape of it. If the paper's due in the autumn you'll be writing it in the summer."

You've done two things. You've mapped a bit of the buying group, and you've attached yourself to the artefact they will actually have to produce. Business cases, specs, capital papers — these are painful documents and the person writing them is grateful to anyone who makes them shorter.

This is a real improvement on a reminder because it creates a reason for contact that isn't "just checking in." But it still doesn't put anything in a diary.

First: book it live

The best response is to stop promising to reach out and start booking.

"Perfect — let's not leave it to me remembering. What does the week of the 14th look like for you? I'll put twenty minutes in now for then. If the timeline moves, move the meeting."

Every rep I have watched flinch at this has flinched for the same reason: it feels presumptuous to book something half a year out. It is not. Senior people book things a long way out constantly. What feels strange to an SDR feels completely normal to someone who plans in fiscal years.

And the acceptance or refusal of that booking is itself a test. Someone with a genuine cycle will often say yes, because a diary entry costs them nothing and saves them the mental load of remembering you. Someone who was brushing you off will suddenly find reasons why they can't commit that far ahead — which tells you what you needed to know, kindly and without a confrontation.

Offer the escape hatch explicitly. "If the timeline moves, move the meeting" removes the last bit of resistance, because now the diary entry isn't a promise about the project, it's just a placeholder. People accept placeholders.

One practical note: send the invite while you are still on the phone, and put a one-line agenda in the body. Not "catch up." Something like "20 mins — where the capital paper landed and whether there's a fit." Six months from now, that line is the only thing standing between your meeting and a decline.

When it's a real capital cycle

Some industries genuinely run on long clocks. Utilities work to regulatory determination periods and asset management plans. Public sector buyers work to committee calendars and procurement thresholds that don't care about your quarter. Manufacturers plan around shutdowns because you cannot take a line down to install something on a Tuesday in March.

In these worlds, "six months" is frequently the honest answer, and treating it as a stall makes you look like you don't understand the business. This is why the discovery work matters more than the objection handling. If you have already asked the questions in the energy and utilities discovery playbook about where they are in the plan cycle and who signs off capital, you will not be surprised by the timeline — you will have predicted it, and you can bring it up before they do. Saying "I assume nothing moves until the next plan submission, so I'm not going to pretend otherwise" buys you more credibility than any close.

The same is true earlier in the process. A cold call into an asset management lead that ignores the determination cycle gets brushed off in the first fifteen seconds, which is why the energy and utilities cold call script opens on the constraint rather than the product. Public sector is even more rigid — a council officer's timeline is set by a committee schedule they don't control, and the government cold call approach is built around getting twenty minutes inside that reality rather than fighting it. In manufacturing, the shutdown calendar is the whole conversation, and the manufacturing discovery questions exist to find the maintenance window before you propose anything that needs one.

When the cycle is real, the game changes from "how do I speed this up" to "how do I make sure I'm the default when it opens."

Earn a small piece of work now

The strongest thing you can do inside a long cycle is get a small amount of work done before the big decision exists.

Not a pilot necessarily — pilots are expensive to approve and can trigger the same procurement machinery you're trying to get ahead of. Something smaller. A site walk. A data pull on one asset. A half-day workshop with the maintenance team. A review of the draft spec. Anything that puts you inside the building doing something useful while the clock runs.

The ask sounds like this:

"If nothing can be bought until the autumn, fine. But someone has to write the requirement, and whoever helps write it usually shapes it. Would it be useful if I spent an afternoon with your team on site between now and then, no cost, so that when you do write it you're writing from something real rather than from vendor brochures?"

Two things make this work. It costs them no budget, so it doesn't touch the gate that's blocking you. And it is framed around their output — the requirement, the spec, the paper — rather than your product.

When the cycle opens, one vendor has been in the building for months and the others are cold-calling. That's not a trick. That's just having been useful earlier than everyone else.

The habit to build

None of this is complicated. What makes it hard is that the calendar stall arrives at the exact moment your guard is down, because it sounds like a yes. You have to be ready to ask an uncomfortable-feeling question at the precise moment you feel relieved.

That's a reflex, and reflexes come from repetition, not from reading. If I were an SDR working long-cycle accounts right now, I'd spend a week running the same objection over and over until "what changes in six months that isn't true today?" comes out of my mouth without me choosing it — and until I can sit in the silence afterwards without flinching. That's the sort of thing we built DrillCall for: putting the same objection in front of you enough times that your first instinct stops being gratitude and starts being curiosity.

Until then, one small change. Next time someone gives you a date, don't write it down. Ask what happens on it. You'll lose a few pipeline entries that were never real, and you'll book a few meetings that otherwise would have quietly evaporated. That trade is always worth making.