atl-btl-messaging
Skill8 starsChanged 4 months agoMITView on GitHub
Above-the-Line (ATL) and Below-the-Line (BTL) messaging framework for targeting executives vs end-users. Use when crafting messages for different seniority levels, deciding message length and tone, or adapting outreach to VPs/C-Level vs Managers/ICs.
2 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- Cold-IQ/ColdIQ-s-GTM-Skillsedited, first seen Nov 8, 2026
- sachacoldiq/ColdIQ-s-GTM-Skillsedited, first seen Oct 9, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- Cold-IQ/ColdIQ-s-GTM-Skills★ 31670% same
- sachacoldiq/ColdIQ-s-GTM-Skills★ 31670% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- ai-personalization-promptsSkill
- bridgebound-firmographic-15Skill
- bridgebound-history-16Skill
- bridgebound-in-market-20Skill
- bridgebound-relationship-39Skill
- bridgebound-symptoms-11Skill
- buying-signals-6Skill
- clay-buying-signals-5Skill
- clay-enrichment-9stepSkill
- cold-call-scriptsSkill
- cold-email-4-sequenceSkill
- cold-email-templates-34Skill
- email-1-variations-7Skill
- email-metrics-benchmarksSkill
- email-writing-frameworksSkill
- frontal-messaging-templatesSkill
- gtm-philosophySkill
- gtm-plays-11Skill
- inbound-triggers-30Skill
- josh-braun-copywritingSkill
- lead-sources-guideSkill
- linkedin-campaign-completeSkill
- linkedin-limits-warmupSkill
- linkedin-success-factorsSkill
- list-building-tipsSkill
- outbound-triggers-6Skill
- outreach-4-categoriesSkill
- personalization-6-bucketsSkill
- personalization-hooksSkill
- personalization-playbooksSkill
- sdr-master-promptsSkill
- sdr-outbound-rulesSkill
The file
Files
ATL vs BTL Messaging Framework
Above-the-Line (ATL) - VPs, C-Level, Directors
Mindset:
- Think past and future (strategic)
- Want validation, not problems solved
- Care about big picture, not daily operations
What They Care About:
- Revenue impact
- Risk reduction
- Strategic initiatives
- Competitive positioning
- Board/investor optics
Message Length: 2-3 sentences only
Language to Use:
- "Strategic initiative"
- "Revenue impact"
- "Competitive advantage"
- "Board-level priority"
- "Risk mitigation"
Example ATL Email:
Subject: Q1 revenue efficiency
{{firstName}},
If you could identify revenue leakage 3 months faster, what would that mean for next year's targets?
We helped {{similar_company}}'s CEO do exactly that.
15 minutes to explore?Fatal ATL Mistake: Talking about operational problems = immediate delegation to subordinate
Below-the-Line (BTL) - Managers, ICs, End-Users
Mindset:
- Think present (tactical)
- Want problems solved immediately
- Care about daily workflow
What They Care About:
- Daily pain points
- Time savings
- Workflow improvements
- Making their job easier
- Looking good to their boss
Message Length: 3-4 sentences acceptable
Language to Use:
- "Stop spending 3 hours every week on..."
- "Eliminate the manual work of..."
- "Never deal with {{pain}} again"
- "Save {{X}} hours per week"
Example BTL Email:
Subject: 3 hours back
Hey {{firstName}},
Stop spending 3 hours every week fighting with Excel.
We helped {{similar_company}}'s ops team cut their reporting time by 70%.
Want to see how?Fatal BTL Mistake: Talking about ROI and strategic impact = doesn't resonate, too abstract
Decision Framework: Who to Target
Target ATL (Executives) When:
- Deal size > $50K ACV
- Strategic/transformation purchase
- Requires budget approval from top
- Long sales cycle acceptable
Target BTL (End-Users) When:
- Product-led growth motion
- User adoption drives expansion
- Bottom-up sale
- Need internal champion first
Multi-Thread (Both) When:
- Complex enterprise sale
- Multiple stakeholders
- Both budget holder and user buy-in needed
Combines with
| Skill | Why |
cold-email-4-sequence | Adjust sequence length for ATL vs BTL |
sdr-outbound-rules | Apply word count rules by seniority |
outbound-triggers-6 | CXO Passdown for ATL targeting |
personalization-6-buckets | Choose bucket by seniority level |
Example prompts
Rewrite this email for a CFO (ATL) instead of a Finance Manager (BTL).Create an ATL email about cost reduction for a VP Operations at a logistics company.I have a BTL champion - write a BTL email I can ask them to forward to their VP.Part of Frontal — free, open GTM skills for your AI agent. Browse the library →
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
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.

