“Just checking in” gives the reader another task: remember the meeting, find the open question and decide whether anything has changed. A better follow-up does that work before it reaches the inbox.
Start with the uncertainty left at the end of the conversation. Was the buyer comparing scope, trying to understand implementation effort or waiting for someone else’s decision? Choose one issue and answer it with evidence you actually have.
Deliver the promised item first
If you offered a comparison or a timeline, send it before asking for a meeting. Keep the description narrow enough to be accurate. A rough planning estimate should not become a guaranteed delivery date simply because the message needs to sound confident.
Consider a fictional small-business buyer who is interested in an AI pilot but worried about the review burden. Another feature list will not answer that concern. A sample evaluation sheet and an explanation of who checks the output might.
Write a message around that concern
Example to adapt: “You mentioned that checking the output could absorb the time saved on drafting. I’ve attached a sample review sheet showing the checks we would measure alongside drafting time. The figures are blank because we have not run your workflow. Would it help to walk through one approved sample together? If this is no longer a priority, let me know and I’ll close the loop.”
This is a fictional example, not a message sent to a real prospect. Its useful features are the specific concern, an honest limit and a small next step. Replace the details only with things that were actually discussed or promised.
Remove the work the reader does not need
- Keep one primary question in the message.
- Name the attachment and explain why it is relevant.
- Separate confirmed information from estimates or proposals.
- Make deferring or declining easy.
- Record the agreed next action so the next follow-up does not restart the conversation.
Avoid inventing a deadline or implying approval from another stakeholder. Those shortcuts may produce a reply while making the underlying relationship less trustworthy.
Review conversations, not just response rates
Look at whether the message resolved the uncertainty and moved the decision towards a clear outcome, including a legitimate no. A quick reply is not proof that the prospect understood the scope. An enthusiastic exchange is not the same as an agreed next action.
Use a small sample of your own appropriately handled sales records to identify repeated unanswered questions. Improve the relevant explanation or document, then see whether it helps subsequent conversations.
Common questions
What should I write instead of “just checking in” in a sales follow-up?
Pick the one uncertainty left at the end of the conversation, such as scope, implementation effort or someone else’s pending decision, and answer it with evidence you actually have. If you promised a comparison or timeline, send it before asking for a meeting.
How do I keep a sales follow-up email honest?
Separate confirmed information from estimates or proposals, and do not let a rough planning estimate become a guaranteed delivery date. Avoid inventing a deadline or implying approval from another stakeholder, and make deferring or declining easy.
Does a quick reply mean my follow-up worked?
Not by itself. A quick reply is not proof that the prospect understood the scope; look at whether the message resolved the uncertainty and moved the decision towards a clear outcome, including a legitimate no.
Editorial notes
Reviewed on 20 September 2026. This is original editorial guidance with a fictional message; no conversion lift or client outcome is claimed. The AI pilot guide shows the kind of evidence a follow-up about automation could use.
Something changed or worth adding?
Send a correction or suggestion
