Practical Guide · The messages and schedule below are illustrative templates, not records of real client correspondence.
How to follow up after sending a proposal used to feel more awkward to me than writing it. Once it was sent, waiting created a temptation to interpret every day of silence as information. A quiet inbox does not tell me whether the person is uninterested, busy, comparing options, or waiting for approval.
I want a follow-up to make the next decision easier, not pressure someone into answering. Respect the timeline already discussed, ask for one useful next step, and decide when to stop.
Use the agreed decision date before choosing a sequence
If the prospect said they would review the proposal by Friday, wait until that window has passed. For a larger proposal or a procurement process involving several people, ask when the next decision is expected and follow that process. A small, requested proposal after an active conversation may need less review time.
If no timeline was agreed, this is a possible starting sequence for a modest project. It is an example, not a universal cadence or a proven conversion formula.
- Day 0 — proposal sent: State what decision is needed and ask about the expected review date. Record the next check in your system.
- Follow-up 1 — around business day 4: Ask whether anything needs clarification and whether there is a likely decision date.
- Follow-up 2 — around business day 9: If there is still no reply, ask whether the work is active or the timing has changed. Add new information only if it actually helps.
- Close the loop — around business day 15: If silence continues, say you are closing the active follow-up and leave a straightforward way to return.
A reply replaces this schedule. If procurement says decisions resume next month, record that date and pause. Do not continue the original sequence alongside the new timeline.
First follow-up: ask about the next decision
Stay in the existing thread where practical. The first message does not need to resell the project or repeat the entire scope.
Hi, I’m following up on the proposal I sent last week. Is there anything about the scope or approach you’d like me to clarify?
Do you have a likely review date? If the timing has shifted, I’m happy to work from the updated timeline.
Adapt “last week” to the actual sending date. Do not imply a prior conversation or an agreed deadline that did not happen.
After no response: make a change in timing easy to explain
Another message should have a purpose beyond demonstrating persistence. This example asks whether the proposal still belongs in the active pipeline.
Hi, checking whether the proposal is still under consideration or whether the project has moved to a later date.
If it is still active, what would be the most useful next step? If priorities have changed, a brief update is enough and I’ll adjust my follow-up.
If you have a useful clarification from the original discussion, include it briefly. Do not manufacture a discount, deadline, scarcity claim, or extra deliverable just to get a reply. I try not to negotiate against silence: address an objection when it is raised, rather than guessing one.
Final message: close your follow-up, not their options
Hi, I’ll close the active follow-up on this proposal for now, so you won’t keep receiving reminders from me.
If the project becomes a priority again, you’re welcome to reply to this thread. We can then confirm whether the scope, timing, and availability still fit.
This closes your reminder sequence. It should not claim that a proposal has expired unless its actual terms say so, or promise that the original price and delivery slot will remain available indefinitely.
Use a stopping rule
- A clear no or a request to stop: Stop the sequence. A polite acknowledgement does not need to become another sales attempt.
- A changed procurement or decision date: Pause and record the new agreed check date. A known delay is not a reason to send more reminders.
- Repeated silence after the planned sequence: Send the final note if appropriate, then remove the opportunity from active follow-up.
- The proposal is no longer relevant: If the requested date has passed or the scope no longer fits, explain that a fresh discussion would be needed. Stop pursuing approval of an outdated offer.
A clear no can be planned around. An indefinite maybe should not occupy the same attention as work with a next step. That is why I treat follow-up as part of decision making, rather than a test of persistence.
Put the next follow-up in a system
A CRM, calendar, or simple list is enough. Keep one record with the proposal link, date sent, agreed decision window, last meaningful reply, next action/date, and status: active, waiting until a stated date, or closed. After each exchange, replace the old reminder with the new next step.
Keep the actual conversation notes alongside that record. Work documentation helps separate what the prospect said from what you guessed while waiting. The system should remind you when there is something useful to do—and let you stop thinking about the proposal when there is not.
Updated 6 October 2026: added an illustrative sequence, three message templates, explicit stopping rules, and a reminder-record structure.
