Sales: Follow-up email

What this skill does

Writes a follow-up email draft to a client with context from the last meeting. Tone is matched to the relationship stage — different for a fresh contact than when waiting for the CFO’s decision.

The draft appears in chat for review. Optionally creates a draft in the inbox via MCP Gmail.

How it works

Reads your latest meeting notes and CRM data first, then writes the email from what actually happened — not a generic “following up on our conversation” opener. Tone shifts based on where you are with the client: fresh contact gets a short inviting note, post-proposal gets a concrete “where are we?” message.

Draft lands in chat. One explicit command sends it via MCP Gmail.

What you get

• A draft that references real specifics from the meeting, not placeholder text
• Tone calibrated to the relationship stage — not the same email to every client
• No AI slop: no “Thanks for your time”, no filler phrases, one clear CTA

Requires

sales-client-crm-local and sales-meeting-recap — the skill reads from the folder structure they create.

Skill file

---
name: sales-followup-email
description: 'ALWAYS use this skill when a salesperson asks for a follow-up email to a client — even if the word "follow-up" is not used explicitly. Triggers: "follow-up to John after today", "write an email to Smith", "email after the meeting", "ping the client", "close the thread with <client>", "/sales-followup-email". The skill reads local client context (recent meetings, CRM data) and generates an email draft with tone matched to the relationship stage. Draft goes to chat for review. Applies anti-AI-slop rules.'
argument-hint: "<client first name, last name, or company>"
---

# Sales Follow-up Email — post-meeting email draft with tone per relationship stage

You are the salesperson's assistant. After a client meeting you write a follow-up email draft: with real context (what we agreed, what we promised, what the client raised), with tone matched to the relationship stage, in natural language without AI slop.

The draft goes to chat for review — you don't save it to the client folder.

## Configuration

- `{CLIENTS}` — client folder (default `Clients/`)
- `{CRM}` — client data file (default `{CLIENTS}/_clients.csv`)

## Workflow

**Step 1:** Find the client and context. Match against `{CRM}` and `{CLIENTS}/<id>-<slug>/Meetings/`.

**Step 2:** Load the most recent (or indicated) meeting + client data from `{CRM}`.

**Step 3:** Choose tone based on relationship stage:

| Relationship stage | Tone | Length |
|---|---|---|
| Fresh contact | Inviting | 80–150 words |
| Ongoing conversations | Continuing | 80–150 |
| After sent proposal | Concrete | 100–200 |
| Negotiating terms | Flexible | 100–200 |
| After a no | Soft | 80–150 |

**Step 4:** Write the draft. Anti-AI-slop rules: no em-dashes (—), no "Thanks for your time", no buzzwords. Subject line from something specific in the meeting. One CTA.

**Step 5:** Deliver draft to chat. Optionally: create draft in inbox via MCP (Gmail/Outlook) on explicit command.

When to use

• “follow-up to John after today”
• “write an email to Smith after the meeting”
• “email thanking them for the call”
• “ping the client”
• /sales-followup-email

How it matches tone

Relationship stage	Tone	Goal
Fresh contact	Inviting, short	Book the next step
Ongoing conversations	Continuing	Small next step
After sent proposal	Concrete	Find out where we’re stuck
Long silence	Re-engagement	Stay visible

Anti-AI-slop rules

No “Thanks for your time”, no em-dashes (—), no buzzwords. Subject line from something specific in the meeting. One CTA.

How to install

1. Download the skill folder via the Download button above or from GitHub
2. In Voicie Desktop: go to the Local tab → find Skills → click the folder icon to open it in Finder
3. Move the downloaded skill folder into that directory
4. Open a new chat — the skill is now available
5. Call it with natural language or /<skill-name>

→ Full guide: How to install skills in Voicie