How do you re-engage a cold client proposal before it expires?
Don't just resend the same document with "checking in" attached — add one new piece of information, cut the ask down to a single yes/no question, and make it plain (and true) what changes once the proposal's expiration date passes.
A proposal doesn't usually go cold because the prospect said no — it goes cold because it got buried under fifty other emails and nobody gave them a reason to come back to it. The fix isn't persistence for its own sake; a fourth "just following up" email reads as noise, not urgency. What actually reopens a stalled deal is new information, a lower-friction way to respond, and a deadline that genuinely means something.
Why the answer is what it is
Silence is usually inbox triage, not rejection
Decision-makers rarely reply to a proposal they're still weighing; they reply to whatever resurfaces at the right moment. Treat non-response as 'hasn't come back up,' not 'no,' and plan your resend around getting it back in front of them rather than apologizing for bothering them.
A plain bump rarely works twice
"Following up on this!" with the same attachment reads as noise the second time it lands. Give the resend a reason to be opened: an updated number, a detail specific to their situation, or a small scope change since the original send.
Make the expiration date do real work
If the proposal has an expiry date, decide up front what actually happens after it lapses — repricing, a lost start date, or a revised scope — and say that plainly when you follow up. A deadline nobody enforces stops functioning as a deadline.
Cut the reply down to one decision
Replace "let me know if you have questions" with a single yes/no question or two named options, like "should I hold the June 1 start date, or push it to July?" The smaller the decision you're asking for, the more likely you get an answer at all.
Change the channel before you change the message
If two or three emails haven't landed, a short call, text, or even a direct message often breaks through faster than a fourth email saying the same thing in a different tone.
What to look for
- Check how many days are actually left before the proposal or quote expires
- Add one new detail to the resend (updated number, scope tweak, relevant case detail) instead of just re-sending the same file
- Turn the CTA into a single yes/no question or two clear options, not an open invitation to 'let me know'
- Include a direct booking link so the prospect can grab time without writing a reply
- Escalate to a call or text if two or more emails have already gone unanswered
- State plainly what changes once the proposal lapses (repricing, lost start date) — and follow through on it
- Log the resend date and set your own follow-up reminder so it doesn't go quiet again
Related questions
How long should a client proposal stay open before it expires?
There's no universal rule, but 2 to 4 weeks is typical for standard agency service proposals — long enough for a real decision, short enough that pricing and scope don't go stale. Whatever window you choose, put the expiration date on the proposal itself so it's never a surprise to the client.
What should you say when a proposal has already expired?
Reissue it rather than pretend the old one still stands. A short note that the original quote lapsed, paired with a refreshed version reflecting today's numbers, is more credible than reviving a stale document and hoping nobody checks the date on it.
Can proposal software actually help stop deals from going cold?
It helps with the mechanics, not the persuasion. HubWho's quote builder puts each proposal on a live link a prospect can open on their phone and accept in one click, includes a bookable-call button right on the page, and lets you bulk re-send every stale quote in your pipeline in one action instead of following up client by client.
How Roffik addresses this
Billing, ACH and card payments, recurring subscriptions, per-client margin tracking, and branded client portals for marketing agencies — built on Midnight + cyan. Learn more about HubWho.