A useful follow-up email reminds the client what you discussed, gives them a reason to reply and asks one clear question. Start with the review date you agreed. If there was no date, allow time for a proper review, then send a short message that helps the client make the next decision.
The examples below are for agencies, consultants and freelancers following up on client work. Replace every bracketed detail and remove anything you cannot support.
When should you follow up?
Use the client’s stated timeline first. If they said they would review the proposal on Friday, do not chase them on Wednesday. If there was no agreement, three to five business days is a practical starting point for an ordinary client request — not a rule for every situation. Allow more time for a complex procurement process or several reviewers, and explain a genuine deadline if the project depends on one.
Before sending, check the recipient, the current proposal link, the earlier conversation and any reply or request to pause. Proposal activity can add context, but an unrecorded view does not prove disinterest, and a recorded view does not prove an intention to buy.
A simple structure
Use a recognisable subject, one sentence of context, one useful detail and one easy question. Keep the question tied to the decision the client actually needs to make.
Instead of “Just checking in. Any update?”, try: “Does phase one cover the pages you need for launch, or should I revise that scope before your review?”
8 follow-up email templates for client work
1. After a discovery call
Use when: you need one missing detail before preparing the proposal.
Subject: [Project] — one detail before I prepare the scope
Hi [Name],
Thanks again for discussing [project or goal]. Before I prepare the proposal, could you confirm [one missing detail]?
That will help me scope [specific part of the work] accurately. If the timing has changed, please let me know.
Thanks,
[Your name]
Customise: ask for the detail that genuinely changes your offer. Avoid sending a long questionnaire disguised as a quick follow-up.
2. After sending a proposal
Use when: the agreed review date has passed, or a reasonable review period has elapsed.
Subject: [Project] proposal — next step
Hi [Name],
Following up on the [project] proposal I sent on [date]. Here is the current link: [proposal link].
Is there anything in the proposed scope you need me to clarify before deciding on the next step?
Thanks,
[Your name]
Customise: name a known open question if there is one. You do not need to mention whether the proposal was opened.
3. After sending a quote
Use when: the client needs to decide whether the defined work fits their needs.
Subject: [Project] quote — confirm the included work
Hi [Name],
The quote covers [short scope summary], with [important exclusion] outside the fee.
Does that match what you need for this stage, or would you like me to quote a smaller first phase?
Here is the quote again: [link].
Best,
[Your name]
Customise: offer a smaller phase only if it is workable. Do not imply a discount you have not decided to give.
4. When another person needs to review
Use when: the client mentioned a colleague, finance team or final approver.
Subject: [Project] — supporting the internal review
Hi [Name],
You mentioned that [person or team] would also review the proposal.
Would a short summary of the scope, fees and responsibilities help with that conversation? I can prepare it around the questions they need answered.
Thanks,
[Your name]
Customise: do not assume the contact lacks authority. Refer only to the review process they actually described.
5. After sending a revised proposal
Use when: you have made changes the client requested.
Subject: Revised [project] proposal — [specific change]
Hi [Name],
I updated the proposal to reflect [requested change]. The current version is here: [link].
[One sentence explaining any effect on scope, fees or timing.]
Does this resolve the point you raised, or is there anything else we should clarify?
Best,
[Your name]
Customise: identify the change rather than asking the client to compare every page. Check that the link opens the intended version.
6. A second follow-up with useful context
Use when: you have something relevant to add after an unanswered follow-up.
Subject: [Project] — a clarification on [decision]
Hi [Name],
One detail that may help with your review: [specific clarification about the proposed work].
For [client’s stated priority], would you prefer [workable option A] or [workable option B]? I can update the proposal once that is clear.
Thanks,
[Your name]
Customise: offer choices that actually matter. Do not manufacture a new “insight” solely to send another email.
7. When a real scheduling deadline is approaching
Use when: capacity or a delivery dependency creates a genuine decision date.
Subject: [Project] — confirm timing by [date]
Hi [Name],
To keep the proposed [start date or milestone], I need [approval or dependency] by [date], because [brief factual reason].
Would you like to proceed on that schedule, or should I revise the timing?
If your review needs longer, I can confirm the next available dates before we commit.
Best,
[Your name]
Customise: use an honest deadline. Avoid invented scarcity or suggesting a slot is reserved when it is not.
8. A final message to close the loop
Use when: earlier messages remain unanswered and another follow-up would add little.
Subject: [Project] — closing the loop for now
Hi [Name],
I have not heard back about the [project] proposal, so I will leave the conversation here for now.
If it becomes a priority again, you are welcome to reply. We can confirm the scope, availability and pricing at that point.
Thank you for considering the work,
[Your name]
Customise: keep it neutral. Closing the loop is not a threat or a tactic to make the client feel guilty.
How many follow-ups should you send?
There is no universal number. Space messages around the agreed review process, add useful context and stop if the person declines or asks you to stop. After unanswered messages with no new information, a neutral close-the-loop email is often more useful than repeating the same request. An active project with a contractual dependency may need its agreed escalation process instead.
Should you reply in the same thread?
Keep the existing thread when it contains the context the client needs. Use a new, descriptive subject if the conversation has changed substantially or the earlier thread is confusing. Whichever you choose, make the current proposal link and the requested decision easy to find.
Keep the next action with your proposal
In Propovo, open Deals → Actions, read the proposal’s status and available feedback, then prepare the next message. Check the recipient, current version and timing before sending through a connected account. Record the outcome and update the deal stage to reflect the actual conversation.
Propovo’s suggestions help organise the work; you decide the message and the next step. Propovo does not read your inbox or track email replies. Learn the proposal follow-up workflow or explore Proposal Copilot.