What you can use
Use three adaptable proposal follow-up emails, a decision checklist, and a simple log to choose the next step without assuming silence means rejection.
SOLOHATCH FIELD GUIDE · OFFERS AND CLIENTS
A proposal follow-up should make the next decision easier: confirm receipt, identify what is still unclear, or agree to pause the conversation.
No reply can have several explanations. The proposal may be waiting for another person, the timing may have changed, the offer may be unclear, or it may no longer be a priority. You do not know which explanation applies until you have more information. Use the examples below as adaptable starting points rather than a universal sequence.
Check the context before sending another message
Re-read the last conversation and the proposal. Did you agree on a review date? Was the proposal requested? Did the recipient know what response you needed? Is there an unanswered question that you should address first?
If a review date was agreed, use it as your reference. If it was not, choose a reasonable point based on the project’s urgency, the recipient’s stated process, and the route through which you are communicating. There is no timing rule here that guarantees a reply.
- Check that the proposal link or attachment is accessible.
- Confirm the message went to the intended contact.
- Make sure the request, scope, and next decision are understandable.
- Respect any request to pause or stop contact.
- Use a suitable professional contact route and follow its rules.
A missing attachment calls for a simple correction. An unclear deliverable may call for a scope clarification. Neither problem is solved by repeatedly sending “just checking in.”
Template 1: confirm receipt and name the next decision
Use this when you have a relevant, ongoing conversation and do not know whether the proposal arrived or can be opened.
Subject: [Project] proposal and next step Hi [Name], I sent the proposal for [specific deliverable] on [date]. Were you able to open it? The main decision is whether [bounded scope] fits what you need for [stated situation]. If useful, I can clarify [specific open point]. Would you prefer to discuss that question, continue reviewing, or pause for now? Best, [Name]
Replace the open point with something real from the conversation. Avoid inventing a concern in order to create urgency. The message should be easy to answer even if the answer is “not now.”
Template 2: clarify a known decision point
Use this when the prospect has already mentioned a question about scope, timing, inputs, or the decision process. Answer that point rather than attaching a new sales argument.
Subject: Clarifying [question] in the [project] proposal Hi [Name], You mentioned [specific concern] when we discussed [project]. The proposal currently includes [relevant included work]. It excludes [relevant boundary]. Before [stage] can start, I would need [specific input or decision]. Does that address the point you were reviewing, or is there another part of the scope we should clarify? Best, [Name]
If the scope needs to change, say so plainly and prepare an updated version after the change is agreed. Do not quietly add work to an old proposal and leave two conflicting versions in circulation.
Template 3: close the loop without pressure
Use this when appropriate follow-ups have not produced a response and you need to decide whether to keep active time or capacity assigned to the conversation.
Subject: Pausing the [project] proposal Hi [Name], I have not heard back on the [deliverable] proposal, so I will pause my follow-up for now. If the project becomes a priority later, you are welcome to get back in touch. We can then reconfirm scope, availability, and timing. Thanks for the conversation, [Name]
Send this only if you intend to pause. It should not be a disguised countdown or a claim that an opportunity will disappear when that is not true.
Choose a follow-up rule you can explain
Prefer an agreed review date over a rigid sequence. When no date was agreed, decide how much active follow-up fits the context before sending the first message. Keep that choice in your notes so you do not continue contacting someone merely because a reminder appears.
One possible personal rule is to send a receipt check, then one relevant clarification if there is a real open point, and finally pause. Another project may need a different approach. The purpose of the rule is to guide your effort and respect the other person’s decision process, not to establish an industry benchmark.
Stop when the recipient asks you to stop, declines, or explains that the project is not proceeding. If they give a later review date, record it and avoid unnecessary messages before that point.
Keep a proposal follow-up log
Proposal / version: Recipient and decision role: Requested by the recipient?: Sent date: Agreed review date, if any: Next decision needed: Known open question: Last message and response: Next action, owner, and date: Status: reviewing / clarification / deferred / declined / paused Reason supplied by the prospect, if known: What remains unknown:
Keep “no reply” as an observation. Do not turn it into “price too high,” “bad lead,” or “offer has no demand” without supporting information. If you change your offer based on silence alone, you may change the wrong part.
Worked example: the approver is unavailable
Illustrative example: a solo designer sends a proposal for a two-page service guide. The contact asked to review it with a colleague but no review date was agreed. After a suitable interval, the designer sends the receipt-check message.
The contact replies that the colleague is away until the following week. The useful next step is to agree when to reconnect and update the log to “deferred.” Offering an immediate discount would not address the reason the contact actually supplied.
If no reply arrives after the designer’s chosen follow-up boundary, the log should say “paused; reason unknown.” That keeps the record accurate and frees the designer to focus on other work.
Choose one useful next action
Before sending another message, write the decision you want the recipient to make and the information they need to make it. If you cannot identify either, improve the proposal or ask a clearer question.
The project scope template can help clarify the deliverable and exclusions. For the wider customer path, use the solo workflow map guide.
This guide was developed with AI assistance. Examples are illustrative, and templates should be adapted to your situation. SoloHatch is operated by My Target Limited. About SoloHatch · Browse all guides