Proposals & decisions
Proposal follow-up: email templates and timing
What to write when a proposal receives no reply. Four email templates, practical timing and a process that makes outstanding decisions visible.
Short answer
Follow up on a proposal at the agreed time first. Without an agreement, around three to five working days can be a starting point, depending on the project. Address a specific open question, offer relevant help and agree a next step. A reply or postponement replaces the default sequence.
Key takeaways
- An agreed response date takes priority over any default interval.
- No reply is not evidence of a price objection.
- Every follow-up must refer to the current proposal version.
- Report open, won and lost proposals with clearly defined denominators.
No response to your proposal: what to clarify first
The conversation went well, the proposal was sent, and then everything went quiet. Before writing another reminder, ask a different question: what decision is actually outstanding on the customer's side?
They may need a technical answer, approval from someone else or a later project date. The proposal may no longer fit. Silence alone does not reliably distinguish these explanations. An immediate discount or urgent closing request may address a concern the customer never raised.
A Reddit discussion among small businesses captures this uncertainty: how many times should you follow up on a quote or proposal before putting an unanswered opportunity aside? Experiences differ. They do not establish a universal number of useful contact attempts.
This guide helps you move an open proposal decision forward with suitable wording, a manageable schedule and a clear separation between automated reminders and personal conversations. It is for proposals that have already been requested, not cold mass outreach.
When should you follow up on a proposal?
An agreed response date is the best starting point. If your contact says the internal discussion will happen on Thursday, a Wednesday reminder is usually not helpful. Record the date and reason alongside the proposal.
If nothing has been agreed, we suggest reviewing an ordinary, non-urgent service proposal after three to five working days and sending a relevant question. This is an organisational starting point, not a scientifically established optimal interval. An urgent repair, a complex consulting project and a formal tender have different decision processes.
Situation | Appropriate next contact | What to avoid |
|---|---|---|
A response date was agreed | On that date or after a reasonable interval. | An extra automatic reminder immediately before it. |
No deadline; ordinary proposal | As a starting point, review after three to five working days and ask a concrete question. | Daily messages with no new reason. |
You still owe the customer an answer | Answer first, then agree the next stage. | Asking for a decision while your own response is missing. |
Internal approval is pending | Clarify the decision-maker, required information and next review date. | Asking for the same status every day. |
The project has explicitly moved | Resume only at the agreed later time. | Keeping the person in a short generic sequence as well. |
Clear rejection or sending restriction | End the active sequence and record the outcome. | Automatically switching to a discount or another channel. |
Your schedule needs an endpoint. An initial question, a second message with a genuine clarification purpose and a clear close can be enough to start. If a conversation begins after the first message, that rigid schedule no longer applies.
Follow up for a reason, not just because time passed
Start with the agreement
An agreed response date takes priority over a default interval.
Clarify one issue
With no agreed date: use about 3–5 working days as a starting point, then ask one specific question.
Offer relevant help
Resolve a missing document or decision, instead of repeating the same email.
Close the open loop
Without a new reason, put it aside; agree a review date if the need is postponed.
The customer replies or proposes a date?
The individual agreement replaces the default sequence.
Editorial starting recommendation, not a scientifically optimal contact count or a promise of success.
What must be clear before the first follow-up email
A well-maintained proposal record needs more than a price and an email address. Record its reference number, current version, send date, scope, contact person, open questions and next agreed action. Include a genuine validity deadline where one exists. Do not invent an expiring reservation to create pressure.
Keep separate records when one person has several proposals. A customer can reject proposal A while still considering proposal B. A single contact status of “rejected” is too broad for that situation. Changes need similar care: when the scope is revised, the old version must not continue receiving automated follow-up.
Before sending, check whether anyone on the team has called or replied personally since the last message. A brief call note with its outcome and next review date prevents automation from interrupting a live discussion.
Why an email-open event is not enough
An open indicator does not reliably establish that your contact read the proposal. Apple explains that Mail Privacy Protection can download remote content in the background. This can distort technical measurements of email opens.
An opened proposal document is not a decision either. In its vendor report State of Proposals 2026, Proposify analyses 742,137 proposals sent through its own platform across 30 industries in 2025. On average, 93% of proposals that were later accepted had been viewed, compared with 80% of those later rejected. The overlap matters: extensive viewing does not reliably separate acceptance from rejection. The platform data is neither independent nor representative of the DACH market, and it does not establish cause or buying intent.
Rejected proposals are still read extensively
Share of the proposal viewed before the decision · 742,137 proposals sent in 2025; report published in 2026
- Later accepted93 %
- Later rejected80 %
View data table
| Category | Share of the proposal viewed before the decision |
|---|---|
| Later accepted | 93 % |
| Later rejected | 80 % |
Viewing depth can add context, but it does not establish buying intent or explain the decision.
Source: Proposify: State of Proposals 2026 · 742,137 proposals sent in 2025; report published in 2026. Proposals across 30 industries sent through the Proposify platform.
Vendor platform data, neither independent nor representative of the DACH market. The association between viewing depth and outcome does not establish intent or causality. Not ONE LOOP results.
Do not treat an open event as proof of interest or rejection. A separate proposal portal may provide different signals, but a view still does not replace an explicit decision. “I noticed you opened our proposal five times” is neither necessary nor a useful basis for a straightforward conversation.
Four follow-up email templates for different situations
Adapt these templates to the actual conversation. Square brackets are placeholders, not ready-made CRM variables. Remove anything that does not fit, and use an appropriate, permitted contact channel. The wording should make a reply easier, not force a particular decision.
1. First follow-up: identify an open question
Subject: [Project] – is there a point we still need to clarify?
Hello [name],
On [date], I sent proposal [reference] for [specific service].
What would you still need to clarify before deciding on the next step? If there is a particular item you would like to discuss, simply reply with the point.
If the documents did not arrive, I am happy to resend them.
Best wishes, [Name]
The message does not pretend to know why the customer has not replied. It offers a substantive discussion and an easy way to flag a delivery issue. If you already know the open question, name it instead of asking a general one.
2. Internal approval: information instead of more pressure
Subject: [Project] – support for your internal discussion
Hello [name],
You mentioned discussing the proposal with [role / team]. Is there any information still missing, perhaps about [relevant point]?
I can send a short summary or explain the point in a joint conversation. When would it be realistic to hear back about the next step?
Best wishes, [Name]
Use this only if internal approval was actually discussed. Assuming the person must consult their manager is not appropriate. An additional summary is useful when it supports a decision, not when it is merely another attachment.
3. Postponed project: agree a specific review point
Subject: [Project] – a suitable time to continue
Hello [name],
Thank you for letting us know that [project] is not moving ahead yet. We will pause further proposal follow-up.
Would you like me to contact you in [agreed period], or would you prefer to get back in touch? If we resume later, we will review the scope, availability and terms again at that point.
Best wishes, [Name]
A later review is not an acceptance. Record the agreed period and stop the short generic sequence. If further contact is not wanted, do not schedule another reminder.
4. Closing message: put the open record aside cleanly
Subject: Proposal [reference] – putting this on hold for now
Hello [name],
We have not yet received a response to the proposal for [service]. We will therefore put it on hold and end this follow-up sequence.
If you would like to revisit the topic later, please get in touch. We can then check whether the proposal still fits your needs and our current schedule.
Best wishes, [Name]
This is an administrative close, not a threat. Do not invent scarcity or automatically delete the entire contact history. A later enquiry can create a new opportunity without losing the history of the previous decision.
When a call is more useful than another email
Another email is not always the best answer to an unresolved proposal. A conversation may help when several service options need comparing, an important question remains open or a callback has already been agreed. The call must fit the existing enquiry and the appropriate contact channel.
A short opening could be: “I'm calling about proposal [reference]. Is this a suitable moment for a quick question?” Follow with a concrete distinction: “Is something still unclear about the scope, or is the main question the timing?”
Allow space for the answer. If the customer says the proposal is too expensive, first clarify whether they mean budget, value or scope. An automatic discount may otherwise address the wrong problem. If they want a smaller scope, prepare a traceable revised proposal rather than making an informal commitment in the follow-up chat.
Finish with a specific agreement: send information, revise an item, discuss the proposal together, review it later or close it. Record that agreement. “Called, no answer” and “Spoke, decision next week” require different next actions.
What to automate – and what should remain personal
Automation can organise work before it sends anything. For many teams, a reliable task with a prepared message is already a substantial improvement. A fully automatic sequence does not have to be the immediate next step.
Task | Recommendation for the first version |
|---|---|
Record the proposal and next due date | Automate once the actual sending event is reliable. |
Remind the owner | Automate; include the proposal reference and context in the task. |
Prepare the first factual follow-up email | Provide a template and allow manual approval where needed. |
Send a standard message | Only when the proposal is clearly open, the version is current and there is no new reply, pause or restriction. |
Negotiate price, scope or contractual details | Handle personally; never manufacture an automatic commitment. |
Interpret an ambiguous reply | Assign it for review instead of automatically marking the deal won or lost. |
Check four things before each proposal email
The right proposal?
Use its ID and current version, not a generic contact status.
Still open?
Account for acceptance, decline and agreed postponements.
Whose turn is it?
Do not remind the customer when your team still owes an answer.
Approve the send
Check due time, ownership and channel; create a task when uncertain.
New version, reply or personal pause?
Do not send the old step; establish the valid next action.
Proposed approval logic. An elapsed wait does not prove the next message is still appropriate.
A suitable starting event might be a reliably recorded proposal send or a deliberately set proposal status. Having an email address is not a substitute. Store the proposal association, check the current state and create the next task.
Immediately before an automatic send, check the version, due time and conversation again. A new reply, revised proposal, personal handover or clear decision stops the previous plan. A customer's answer about proposal A must not change proposal B without checking the context.
Be especially careful with tasks your team still owes. If the customer asked a question and your answer is missing, the customer's decision is not overdue. The next action belongs to you.
Common proposal-follow-up mistakes
Symptom | What to inspect | Useful correction |
|---|---|---|
Customer receives a message about the old price | Linked proposal version and outstanding send plans. | End the old sequence; track the revised version with its own agreement. |
Two colleagues follow up in parallel | Ownership and personal activity in the history. | Assign one owner and a shared next task. |
A reminder arrives after a rejection | Stop event, wait step and final pre-send check. | Re-check the decision before any further message. |
Many reminders, little clarity | Questions being asked and the actual decision stage. | Resolve a specific point instead of rephrasing the same check-in. |
“Sounds good” automatically becomes a won deal | Free-text interpretation rule. | Have a person clarify ambiguous statements and confirm the next action. |
Test with sample proposals and your own designated test contacts first. Deliberately revise a proposal shortly before a planned message. Reply once before and once after a waiting period expires. Also check whether a manual pause after a call remains in place until someone deliberately sets the next review date.
These are tests to perform and expected behaviours, not completed tests in your account. An automation is ready for use only when its actual signals and exceptions match your proposal process.
Numbers that help you manage open proposals
Start with a reliable overview: which proposals are open, where your team still owes an answer, which due dates have passed, and which opportunities were explicitly postponed or declined. Adding up all quoted prices does not answer those questions.
For success rates, the denominator matters. Consider an illustrative example: from one cohort of 20 proposals, five were won, three were lost and twelve remained undecided within a defined observation period.
Example measure | Calculation | Result |
|---|---|---|
Won as a share of all proposals sent | 5 divided by 20 | 25% |
Won as a share of decided proposals | 5 divided by 8 | 62.5% |
Still open | 12 out of 20 | 60% |
Both win rates are mathematically correct, but answer different questions. The twelve open proposals must not also be classified as lost. Compare cohorts with equal observation windows and similar proposal types. Otherwise, a higher rate may simply reflect more time to reach a decision. These example values are not an industry benchmark or ONE LOOP customer results.
Add operational measures: the share of proposals with an agreed next action, overdue tasks and time to an explicit decision. Record price as a loss reason only when feedback supports it. Silence remains “no response”, not an invented rejection over price.
Start a clear proposal process with ONE LOOP
Begin with a pipeline for open proposals, clear ownership and a shared task list. Each record needs the current proposal version, a status and the reason for the next contact. ONE LOOP can connect history, tasks and the sales process; configure individual rules to match your account setup.
Start with prepared templates and manual approval. Automate sending only where the context can be identified reliably. Individual replies and changes stay visible to the team. That allows automation to grow from an understandable process rather than becoming a second, invisible conversation alongside sales.
If enquiries disappear before a proposal is sent, start with the lead-follow-up guide. If the next step is a meeting, add an appointment process with clear reminder and cancellation rules. The ONE LOOP sales platform explains how the capabilities connect.
Good follow-up is not about sending the largest number of messages. It gives an open decision an appropriate next step, and makes sure that a finished sequence really stays finished.
FAQ
