A good follow-up does more than say "just checking in." It reminds the reader what they are deciding, makes the next step easy, and avoids pretending that a generic template is personal.
NudgeForMe can review previously sent conversations and prepare follow-up drafts. Its Research & Draft option can add supported research context when your plan and connected providers allow it. That context needs verification: even a plausible company fact is useless if it belongs to the wrong person, is outdated or distracts from the real request.
Use case 1: Revive a stalled sales proposal
Situation: On October 20, a founder emailed a prospect a proposal with two package options. The buyer said they would review it, but nobody followed up.
Weak follow-up: "Bumping this to the top of your inbox."
Better approach: Refer to the specific decision and offer a lower-friction next step:
Hi Morgan — following up on the two options I sent for the pilot. Would a shorter one-page comparison help your team decide, or should I circle back next week?
Research is useful only if it adds something relevant, such as a verified new project announcement that changes the scope. Do not insert "I saw your exciting news" just because a search found a namesake.
Use case 2: An agency waiting on client approval
Situation: A creative agency sent revised campaign assets and needs approval before launch. The original message remains unanswered.
Draft example:
Hi Alex — quick follow-up on the revised campaign assets shared Monday. We can keep the planned launch date if your team approves the final versions by Thursday. Is anything still blocking sign-off?
The value here comes from the existing email context, not external company research. Prioritize the attachment/version, the real deadline and the person responsible for approval.
Use case 3: Reconnect after a hiring conversation
Situation: A recruiter sent an interview availability request and hasn't heard back. Before generating a draft, confirm the candidate didn't respond via scheduling software, SMS or another recruiter.
Draft example:
Hi Taylor — checking whether you're still interested in scheduling the next conversation. If the timing has changed, no problem; let me know and I can adjust the process.
Avoid treating lack of reply as proof of interest. If the candidate has opted out, do not follow up.
Use case 4: Follow up on a partner introduction
Situation: A founder was introduced to a potential integration partner, sent a useful overview, and lost track of the thread. A fresh company update might explain why the integration is more timely—or it might be irrelevant.
A good follow-up can be short:
Hi Jordan — following up on the integration overview I sent. Would it be useful to compare the two technical approaches in a 15-minute call, or is this not a priority right now?
If you do mention a public announcement, link to the original source and verify the company, publication date and applicability. Don't imply personal familiarity with a post you have not read.
How Research & Draft fits into a safe workflow
- Identify a previously sent conversation with a legitimate, unresolved next step.
- Read the entire thread before adding any outside information.
- Use supported research providers only when they can answer a relevant question.
- Verify the recipient identity, company association, timing and source.
- Generate a concise draft that mentions one real decision or next action.
- Review the message in your mailbox before sending.
In an API-based draft workflow, POST /drafts accepts a research boolean where supported. The API returns a draft; it does not send the message. See the documented REST endpoint and draft workflow.
What good personalization does not look like
- Inventing an acquisition, funding round, promotion or personal milestone.
- Mentioning a stranger's social post solely to manufacture rapport.
- Using old research as if it were current.
- Adding irrelevant facts when the sender simply needs a document approved.
- Sending multiple follow-ups after the recipient has replied or opted out.
A thoughtful follow-up often needs less research, not more. When the original thread already provides enough context, make the next step easy and keep the message brief.
Related reading
- Follow-up examples by scenario
- Find forgotten conversations
- NudgeForMe API draft creation tutorial
- Official Research & Draft and developer documentation
If the original thread already has what you need, write the follow-up from that context.
A better follow-up habit starts here.
Get practical email follow-up tips and occasional product updates. Just your name and email — no mailbox connection required.
Loading secure subscription form…
Subscribe only if you want these messages. Unsubscribe any time. See our Privacy Policy.