Why good proposals still need follow-up
A client can like your proposal and still not reply. They may be comparing suppliers, waiting for a stakeholder, reviewing budget, or simply dealing with a busy week. Silence does not automatically mean rejection. A follow-up gives the client a low-pressure opportunity to tell you what is happening. It also gives you a chance to discover whether the obstacle is price, timing, scope, internal approval, or lack of urgency.
Choose the follow-up timing based on the buying process
There is no universal "perfect" number of days. For a small project, a follow-up after two or three business days can be reasonable. For a larger proposal with several stakeholders, a longer interval may make sense. The key is to match the timing to the decision process you discussed. If the client said they would review proposals Friday, following up Monday is more useful than sending an arbitrary message the next morning.
Make the first follow-up easy to answer
Do not send a paragraph that asks the client to write an essay. A simple question works better: "Have you had a chance to review the proposal, and is there anything you would like me to clarify?" This gives them two easy paths: confirm they are reviewing it or tell you what needs attention. The goal is conversation, not pressure.
Follow up with value when possible
The strongest follow-ups add context rather than repeating "just checking in." If you noticed a relevant issue during the proposal process, share a useful observation. If you prepared two scope options, explain when each one makes sense. If a timeline window is genuinely becoming constrained, say so accurately. Do not manufacture urgency. Trust is more valuable than a forced deadline.
Use the proposal itself as the follow-up anchor
A proposal with clear sections makes follow-up easier. You can refer to a specific item: "I wanted to check whether the content migration section matches what your team had in mind." This is much more useful than asking whether they "liked the proposal." Specific questions encourage specific answers.
What to do when the client says it is too expensive
Do not immediately discount the project. First ask what they are comparing the proposal against or which part of the scope is causing concern. Sometimes the issue is not the total but the payment schedule, timing, or inclusion of a deliverable they do not value. If necessary, offer a reduced scope rather than the same work for less money. That protects the relationship and your margin.
What to do when the client goes completely silent
After a few useful follow-ups, close the loop politely. You can say that you will assume the project is not moving forward for now and that they are welcome to reach out if priorities change. This removes the awkwardness and protects your pipeline. It also gives you a clean reason to stop spending time on an uncertain opportunity.
Create proposals that make follow-up easier
A vague proposal creates vague follow-up conversations. A clear document gives you concrete points to discuss: scope, deliverables, price, assumptions, timeline, and next steps. For Google Docs users, a repeatable proposal structure makes this easier because each new proposal has the same commercial logic. Tools such as Docs Estimator can help standardize the estimate portion so you spend more time on the client-specific strategy.
A simple follow-up sequence
For many small projects, a practical sequence is: initial follow-up after the expected review window, a second message that addresses a likely question or adds useful context, and a final close-the-loop message. Adjust the sequence to the client and deal size. The objective is not to maximize the number of messages. It is to make the decision process easier while preserving a professional relationship.