agentleFS
Frontal-soFrontal-so/outbound-skills/skills/personalization-playbooks/SKILL.md

personalization-playbooks

Skill8 starsChanged 4 months agoMITView on GitHub

Camp Personalization vs No Personalization playbooks by outreach category - Inbound, Postbound, Bridgebound, and Outbound. Use when deciding personalization level, building automated sequences, or creating messaging templates.

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

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Personalization Playbooks

Camp Personalization Playbook (Manual/High-Touch)

INBOUND

First Line: Trigger-Based Relevance ONLY
Second Line: CTA to Book Time (Optional: Core-Static Relevance)

Example:

Thanks for downloading the Cold Email Playbook.

Got 15 minutes to discuss how to apply it at {{company}}?

POSTBOUND/BRIDGEBOUND

First Line: Trigger-Based Relevance + ("but more importantly") Personalization
Second Line: Personalization "Hook" + Core-Static Relevance

Example:

Saw you attended our webinar on signal-based outbound—but more importantly, your recent post about "outbound being dead" caught my attention.

You mentioned reply rates dropping below 1%. We've been helping B2B SaaS companies hit 15%+ with signal-first targeting.

Worth a quick chat?

OUTBOUND

First Line: Personalization Title or Summary + Personalization Excerpt
Second Line: Personalization "Hook" + Core-Static Relevance

Example:

Your post on SDR burnout—specifically the line "throwing bodies at the problem doesn't scale"—resonated.

We work with SaaS companies doing $5-20M who've hit that wall. Most are shifting from volume to signal-based.

Curious if that's on your radar?

Camp No Personalization Playbook (Automated/Scale)

INBOUND

First Line: Trigger-Based Relevance ONLY
Second Line: CTA to Book Time (Optional: Core-Static Relevance)

Example:

Thanks for requesting a demo.

Let's find 15 minutes to walk through how {{product}} works for {{industry}} companies.

[Calendar link]

POSTBOUND/BRIDGEBOUND

First Line: Trigger-Based Relevance
Second Line: Core-Static Relevance

Example:

Noticed you've been checking out our pricing page.

We work with B2B SaaS companies doing $5-20M ARR on outbound.

Worth a quick call to see if there's a fit?

OUTBOUND

First Line: Core-Static Relevance (Lean on Pattern Interruptive Opener)
Second Line: Core-Static Relevance ("We work with...")

Example:

Quick question: How's your team handling pipeline predictability right now?

We work with B2B SaaS companies doing $5-20M who struggle with inconsistent lead flow.

Worth exploring?

Decision Matrix

FactorUse PersonalizationSkip Personalization
Deal size>$25K ACV<$25K ACV
Volume<50/day>100/day
ICP fitTier 1 accountsTier 2-3 accounts
Signal strengthWeak signalsStrong signals
CompetitiveHigh competitionLow competition

Combines with

SkillWhy
outreach-4-categoriesMatch playbook to lead category
personalization-6-bucketsFind data for personalization
personalization-hooksCreate hooks for Camp Personalization
cold-email-4-sequenceApply playbook to sequence

Example prompts

Which playbook should I use for a $15K ACV deal with strong intent signal?
Write a Camp Personalization Bridgebound email for this prospect: [details]
Create a No Personalization Outbound template for targeting DevOps managers.

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.