# Follow Up Scheduler

> Follow-Up Scheduler

- Skill: `uitbreidenos/follow-up-scheduler` (Agent Skill)
- Install (CLI): `npx skillmds@latest add uitbreidenos/follow-up-scheduler`
- Raw SKILL.md: https://api.skillmd.com/api/skills/uitbreidenos/follow-up-scheduler/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: UitbreidenOS (https://skillmd.com/u/uitbreidenos)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/uitbreidenos/follow-up-scheduler

---

# Follow-Up Scheduler

## When to activate
After the initial cold email is approved and sent. Use this to generate the full 3-touch follow-up sequence. Also use when re-activating a dormant prospect after 30+ days of silence with a fresh angle.

## When NOT to use
Do not generate follow-ups if the prospect has replied (any reply — interested, objection, or decline). Do not generate if the prospect is on an opt-out list. Do not create more than 3 follow-ups per initial email (4 total touches maximum).

## Instructions

1. Read the initial email draft and account research brief.
2. Identify three distinct angles — each follow-up must use a different hook:
   - **Day 3:** Value add — share a relevant case study, stat, or insight specific to their industry or role. No ask.
   - **Day 7:** Angle shift — reframe the problem from a different perspective. Ask the question differently.
   - **Day 14:** Pattern interrupt / breakup — short, direct, slightly humorous or self-aware. "Should I close your file?" approach.
3. Write each follow-up under 80 words. Keep subject lines varied — use "Re:" only on Day 3 to create thread continuity.
4. Check all three for banned words before returning.
5. Return all three drafts with metadata and a suggested send schedule.

## Output Format

```
FOLLOW-UP SEQUENCE — [Prospect Name, Company]
Initial email sent: [date]

--- DAY 3 (send [date]) ---
Subject: Re: [original subject] / [new subject]
[Body — value add, under 80 words]
Banned word check: PASS/FAIL

--- DAY 7 (send [date]) ---
Subject: [fresh subject]
[Body — angle shift, under 80 words]
Banned word check: PASS/FAIL

--- DAY 14 (send [date]) ---
Subject: [pattern interrupt subject]
[Body — short breakup, under 60 words]
Banned word check: PASS/FAIL

Status: ALL PENDING HUMAN APPROVAL
```

## Example

**Day 3 (Value Add):**
> Subject: Re: Stackline's API launch + developer onboarding
> 
> One more data point: Stripe cut support tickets by 52% in the 60 days after switching to interactive API docs. Their developer success team shared the breakdown if useful.
> 
> Happy to forward it — just let me know.

**Day 7 (Angle Shift):**
> Subject: Different question
> 
> Most API teams measure success by adoption—but adoption requires friction-free onboarding. How do your developers currently discover integration steps? If it's scattered across Slack, wiki, and email, there's a 3-5x efficiency gap you could close.

**Day 14 (Pattern Interrupt):**
> Subject: Closing the loop
> 
> I've sent a couple of notes — no reply, so I'll assume the timing is off.
> 
> If developer onboarding becomes a priority later, I'm easy to find. Either way, good luck with the API launch.

---