How to follow up after sending a proposal

You sent the proposal. The scope was clear, the call went well, they said they were keen. Then nothing. No reply, no objection, not even a sign that anyone opened it.

Following up after sending a proposal comes down to two decisions: when you go back in, and what you put in the message when you do. A calendar reminder handles the first one badly and the second one not at all.

Why proposals go quiet after you hit send

Silence is the least informative thing a buyer can do, which is what makes it so difficult. They might be comparing you against two other quotes, waiting on someone's approval, or dealing with something that has nothing to do with you. Treating every quiet inbox as a no makes you disappear too early. Treating it as a maybe makes you chase too hard.

I have sent a lot of decks, proposals and one-pagers over the years, first doing go-to-market at a data enrichment company and now building LiveDocument. The pattern barely changes. A proposal gets a warm reaction on the call and then becomes one more unread thing in a crowded inbox. The deal rarely dies because the document was bad. It stalls because nobody made the next step obvious.

There is some evidence that the first open is the moment that matters. Proposify, which sells proposal software and is therefore reporting on its own customers rather than the market, analysed 1.3 million proposals and found 42.5% of closed-won proposals were won within 24 hours of that first open. Treat that as a nudge rather than a law: it is one vendor's dataset, and deals that close fast were probably always going to. What it does suggest is that an open is worth noticing.

Chasing asks for attention, guiding earns it

"Just checking in" hands all the work back to the buyer. They have to find the proposal, remember the conversation, decide what to say, then write a reply. You have made their day harder and called it persistence.

A follow-up worth sending does something specific. It clarifies a pricing assumption, points at the section they actually care about, answers the objection you know is coming, or offers to walk them through it. The question is not "have you decided?" It is "here is the bit you were probably stuck on."

The rule I try to hold myself to: follow up because you have something to add, not because a CRM told you an email was due.

One unanswered email tells you almost nothing, and the honest version of that statement is that nobody really knows the right number of touches. The figures that get passed around on this are mostly vendor blog posts citing each other. What I would say from doing it myself is that stopping after one email is giving up, and emailing every second day is not persistence, it is pressure.

The cadence that keeps momentum without pressure

Start with whatever the buyer told you about their own process. If they said they need a fortnight, give them a fortnight. If nothing was agreed, run a short sequence across two to three weeks rather than leaving the proposal to go cold.

Start with context, not a demand

Send the first follow-up two or three business days after delivery. Keep it short, confirm the proposal is actually reachable, and offer one useful clarification.

Do not ask for a decision in the first touch. Ask about the process instead:

"Which part would be most useful to walk through: scope, timing or pricing?"

That is a much easier email to answer than "are you ready to move forward?", because answering it does not commit them to anything.

Give each later touch its own job

If nothing comes back, leave five to seven days before the next message, then stretch the gap after that. Three or four touches across a two to three week window is about the ceiling, and every one of them needs something new in it. Past four you are not being persistent, you are being a problem.

The shape I use:

First touch, two to three business days in: confirm context, offer to clarify one section.
Second touch, around day seven: address the objection you would raise if you were them, usually implementation, scope or internal approval.
Third touch: send something genuinely useful with no ask attached. A walkthrough, or the answer to a question that came up in discovery.
Final touch: give them a clean way out. Continue, pause, or close the conversation.

Do not send on consecutive days unless they are actively asking you for things. And if they say no, stop. If they say the timing is wrong, agree a date and actually put it in the calendar. If the sequence runs out with no reply, close the loop politely and move on rather than letting the deal rot at the bottom of a pipeline report.

Using open alerts and page analytics to decide who to chase

A fixed cadence treats every proposal as if it carries the same level of interest, and it obviously does not. Someone who has opened the pricing page twice is in a different conversation from someone who has not opened the document at all.

Use the calendar as your safety net and engagement as your priority list.

Read behaviour as a question, not an answer

This is where it is easy to talk yourself into things. An open tells you someone looked. A reopen tells you someone looked again. Neither one tells you why, and the moment you start narrating motive from a notification you are writing fiction about a stranger's afternoon.

What the signals are useful for is ordering your day and choosing a subject line. Roughly how I prioritise:

A recent, meaningful view: get in touch while it is still fresh in their mind.
A reopen or return visit: worth asking whether a particular section needs clarifying. It may indicate a second read, or someone else looking over their shoulder.
Time on pricing or scope: talk about commercial assumptions rather than repeating your introduction.
A new viewer on a shared link: another stakeholder may have entered the process. Ask who else needs context rather than assuming you know who it was.
No engagement at all: run the normal cadence and resist the urge to invent a reason.

The useful question is never "did they open it?" It is "what were they trying to work out?"

Match the message to the page

If they spent time on implementation, send a short explanation of how delivery actually runs. If pricing held their attention, clarify what is included and where there is room to move. If a credentials or team section drew interest, that usually means someone internal is assessing risk, so give them the thing that makes that easier.

Resist automating this into an ambush. A message that arrives ninety seconds after someone opens a document does not read as attentive, it reads as surveillance. Same day is plenty.

If you are tracking documents this way, tell people you are doing it. Viewer activity is personal data, so keep access to it inside the deal team, and do not hang on to viewer records once the deal is decided either way. My longer write-up on PDF analytics goes into what document activity can and cannot tell you.

What to say in each follow up

The wording matters less than the job the message is doing. Every follow-up should either reduce uncertainty or make the next step smaller.

The first note adds context. Reference the conversation that produced the proposal and point at the section tied to whatever they said mattered most. Do not re-attach the same file unless there is a reason, because a second identical PDF is not new information.

The second note should handle the objection before they have to raise it:

"One thing that usually comes up here is how the implementation fits around work you already have running. The proposal assumes [assumption]. If that is wrong, I can redo that section."

That does not invent a concern or pressure anyone into admitting one. It gives them a safe way to correct you, which is a much easier email to send than a list of problems.

Let the signal choose the focus

A third message can be stakeholder-aware. If the proposal seems to have travelled beyond your original contact, ask whether anyone else needs their own version of the explanation. This is the point where a dense document starts costing you, because the person now reading it was not on the call.

It is also the specific gap LiveDocument exists to close: you attach a recorded walkthrough to the PDF and share both as one link, so the second reader gets your explanation rather than forty pages and no context. It will not write your sequence, it is not a CRM, and it does not do e-signature, so the proposal itself and the chasing are still your job.

Buyer signal	What it might mean	Where to aim the next message
Opened once	They have started reading	Point at the section tied to their stated priority
Reopened	A second read, or a colleague looking	Ask whether a specific section needs clarifying
Time on pricing	Commercial fit is being weighed up	Explain assumptions, inclusions and where scope can flex
Time on implementation	Delivery risk is the worry	Offer a short delivery explanation or walkthrough
A new viewer appears	It may have reached another stakeholder	Ask who else needs context, do not guess who
Nothing at all	They are busy, or it never landed	Confirm access and ask about their review process

Keep the close simple. One action, not a menu. "Would it help to talk through the pricing page?" is a far easier email to answer than "please share your feedback on the proposal."

The mistakes that actually stall deals

The worst one is repeated contact with no new reason. Daily emails, "per my last email", passive-aggressive requests for an update. None of it creates momentum. It just makes the buyer responsible for managing your anxiety about your own pipeline.

Resending the same PDF is the other one. Sometimes an attachment genuinely got blocked, but most of the time it sends them back into the same document with no better way through it. Reference a page, an assumption or an open question instead.

Do not mistake activity for intent

Someone might have opened your proposal by accident, forwarded it without reading it, or skimmed page one before a meeting pulled them away. A proposal can rack up opens and still be completely stuck.

Reply data needs the same scepticism. Count unique human replies divided by delivered emails, and strip out auto-replies, out-of-office messages and bounces before you do. If your reporting counts the out-of-office, you are measuring inbox noise and feeling good about it.

The calmer approach is to look at four things together:

Activity: did anyone open, reopen or revisit a relevant page?
Context: does that fit what they said mattered?
Response: did a real person reply or ask something useful?
Progress: is the next step clearer than it was last week?

Your follow-up should help diagnose the blockage, not celebrate the notification.

Turning it into something repeatable

Two controls, running together. A light calendar sequence so nothing good disappears, and real-time activity so you can move an individual follow-up forward when someone actually engages.

Before you send the next proposal, write down what the buyer said about their review process and which single section is most likely to need explaining. Send a link that is easy to return to, say where to start, and set the first reminder for the agreed date or two to three business days out if nothing was agreed.

Then keep a short record per opportunity. Status, the page or topic that got attention, the specific value the next message adds, the approval step still missing, and the point at which you will stop. That last field is the one people leave blank, and it is the reason old deals sit in pipelines pretending to be alive.

Templates help with consistency as long as they do not flatten the conversation. Keep reusable shapes for the context note, the objection response and the close-out, then change the evidence around the buyer's actual problem. If the proposal itself is the bit that needs work, this sample sales proposal is a reasonable starting point for making scope and next steps clear, and a clear proposal needs less following up in the first place.

Most of what I have written here comes from being on the wrong end of it. I built LiveDocument because I got tired of sending something good into an inbox and spending a week guessing what happened to it.