Start with the buyer’s decision date
The best next date is one the buyer helped choose. When you send a proposal, ask when they expect to review it and who else needs to approve it. A consultant selling a small audit and an agency proposing a multi-stage redesign should not assume the same buying process. Write the expected decision date beside the proposal amount before setting reminders.
Use this line when sending: “I’ve attached the scope we discussed. When do you expect to make a decision?” Once they answer, schedule your follow-up around that answer. If they say the committee meets next Thursday, do not send three reminders before Thursday. Ask whether a Friday follow-up works. The agreement is more useful than a sequence chosen without context.
If there is no response and no stated timeline, use a default with a stopping point. The day 3, 10, and 21 schedule below gives each touch a different job. Count elapsed calendar days from sending, then move any weekend or holiday reminder to a normal working day for the recipient. Do not treat the exact dates as a rule about buyer behavior.
Day 3: confirm that the proposal can move forward
The first follow-up checks for an obstacle rather than asking for a rushed decision. Perhaps the attachment was missed, the scope is unclear, or another person needs a copy. Keep the original email thread so the buyer can find the proposal. Ask one question, and choose the question that matches the conversation you actually had.
Example: “Hi [name], following up on the [project] proposal I sent on [date]. Is there anything missing that you need before reviewing the scope?” If you already discussed a start date, use that instead: “Does the proposed [date] start still fit your review timeline?” Send one version, not both questions together.
A real deadline changes the schedule. If a reserved start date expires this week, explain that constraint when sending the proposal and remind the buyer before it expires. Do not invent competing clients or a vanishing slot to create urgency. If you cannot reserve capacity without an agreement, say that availability will need to be reconfirmed.
Day 10: resolve a concrete decision obstacle
A second message needs a reason beyond the passage of time. Review your discovery notes. Did the buyer ask about handover, scope boundaries, or how a smaller first phase might work? Answer one of those points accurately. If nothing new is available, ask about the review process rather than manufacturing a case study or sending an unrelated article.
Example: “Hi [name], one clarification on the [project] proposal: the handover session is included in the quoted scope. Is there a scope question holding up the review?” Use this only if the session really is included. A follow-up should make the existing offer easier to evaluate, not quietly add work you have not priced.
If the buyer replies “we need another month,” stop the default sequence. Ask for a specific reconnection date and record it. If the reply is about price, clarify whether the issue is budget, scope, or timing before preparing a different offer. A smaller phase can be an option, but silence alone is not evidence that a discount is needed.
Day 21: close the active loop without a threat
The third touch gives the buyer an easy way to state whether this is still active. It is also your own stop rule. You need a record that distinguishes an unanswered proposal from a current conversation. Leaving every silent proposal marked as likely work makes next month’s capacity plan difficult to trust.
Example: “Hi [name], should I keep the [project] proposal active, or close it for now? If the timing has changed, I’m happy to revisit when there’s a review date.” Avoid guilt, accusations, or claims that this is the buyer’s last chance. You are clarifying your planning, not requiring them to justify their silence.
After another reasonable response window, archive an unanswered proposal as dormant. For example, review it at the end of that working week. Do not count its value as booked work. Reopen it if the buyer returns, checking scope, price validity, and capacity again. A dormant record preserves the context without filling your calendar with repeated chase reminders.
Adapt the schedule and track the next action
Three touches are an example limit for an ordinary unanswered proposal, not an obligation. A clear no ends the sequence immediately. A request to stop contact ends it too. An agreed procurement process may take longer and require different dates. If you suspect delivery failed, verify the address you were given; do not jump across personal channels to force a response.
Keep a small record: proposal sent date, value, stated decision date, last contact, status, and next action date. For a hypothetical $4,000 proposal sent on November 2, the default reminders would fall around November 5, 12, and 23. A reply on November 12 asking for December 1 replaces the final reminder with that agreed date. No reply leaves the proposal dormant after the closing touch.
Review due follow-ups before opening a new prospecting list. Pick the one with a current buyer signal and a clear unanswered question. OneMove can help choose one move a day from the pipeline context you provide, with an evening check-in and a weekly scoreboard. Your own proposal record remains the place to keep the agreed dates and the actual replies.