
How to respond to “reach out next quarter”
Real timing or a polite no? One question to tell them apart, what to write in each case, and a follow-up that gets read three months later.
Answer the timing, not the brush-off. When a prospect writes "reach out next quarter", reply the same day with one question that tells you whether the delay is real ("What changes for you in January?"), offer a specific date to come back, and ask permission to send one useful thing in between. Then put that date somewhere you will actually see it, and when it comes, open with something new, not "circling back as discussed".
That is the whole method. The rest of this piece is how to tell the two kinds of "next quarter" apart, what to write in each case, and what the follow-up should look like three months later.
Two different replies hide behind the same words
"Reach out next quarter" covers two situations that need opposite handling.
A real timing problem. Budget resets in January. They are mid-migration and nobody has bandwidth. A new VP starts next month and will own the decision. The interest is genuine, and pushing now only burns goodwill.
A polite no. The prospect doesn't see the problem, or doesn't see it as theirs, and "next quarter" is the least awkward way to end the thread. Push on it and you get silence.
You can't tell which from the words alone. You can tell from the answer to one specific question. That is why the first reply matters more than the follow-up three months later: it is the only moment where the prospect is still talking to you and will answer.
There is a reason to take the real-timing case seriously. In the 6sense 2024 Buyer Experience Report, buyers said they were about 70% through their buying process before talking to sellers, and 81% already had a preferred vendor at first contact. A prospect who tells you about their timeline is letting you into the part of the process you normally never see. Being the vendor they remember when the quarter turns is worth more than a meeting this week.
- of the buying process is done before buyers talk to sellers
- ~70%
- of buyers already have a preferred vendor at first contact
- 81%
The first reply: one question, one date, one offer
Keep it short. Three or four sentences, no pitch, no deck attached. Here is a version that works in email, LinkedIn or a messenger:
Makes sense, thanks for telling me straight. Quick question so I come back at the right moment: what changes in January? Budget, a project wrapping up, someone new joining? I'll write on the 13th unless you'd rather pick another week.
Why each part is there:
- "Thanks for telling me straight" rewards the prospect for answering instead of ghosting. People who feel heard keep talking.
- "What changes in January?" is the diagnostic. A real timing problem has a concrete answer: "our budget is approved in December", "we finish the CRM switch in February". A brush-off has a vague one, or none.
- A specific date turns "later" into a commitment. "I'll reach out in Q1" is easy to agree to and easy to forget. "The 13th" is something they can say no to, which makes a yes mean something.
If you sell something where timing really does drive cost (contracts that auto-renew, seasonal demand, a regulation with a deadline), you can add one line about it. Only if it's true for them. A made-up "cost of waiting" reads as pressure.
What to do with each kind of answer
The prospect's reply to your question sorts the deal. Here is how to read it.
Real timing
- Names a reason: budget, project, new hire
- Gives a month or an event
- Agrees to your date or proposes one
- Asks a question back
Polite no
- “Just busy right now”
- No reason, no date
- Ignores your question
- Replies only to say “sure”
If it's real timing, write down the reason, not just the date. "Budget approved mid-December, decision with new Head of Ops starting Jan 6" is what you'll need in three months; "follow up Q1" is not. Ask one more thing while you have them: who else will be involved. And offer something small that helps them prepare, for example "Want the one-page checklist we give teams before a migration like this? Useful whether you pick us or not." Only offer it if it exists and is worth reading.
If it's a polite no, don't argue with it. Accept, leave the door open, and stop the sequence:
Got it. I'll leave it here and won't fill your inbox. If this lands on your list later, just reply to this thread.
Then actually stop. The worst outcome is a "polite no" that you treat as real timing: three months of check-ins to someone who already decided. If you need a rule for how many follow-ups are reasonable in general, we covered it in how many follow-ups before giving up, and the clear "no" case in how to respond to "not interested".
If they don't answer your question at all, treat it as a soft no with a date. Send nothing in between, and write once on the date you named.
The follow-up three months later
Most of these deals die here, not in the first reply. The rep comes back with "Hi, circling back as discussed, is now a better time?" The prospect has no memory of the conversation and no reason to answer.
A follow-up that gets read does three things: reminds them what they told you, brings something new, and asks for something small.
Coming back on the date you agreed
- Use their wordsQuote the reason they gave: “You mentioned budget would be set in December.” It proves you listened and saves them rereading the thread.
- Bring one new thingA change at their company, a relevant customer story, a feature they asked about. Something they couldn't have known three months ago.
- Ask for a small stepA 15-minute call or a yes/no question. Not “let me know your thoughts”.
- Reply in the same threadWrite where the conversation happened, so the history is one scroll up.
- One more, then closeNo answer in a week: one short nudge, then a polite close. Don't restart a full sequence.
An example:
Hi Maria, you said in October that the ops budget would be set in December and Daniel would own this from January. Since then we've added Telegram, which you'd asked about. Worth 15 minutes next week to see if it fits what Daniel is planning?
Compare that to "Just checking in". Same length, but this one can only have been written to her.
Where these deals actually get lost
The method above isn't the hard part. The hard part is logistics:
- The date lives in someone's head. A rep leaves, goes on holiday, or simply has 40 other threads. The reminder is in a CRM task nobody opens, or nowhere.
- The reason doesn't get written down. Three months later you know the date but not why, so the follow-up is generic.
- The conversation was in a messenger. The prospect said "next quarter" in WhatsApp or on LinkedIn, the CRM has an email address, and nobody connects the two.
The fix is boring: the reminder and the reason must sit inside the conversation itself, in the same channel where the prospect wrote. If they're in a separate system, plan on losing some of these deals.
This is where Nitrino helps. It reads replies across email, LinkedIn, Telegram, WhatsApp and Instagram, answers in the account owner's voice, keeps reminders on the conversation and comes back to threads that went quiet by itself, and calls a person in when a decision is needed. If your "next quarter" leads tend to disappear, see how it works.
Short version
- Reply the same day; don't let "next quarter" end the thread.
- Ask one question: what changes by then?
- Name a specific date and ask if it works.
- Real timing: write down the reason and who decides. Polite no: accept and stop.
- On the date, use their words, bring one new thing, ask for a small step.
