client-follow-up-and-reengagement
Skill1 starsChanged 3 months agoMITView on GitHub
Write a warm, personal re-engagement email to a pre-venture client who has gone quiet — no recent meeting, no transcript, just whatever client history is on hand. Use whenever asked to personalize an outreach email from a Neoserra report or uploaded client file, write a warm email inviting a client to catch up, reconnect with an inactive or unresponsive client, nudge a stalled pre-venture client back into advising, or improve follow-up/re-engagement rates for clients who went dark after an initial session. Trigger on an uploaded Neoserra report or client file with no accompanying meeting notes. Distinct from transcript-to-action-plan-client-email — that skill drafts a follow-up right after a meeting, from that meeting's transcript. This skill has no transcript and no meeting to draw from — it works from a client's past record alone to reopen contact with someone who dropped off.
In this repository14 other files it gives its agents.
- business-model-canvas-helperSkill
- business-service-provider-referral-engineSkill
- mdsbdc-debt-helperSkill
- proposal-buddySkill
- sbdc-grant-advisorSkill
- sbdc-marketing-plan-generatorSkill
- sbdc-success-storySkill
- sbdc-training-newsletterSkill
- sbdc-underwriter-and-capital-coachSkill
- sbdc-workshopsSkill
- tam-sam-somSkill
- transcript-to-action-plan-client-emailSkill
- transcript-to-meeting-notesSkill
- transcript-to-sopSkill
The file
Files
Client Follow-up and Reengagement
Reconnecting with a client who's gone quiet works if the email reads like someone remembered their specific project, not like a retention campaign. The goal is to get them back into advising — and that depends entirely on whether the first line sounds personal or automated.
Start from what's on record
Pull from whatever client history is available — a Neoserra report, an uploaded client file, or details given in chat. Before drafting, note:
- what services or advising sessions the client already used
- any business idea, goal, or aspiration they mentioned
- anything that's changed since — a program update, a new resource, general progress — that gives a real reason to meet again
Weave these in as specific references, not a recap of their file. "I remember you were exploring the catering side of your bakery idea" gives someone a reason to reply; a summary of their intake form doesn't.
No client history? Write it warm anyway
If no report or details are available, don't stall waiting for them, and don't let the email read as generic just because the input was thin. Default to warm, inviting language that works for any pre-venture client — genuine interest in how their idea is coming along, an open invitation to catch up.
Always ask for the meeting
Every email closes with an invitation to schedule time, framed as being for the client's benefit — their next step, their progress — not for closing out a file. Getting them back on the calendar is the actual point of the email, not a friendly note on its own.
If the reply surfaces an accomplishment, record it
The source GPT named "data collection regarding SBDC Milestones" as a goal but never said what to collect or how, so this section is the minimum honest reading of that intent rather than a procedure Brandon wrote.
When the client history you're working from — or the client's reply — shows something they actually completed since going quiet, match it against references/neoserra-milestones.md and note it separately from the email draft, using that file's exact category wording. Neoserra reporting keys off those names, so a paraphrase does not register. Hand it to the advisor as a short "worth logging" line; do not put milestone language into the email itself, which would make a warm note read like file maintenance.
Voice
Warm, professional, and supportive — business insight delivered with a personal touch. Avoid cold or transactional phrasing ("following up on your file," "per our records"); it reads as automated, which is exactly what fills the rest of the client's inbox. Write like someone who remembers their entrepreneurial journey, not like someone closing a ticket.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

