How to handle the "bad timing" objection
"Now is not a good time" is one of the most common stalls, and it is genuine about half the time. The job is to find out which.
A vague "circle back later" with no anchor usually means the deal was never qualified. Test it rather than accept it.
Short answer
Handle "bad timing" by testing whether it is a genuine timing issue or a polite brush-off: ask what would need to change for the timing to be right. If real, quantify the cost of waiting and set a concrete follow-up tied to the trigger. If it is a soft no, gently surface the real objection so you can address it or disqualify.
How to respond
Test, quantify, or disqualify.
- Test it: "What would need to change for the timing to be right?" A concrete answer means real timing; a vague one means a soft no.
- Quantify the cost of waiting: if the problem is costing money now, delay has a price worth naming.
- Anchor a follow-up: tie it to the specific trigger or date, not "sometime next quarter."
- If it is a soft no, surface the real objection: "Is it truly timing, or is there a concern about fit or value?"
Real timing vs soft no
Real timing has a specific reason and date: a budget cycle, a launch, a reorg. A soft no is vague and open-ended. Treat real timing as a nurture with a dated follow-up, and treat a soft no as an objection to surface and address now.
How Ardovo runs this
Ardovo turns this from a slide no one opens into how the work actually happens. The stages, exit criteria, and plays live in the deal object, and Rook flags any deal that skips a step, drafts the next artifact, and keeps the data honest, so timing objections get tested and dated gets followed instead of forgotten.
Frequently asked questions
How do I handle "now is not a good time"?
Test whether it is real by asking what would need to change for the timing to be right. A concrete answer means genuine timing, so quantify the cost of waiting and set a dated follow-up tied to the trigger. A vague answer usually signals a soft no you should gently surface.
Is a timing objection usually genuine?
About half the time. Real timing objections have a specific reason and date, like a budget cycle or a launch. Vague, open-ended ones are often polite brush-offs hiding a concern about fit or value. Testing the objection tells you which, so you respond appropriately.
How do I follow up on a real timing objection?
Anchor the follow-up to the specific trigger or date the buyer named, not a vague "next quarter," and quantify the cost of waiting so the delay has a real price. Set a reminder tied to the event so you reach back out while the timing is finally right.