Most typical phrasing
“Not now, maybe later.”
Optional analytics
FlowDockr only loads optional analytics and third-party tools after you allow them. Read the Privacy Policy.
The client is not rejecting the work forever, but they are putting it off. You need to respond in a way that keeps the door open without hovering around the lead. Get a professional reply you can adapt and send.
Start with 2 free drafts. No subscription required.
Typical client message
“Not now, maybe later.”
Situation snapshot
The client is not rejecting the work forever, but they are putting it off. You need to respond in a way that keeps the door open without hovering around the lead.
Reply goal
Acknowledge the timing issue and offer a simple way to revisit the conversation later.
Client message generator
Write a reply when a client says not now, maybe later. Keep the tone warm, low-pressure, and easy to pick back up later.
Review the suggested approach and choose the response that best fits your client conversation.
Your polished reply will appear here
Generate a result to see the send-ready message, the reasoning behind it, and follow-up guidance if the client keeps pushing.
Why this works
What it protects
Acknowledge the timing issue and offer a simple way to revisit the conversation later.
How it sounds
Just checking in on this in case it is still active on your side. If it would help, I'm happy to answer any open questions or outline the cleanest next step.
Next step
Avoid turning a soft delay into a long thread of vague check-ins.
These are the real wording patterns this scenario is built to handle.
Most typical phrasing
“Not now, maybe later.”
Other ways this shows up
“The timing is not right for us at the moment.”
Reply playbook
Use this when the search intent is "client says not now maybe later reply" and the client message matches this negotiation stage. It also covers searches like "not now maybe later client reply".
Step 1
The client is not rejecting the work forever, but they are putting it off. You need to respond in a way that keeps the door open without hovering around the lead.
Step 2
Acknowledge the timing issue and offer a simple way to revisit the conversation later.
Step 3
Avoid turning a soft delay into a long thread of vague check-ins.
Concise
Just checking in on this in case it is still active on your side. If it would help, I'm happy to answer any open questions or outline the cleanest next step.
Best for: Use when you need a short reply that keeps the thread moving.
Warm
Wanted to circle back in case this is still under review. If timing changed on your side, no problem. If it is still live, I can help you decide on the next step.
Best for: Use when you want to preserve trust while still keeping the boundary clear.
Firm
Acknowledge the timing issue and offer a simple way to revisit the conversation later. If the client wants a different path, make the tradeoff explicit before you continue.
Best for: Use when the client is repeating the pressure or treating the boundary as optional.
Acknowledge the timing issue and offer a simple way to revisit the conversation later.
Use a softer tone when the client is still collaborative and the pressure looks like uncertainty rather than bad faith.
Avoid turning a soft delay into a long thread of vague check-ins.
More client no-response, delayed decision, and proposal follow-up conversations.
More client no-response, delayed decision, and proposal follow-up conversations.
Client ignored your last message
Your last message got no response and you do not want the follow-up to feel awkward. The goal is to restart the thread with a useful nudge, not a guilt trip.
Client keeps saying they will get back to you soon
The client is not fully ghosting, but keeps sending vague delay messages without making a decision.
Client says they will think about it
The client has not said yes or no, and vague waiting can drag on. You need a reply that keeps momentum without forcing the decision too hard.