Proposal sent and then silence? These 5 follow-up emails, each with a subject line and body text, are based on tracking data and work better than "Just checking in...".
Sending the proposal is the easy part. The waiting that follows is where most deals quietly die. A practical rule for the first follow-up is 2 to 3 working days after sending, provided the client has opened the proposal. If it has not been opened yet, wait one more day and send a short reminder rather than a substantive question. With proposal tracking you do not have to guess. Proposal Expert shows you when the proposal was opened, which sections were read and for how long, and summarises that in an engagement score from 0 to 100. This article gives you five examples, each with a subject line and a short body you can adapt to your own situation.
The classic follow-up opens with "I just wanted to check whether you received my proposal". That sentence has three problems. It asks the client to do work without giving anything back, it contains no new information, and it shows you do not know what happened on your own side. A good follow-up does the opposite. It is specific about what you have seen or heard, it gives a reason to respond now, and it makes replying easy by asking one concrete question the client can answer in a sentence. Keep it short. Four or five sentences is enough, because the client already has the proposal and does not need it summarised again.
Subject: Question about the timeline in our proposal. "Hi Sarah, I noticed you looked at the timeline section yesterday. I can imagine the six-week lead time raises questions, especially with your launch in November. Shall I call this week to walk through the phasing? Fifteen minutes is plenty, I will work around your calendar." This email works because it is specific. You name the section the client actually read, you address a likely concern before the client has to put it into words, and you ask a small, low-risk question.
Subject: A similar project for a logistics company. "Hi Sarah, it occurred to me that we ran a similar project last year for a logistics company that faced the same challenge with their ERP integration. I have attached a two-page summary of that project, the section on data migration is particularly relevant to you. If it raises any questions about our proposal, I would be glad to hear them." The principle is to give before you ask. You send something that is useful on its own, a case study, a relevant article or a client reference, and tie it loosely to the open proposal.
Subject: A May start is still possible. "Hi Sarah, a quick update on our planning. If we have your approval by the end of April, I can have the team start in the second week of May and we will hit your end-of-June deadline. After that the start probably moves to July, because we will be on another project. Shall we settle on a yes or no this week, so you have clarity too?" Scarcity only works when it is real. Do not invent a capacity problem, but if your calendar is genuinely filling up, that is relevant information for the client. Asking for a yes or no is deliberate, because a no is better than a month of silence.
Subject: Shall I close the file? "Hi Sarah, I have not heard from you in a few weeks, so I assume you have decided to go in a different direction. That is completely fine. Would you be willing to tell me in a few sentences what tipped the balance? It helps me make better proposals next time. If it was simply a matter of timing, let me know and I will get back in touch in a few months." This email usually produces one of two things: a late reply because the client notices the door is closing, or honest feedback you would never have received otherwise.
Subject: What changed in your market this quarter. "Hi Sarah, no proposal this time, just a short update. Over the past few months we have completed three projects in your sector and drawn a few lessons from them that I would like to share. I have summarised them on one page, see the link below. If the topic comes back onto the table, you know where to find me." A deal that looks dead is often just postponed. One update per quarter keeps you in view without becoming intrusive. Keep it informative, keep it short and do not ask for anything.
Automation is useful for timing, not for content. Use this sequence. 1. Set a reminder per proposal for day 3, day 7 and day 14 after sending, so you never forget to follow up. 2. Before you send, look at the tracking data: has the proposal been opened, which section was viewed longest, has it been forwarded to a colleague. 3. Pick the example that fits what you see. A high engagement score and a long time on the pricing page calls for example 1 with a question about the price breakdown, no opening at all calls for a short reminder. 4. Always rewrite the first two sentences by hand, the rest can come from your template. 5. Log the response in your CRM so your colleagues know where the deal stands. Proposal Expert sends automatic reminders on the days you choose and syncs the status with HubSpot, Salesforce and Monday.
Four or five emails spread over three weeks is a reasonable sequence for most business proposals, as long as each one brings something new. The problem is rarely the number, it is the content. Five rounds of "just checking in" is too many, five emails that each give a different reason to respond is not.
Email first, then call. An email gives the client room to respond at a quiet moment and leaves a trail you can read back. A call works well as a complement to example 1 or 3, when you have a concrete question and the client has opened your email but not answered it. Never call cold after a proposal that has not been opened yet.
That is good news, because it means your contact is looking for internal support. Tracking shows the proposal was opened from a different device or address. In your next follow-up, ask your contact whether you can clarify anything for the new reader.