Follow up on a sent proposal within 24-48 hours with a message that adds new value — a case study, an answer to a likely objection, a relevant example — never a bare "just checking in." That single swap is the difference between a follow-up that gets read and one that gets ignored, because "just checking in" gives the prospect nothing new to respond to.
Most freelancers either don't follow up at all, or follow up once and give up. Both are mistakes, and both are fixable with a specific sequence.
Why Follow-Up Matters More Than the Proposal Itself
60% of proposals go completely silent after they're sent. That number alone makes follow-up the highest-leverage activity in your entire proposal process — higher leverage than another hour spent polishing the document. And the silence isn't necessarily a "no": 42.5% of closed-won deals close within 24 hours of the client opening the proposal, meaning a large share of "silent" prospects are simply distracted, not uninterested. Follow-up is how you catch them at the moment they re-open it.
There's also a decay clock running that most freelancers don't account for. On day 1 after sending, a prospect is roughly 80% ready to move forward. By day 7, they're reconsidering whether they need the project at all. Every day without a follow-up is a day closer to that reconsideration point — which is exactly why the psychology behind proposal timing, covered in the psychology of web design proposals that win, treats follow-up speed as a conversion lever, not just good manners.
The Follow-Up Sequence
| Touch | Timing | Goal | What to include | |---|---|---|---| | 1 | 24-48 hours after sending | Confirm receipt, stay top of mind | Short, low-pressure check-in with one new detail | | 2 | Day 4-5 | Add value, address a likely objection | A relevant example, mini case study, or answer to an unasked question | | 3 | Day 7-8 | Create gentle urgency | Reference proposal expiration or your current availability | | 4 | Day 12-14 | Final direct ask | A clear yes/no question, not another open-ended nudge | | 5 (optional) | Day 21 | Long-term nurture | Move to a "check back in a quarter" list, not a hard close attempt |
This mirrors the broader cold outreach data on cadence: 4-5 touches spread across roughly 21 days consistently outperforms both single-touch and over-persistent approaches. The mechanics are nearly identical to the cold email follow-up sequence that actually works — a proposal follow-up is just a cold follow-up sequence applied to a warmer, further-along lead.
What to Actually Say at Each Touch
Touch 1 — the confirmation nudge. Keep it under three sentences. The goal isn't to sell, it's to surface any blocker before it hardens into silence.
"Hi [Name] — wanted to make sure the proposal landed okay on your end. Happy to hop on a quick call if anything needs clarifying before you decide."
Touch 2 — the value-add. This is the touch most freelancers skip, and it's the one that recovers the most stalled deals. Instead of asking "any updates?", give them a reason to re-engage.
"Thought this might be useful — here's a quick before/after from a similar [industry] project I did last month. Happy to walk you through how it applies to what we discussed for [Business Name]."
Touch 3 — gentle urgency. Only use real constraints, never invented ones. If your proposal has an expiration date (it should), this is where you reference it.
"Just flagging that the pricing in your proposal is valid through [date] — after that I'll need to re-quote based on my current schedule. No pressure either way, just want you to have the full picture."
Touch 4 — the direct ask. By this point, ambiguity is the enemy. Ask a question that only needs a yes or no.
"Totally understand if the timing isn't right — would it help to revisit this in a month or two, or is this not something you're planning to move forward with? Either answer is fine, just want to stop cluttering your inbox if it's a no."
The Opener to Never Use
"Just checking in" is consistently the worst-performing follow-up opener. It asks the prospect to do the work of remembering the context, generating a response, and re-engaging — all without giving them anything back. Every message in the sequence above either adds information, asks a specific question, or creates a real (not fake) deadline. That's the actual rule: never send a follow-up that doesn't contain something the first email didn't have.
What to Do If They Ask for a Discount Mid-Sequence
A follow-up sometimes surfaces a price objection instead of a yes. Don't discount the same scope — offer a smaller one at a lower price, and hold your rate. This keeps the sequence moving without training the client to expect a markdown on request, and it's worth having a ready answer before you need it rather than improvising one under pressure.
When to Stop Following Up
Stop after the direct ask in touch 4 gets a clear no, or after touch 5 gets no response at all. Continuing past that point stops looking persistent and starts looking like you have nothing else going on — which undermines the same trust signals a well-structured proposal built in the first place. Move the lead to a quarterly check-in list instead of deleting it; timing, not interest, kills most of these deals, and timing changes.
Prevent the Need for a Long Sequence in the First Place
The best follow-up sequence is a short one, because the deal closed on touch 1 or 2. The single biggest lever for that is booking a walkthrough call before you send the proposal at all — a prospect with a call on the calendar has to actively cancel to go quiet, which is a much higher-friction action than ignoring an email. We cover why ghosting happens in the first place, and how to structurally prevent it, in why clients ghost after a proposal.
Where Runvax Fits
Manually tracking which prospect is on which follow-up day, for every open proposal, is exactly the kind of admin that eats freelancer time — industry data puts 36% of freelancer time in admin tasks that connected tools could automate. Runvax's pipeline flags any prospect untouched for 3+ days with a "needs follow-up" flag automatically, so the sequence above runs on a reminder system instead of your memory.