Clients ghost after a proposal mostly because responding requires effort they haven't found time for, not because they've decided no — 60% of proposals go silent, yet 42.5% of closed-won deals close within 24 hours of the client actually opening the document. That gap between "went quiet" and "said no" is the whole story: most ghosting is delay, not rejection, and it's preventable with the right structure.
The Real Reasons Clients Go Quiet
It rarely comes down to a single dramatic reason. In order of how often each actually happens:
- They got busy and the proposal fell off their radar. No malice, no decision — just a full inbox and a task that felt postponable.
- The price surprised them and they don't know how to respond. Rather than negotiate, many people avoid the conversation entirely.
- They're comparing you against other quotes and waiting to have all the information before replying to anyone.
- The proposal didn't make the next step obvious, so there was no clear action to take.
- They genuinely went with someone else — the least common reason, despite being the one freelancers assume by default.
Notice that four of the five reasons have nothing to do with the quality of your work or your price being wrong. They're about friction, timing, and unclear next steps — all fixable on your end, not theirs.
The Data Behind the Silence
| Stat | What it means for you | |---|---| | 60% of proposals go silent | Silence is the norm, not a signal you did something wrong | | 42.5% of closed-won deals close within 24 hours of the proposal being opened | Speed of follow-up after that open matters more than proposal polish | | Day 1: prospect is ~80% ready to move forward | Your best shot is fast, not perfect | | Day 7: prospect is reconsidering whether they need the service at all | Every day of silence erodes the deal, even if they never explicitly declined |
The pattern across all four numbers is the same: readiness is highest right after they open the proposal, and it decays on a clock you can't see. Treat silence as a countdown, not a rejection.
Why "Just Checking In" Makes Ghosting Worse
When freelancers do follow up, the default message is some version of "just checking in" — and it's consistently the lowest-performing opener available. It asks the prospect to generate a reply from nothing, which is exactly the kind of low-priority task that gets pushed to tomorrow, and then next week. A follow-up that adds something new — a case study, an answer to an objection they probably have, a specific yes/no question — gives them a reason to engage instead of a reason to defer again. The full sequence and message templates are in how to follow up after sending a proposal.
The Structural Fix: Book the Call Before You Send
The single most effective way to prevent ghosting isn't a better follow-up message — it's changing what happens before you send the proposal. If you book a short walkthrough call to present the proposal live, or schedule a call for right after you send it, the prospect now has something on their calendar. Going quiet requires actively cancelling a meeting, which is a much higher-friction action than simply not replying to an email that arrived in a full inbox.
This flips the default. An unbooked proposal makes silence the path of least resistance. A booked call makes silence require a decision.
| Approach | Default behavior if they hesitate | |---|---| | Proposal sent cold, no call booked | Silence — easiest option, no action required | | Proposal sent, call already booked | Must actively cancel or reschedule — a visible action | | Proposal presented live on a call | No ghosting possible — objections surface in real time |
Other Ways to Prevent Ghosting Before It Starts
- Set a clear next step, not an open-ended one. "Reply to confirm and I'll send the deposit invoice" gives a single obvious action. "Let me know if you have any questions" invites no action at all.
- Put an expiration date on the proposal. A deadline creates urgency and gives you a natural, non-awkward reason to follow up ("just flagging this expires Friday") instead of an empty check-in.
- Address the likely price reaction inside the proposal itself. If you expect sticker shock, a short line explaining what's included and why prevents the silent, avoidant reaction described above.
- Send fast. Proposals sent within 24 hours of the conversation land while the prospect is still at peak interest, before the readiness curve starts decaying.
What to Do Once a Prospect Has Gone Quiet
If the call-booking prevention step wasn't in place and a prospect has already gone silent, the recovery path is the structured follow-up sequence — 4-5 touches over about 21 days, each one adding something new rather than repeating "checking in." That cadence mirrors what works in cold outreach generally; see the cold email follow-up sequence that actually works for the underlying data on why more touches beyond that range actually reduce reply rates.
For the pricing structure that tends to reduce the "surprised by the number" version of ghosting specifically, see three-tier pricing for web design proposals — giving a prospect options instead of a single take-it-or-leave-it number removes one of the most common reasons people avoid replying altogether.
Ghosting Is a Symptom, Not the Root Problem
If a large share of your proposals go silent and never come back even after a full follow-up sequence, the issue is often upstream — the deal was never as warm as it looked, or the proposal was sent to a lead who wasn't genuinely ready to buy. Revisit the full framework in the psychology of web design proposals that win for how trust, timing, and structure combine to prevent this earlier in the process.
Where Runvax Fits
Runvax's pipeline is built around this exact problem: prospects sitting in the "Proposal" stage untouched for 3+ days get an automatic "needs follow-up" flag, so a stalled deal never quietly falls off your radar the way it falls off theirs. Try Runvax free to find no-website leads, send outreach, and keep every proposal moving through a pipeline instead of an inbox you forget to check.