agentleFS
Frontal-soFrontal-so/outbound-skills/skills/sdr-outbound-rules/SKILL.md

sdr-outbound-rules

Skill8 starsChanged 4 months agoMITView on GitHub

SDR outbound writing rules, 8 allowed messaging frameworks, and tone guidelines by offer type. Use when training SDRs, creating messaging guidelines, or standardizing outbound quality.

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before sending any outreach:

    line 106

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SDR Outbound Writing Rules

Core Writing Rules

Emails: 60-90 words maximum
No bullets in cold emails
One CTA only

CTA Rules:
- Clear and direct
- Respectful of their time
- Scheduling-oriented when possible

Personalization Inputs to Use

  • Name
  • Company
  • Role
  • Industry
  • Challenge (if known)
  • Goal (if known)
  • Source/trigger
  • Familiarity level

8 Allowed Messaging Frameworks

1. Before/After

Show transformation from current state to desired state.

2. Pattern Interrupt

Break expected email patterns to grab attention.

3. Ask Before Pitch

Lead with question, earn right to pitch.

4. Upfront Value

Provide value before asking for anything.

5. Do the Math

Calculate potential impact with numbers.

6. Challenge of Similar Companies

Reference industry-specific patterns.

7. Neutral Insight

Share third-party resource, build trust.

8. Typical Problems by Role

Address role-specific pain points.


Tone by Offer Type

Agency Services

  • Consultative
  • Strategic
  • Calm
  • Position as trusted advisor

Accelerator

  • Slang professional
  • Friendly
  • Curious
  • Approachable expert

Outbound Cold

  • Pattern interrupt
  • Short
  • Clear
  • Direct but not aggressive

Quality Standards

Good Email

  • 60-90 words
  • One clear CTA
  • Specific social proof
  • Relevant trigger
  • Human tone

Bad Email

  • 150+ words
  • Multiple CTAs
  • Vague claims
  • No personalization
  • Corporate tone

Review Checklist

Before sending any outreach:

  • Under 90 words?
  • Single CTA?
  • Trigger or personalization included?
  • Social proof specific (numbers)?
  • Tone matches offer type?
  • No buzzwords?
  • No fake enthusiasm?
  • Would you respond to this?

Combines with

SkillWhy
sdr-master-promptsAI prompts following these rules
email-writing-frameworksApproved framework structures
josh-braun-copywritingQuality writing principles
email-metrics-benchmarksTrack rule impact on metrics

Example prompts

Review this email against the SDR outbound rules checklist.
Rewrite this 150-word email to be under 90 words.
Which of the 8 frameworks should I use for a cold outbound campaign?

Part of Frontal — free, open GTM skills for your AI agent. Browse the library →

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.