How to respond when a prospect says it is not the right time

Stop the 'check back in six months' loop. Learn how to identify specific business triggers that turn timing objections into concrete follow up dates.

Get started

Short answer

When a prospect says it's not the right time, don't ask to check back in six months. Ask what specific event or milestone would change their priority. That turns a vague objection into a concrete trigger you can track and follow up on.

Why the standard response fails

Most reps are too accommodating when they hit a timing objection. When a prospect says it's not a good time, the instinct is to answer 'I understand, I'll check back in a few months.' That reply feels polite and costs you the lead. It gives the prospect an easy exit and no reason to think about you again.

Checking in isn't a value proposition. If you come back in three months and open with 'just checking in as promised,' you're reminding them that a salesperson is waiting on their calendar. You haven't solved anything. You've marked a date and hoped.

The fix is to move from a time based follow up to a trigger based follow up. A trigger is a specific business event that makes your product necessary, like a database migration going live, a new head of sales starting, or a budget cycle opening. When you know the trigger, your next message answers a current problem instead of asking for attention.

There's a second reason the standard response fails. It tells the prospect you weren't listening. They gave you a reason, even a vague one, and you replied with a calendar. One more question shows you heard the constraint and want to work around it rather than through it.

The check back in Q3 approach

  • I totally understand. I'll reach out again in September to see if things have calmed down.
  • No problem at all. I'll put a note on my calendar to follow up in six months.

The trigger approach

  • I understand. Usually that means a specific project is taking priority. What milestone are you hitting before this becomes a focus?
  • That makes sense. Is there a particular event or date when your team will be ready to look at this again?

How to identify the real trigger

To find the trigger, ask about the work blocking them. People are rarely too busy in a general sense. They're too busy doing one specific thing, and your job is to name that thing out loud so they can confirm or correct you.

Once you know the project, like a CRM migration or a board meeting, you can judge whether your product helps that project or truly has to wait. Sometimes the answer is that your tool would make the migration easier, which means the objection was never about timing. Other times it genuinely has to wait, and now you know why.

Then ask whether the problem you solve is still a priority after that event. If they say no, stop. If they say yes, you have a reason to come back that both of you agreed on, and the next message writes itself.

Keep the question open enough to answer in one line. 'What's taking up most of your team's time right now?' works better than a list of options, because it lets them describe their world in their own words and gives you the phrase to use later.

Example

  1. Prospect

    Thanks for reaching out, but it's just not a good time for us right now.

  2. You

    I understand. Usually when people say that, it's because they're focused on a specific project or goal. Is there a particular milestone you're hitting first?

  3. Prospect

    Yes, we're migrating our entire customer database to a new system until October.

  4. You

    That makes sense. Once that migration is live, does lead scoring become a priority, or is it still secondary to other goals?

  5. Prospect

    It'll be a priority. We'll have clean data for the first time and no way to score it.

Categorizing the not now response

Not every 'not now' is about timing. Some are polite ways of saying they don't see the value. You have to tell a resource constraint apart from a value gap, because the follow up for each one is different.

If a prospect can't name a specific project or milestone, they're probably not interested. If they give a vague timeframe like 'next quarter' with no reason attached, they're pushing you away politely. Pushing harder on timing in that case makes it worse, because you're arguing with a decision they already made.

The table below is how I sort the replies I get. The action column matters more than the meaning column, because the meaning is a guess and the action is something you can do today.

Too busy, no time

Response
Low priority or overwhelmed
Likely meaning
Ask for the specific project taking their time

Next quarter or next year

Response
Budget or planning cycle issue
Likely meaning
Ask what changes when the new budget opens

Not a fit right now

Response
No value perceived
Likely meaning
Stop pushing timing and go back to the problem

We already have a tool

Response
Comparison or contract lock in
Likely meaning
Ask when the current contract renews

Setting the follow up anchor

Once you have the trigger, anchor the follow up. An anchor is a mutual agreement on when and why you'll reappear. It stops you sounding like a pest and makes the next message feel expected rather than random.

Acknowledge the constraint first. When you agree they're busy, they stop defending their time and start talking about their schedule. That shift is what makes the rest of the conversation possible, and it takes one sentence.

Don't set the follow up for the exact day the project ends. People are catching up after a big milestone, and your message lands in their worst week. Aim for a week or two after the event and say why you picked that date, so the reason is on the record.

  1. 1

    Acknowledge the constraint

    Validate their current focus so they feel heard before you ask anything else.

  2. 2

    Isolate the trigger

    Ask for the specific date or event that ends the current constraint.

  3. 3

    Confirm the future outcome

    Ask if the problem you solve will be a priority once that trigger is hit.

  4. 4

    Set the reminder

    Put a calendar alert one week after the event, with the trigger written in the note.

Never ask 'when should I follow up?' Suggest a date based on the trigger they gave you and let them correct it.

What to write when the trigger arrives

The follow up itself has to reference the trigger. If you open with 'just checking in,' you've thrown away the one thing that made this message different from everything else in their inbox that morning.

Name the event, name the problem, and ask a question that can be answered in one line. Keep it short. You're picking up a conversation that already had a reason behind it, not starting a new pitch.

If they don't reply to the first attempt, wait a week and try once more with a different angle on the same trigger. After two attempts with no reply, move them out of the active list. A trigger that produced nothing is information too, and it keeps your list honest.

Paste this job

Hi {first name},

Back in {month} you mentioned {trigger, e.g. the CRM migration} was taking up the team's time until {date}. Assuming that's wrapped up, is {problem} back on the list this quarter?

If it's still parked, tell me and I'll leave it alone until {next trigger}.

{your name}

Doing this with Kinlead

Kinlead's reply modes let you decide who handles the first exchange. Hand-off mode gives you the conversation at the first reply, which is what you want if you'd rather dig for the trigger yourself and set the anchor in your own words.

If you'd rather the AI handle the opening, put your trigger questions into the campaign's sales playbook. The playbook is your own script, so the AI asks what you'd ask instead of a generic 'when should I follow up.'

Replies from every campaign land in one inbox, classified by intent, so you can pull the not now replies into one place and work them in order. You can see the flow on the demo page.

Put your trigger question in the playbook word for word. The AI copies your phrasing better than it invents its own.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? How to respond when a prospect says it is not the right time.md