9 Proposal Follow-Up Templates That Don't Sound Pushy
Copy-paste follow-up messages for every stage after sending a proposal — no opened it yet, priced-shopped, gone quiet — with the reasoning behind each one.
The reason most follow-up messages sound pushy is not the wording. It is that they ask the client to do something the client is not ready to do, and both people can feel it.
"Just following up — any thoughts?" asks for a verdict. If they have not read the proposal properly, the only honest answer is an admission, and most people would rather say nothing than admit they have not got to it. So they say nothing, and you read the silence as a no.
Below are messages for nine real situations. Each one is written to be answerable — the ask matches what the client has actually done. Swap the names and specifics; do not send them verbatim, because the specifics are what makes them not sound like a template.
Before You Pick One
Two things decide which message is right:
- What they have done. Opened it? Read the pricing? Come back twice? Nothing at all?
- Where the conversation lives. Follow up in the channel you have been using. If it has been WhatsApp, an email suddenly appearing reads as escalation.
If you have no idea what they have done, start with template 1 — it is the safest under uncertainty because it assumes nothing.
1. The Neutral Nudge (2–3 days, no information)
Use when you cannot tell whether they opened it.
Hi Priya — just making sure this landed. Here is the proposal again in case it got buried: [link]
Happy to walk through any part of it if that is easier than reading.
Why it works: it assumes a delivery problem, not a decision problem. Nobody has to confess anything, and the offer of a call gives them a lower-effort option than reading.
2. They Have Not Opened It (3+ days)
Hi Tom — I do not think this one reached you properly. Resending here: [link]
It opens on a phone, so no need to be at a desk.
Why it works: it names the likely cause and removes the friction. "Opens on a phone" matters more than people expect — a large share of first reads happen on mobile, and a PDF attachment is exactly what does not survive that.
3. They Skimmed It Once
Hi Sara — one thing I should have made clearer in the proposal: the three phases are separable, so we do not have to commit to the whole thing on day one.
Would a short call this week be useful?
Why it works: it gives them something new rather than repeating the ask. The new information is a genuine reduction in commitment, which is usually what is stalling a skim-and-park.
4. They Spent Real Time on Pricing
Hi Marcus — figured the budget is the part worth talking through.
The number assumes the full scope. If it is more than you want to commit up front, we could start with the discovery phase and decide the rest after — happy to send that version if it helps.
Why it works: it addresses the real question without discounting. Restructuring the commitment solves the problem far more often than cutting the price, and it does not teach the client that your rates are negotiable.
What not to send here: "I could do 10% off if you sign this week." You have just told them the first number was not real.
5. They Came Back a Second or Third Time
Hi Anna — glad this is still under consideration. If it is going to anyone else internally, I am happy to put together a one-page version for them.
And if there is a specific bit that is not sitting right, tell me straight — I would rather fix it than have it quietly die.
Why it works: repeat visits usually mean it is being shown to someone else, or that one specific objection is unresolved. This addresses both, and the last line gives explicit permission to raise the objection.
6. The Deadline That Actually Exists
Hi Dan — my calendar for October is filling up. I can hold the slot for this project until Friday, after which the start date moves to November.
No pressure either way — just did not want the timeline to shift without telling you.
Why it works: it is true. Invented scarcity is transparent and it damages trust with exactly the clients you want. Only send this if you would genuinely turn the work away or reschedule it.
7. The Value Reminder (a week, still nothing)
Hi Rachel — while this has been sitting, I finished a similar project for [comparable client]. The short version: [one concrete outcome].
Thought it might be useful context. Proposal is still here if you want another look: [link]
Why it works: it is a reason to make contact that is not "have you decided". A concrete outcome does more than any adjective about your process.
8. The Break-Up (two weeks, no engagement)
Hi Marcus — assuming the timing is not right on this one, so I will stop chasing.
If it comes back around later in the year, message me and I will refresh the numbers. Genuinely no hard feelings either way.
Why it works: it removes the social awkwardness that was causing the silence. This message produces replies at a surprisingly high rate — often "sorry, it has been chaos here, can we pick it up next month?" — precisely because it does not demand anything.
9. The Re-Open (one to three months later)
Hi Priya — you mentioned the budget might free up after Q1. Circling back in case it did.
Happy to redo the proposal against whatever the scope looks like now.
Why it works: it references something specific they said, which proves you were listening and dates the relationship. Generic "checking in after a while" messages get ignored; this one has a reason attached.
Three Phrases to Delete
Some wording does damage regardless of which template it sits in.
"Just following up." It announces that the message contains nothing. If the only content is the fact of contact, the client learns your messages are safe to ignore. Lead with the actual reason instead — and if there is not one, do not send it.
"I know you're busy." Well-intentioned, but it hands them a ready-made excuse and pre-apologises for existing. It also, oddly, reads as passive-aggressive to some people. Cut it.
"Any thoughts?" / "Any updates?" Both ask for a verdict from someone who may not have read the document. Replace with a specific, answerable question: "Does the February start still work?" is easy to answer. "Any thoughts?" is not.
Worth noting the pattern underneath: every one of these fails for the same reason — it asks the client to supply the substance of the conversation.
What Makes All of These Work
They are short. A long follow-up implies the first document did not do its job.
They ask for something small. A reply, a call, a version for a colleague — never "please decide now".
They give a reason for existing. New information, a real deadline, a relevant result. "Bumping this" is not a reason.
They are easy to say no to. Counter-intuitively, this is what gets replies. When declining is comfortable, so is answering.
Adapting These Without Making Them Worse
Two failure modes when people edit templates.
Over-personalising the opening, under-personalising the substance. "Hope you had a great weekend at the lake!" attached to a generic ask is worse than no personalisation — it signals effort spent on the wrong half. The specific detail belongs in the reason for writing, not the pleasantry.
Making it longer. Every template above is short on purpose. The instinct when a message feels weak is to add justification, and it reliably backfires: length reads as anxiety, and a long follow-up implies the proposal itself did not do its job.
A useful test before sending: can they reply in one line? If answering properly requires a paragraph, you have asked for too much, and the most likely outcome is no reply at all.
Also worth adapting for channel. These are written to work as WhatsApp messages — short paragraphs, no formal sign-off. If you are sending by email you can add a greeting and a name, but resist restoring the full letter format. The proposal is the formal document; this is a conversation.
On Automating This
You can automate the first one or two of these, and it is worth doing — the messages that get skipped are the ones you did not have time to send.
But cap it hard. In ClosingMoment, at most two automated emails go to any proposal, spaced at least 24 hours apart, and everything stops the instant the client accepts. Automation that keeps firing after a human has replied is how a reasonable sequence becomes spam, and it is very hard to recover a relationship from that.
Everything after the second message should be written by you, informed by what they actually did.
The Short Version
Pick the message that matches what the client has done, not how many days have passed. Keep it short, make the ask small, and give them an easy way out — which is, reliably, what makes them answer.
If you do not know what they have done, that is the fixable part.
A follow-up also only works if the thing it follows up on was clear. If the scope or timeline left room for doubt, start from a complete proposal template — free to copy, no signup — and there is a timing calculator that tells you when to send each of these messages.
Continue reading
Your Client Opened the Proposal and Didn't Reply. Now What?
What it means when a proposal gets read and then goes silent — the five most common reasons, how to tell them apart, and the message that fits each one.
How Long Should You Wait to Follow Up on a Proposal?
A follow-up schedule based on what the client has actually done, not a fixed number of days — plus what to send at each stage and when to stop.