Skip to content

Proposal Follow-Up Email Examples

Plenty of proposals go quiet not because the answer is no, but because the client got busy. These nine emails cover each stage of following up, from the first check-in to a polite close. Copy them and change the brackets.

Updated September 30, 2026

A simple follow-up schedule

There's no magic number of days. This is a reasonable default you can shorten for urgent projects or stretch for slow-moving clients:

Each follow-up should give the client a reason to reply: a question, a new option or a real deadline. "Just checking in" on its own gives them nothing to respond to.

1. The first check-in

Keep it short, resend the link, and offer an easy next step.

First check-in
Subject: Re: Proposal for [project]

Hi [Name],

Just making sure the proposal reached you. It's here if it's easier to open again: [link]

If it helps, I'm happy to go through it on a 15-minute call this week. Thursday or Friday afternoon both work for me.

[Your name]

2. When they've opened it but gone quiet

If you send proposals as a trackable link, you'll know when a client has read it. Don't quote the tracking back at them ("I saw you opened it three times") — just use it to time a question that makes replying easy.

Opened, no reply
Subject: A question on the [project] proposal

Hi [Name],

I noticed you've had a chance to look through the proposal. Usually at this stage there's a question about scope or timing that's easier to answer in a quick reply than to think through alone.

Is there anything in there you'd like me to change or explain?

[Your name]

3. Adding value instead of asking

A follow-up that's useful to the client even if they never hire you. It only works if the idea is specific to them.

Value-add follow-up
Subject: One idea for [project]

Hi [Name],

While thinking about your [project], I came across [a relevant example, an article, an idea specific to them]. It's relevant to what you said about [their problem], because [one sentence on why].

No action needed. The proposal is still here when you're ready: [link]

[Your name]

4. Responding to a price objection

Cutting your price for the same work teaches the client your first number wasn't real. Cut scope instead, and keep the part that solves their main problem.

Price objection reply
Subject: Re: Proposal for [project]

Hi [Name],

Thanks for being straight with me about the budget. Rather than lower the price on the same scope, here's a version that fits closer to [their number]:

- Keep: [the core deliverables that solve the main problem]
- Move to a later phase: [the nice-to-haves]
- New price: [amount]

That still gets you [the key outcome] by [date], and we can add the rest later if it makes sense. Would that work?

[Your name]

5. A real start-date deadline

Only send this if the scheduling constraint is true. A made-up deadline is easy to see through and hard to walk back.

Start date follow-up
Subject: Start date for [project]

Hi [Name],

A quick heads-up on scheduling: I'm booking projects for [month] now. If you'd like to go ahead, confirming by [date] would let me hold a [start date] start for you.

If the timing's changed on your side, that's completely fine. Just let me know and I'll stop nudging.

[Your name]

6. After a call, with the updated proposal

List the changes so the client doesn't have to re-read everything to find them.

Post-call follow-up
Subject: Updated proposal after our call

Hi [Name],

Thanks for the time today. I've updated the proposal with the changes we discussed:

- [Change 1, e.g. added the second landing page]
- [Change 2, e.g. moved launch to 12 March]
- [Change 3, e.g. split payment into three milestones]

Updated version: [link]

If that all looks right, you can accept it directly from the link and I'll send the first invoice.

[Your name]

7. When they said "we'll get back to you"

Often the delay is an internal conversation you're not part of. Offer something that helps the person championing you inside the company.

Waiting on their team
Subject: Re: Proposal for [project]

Hi [Name],

You mentioned you'd be discussing the proposal with [person/team] this week. Is there anything I can send to make that conversation easier, like a one-paragraph summary or a breakdown of the options side by side?

[Your name]

8. Closing the loop

Saying you'll stop following up can prompt a reply, because it asks for nothing and gives the client an easy way to say where things stand.

Close the loop
Subject: Closing the loop on [project]

Hi [Name],

I haven't heard back, so I'll assume the timing isn't right and stop following up. No hard feelings at all.

If things change, the proposal is still here: [link]. I'd be glad to pick it back up.

[Your name]

9. After a no: ask why

One line of honest feedback is worth more than any template. Keep the request tiny so it's easy to answer.

Asking for feedback
Subject: Re: Proposal for [project]

Hi [Name],

Thanks for letting me know, and good luck with the project.

If you have a minute, I'd really value one line on what tipped the decision: price, approach, timing, or something else. It helps me write better proposals.

[Your name]

Subject lines that work

What not to do

Related