Weekly Personalized Follow-Up Drafts
Every week your clone reads the CRM, email and open cases for your target accounts and saves a personalized follow-up draft for each, ready for you to review and send.
Each week your clone pulls accounts from Salesforce or HubSpot that match your filter, reads the latest email thread, CRM notes, open deal and open cases, and drafts a follow-up per primary contact with a clear next step and ask. Drafts are saved in Gmail or Outlook (never sent), and you get a summary table plus a list of skipped accounts such as open escalations or recent contact.
At a glance
- Difficulty
- Intermediate
- Setup time
- 30–60 min
- Built for
- Sales, Customer Success
Version 1.0.0 · updated 2026-10-22
Overview
Follow-ups slip because the context is scattered across the CRM, email and notes, and writing a dozen thoughtful emails takes a morning. Deals stall and quiet accounts drift. Weekly Follow-Up Drafts does the research and first draft and leaves the sending to you.
Following up with the right account at the right time is the work that keeps deals moving and customers close. It is also the work that slips: the list lives in the CRM, the context lives in email and notes, and writing 15 thoughtful emails takes a whole morning.
Weekly Personalized Follow-Up Drafts does the research and the first draft. Every week your clone:
- pulls accounts from Salesforce or HubSpot that match your
{FILTER}(for example: you own it, stage is X, no activity in N days), - reads the latest email thread with each account's contacts (Gmail or Outlook),
- reads CRM notes, the open opportunity or deal, recent activities and open cases,
- drafts one personalized follow-up per primary contact: it references the last conversation, any open question or commitment, proposes a next step and makes a clear ask,
- saves each one as a DRAFT in Gmail or Outlook (never sent),
- emails you a summary table (account, contact, why now, draft subject, link to the draft) and a list of skipped accounts with reasons,
- optionally logs a CRM task "Follow-up drafted" (and "Follow-up sent" after you tell it you sent).
What you get:
| Benefit | What it looks like |
|---|---|
| A follow-up habit that runs itself | A fresh batch of drafts waiting every Monday morning |
| Real personalization | Each draft cites the last thread, a commitment or an open question, not a generic template |
| No awkward mistakes | Accounts with an open escalation or a recent touch are skipped and flagged, not emailed |
| Time back | 5–10 minutes saved per account on research and first drafts |
| You stay in control | Drafts only. Nothing is ever sent without you |
Who it’s for
- Sales reps and account executives who need steady follow-up on open deals and quiet accounts.
- Customer Success Managers who want proactive check-ins with accounts that have gone quiet.
- Sales and CS managers who want a consistent follow-up rhythm across the team (each person runs their own).
It is built for one-to-one, relationship-style follow-ups to accounts already in your CRM. It is not a mass-mailing tool (see customer-email-program or cold-email-sequence for that).
How it works
Trigger: scheduled task ({RUN_TIME}, e.g. Monday 7 AM)
or on demand: "Draft this week's follow-ups"
│
▼
┌───────────────────────────────────────────────────────────────────┐
│ "Weekly Follow-Up Drafts" skill │
│ │
│ 1. Pull target accounts from the CRM using {FILTER} │
│ (cap at {MAX_ACCOUNTS}, remove {EXCLUDE_LIST}) │
│ 2. For each account, read: │
│ · latest email thread (search by domain AND contact emails) │
│ · CRM notes · open opportunity/deal · recent activities │
│ · open cases (or open support notes/tasks in HubSpot) │
│ 3. Skip and FLAG when: │
│ · no email thread · no contact email │
│ · contacted within {COOLDOWN_DAYS} │
│ · open escalation │
│ 4. Draft one follow-up per primary contact │
│ (last conversation · open question · next step · ask) │
│ in {TONE}, signed with {SIGNATURE} │
│ 5. Save each as a DRAFT in Gmail or Outlook (never send) │
└───────────────────────────────┬───────────────────────────────────┘
│
▼
┌───────────────────────────────────────────────────────────────────┐
│ Summary email to YOU │
│ · table: account · contact · why now · draft subject · link │
│ · skipped accounts and the reason for each │
│ Optional: CRM task "Follow-up drafted" │
└───────────────────────────────┬───────────────────────────────────┘
│
You review, edit and send from your inbox
│
▼
Optional: tell the clone "sent" → CRM task "Follow-up sent"How each account is researched
| Source | What the clone reads | Why |
|---|---|---|
| Latest thread with the account (search by domain and by each contact's email address) | The last conversation, open questions, commitments | |
| CRM notes and activities | Recent notes, calls, meetings and tasks | What happened outside email |
| Opportunity or deal | Stage, amount, close date, next step | The right next step and ask |
| Cases (Salesforce) or support notes/tasks (HubSpot) | Open items and any escalation flag | Don't send a sales-style nudge into an open problem |
Setup, step by step
- Check requirements (5 min)Open REQUIREMENTS.md and run the pre-flight checklist. You need a CRM connection, an email connection that can read mail and create drafts, and the ability to create a scheduled task.
- Hand the instructions to your clone (2 min)Paste or upload CLONE-INSTRUCTIONS.md into a chat with your clone and say: "Please set up this use case for me. Show me a plan before changing anything."
- Review the discovery table (5 min)The clone reports which operators and connections it has and which are missing.
- Answer the placeholder questions (5 min)See section 6.
- Approve the plan (2 min)Say "yes" only when it looks right.
- Do your part (10–20 min)Only you can: - Connect your own Salesforce or HubSpot account (read access to accounts/companies, deals, contacts, activities and cases; write access only if you want the optional follow-up task). - Connect your own Gmail or Outlook with permission to read mail and create drafts. - Optionally connect Slack or Teams for delivery.
- Save the Weekly Follow-Up Drafts skill (5 min)The clone saves it, or gives you the full text to paste.
- Run the test plan (10–15 min)Run it on one or two test accounts that use your own email address as the contact.
- Turn on the scheduleA weekly task at {RUNTIME}.
The full walkthrough is in the README. The Clone Instructions file tells your clone exactly what to do.
What you’ll need
Your clone matches these to the exact skill names in your workspace. Confirm them in your skill catalog before saving the skill. Your clone will report the exact names it finds.
Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.
Pick one CRM (required):
| # | Skill / operator (exact name) | What it's used for | Notes |
|---|---|---|---|
| 1 | Salesforce Account Operator | Pull target accounts by {FILTER} | Salesforce users |
| 2 | Salesforce Opportunity Operator | Open opportunity details (stage, amount, close date, next step) | Salesforce users |
| 3 | Salesforce Contact Operator | Primary contacts and their emails | Salesforce users |
| 4 | Salesforce Activity Operator | Notes, recent activities, "no activity in N days"; optional follow-up task | Salesforce users |
| 5 | Salesforce Case Operator | Open cases and escalations | Salesforce users |
| 6 | HubSpot Company Operator | Pull target companies by {FILTER} | HubSpot users |
| 7 | HubSpot Deal Operator | Open deal details | HubSpot users |
| 8 | HubSpot Contact Operator | Primary contacts and their emails | HubSpot users |
| 9 | HubSpot Engagement Operator | Notes, activities, support notes/tasks; optional follow-up task | HubSpot users (no ticket operator exists) |
Also required:
| # | Skill / operator (exact name) | What it's used for | Notes |
|---|---|---|---|
| 10 | Google Gmail Operator or the Outlook email operator | Read threads, create drafts, send the summary to you | Must be able to create drafts |
| 11 | Weekly Follow-Up Drafts (custom skill) | The workflow itself | Saved from CLONE-INSTRUCTIONS.md section 7 |
| 12 | Scheduled task (via the platform tool) | Weekly run at {RUN_TIME} | Not needed for on-demand only use |
Known gotchas
- Drafts only. Review before sending. The clone never sends. Read every draft: names, numbers, dates and promises.
- Personal email domains need a search by contact email. If a contact uses a personal address, searching by domain finds nothing or the wrong people. The clone searches by domain and by each contact's email address.
- Open escalation means no draft. Accounts with an open escalation are flagged, not drafted. Resolve the issue first, then follow up personally.
- Keep batches small. 10–15 accounts review well. Large batches get skimmed and mistakes slip through.
- Drafts may not be editable by the clone after creation. Gmail and Outlook drafts can't always be edited by the clone once created. If you want a change, ask the clone to regenerate the draft, then delete the old one.
- Each user connects their own CRM and email. No shared accounts. Drafts appear in the connected user's mailbox.
- HubSpot has no ticket operator. Open support items are read from notes and tasks, so an "escalation" must be marked there (for example a note or task labeled "Escalation") to be detected.
- Email threads may be missing. If the email history lives in another mailbox or the contact was never emailed from your account, the account is skipped as "no email thread".
- Read every instruction before saving the skill. You are responsible for what your clone does.
Questions
Will it send emails to my customers?
No. It only saves drafts. You send them.
Which CRMs and mail systems work?
Salesforce or HubSpot, and Gmail or Outlook. See the mapping tables in REQUIREMENTS.md.
How does it pick accounts?
From your {FILTER}, capped at {MAXACCOUNTS}, minus {EXCLUDELIST}.
What if an account has an open problem?
It is skipped and flagged in your summary. No draft is created.
Can it edit a draft after I ask for changes?
Not reliably. It creates a new draft. Delete the old one.
What if a contact uses a personal email address?
The clone searches by the contact's email address as well as by domain.
Can it log what it did in the CRM?
Optionally, as a task "Follow-up drafted", and "Follow-up sent" after you tell it you sent.
Can the whole team use it?
Yes. Each person connects their own CRM and email and gets their own batch.
Can I run it on demand?
Yes: "Draft this week's follow-ups."