Skip to content
LLeadPilotBack to home
GUIDE

Proposal follow-up email after no response: 3 templates

Last updated November 21, 2026

  1. Home
  2. Resources
  3. Proposal follow-up email after no response: 3 templates

By LeadPilot · Practical guidance for independent service businesses

Copy a proposal follow-up email for a first check-in, a missed decision date or a final note. Personalise the draft and try scheduling the next contact in the demo.

Choose your email

Personalise this email

All fields are optional. Details stay in this tab. Copy or download the draft to keep it.

Set a follow-up date in the demo

On this page

  1. Start with the decision, not a generic reminder
  2. When should you follow up on a proposal?
  3. Template 1: check that the proposal reached the right person
  4. Template 2: follow up after the agreed decision date
  5. Template 3: close the loop without applying pressure
  6. What to record after each message
  7. How to use this workflow in LeadPilot
  8. Can a follow-up guarantee a reply?
  9. Additional situation: a client questions the price
  10. Additional situation: you have sent a revised scope
  11. Additional situation: the project has been postponed

Start with the decision, not a generic reminder

A useful proposal follow-up reminds the client what they are deciding and makes the reply easy. Name the project, refer to the proposal and ask one relevant question. Check the conversation before writing: a client who promised an answer next week needs a different message from someone whose approval date has already passed. The examples below are editable starting points for an existing client conversation, not a cold-email campaign.

When should you follow up on a proposal?

Use the date you agreed with the client first. If there was no agreement, a few business days after sending can be a reasonable first check for a small service project. A procurement review or a multi-person decision may need longer. This is a suggested workflow, not a response-rate benchmark or a universal schedule. Ask for the review date when you send the proposal so you do not have to guess later.

  • Before sending: confirm the intended recipient, scope, fee and requested decision.
  • At the agreed review date: check whether the client has questions or needs a different timeline.
  • After continued silence: send one relevant clarification or a close-the-loop note, then pause unless invited to continue.
  • After a refusal or request to stop: record the outcome and stop following up.

Template 1: check that the proposal reached the right person

Use this when the client has not acknowledged the proposal and you need to establish the next step. Keep the original email thread when appropriate. Replace every bracketed detail and include only the link or attachment the recipient needs.

Subject: [Project] proposal — review date

Hi [Name],

I sent the proposal for [specific outcome] on [date]. Is it with the right person for review?

It covers [deliverable] for [fee and currency], with [key timing or dependency]. Here is the proposal for reference: [link].

Would [date] be a realistic time to check back, or is there another review date I should use?

Best,
[Your name]

Template 2: follow up after the agreed decision date

Use this when an agreed review date has passed. Ask about the obstacle rather than repeating the entire pitch. If the client raises a price, scope or timing concern, address that concern before asking for approval again.

Subject: Re: [Project] proposal

Hi [Name],

We planned to review the [project] proposal around [date]. Is there anything in the scope, fee or timeline that needs clarification before you decide?

If priorities have changed, I can update the proposed next step. What would be most useful from me now?

Best,
[Your name]

Template 3: close the loop without applying pressure

Use this after reasonable attempts to clarify an existing opportunity. Do not invent scarcity, claim another buyer is waiting or add a deadline that does not exist. A pause is useful information: it lets you keep the pipeline accurate and leaves the client free to return later.

Subject: Should I pause [project]?

Hi [Name],

I have not heard back about [project], so I will pause my follow-ups for now.

If the work is still planned, let me know the timing and we can confirm the scope and availability again. If it is no longer a priority, no further action is needed.

Thanks for considering the proposal,
[Your name]

What to record after each message

Save the last contact date, the question you asked, the next agreed date and what you are waiting for. A next action should be something you can do: confirm the approval contact, answer a scope question or ask for the review date. “Waiting” alone gives you nothing to review tomorrow. Treat a proposal view as a signal that the link was opened, not as proof that the budget has been approved.

  • Reply received: note the question and set the next action.
  • More time requested: record the new date rather than continuing the old schedule.
  • Scope changed: revise the proposal and confirm which version is being reviewed.
  • Accepted: agree on contract, payment and kickoff steps through your normal process.
  • Declined or paused: record the reason if the client shares it; do not manufacture one.

How to use this workflow in LeadPilot

Open the relevant client record, review the saved proposal and messages, and set a follow-up date. Edit the wording for that client and send it through your own email or messaging app. LeadPilot does not automatically send these emails. Use the interactive demo before signing in to see how a pipeline, proposal decision and dated next action fit together.

See how proposal views and client decisions are recorded before choosing your next follow-up. A view is not acceptance; you send the message yourself.

Keep the review date beside the client with CRM follow-up planning and task reminders. You can start a free workspace with 100 contacts, 25 active deals and three new proposals per UTC calendar month.

Can a follow-up guarantee a reply?

No. A clear message can reduce confusion, but the client may have changed priorities, lost budget or chosen another option. Judge the process by whether your records are accurate and each live opportunity has a useful next step. Do not interpret silence as acceptance or keep sending messages after the recipient asks you to stop.

Additional situation: a client questions the price

Use this after a specific budget concern, not merely after silence. Ask which outcome is essential before offering a smaller scope. Do not imply a discount, deadline or availability you have not agreed. Save the stated concern and the next decision beside the proposal.

Subject: Re: [Project] scope and budget

Hi [Name],

Thanks for explaining the budget concern. The current [currency and fee] covers [deliverables], including [important boundary].

Which outcome is most important for this phase? If [optional deliverable] can wait, I can prepare a separate reduced-scope option for you to compare. I will confirm its fee and timing before any work changes.

Would that comparison help, or should we pause for now?

Best,
[Your name]

Additional situation: you have sent a revised scope

Use this after the client requested a change and you have actually issued a new proposal. Identify the version being reviewed and summarise the change. Do not treat an earlier approval as acceptance of a new fee or scope.

Subject: Revised [Project] proposal — [version/date]

Hi [Name],

Here is the revised proposal we discussed: [link]. Please review version [version/date]; it replaces [earlier version] for this decision.

The change is [specific addition or removal]. The revised total is [currency and fee], with [timing or dependency change]. The remaining inclusions and exclusions are listed in the document.

Does this match the change you requested, and when would be a realistic review date?

Best,
[Your name]

Additional situation: the project has been postponed

Use this when the client has explicitly delayed the project. Agree whether and when to reconnect instead of continuing the old reminder schedule. If the client asks for no further contact, stop. Before restarting, reconfirm scope, availability and any quote that may have changed.

Subject: Pausing [Project] until your next review

Hi [Name],

Thanks for letting me know that [Project] is postponed. I will pause the current follow-ups.

Would you like me to check back around [suggested month/date], or would you prefer to contact me when the timing is clearer?

When you are ready, we can reconfirm the scope, fee and availability before agreeing a new start date.

Best,
[Your name]

Continue your workflow

  • Freelance proposal checklist with a scope worksheet
  • A freelance client pipeline: stages and a tracker example
  • Freelance client onboarding checklist and welcome email

See how this fits a freelance CRM workflow or a consulting practice.

All resources
FeaturesFor freelancersFor consultantsResourcesSecurityGuidePrivacyTermsRefundsSupport