When to Follow Up After Sending a Proposal
By Oleh Tsyupa, Founder of PDFTrackr · Published 2026-08-24 · Updated 2026-08-24
8 min read45.2% of recorded sessions on a multi-page document never got past page one.
11.5% rendered no page at all and another 33.7% saw page one and stopped, while 54.8% reached some page beyond the first. The two groups also behave differently in the clock: a session that stopped on page one ran a median of 14.2 seconds against 75 for one that got past it. A follow-up written on "they opened it" is therefore written on close to a coin flip. These are all document types in our corpus, not proposals — we do not cut this data by document type, and a proposal-only figure would be invented. The full breakdown lives on our opened-versus-read page.
Based on 3,496 recorded sessions across 234 documents and 262 share links, 22 Sep 2025 – 5 Aug 2026, extracted 5 Aug 2026 — multi-page documents only, because a one-page document has no second page to get to. That restriction drops 150 sessions from the 3,646 recorded: 80 on one-page documents, and 70 more whose document has no page count on record — the second group is dropped because its page count is unknown, not because it is one. Every recorded session inside the restriction is counted, including the automated ones, so that the group which renders no page at all stays visible. Figures are medians, not averages.
You can have that signal on the next proposal without changing anything else about how you send it: create a free tracked link and paste it into the email in place of the attachment — 50 files, 12 months of history, no card. The rest of this page is the comparison.
The four timing rules compared
Each rule is a different bet about what the silence means. The column that matters is the last one: what has to be true for the rule to give the right answer.
| Rule | When you send | What it assumes | When it is wrong |
|---|---|---|---|
| The calendar rule | Three to five days after sending; a week for a long proposal | That review time is roughly the same for everyone | The prospect read it in the first hour, or has not opened it at all |
| The read trigger | The same day the document is read past the first page | That you sent a link rather than an attachment | The reading was a colleague, or a scanner, rather than the buyer |
| The silence rule | At the calendar deadline, when nothing was recorded at all | That no signal means the document did not reach the right person | Delivery failed, or the file was forwarded and read elsewhere |
| The sequence rule | A second message a week later, a third about a month on | That persistence is what closes the gap | Repetition without new information reads as pressure |
Rule 1 — the calendar rule, and what it is really for
Every ranking answer to this question gives you a number of days, and they cluster tightly. Indeed's career guide is representative.
“Follow-up emails are often most effective when sent three to five days after sending your proposal.”— Indeed Career Guide, “How To Write a Follow-Up Email After Sending a Proposal in 6 Steps”. Read via search retrieval on 2026-08-24; the host does not resolve from our network, so the page was not fetched directly and the sentence is reproduced as the retrieval returned it.
The reasoning is sound: it gives the client time to read before you interrupt. Guidance aimed at longer documents stretches the same logic — a week as the general rule of thumb, and two weeks when the proposal is particularly long.
What the number cannot do is tell you which of the two failure modes you are in. Waiting five days after a proposal that was read to the end on Tuesday morning wastes the only moment when your document was the thing on their screen. Waiting five days after a proposal that never arrived wastes five days. The calendar rule is a good deadline and a poor trigger, and that is the whole argument of this page.
Rule 2 — follow up on what the reading says
Send the proposal as a tracked link and the document reports back: which pages rendered, how long each held the reader, whether anyone came back to it. The reading, not the calendar, then sets the day.
Three patterns are worth acting on, and Proposify's own follow-up guidance describes them before we do — we are citing that advice rather than improving on it. A document read past the first few pages in one sitting is the strongest moment you will get; follow up the same day, and refer to what they were reading rather than to the proposal in general. A document opened and abandoned early is not disinterest so much as a bad moment — give it a day or two, then send something shorter than the proposal. A document opened again days later usually means it is being shown to someone else, and that is when a second copy, or an offer to walk a colleague through it, lands.
The mechanics of getting that signal at all are set out in how to know if a client read your proposal. The point here is narrower: the reading is what tells you which of the three messages to write.
Rule 3 — what to do when there is no signal at all
No recorded reading is genuinely useful information, and it is the case the calendar rule handles worst. It means the document did not reach the person who decides — a spam filter, the wrong address, an unopened thread, a decision-maker who was never on the email.
The right follow-up in that case is not a nudge about the proposal. It is a message that re-delivers it and makes it trivially easy to open, sent at the calendar deadline rather than before. Chasing a decision that nobody has had the chance to make is the most common way a good proposal dies quietly.
One caution, because it is the mistake this rule invites: an absence of recorded reading is not proof nobody read it. A forwarded copy, a downloaded file opened offline, or a reader who closed the tab before anything was recorded all look like silence. Treat it as a strong hint about delivery, never as evidence about the person.
Rule 4 — the second and third message
The published sequences agree on shape more than on dates: a small number of follow-ups, spaced further apart each time, and then a clean stop. Three messages is the usual ceiling — the second about a week after the first, the third a good deal later.
The part worth borrowing is the discipline of a stop. The part worth changing is what each message contains. A second message that repeats the first adds nothing; a second message that answers the question the reading data implies — the pricing page they sat on, the section they never reached — is a different email, and it is the one the earlier rules make possible.
What none of these rules can tell you
None of them tells you who was reading. A tracked link records a session, and an email gate records an address somebody typed — a person can type any address. One link per recipient is the more reliable shape, because the link itself carries the identity.
None of them follows a downloaded copy. Once the PDF is on a laptop it is a copy, and the reading that happens there is invisible to every method on this page. Nor does any of them measure agreement: a proposal read to the last page is a proposal that was read, and people read carefully before saying no. The difference between an open, a click and a genuine read is set out in opened, clicked or actually read.
Where the calendar rule wins
It works when you sent an attachment, which is most of the time. A rule that needs no instrumentation applies to a proposal already sitting in someone's inbox as a PDF, and a reading signal does not. If the document has gone out, the calendar is the only rule available to you, and it is better than nothing by a wide margin.
It also wins on relationships that are not transactional. Public-sector and grant processes publish their own decision timelines, and following them beats any behavioural signal — reading data on a submitted bid tells you a reviewer opened it, not that the committee has met. Where a stated timeline exists, that is the rule, and ours is noise.
And it is the honest default when the signal is thin. One session, on one page, from an unidentified visitor is not enough to act on. The calendar deadline is what stops you reading tea leaves.
When Pro becomes the right choice
Free covers this whole workflow for one proposal at a time. Per-page reading, the email gate and 12 months of history are all on the free plan — free is not a preview of the data — and if you check yesterday's activity over coffee, the daily summary is the right instrument.
Pro becomes the right choice when the timing has to be same-day rather than next-morning. A real-time open alert reaches you while the proposal is still on the reader's screen, which is the entire premise of rule 2 and the one thing a digest cannot do. The return-visit alert is the other half: you are told when a prospect comes back to a proposal days later, which is usually the moment it is being shown to somebody who has not seen it. At $9/mo that is the trade — the difference between following up on Tuesday afternoon and following up on Wednesday. Full limits are on the pricing page, and the live demo shows the readout on sample data.
Frequently asked questions
How long should you wait before following up on a proposal?
The published guidance clusters at three to five days, stretching to a week or two for a long proposal. Treat that as a deadline rather than a trigger: if you sent the proposal as a tracked link and it was read closely on day one, following up the same day is better, and if nothing was recorded by the deadline the right message re-delivers the document rather than chasing a decision.
Is it better to follow up when the proposal is opened?
Follow up when it is READ, which is not the same event. In our own production data 45.2% of recorded sessions on a multi-page document never got past page one, and a session that stopped on page one ran a median of 14.2 seconds against 75 for one that got past it. An open alert on its own fires for both groups.
How many times should you follow up on a proposal?
Published sequences settle on about three messages, spaced further apart each time, and then a stop. The number matters less than what changes between them: a second message that repeats the first adds nothing, while one that answers the question the reading implies — the section they sat on, or the one they never reached — is a different email.
What does it mean if the client never opened the proposal?
Usually that it did not reach the person who decides, rather than that they are not interested. Send a message that re-delivers the document and makes it easy to open. But no recorded reading is not proof nobody read it: a forwarded copy, a downloaded file opened offline, or a tab closed before anything was recorded all look the same from your side.
Can you track whether a proposal was read if you sent it as an attachment?
No. An attachment is a copy that lands on the recipient's disk with no connection back to you, so nothing about opening it is reported to the sender. To get a reading signal you have to send a link to a hosted copy instead of the file — that is what makes pages, time per page and download clicks measurable at all.
Does following up faster actually win more deals?
We cannot tell you that, and neither can anyone quoting a conversion figure at you. What our data supports is narrower and checkable: the reading behind an 'opened' notification varies enormously, so a follow-up timed on reading is aimed at a different moment from one timed on an open. Whether that closes more work depends on your market, not on ours.
Sources
- Indeed Career Guide — How To Write a Follow-Up Email After Sending a Proposal in 6 Steps (the three-to-five-day rule, quoted above). Read via search retrieval; the host does not resolve from our network and the page was not fetched directly (accessed 2026-08-24)
- FundsforNGOs — How To Follow Up After Submitting A Proposal (the one-week rule of thumb, two weeks for a long proposal). Read via search retrieval; not fetched directly (accessed 2026-08-24)
- Proposify — How to Follow Up on a Sales Proposal (the Right Way): guidance on timing a follow-up to viewing behaviour. Cited for its advice, not for any product claim. Read via search retrieval; not fetched directly (accessed 2026-08-24)
- Bonsai — The why, when, and what of follow up emails after proposals (the three-message sequence). Read via search retrieval; not fetched directly (accessed 2026-08-24)
Time the next follow-up on what they actually read
Send the proposal as a tracked link and see which pages the client reached before you decide when to write. Free plan: 50 files, 50 links, 12 months of history, no card.
Start tracking freeKeep reading: how to know who opened your PDF, how to know if a client read your proposal, and how free PDF tracking works.
Oleh Tsyupa
Founder, PDFTrackr
Has analysed over 3,000 tracked document-viewing sessions on PDFTrackr.