When to follow up on a proposal (and what to say)
MumenLabsAugust 10, 2026
From MumenLabsBuild your own document tracking
Follow up on a proposal within a day of it being read, not on a fixed schedule. The best moment is while the document is still fresh in the reader's mind, and the only way to know when that is, is to send the proposal as a tracked link so you can see when it was actually opened and which parts held attention. Following up on a calendar means half your messages arrive too early to be useful and half arrive after the decision was made.
Last updated: August 2026
The problem with "follow up in three days"
Every sales guide gives you a cadence — three days, then a week, then two. The cadence is a substitute for information. It exists because, with an emailed attachment, you genuinely have nothing else to go on.
The result is predictable. If they read the proposal an hour after you sent it, your three-day follow-up is two days and twenty-three hours late. If they have not opened it at all, your follow-up asks "any thoughts?" about a document they have not seen, which is mildly embarrassing for both of you and teaches them that your messages can be ignored.
Follow up on a signal instead
With a tracked link, four situations become distinguishable, and each has an obvious right move.
1. Not opened yet
When to act: two or three days, then again a week later. What to say: nothing about the content. Assume delivery failed rather than interest did — "wanted to make sure this reached you, here it is again" costs nothing and is often literally true. Spam filters and busy weeks are the most common explanation by a wide margin.
2. Opened, read properly, then silence
When to act: the next working day. What to say: something specific to what they read. If they spent four minutes on scope and thirty seconds on your background, ask a scope question. The message should read like a continuation of their thinking, not a nudge.
3. Opened briefly and closed
When to act: wait a couple of days, then send something different. What to say: do not repeat the proposal. A short skim usually means it was triaged, not evaluated. Give them a reason to open it properly — a one-line summary of the outcome you are proposing, or an answer to the objection you suspect.
4. Opened repeatedly, especially by more than one person
When to act: immediately, and treat it as the strongest signal you get. What to say: make internal selling easy. Someone is showing your document to someone else, and that person has questions you are not in the room for. Offer a short call, or send the one-page version they can forward.
Reading the page-level data
Per-page reading time turns a vague sense into a specific sentence. Some reliable readings:
- A long stop on pricing is not a bad sign. It is the sign of someone seriously considering the money. Talk about payment terms and phasing, not discounts.
- A drop-off at a process or methodology section usually means it is too long, not that they disagree. Answer the question that section was supposed to answer, in two sentences.
- Skipping straight to the last page means they wanted the number and the timeline. Lead your follow-up with both.
- A second read of the same page days later is the highest-intent event in the whole dataset. That is the day to call.
Make sure the signal is real
One thing will quietly ruin all of this: a tracker that counts automated fetches as opens. Messaging apps fetch any link you paste within seconds to build a preview card, and many corporate mail systems pre-fetch links to scan them before delivery. If those count as reads, your "opened" timestamp is the moment you sent the message, and every conclusion above is built on it.
So the first thing to check in any tool is whether it separates automated previews from human opens. If it does not, the timing advantage you were paying for is noise. More on this in how to know if a client opened your proposal.
A follow-up sequence that respects the reader
Two useful rules once you have the signal:
- Never send a follow-up with no new information. "Just checking in" is a tax on the reader's attention. If you have nothing to add, add something: a relevant example, a revised timeline, an answer to a question they did not ask out loud.
- Say what happens next. End with a specific, small next step and a date. Most proposals do not die from rejection; they die from nobody being responsible for the next move.
Frequently asked questions
How many times should I follow up? Three or four times over two to three weeks, then stop and say you are stopping. "I will leave this with you — happy to pick it up whenever the timing is right" closes the loop without burning the relationship, and it gets replies surprisingly often.
Should I mention that I can see they opened it? Usually not. It changes the register of the conversation without adding anything. Use the information to time and shape the message, not as a subject line. The exception is a document where readers identified themselves at a gate — that is explicit and mutual, so referring to it is normal.
What if they open it and never reply at all? Repeated opens with no reply almost always mean an internal blocker: budget, timing, or someone who has not been convinced. Ask directly and gently what would need to be true for this to go ahead.
Does any of this work with an emailed attachment? No. Attachments give you no read data at all, which is why the calendar cadence exists in the first place. Send it as a tracked link and the timing question answers itself.
Time the message, not the calendar
The difference between a proposal that closes and one that goes quiet is often just when you spoke next. Track your next proposal and let the document tell you when to pick up the phone.
Read next: how to know if a client opened your proposal and document tracking without a subscription.
More in Document Tracking
Get all your tools in one free account
You came here to get something done — now keep the whole toolbox handy. QR codes, a link-in-bio page, PDF and image tools, all on one wallet. Pay only for what you use.
Free account · takes a few seconds · no subscriptions
Back to blog