Your follow-up is asking them to do your job
You sent the proposal last Tuesday. It is now Friday, and the thread has slid below a dozen newer messages. You type, “Just checking in to see if you had a chance to review.” Then you stop, because you can feel what it asks of them.
They need to remember the proposal. Reopen it. Work out whether they have enough information. Decide what to say. Your follow-up did not make the next move easier. It handed the next move back to them.
That is why “just checking in” gets ignored. Not because checking in is rude. Because it creates homework at the exact moment the recipient is trying to clear their inbox.
A follow-up is not a reminder that you exist
A busy client rarely opens a vague follow-up and thinks, “I should reply to this.” They see an unfinished task with no obvious starting point.
The phrase itself is not the problem. You can replace it with “circling back,” “touching base,” or “following up on this.” The outcome stays the same if the email still requires the reader to reconstruct the work.
Consider what sits behind a proposal review. Someone may need to remember which option their team preferred, compare it with a budget, ask procurement a question, or decide whether the project belongs in this quarter at all. “Any thoughts?” bundles all of that into a two-word request.
That is a lot to ask from a message that offers nothing new.
The useful question is not, “How do I sound less pushy?” It is, “What work am I removing for this person?”
Why vague follow-ups create a context-switch tax
Every email competes with the work already in front of the reader. A vague follow-up adds a context switch: they must leave their current task, recover a past conversation, and figure out what response will satisfy you.
That cost is invisible to the sender because you still have the deal in your head. You remember the call, the objections, the deadline, and the promised next step. The recipient does not carry all of that context into their inbox.
Imagine a buyer who said they needed sign-off from finance before choosing between a $12,000 annual plan and a smaller pilot. A week later, you write:
Just checking in to see whether you had a chance to review the proposal.
They now have to reopen the proposal and remember which question finance was meant to answer. The email has no route forward.
Compare it with this:
On our call, you said finance needed to compare the annual plan with a 90-day pilot. I pulled the pilot scope into a one-page summary and added the implementation hours. Would it help if I joined the 20-minute finance review on Thursday, or should I send the summary to someone else?
The second message does three jobs. It restores the relevant context. It contributes a useful artifact. It offers two concrete ways to move.
It is still a follow-up. It simply does not make the recipient do the filing first.
Bring the missing piece, not another nudge
A strong follow-up earns attention by carrying something forward. That something does not need to be a whitepaper or a major announcement. It only needs to make the recipient's next decision smaller.
There are four reliable ways to do that.
Name the exact thread
Do not make the reader search their memory. State the decision, promise, or open question that the message relates to.
Instead of:
Wanted to check whether you had any thoughts.
Try:
You mentioned that your CS lead wanted to see how renewal risk would show up before a QBR. I recorded a two-minute walkthrough of that view.
The detail tells them why this email exists before they have to scroll.
Add a changed fact
A follow-up becomes easier to answer when it contains new information. The changed fact can be small: a customer example relevant to their industry, an answer you found after the call, a product capability they asked about, or a timing trigger they gave you.
This is different from attaching collateral because a sequence says you should. The added item has to resolve something that was already live in the conversation.
For a prospect who said security review was the blocker, a useful follow-up might include the completed security questionnaire and ask who should receive it. For a client waiting on a decision, it might summarize the two options their team discussed, including the tradeoff they care about.
Reduce the response to one decision
“Let me know what you think” asks for an open-ended response. Most people postpone open-ended work.
Instead, make the decision explicit and bounded:
- Should we keep the current rollout date, or move it to the first week of August?
- Is the integration question still with your IT team, or should I close the loop for now?
- Would a 15-minute working session solve this faster than email?
A small decision can still produce a no. That is fine. A clear no is more useful than a thread that stays technically open for another month.
Do the first draft of their reply
Sometimes the real obstacle is that the recipient needs to coordinate other people. You can make that easier without pretending to know their internal process.
For example:
If it is useful, you can forward this: “We are deciding between the pilot and annual option. The difference is implementation scope, not core functionality. Can you confirm which budget this should come from?”
You are not asking them to write the summary, translate your offer, and choose the next meeting. You supplied the first draft.
The best next step is often smaller than a meeting
Sales and CS teams often treat a reply as the objective. It is not. Progress is the objective.
That matters because a meeting request can be more work than the recipient wants to accept. If they need one document, one stakeholder name, or a yes-or-no answer first, asking for 30 minutes creates unnecessary friction.
A good follow-up matches the smallest credible next step. Sometimes that is a meeting. Often it is a forwarding request, a choice between two options, or a one-line confirmation that the timing has changed.
This is also why generic follow-up templates underperform. The message may look polished, but it cannot know the one detail that lowers the reader's effort in this specific thread.
The work happens before writing: capture what was promised, what is blocked, who owns the decision, and what would make the next move easy. Without that context, reps fall back to “just checking in” because it is the only sentence they can safely write.
That is the problem behind follow-up paralysis. When the account history is scattered across calls, inboxes, and notes, the sender lacks the context needed to make a useful ask.
Stop measuring follow-up by sends
A sequence can show ten completed tasks while producing ten messages that create work for the recipient. Activity is not momentum.
Review follow-ups by a simpler standard: could someone answer this without reopening the entire relationship?
If the answer is no, the message probably needs one of three things:
- The relevant context from the last conversation.
- A new, useful input that changes or clarifies the decision.
- A smaller next step with a named owner.
This standard changes how you manage follow-up in a CRM, too. A contact list is not enough. The record needs the next action and the reason it is timely, not just a date that says “follow up.” That is the gap between a task queue and a system that helps someone decide what to do next, as we wrote in Your CRM is a list. Your reps need a next move..
A practical rewrite before you hit send
Before sending a check-in, take 60 seconds and answer four questions:
- What specific event or decision is this replying to?
- What is new or clarified since the last message?
- What is the smallest useful action the recipient can take?
- Can they understand the request without opening old tabs or asking someone else what this is about?
If you cannot answer those questions, do not polish the phrase. Go back to the account context.
A useful rewrite might be as short as this:
You asked us to hold the onboarding date until the new admin starts. They join on August 4. I have reserved the setup slot for that week. Should I send the agenda to you, or directly to the new admin once they start?
It is short because it has already done the hard work. The reader knows the history, the new fact, and the choice.
“Just checking in” is not inherently annoying. It is empty. When your follow-up restores context, reduces the decision, and contributes something useful, it stops feeling like a nudge and starts feeling like help.
That is the kind of customer context a CRM should preserve, not bury. The account does not need another reminder that a follow-up is due. It needs enough history to make the next email worth opening. For more on what gets lost when that context lives outside the system, read The deal died on a call you never logged.