ABM 1-to-Many (Programmatic) skill
Runs programmatic 1-to-many ABM for 50-200+ accounts: automated personalization, scaled outbound, intent-based targeting, and lookalike expansion.
by LeadMagic·MIT license·★ 62 Stars on the repo·GitHub ↗
npx degit LeadMagic/gtm-skills/skills/abm/abm-1-to-many#main ~/.claude/skills/abm-1-to-manyChecked ·commit main
Inside this skill
SKILL.md · the author's own words# ABM 1-to-Many (Programmatic) ## Overview Programmatic ABM for 50-200+ accounts using automation, lookalike modeling, and scaled personalization. This tier uses the same methodology as 1-to-1 and 1-to-few but replaces manual effort with AI and workflow automation. ## Authoritative Foundations - **TOPO (now Gartner) — Programmatic ABM** — Treat 1:many as automated personalization by segment: shared messaging, intent-triggered play… - **Clay — Waterfall enrichment** — Waterfall enrichment, Claygent research, and table-based automation for building and refreshing large a… - **ITSMA — Account-Based Marketing** — Tier-based ABM (1:1 / 1:few / 1:many); measure pipeline from target accounts, not lead volume. ## When to Use - "Scale ABM to more accounts" - "Programmatic ABM setup" - "Automated account-based outreach"
Word-for-word excerpt, not a result. Read the full SKILL.md ↓
Files of ABM 1-to-Many (Programmatic)
Show the full text141 lines
ABM 1-to-Many (Programmatic)
Overview
Programmatic ABM for 50-200+ accounts using automation, lookalike modeling, and scaled personalization. This tier uses the same methodology as 1-to-1 and 1-to-few but replaces manual effort with AI and workflow automation.
Authoritative Foundations
- TOPO (now Gartner) — Programmatic ABM — Treat 1:many as automated personalization by segment: shared messaging, intent-triggered plays, and account-level measurement.
- Clay — Waterfall enrichment — Waterfall enrichment, Claygent research, and table-based automation for building and refreshing large account lists.
- ITSMA — Account-Based Marketing — Tier-based ABM (1:1 / 1:few / 1:many); measure pipeline from target accounts, not lead volume.
When to Use
- "Scale ABM to more accounts"
- "Programmatic ABM setup"
- "Automated account-based outreach"
- "Expand ABM coverage without headcount"
Step-by-Step Process
Phase 1: Lookalike Expansion
Start from Tier 1-2 winners and expand:
- ICP lookalike: Find accounts matching your top 10% win profile
- Intent lookalike: Accounts showing similar buying signals to closed-won
- Engagement lookalike: Accounts engaging with content the way winners did pre-opportunity
- Trigger lookalike: Accounts with same triggers (funding, hiring, tech change)
Phase 2: Automated Account Intelligence
Use enrichment and AI to auto-build briefs:
- Clay workflow: pull firmographics, technographics, news, signals
- AI summarizes: company snapshot, pain hypothesis, relevant proof points
- Auto-prioritize: score accounts 0-100 and assign to SDR queues
Phase 3: Scaled Personalization
- Dynamic landing pages: URL params personalize hero/headline by industry/company
- Tokenized email sequences: Merge fields beyond first name — industry, tech stack, signal
- Automated LinkedIn: AI drafts personalized connection notes and DMs
- Retargeting: Account-based ad audiences on LinkedIn by company name or domain
Phase 4: Automated Cadence Orchestration
- SDR assigned accounts per round (rotating to prevent burnout)
- Automated task creation in CRM per account
- AI drafts first outreach; SDR reviews and sends
- AI handles replies (OOO, not interested, wrong person); SDR handles positive replies
Phase 5: Feedback Loop
- Weekly review: which accounts engaged, which didn't
- Kill accounts after 8 touches with no reply
- Feed winners back into lookalike model
- Continuously refine ICP based on engagement patterns
Output Format
Programmatic ABM plan with: lookalike criteria, enrichment workflow, personalization templates, SDR routing rules, and optimization framework.
Quality Check
Before delivering, verify:
- All required sections are complete
- Output matches the user's stated need
- Named frameworks are cited for key recommendations
- No vague claims — every recommendation has a specific action
- Deliverable is ready for operational use, not just conceptual
Common Pitfalls
- Treating ABM as a marketing-only initiative. ABM requires tight sales alignment. Without BDRs assigned to specific accounts and shared account briefs, marketing produces content nobody uses. Fix: weekly ABM standups with marketing + BDRs + AEs.
- One-size-fits-all tiering. Applying the same playbook to Tier 1 and Tier 3 accounts. Fix: Tier 1 gets custom content and executive engagement; Tier 3 gets automated personalization.
- Measuring ABM on MQLs. ABM success is pipeline from target accounts, not lead volume. Fix: track coverage %, engagement depth, pipeline created, and win rate by tier.
Execution Artifacts
references/framework-notes.md— named frameworks, citation anchors, and operating assumptionstemplates/output-template.md— copy-paste deliverable structure for the userscripts/check-output.py— local checklist validator for required sections This skill includes lightweight artifacts the agent can load on demand: Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.
Implementation Depth
Use this section when the user asks for a finished asset, not a high-level explanation.
Diagnostic Questions
- What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
- Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
- What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
- What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
- What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
Framework Application
Map the recommendation explicitly to the named frameworks in this skill:
- TOPO Programmatic ABM: apply only the part that directly improves the requested deliverable.
- Clay Automation Patterns: apply only the part that directly improves the requested deliverable.
- ITSMA — Account-Based Marketing: apply only the part that directly improves the requested deliverable.
Deliverable Standard
A strong output from this skill includes:
- A crisp diagnosis of the current situation
- A recommended path with tradeoffs, not a generic list
- A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
- A measurement plan with leading and lagging indicators
- Risks and edge cases called out before execution
Adaptation Rules
- For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
- For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
- For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
Related Skills
- clay-automation, ai-sdr-setup, list-building, signal-scoring, icp-scoring
| 1 | |
| 2 | name abm-1-to-many |
| 3 | description >- |
| 4 | Runs programmatic 1-to-many ABM for 50-200+ accounts: automated |
| 5 | personalization, scaled outbound, intent-based targeting, and lookalike |
| 6 | expansion. Use when ABM coverage must grow without adding headcount or when |
| 7 | the user wants automated account-based outreach. Triggers on: "1-to-many ABM", |
| 8 | "programmatic ABM", "scaled ABM", "automated ABM". |
| 9 | license MIT |
| 10 | compatibility Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed |
| 11 | metadata |
| 12 | version "1.0.0" |
| 13 | author LeadMagic |
| 14 | category abm |
| 15 | tags [abm, 1-to-many, programmatic-abm, scaled, automation] |
| 16 | frameworks |
| 17 | - "TOPO (now Gartner) — Programmatic ABM" |
| 18 | - "Clay — Waterfall enrichment" |
| 19 | - "ITSMA — Account-Based Marketing" |
| 20 | |
| 21 | |
| 22 | # ABM 1-to-Many (Programmatic) |
| 23 | |
| 24 | ## Overview |
| 25 | Programmatic ABM for 50-200+ accounts using automation, lookalike modeling, |
| 26 | and scaled personalization. This tier uses the same methodology as 1-to-1 and |
| 27 | 1-to-few but replaces manual effort with AI and workflow automation. |
| 28 | |
| 29 | ## Authoritative Foundations |
| 30 | **TOPO (now Gartner) — Programmatic ABM** — Treat 1:many as automated personalization by segment: shared messaging, intent-triggered plays, and account-level measurement. |
| 31 | **Clay — Waterfall enrichment** — Waterfall enrichment, Claygent research, and table-based automation for building and refreshing large account lists. |
| 32 | **ITSMA — Account-Based Marketing** — Tier-based ABM (1:1 / 1:few / 1:many); measure pipeline from target accounts, not lead volume. |
| 33 | |
| 34 | ## When to Use |
| 35 | "Scale ABM to more accounts" |
| 36 | "Programmatic ABM setup" |
| 37 | "Automated account-based outreach" |
| 38 | "Expand ABM coverage without headcount" |
| 39 | |
| 40 | ## Step-by-Step Process |
| 41 | |
| 42 | ### Phase 1: Lookalike Expansion |
| 43 | Start from Tier 1-2 winners and expand: |
| 44 | **ICP lookalike:** Find accounts matching your top 10% win profile |
| 45 | **Intent lookalike:** Accounts showing similar buying signals to closed-won |
| 46 | **Engagement lookalike:** Accounts engaging with content the way winners did pre-opportunity |
| 47 | **Trigger lookalike:** Accounts with same triggers (funding, hiring, tech change) |
| 48 | |
| 49 | ### Phase 2: Automated Account Intelligence |
| 50 | Use enrichment and AI to auto-build briefs: |
| 51 | Clay workflow: pull firmographics, technographics, news, signals |
| 52 | AI summarizes: company snapshot, pain hypothesis, relevant proof points |
| 53 | Auto-prioritize: score accounts 0-100 and assign to SDR queues |
| 54 | |
| 55 | ### Phase 3: Scaled Personalization |
| 56 | **Dynamic landing pages:** URL params personalize hero/headline by industry/company |
| 57 | **Tokenized email sequences:** Merge fields beyond first name — industry, tech stack, signal |
| 58 | **Automated LinkedIn:** AI drafts personalized connection notes and DMs |
| 59 | **Retargeting:** Account-based ad audiences on LinkedIn by company name or domain |
| 60 | |
| 61 | ### Phase 4: Automated Cadence Orchestration |
| 62 | SDR assigned accounts per round (rotating to prevent burnout) |
| 63 | Automated task creation in CRM per account |
| 64 | AI drafts first outreach; SDR reviews and sends |
| 65 | AI handles replies (OOO, not interested, wrong person); SDR handles positive replies |
| 66 | |
| 67 | ### Phase 5: Feedback Loop |
| 68 | Weekly review: which accounts engaged, which didn't |
| 69 | Kill accounts after 8 touches with no reply |
| 70 | Feed winners back into lookalike model |
| 71 | Continuously refine ICP based on engagement patterns |
| 72 | |
| 73 | ## Output Format |
| 74 | Programmatic ABM plan with: lookalike criteria, enrichment workflow, personalization |
| 75 | templates, SDR routing rules, and optimization framework. |
| 76 | |
| 77 | |
| 78 | |
| 79 | ## Quality Check |
| 80 | |
| 81 | Before delivering, verify: |
| 82 | [ ] All required sections are complete |
| 83 | [ ] Output matches the user's stated need |
| 84 | [ ] Named frameworks are cited for key recommendations |
| 85 | [ ] No vague claims — every recommendation has a specific action |
| 86 | [ ] Deliverable is ready for operational use, not just conceptual |
| 87 | |
| 88 | ## Common Pitfalls |
| 89 | |
| 90 | **Treating ABM as a marketing-only initiative.** ABM requires tight sales alignment. Without BDRs assigned to specific accounts and shared account briefs, marketing produces content nobody uses. Fix: weekly ABM standups with marketing + BDRs + AEs. |
| 91 | **One-size-fits-all tiering.** Applying the same playbook to Tier 1 and Tier 3 accounts. Fix: Tier 1 gets custom content and executive engagement; Tier 3 gets automated personalization. |
| 92 | **Measuring ABM on MQLs.** ABM success is pipeline from target accounts, not lead volume. Fix: track coverage %, engagement depth, pipeline created, and win rate by tier. |
| 93 | |
| 94 | ## Execution Artifacts |
| 95 | |
| 96 | `references/framework-notes.md` — named frameworks, citation anchors, and operating assumptions |
| 97 | `templates/output-template.md` — copy-paste deliverable structure for the user |
| 98 | `scripts/check-output.py` — local checklist validator for required sections |
| 99 | This skill includes lightweight artifacts the agent can load on demand: |
| 100 | Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice. |
| 101 | |
| 102 | ## Implementation Depth |
| 103 | |
| 104 | Use this section when the user asks for a finished asset, not a high-level explanation. |
| 105 | |
| 106 | ### Diagnostic Questions |
| 107 | |
| 108 | What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led? |
| 109 | Which ICP tier is the output for: small business, mid-market, enterprise, or mixed? |
| 110 | What proof is available today: customer stories, usage data, third-party validation, screenshots, or none? |
| 111 | What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow? |
| 112 | What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure? |
| 113 | |
| 114 | ### Framework Application |
| 115 | |
| 116 | Map the recommendation explicitly to the named frameworks in this skill: |
| 117 | |
| 118 | TOPO Programmatic ABM: apply only the part that directly improves the requested deliverable. |
| 119 | Clay Automation Patterns: apply only the part that directly improves the requested deliverable. |
| 120 | ITSMA — Account-Based Marketing: apply only the part that directly improves the requested deliverable. |
| 121 | |
| 122 | ### Deliverable Standard |
| 123 | |
| 124 | A strong output from this skill includes: |
| 125 | |
| 126 | A crisp diagnosis of the current situation |
| 127 | A recommended path with tradeoffs, not a generic list |
| 128 | A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan |
| 129 | A measurement plan with leading and lagging indicators |
| 130 | Risks and edge cases called out before execution |
| 131 | |
| 132 | ### Adaptation Rules |
| 133 | |
| 134 | For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity. |
| 135 | For mid-market: include workflow ownership, handoffs, integrations, and enablement assets. |
| 136 | For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements. |
| 137 | |
| 138 | |
| 139 | ## Related Skills |
| 140 | clay-automation, ai-sdr-setup, list-building, signal-scoring, icp-scoring |
| 141 |
Discussion
Browse more free Claude skills.