Proposal Follow-Up Email: Timing and 3 Examples

A proposal follow-up works best when it is expected, brief, and easy to answer. If you agreed on a decision date, write on that date. If you did not, a first message after two to five business days is a reasonable starting point, adjusted for the size of the purchase and the number of people involved.

The aim is not to guess why the client is quiet. It is to confirm the proposal arrived, answer a likely question, or agree on what happens next.

When to follow up after sending a proposal

Use the buying process you already know:

• A response date was agreed: follow up on that date.
• One person is deciding on a straightforward project: consider two or three business days.
• Procurement, a committee, or budget approval is involved: allow more time and ask about the internal timeline.
• The proposal has an expiry or provisional start date: write early enough for the client to act before it passes.

These are planning ranges, not rules. A five-figure project reviewed by several stakeholders may take longer than a small piece of work for an existing client. The cleanest approach is to agree on the next contact before ending the sales call:

I will send the proposal on Tuesday. Would Friday be a sensible day for me to check whether anything needs clarifying?

That sentence makes the follow-up part of the process instead of an unexpected chase.

Use tracking as context, not mind-reading

An open event can confirm that the proposal link was accessed. It cannot tell you who read every section, what they thought, or whether price is the problem.

Use the signal conservatively:

• No recorded open: check delivery and ask whether the link reached the right person.
• One or more opens: ask a specific question about scope, timing, or the decision process.
• A client message or decision: respond to what they actually said rather than interpreting the open count.

Shared links, privacy tools, forwarded emails, and repeat visits can all affect tracking. Treat the data as one input alongside the conversation.

What to do when the proposal was viewed but the client has not replied

A recorded view answers one narrow question: the secure proposal page was accessed. It does not explain who read it, what they thought, or why nobody replied.

Choose the next message from the process you agreed with the client:

• The decision date has not arrived: wait unless the client asked for something.
• The decision date is today: follow up as planned and offer one clarification.
• The date passed: ask whether the project, timing, or approval route changed.
• No date was agreed: use the same two-to-five-business-day range as the first follow-up.

Do not write “I saw you opened the proposal.” Start from a fact the client recognises: the project, the agreed review date, or a real choice in the scope. If repeated activity makes a specific question more useful, ask it without quoting the view count.

Keep the context together

Want to send professional proposals in less time?

Try Proposa for free and reuse templates designed to speed up prep and increase approvals.

Try Proposa for freeExplore proposal software

How to write the first follow-up

A useful first message contains four parts:

1. the proposal or project you mean;
2. the reason for writing now;
3. one helpful question or clarification;
4. a small next step.

Remove apologies and generic openings such as “just checking in.” They take space without helping the client decide.

Example 1: confirm delivery

Use this when there is no sign that the proposal arrived. Do not say that tracking proves it was unread.

Subject: Website proposal for North Street

Hi Sam, I sent the website proposal on Tuesday and wanted to confirm that the link reached you. If it did, no action is needed today; we can review questions on Friday as planned. If not, I will resend it in a different format.

Example 2: clarify the choice

Use this when the client is comparing two scopes or timelines.

Subject: One detail on the launch options

Hi Sam, one point may help with the internal review. Option B keeps the 30 April launch by running testing alongside the build; Option A moves testing to the following week. If useful, I can send a two-line comparison or talk it through for ten minutes on Wednesday.

Example 3: ask about the decision process

Use this when other stakeholders are involved and you do not know the schedule.

Subject: Next step for the reporting project

Hi Sam, I know the proposal needs input from finance and operations. Is there a review date I should work towards, and would either team benefit from a shorter summary of scope and cost? I can prepare that before the meeting.

The examples are starting points. Keep the facts that belong to the client and remove anything you cannot genuinely offer.

Add something useful without inventing an objection

A follow-up can clarify:

• a scope boundary that was discussed on the call;
• the difference between two real options;
• how the timeline depends on client feedback;
• an answer to a question the client already asked;
• the date until which a start slot or price is available, if that date is genuine.

Avoid manufacturing urgency or assuming that silence is a price objection. Offering a discount before the client mentions budget can create a negotiation that did not exist. If budget is the stated issue, propose a smaller scope and explain what changes.

For example:

If the first-phase budget is capped at EUR 5,000, we can move reporting and the admin dashboard to a later phase. I can revise the scope so the reduced version and its trade-offs are clear.

A simple follow-up sequence

If the client has not given you a preferred cadence, you can use this as a flexible baseline:

1. First follow-up: two to five business days after sending. Confirm delivery or offer one clarification.
2. Second follow-up: roughly four to seven business days later. Ask about the decision process or add information that was not in the first message.
3. Close the loop: if there is still no response, say you will stop following up and explain how to restart the conversation.

There is no magic number of messages. Stop sooner if the client asks for space; continue at an agreed date if their procurement cycle is longer.

Closing email example

Subject: Closing the loop on the website proposal

Hi Sam, I have not heard back, so I will close the loop for now rather than keep filling your inbox. The proposal can be revisited if the project becomes active again; at that point I will reconfirm scope, price, and availability. Thanks for considering it.

This is clear without pretending the project is gone forever or using a false deadline.

Common follow-up mistakes

• Writing only “Any update?” Give the client enough context to answer.
• Apologising for a reasonable message. Be courteous and direct.
• Interpreting opens as intent. Ask instead of claiming to know.
• Sending a long sales pitch. Keep the message focused on one decision.
• Changing the price without changing scope. Wait for a real budget conversation.
• Using false scarcity. Mention availability only when it is genuinely limited.
• Following up after the client asked you not to. Respect the channel and timing they chose.

Checklist before sending

• Am I following an agreed date or a reasonable interval?
• Have I named the project and why I am writing now?
• Does the message contain one useful question or clarification?
• Is the next step easy to answer?
• Have I avoided guessing what tracking data means?
• Are any deadlines or availability claims accurate?

Save the examples as templates, but rewrite the details for each opportunity. With Proposa proposal tracking, opens, client messages, and decisions stay attached to the proposal, so the next message can use the facts you have without pretending the data says more than it does.

Built for freelancers

Want to send professional proposals in less time?

Try Proposa for free and reuse templates designed to speed up prep and increase approvals.

Try Proposa for freeExplore proposal software