Why Proposals Die in Silence
Here's the uncomfortable asymmetry of proposal follow-up: to you, the proposal is a decision waiting to happen. To the prospect, it's one email in a week of two hundred. They opened it on their phone between meetings, thought "looks interesting, I'll read it properly later," and later never came. No rejection occurred. No decision occurred. The proposal just sank.
Most freelancers and agencies respond to this with a single timid follow-up ("Just checking in!") about a week later, then quietly give up—usually out of fear of being annoying. Meanwhile the data on sales touches has said the same thing for years: a large share of positive replies arrive after the third contact, from a sequence most senders never complete.
Reframe: follow-up is a service, not a nuisance
The prospect asked for the proposal. Following up is helping them finish something they started—it's the professional equivalent of a waiter returning to take the order. What's actually annoying is contentless nagging ("just bumping this!"), and the fix for that is a cadence where every touch gives them something new.
This guide is the strategy layer: timing, touch count, channel mix, and the message behind each touch. It's tool-agnostic—you can run it from calendar reminders and a text file. (For turning it into a daily queue that never forgets, see how Corcava manages follow-ups.)
Three Principles of Follow-Up That Works
1. Every touch needs a reason to exist
"Checking in" and "bumping this" ask the prospect to do your selling for you. Each message should add one thing: an answer to a question they probably have, a relevant example, a deadline that's real, or a graceful exit. If a touch adds nothing, it teaches the prospect to ignore you.
2. Widen the gaps as the sequence ages
Early touches come fast, while the proposal is warm—days 2 and 6. Later touches spread out—days 13, 21, 30. Front-loading catches the "meant to reply" cases cheaply; the long tail catches the "budget meeting was postponed" cases without suffocating anyone.
3. The sequence has an end, and the end is explicit
An open-ended drip is how you become spam. Five touches, then a clean, stated close—the "breakup" message. Paradoxically, the breakup is often the highest-reply touch in the sequence: real deadlines, even soft ones, force decisions. After it, the deal gets closed as no-response in your pipeline, not left to rot.
That last step—actually closing the record with a reason—is what connects your cadence to your learning loop. If "went dark after proposal" is a category you track, you can measure whether cadence changes reduce it. That's the job of an outreach outcomes taxonomy.
The 5-Touch Cadence (Copy This)
The default schedule for a typical freelance or agency proposal ($2K–$25K, decision cycle of a few weeks). Day 0 is the day you send the proposal.
| Touch | Day | Channel | Job of the message |
|---|---|---|---|
| 0 | Day 0 | Send the proposal and set the follow-up expectation inside it: "I'll check back Thursday unless I hear from you sooner." This pre-authorizes every later touch. | |
| 1 | Day 2 | Email (same thread) | Confirm receipt, invite questions. Short—two sentences. Catches "it went to spam" and "I skimmed it" cases. |
| 2 | Day 6 | Email (same thread) | Add value: answer the objection they're most likely sitting on (usually price, timeline, or "will this actually work for us"), or share a relevant result/example. |
| 3 | Day 13 | Switch channel: call, LinkedIn, or the platform you met on | Same person, different door. Channel switching resets attention and signals seriousness without adding volume to a possibly-ignored inbox. |
| 4 | Day 21 | Email (new thread) | Introduce a real constraint: your start-date availability, a price hold expiring, a capacity window. Must be true—fake urgency reads instantly. |
| 5 | Day 30 | The breakup: close the loop gracefully, leave the door open, stop. Then close the record as no-response with a reason. |
Two rules sit on top of the schedule. First, any reply resets the cadence—a response, even "we need another week," moves the deal back into live conversation and the clock restarts from their new commitment. Second, the cadence pauses for stated timelines: if they said "we decide after the 15th," your day-6 value touch still goes out, but the constraint and breakup touches shift to respect their date. Following up before a date they gave you reads as not listening.
If you want this as a fill-in worksheet—touch dates, channels, and message angles per prospect—grab the free outreach sequence tracker template.
What to Say: Templates Per Touch
Skeletons, not scripts—replace the brackets and cut anything that doesn't sound like you. Every one of these is under 90 words on purpose: follow-ups get read on phones.
Touch 1 (Day 2) — receipt check
"Hi [name] — wanted to make sure the proposal landed on your side. Happy to walk through any part of it on a quick call, or answer questions right in email. Anything unclear so far?"
Touch 2 (Day 6) — value add
"Hi [name] — one thing I'd flag while you're reviewing: the [phase/line item] is where clients usually have questions, so here's the short version of why it's there: [two-sentence rationale]. For context, we did something similar for [comparable client] — [one-line result]. Glad to unpack any of it."
Touch 3 (Day 13) — channel switch (voicemail or LinkedIn)
"Hi [name], it's [you] — sent over the [project] proposal a couple of weeks back and didn't want it to slip through the cracks. No pressure either way; even a 'not now' is useful so I can plan capacity. Email or a 10-minute call, whatever's easiest."
Touch 4 (Day 21) — real constraint
"Hi [name] — a scheduling heads-up rather than a nudge: I'm booking [month] now, and the [start date / pricing] in the proposal holds until [date]. If the project's moved down your list, that's completely fine — I'd just rather re-quote later than have the proposal quietly go stale."
Touch 5 (Day 30) — the breakup
"Hi [name] — I'll close the file on this for now so I stop cluttering your inbox. If priorities shift and [project] comes back around, I'd genuinely enjoy working on it — just reply to this thread and we'll pick it up. Wishing you a strong [quarter/season]."
Notice the emotional register: zero guilt, zero passive aggression ("per my last email…"), and an easy out in almost every message. Making "no" cheap to say is counterintuitive but correct—a fast no frees your pipeline, and prospects who feel safe saying "not now" come back later far more often than prospects who were cornered.
Worked Example: The Math of Touch 3
A two-person web studio sends roughly 8 proposals a month at an average value of $6,000, winning 2 (25%). Their old habit: one follow-up at day 7, then silence. Of the 6 monthly non-wins, their records show about 4 were never actually rejected—they just went quiet.
They adopt the 5-touch cadence. Nothing else changes—same proposals, same prices, same leads. Suppose the cadence recovers just one of those four silent deals per month, a conservative outcome for going from one touch to five:
- Before: 2 wins × $6,000 = $12,000/month from proposals
- After: 3 wins × $6,000 = $18,000/month — a 50% revenue lift
- Extra cost: four additional short messages per proposal ≈ 20 minutes each proposal, ≈ 2.7 hours/month total
- Effective rate of follow-up time: $6,000 / 2.7 hours ≈ $2,200/hour
There is no other activity in a service business—not prospecting, not portfolio polishing, not posting on LinkedIn—with that return per hour. The leads were already generated, the proposal already written; follow-up is pure margin on sunk effort.
The catch: the math only works if the cadence actually executes on all 8 proposals, every month, including busy ones. Which is precisely where willpower-based systems fail—and why the last section is about removing willpower from the loop.
Adjusting for Deal Size and Channel
- •Small/fast deals (under ~$2K, platform gigs): compress everything—touches at days 1, 3, and 7, then close. Platform clients hire in days; a day-30 breakup message is a eulogy.
- •Large deals ($25K+, multiple stakeholders): stretch to 6–7 touches over 60–90 days, and vary the recipient, not just the channel—your champion may be stuck internally, and a well-placed "anything I can prepare for [decision-maker]?" arms them.
- •Warm referrals: keep the same schedule but soften touch 4—constraint messages read differently when a mutual contact is implicitly watching.
- •Cold outreach that produced the proposal: you have less relationship capital, so earn each touch harder—touch 2's value-add matters most, and skipping it to send a bare "thoughts?" will burn the thread.
Whatever variant you run, write it down as the cadence—named touches, fixed offsets. A documented cadence can be delegated, measured in your weekly pipeline review (overdue touches are its best health metric), and improved deliberately. "I follow up when it feels right" can't be any of those things.
Making the Cadence Automatic
A cadence on paper fails the first week client delivery gets heavy—the day-6 touch slips to day 10, day 13 never happens, and the sequence dies exactly when the pipeline needs it most. The fix is structural: every proposal, the moment it's sent, gets its next touch scheduled with a date. One glance each morning at a queue of due follow-ups replaces remembering entirely.
You can build that queue with calendar reminders. It's just fragile—reminders don't know when a prospect replied, don't reschedule the rest of the sequence, and don't tell you which touches actually convert. A pipeline tool does. In Corcava's outreach tracking, every record carries a next-action date that feeds a daily follow-up queue, and each sent touch lands in the activity log—so you can finally see which touch number wins your deals.
Put this cadence on rails
Load your open proposals into Corcava, set the touch dates once, and work tomorrow's follow-ups from a queue instead of memory.
No credit card required