A dependency needs to be completed
The project cannot start until a migration, hire, or reorganization is complete.
Clue: The prospect names an external action and an identifiable owner.
Timing and priority
“This isn’t the right time.”
Responding to “this isn’t the right time”
Timing may depend on a project, workload, risk, or simply a low priority.
What the prospect may really mean
The statement alone is not enough. Look for the meaning that fits the clues already present in the conversation.
There’s not enough capacity
The team sees value in the topic but can’t take on another deployment.
Clue: The objections are about time, resources, or user availability.
The urgency hasn’t been established
The problem exists, but its consequences aren’t enough to displace other priorities.
Clue: No event or cost of maintaining the status quo makes action necessary.
The delay is a way to avoid saying no
The prospect doesn’t want to move forward and uses timing as a more comfortable way to say so.
Clue: They can’t name a trigger, date, or condition for revisiting the topic.
Dig deeper before responding
Choose a question, listen to the full answer, then paraphrase it. An objection is not handled by reciting a questionnaire.
- 1
« What needs to change for the timing to be right? »
- 2
« What project or constraint needs to be resolved first? »
- 3
« What would be the impact of waiting until then? »
- 4
« Who can confirm that the condition for revisiting the topic has been met? »
- 5
« What date is tied to a real event rather than a courtesy follow-up? »
Mistakes that shut down the conversation
Creating false urgency
A promotion or pressure that isn’t relevant to the situation won’t change the prospect’s priorities.
Asking for an arbitrary date
A date without a trigger often leads to the same conversation again a few months later.
Downplaying the work involved in a change
The prospect needs to be able to explain who will do the work and under what conditions.
Several ways to respond
The right approach depends on what the objection means. These examples are starting points, not scripts to impose.
Identify the trigger
When the delay appears to be tied to a real dependency.
“What needs to be completed or decided for the timing to be right?”
The follow-up is tied to an observable event.
Measure the cost of waiting
When the problem is acknowledged but not a priority.
“If you wait until that date, what impact will the problem continue to have?”
The prospect evaluates the trade-off between acting and waiting.
Test whether the delay is real
When no condition for revisiting the topic can be identified.
“Is this really a timing issue, or just not a high enough priority right now?”
The question offers two acceptable interpretations and discourages polite brush-offs.
Two possible conversations
These dialogues are illustrative. They show the logic of diagnosis, not a one-size-fits-all formula.
A real dependency
The company is completing a CRM migration.
Prospect
« It’s not the right time while the migration is underway. »
Sales rep
« What step in the migration needs to be completed before we revisit this? »
Prospect
« Manager training, scheduled for late September. »
Sales rep
« Let’s check in right after that training with the person responsible for the rollout. »
Key takeaway: The date is based on an event and an owner, not a guess.
A low-priority project
The prospect can’t name any expected change.
Prospect
« It’s simply not the right time. »
Sales rep
« What would make the timing better? »
Prospect
« Honestly, nothing specific. We have other priorities. »
Sales rep
« Thanks, that’s clear. I’d rather close this out than schedule a follow-up without a reason. »
Key takeaway: An honest disqualification is better than an artificially inflated pipeline.
What Objeqo can detect in real time
- Words related to timing, workload, or a dependency
- Delay without a concrete event
- A competing project already identified as a priority
Contextual analysis
Objeqo connects the delay to projects, constraints, dates, and impacts already captured in the call memory.
How Objeqo helps
Objeqo suggests identifying the trigger, assessing the cost of waiting, or checking whether the project still warrants a next step.
When not to step in
If the trigger, date, and owner are already clear, Objeqo avoids asking the same timing question again.
Frequently asked questions
What follow-up date should I choose?
A date just after an event that will actually change the prospect’s capacity or priorities.
Should I make the case for urgency?
Only based on consequences the prospect has already acknowledged. Don’t manufacture sales urgency.
When should I walk away?
When the prospect sees no trigger, no impact from waiting, and no reason to revisit the topic.
Continue with a related objection
Timing and priority
“Call me back later.”
The prospect may be unavailable, waiting for an event, or putting off a topic that doesn’t yet deserve their attention.
Price and budget
“We don’t have the budget.”
A budget constraint may be real, temporary, tied to the wrong cost center, or a sign that the priority is too low.
Interest and change
“We’d rather not change anything for now.”
The status quo protects habits, stability, responsibilities, and sometimes the decision-maker’s internal credibility.
On your next call