Skip to content

JasonColapietro/suede-creator-skills / skills/suede-cold-email

suede-cold-email

Verified

Use when asked "write a cold email" or to repair B2B outbound to qualified prospects. Suede produces sourced personalization, short subjects, bodies under 75 words, one ask and bounded follow-ups, with current sender-rule checks. NOT FOR: prospect qualification (use suede-prospecting), opted-in lifecycle email (use suede-emails), or broader sales collateral (use suede-sales-enablement).

FileKindSize
CARD.mdmarkdown4.4 KB
SKILL.mdskill md9.9 KB
agents/openai.yamlconfig558 B
evals/evals.jsonconfig6.9 KB
references/benchmarks.mdmarkdown6.1 KB
references/follow-up-sequences.mdmarkdown2.6 KB
references/frameworks.mdmarkdown3.8 KB
references/personalization.mdmarkdown3.0 KB
references/subject-lines.mdmarkdown1.8 KB
references/usage-contract.mdmarkdown889 B

references/follow-up-sequences.md

View on GitHub
# Follow-Up Sequences

The first email draws most replies (about 58% in Instantly's 2026 benchmark),
but the remaining 42% or so arrive on follow-ups. A sequence that stops after one
send gives up nearly half its replies. The follow-up only works when it adds
something new.

## Length: 3 to 5 emails total

More touches catch different timing windows, but complaint rates climb with
every extra email, and a complaint rate near Gmail's 0.3% ceiling puts the whole
domain at risk. Cap at four follow-ups. Stop sooner when the account shows
complaints or unsubscribes rising.

## Cadence

Widen the gap after each touch.

| Touch | Day | Job |
|---|---|---|
| First email | 0 | Most research effort goes here |
| Follow-up 1 | 3 | A different angle |
| Follow-up 2 | 7 to 8 | Proof from a similar company |
| Follow-up 3 | 14 | A useful insight or resource |
| Follow-up 4 | 21 to 28 | The close-out |

Send midweek during the prospect's working hours. Treat day and hour as a test,
not a rule.

## One new idea per touch

| Touch | Angle | Purpose |
|---|---|---|
| First | Personalized observation, core problem, soft ask | Open the conversation |
| Follow-up 1 | A second reason the problem matters | Show another benefit |
| Follow-up 2 | Short story or result from a comparable company | Credibility |
| Follow-up 3 | An insight, trend, or free resource | Prove expertise without asking |
| Follow-up 4 | Close the loop | Remove pressure and leave the door open |

Each email must stand alone. The reader may never have opened the earlier ones.

## The close-out email

Acknowledge the silence, offer one last useful thing, say this is the final
note, and leave the door open.

> I haven't heard back, so I'll assume the timing is off. One thing before I
> close the loop: [one-sentence insight or resource]. If that changes anything,
> reply anytime. Either way, good luck with [their goal].

A numbered-reply version removes almost all friction:

> Since I haven't heard back, I'll keep it simple. Reply with a number:
> 1, let's talk. 2, check back next quarter. 3, please stop.

**Honor it.** After a close-out, do not contact that person again in this
sequence. A "3" or any opt-out goes on the suppression list immediately.

## Phrases that kill replies

- "I never heard back"
- "Just checking in"
- "Bumping this to the top of your inbox"
- "Did you see my last email?"
- "Following up on my previous message"

## Ask size by seniority

- Executives and founders: the smallest possible ask. "Curious?" or "Worth two
  minutes?"
- Mid-level managers: a specific, concrete offer. "Want me to walk through how
  [Company] cut [task] by [verified amount]?"
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall