Abm strategy skill

Designs an account-based marketing program: tier selection, account scoring, channel orchestration, BDR alignment (account-based sales development), and a measurement framework.

by LeadMagic·MIT license·★ 62 Stars on the repo·GitHub ↗

Use now

Inside this skill

SKILL.md · the author's own words
# ABM Strategy

## Overview
ABM is not "send a gift and call it ABM." It's a systematic approach to treating
accounts as markets of one — aligned sales and marketing motions against a curated
set of target accounts. This skill designs the full ABM program: tier selection,
account intelligence, channel orchestration, and measurement.

## When to Use
- "Design our ABM strategy"
- "Set up account-based marketing"
- "Build a target account program"
- "How do we run ABM?"
- "Account selection for enterprise"

## Authoritative Foundations

Word-for-word excerpt, not a result. Read the full SKILL.md ↓

Files of Abm strategy

LeadMagic/main1 file shown
SKILL.md
Show the full text182 lines

ABM Strategy

Overview

ABM is not "send a gift and call it ABM." It's a systematic approach to treating accounts as markets of one — aligned sales and marketing motions against a curated set of target accounts. This skill designs the full ABM program: tier selection, account intelligence, channel orchestration, and measurement.

When to Use

  • "Design our ABM strategy"
  • "Set up account-based marketing"
  • "Build a target account program"
  • "How do we run ABM?"
  • "Account selection for enterprise"

Authoritative Foundations

  • ITSMA ABM Framework — Three tiers of ABM: Strategic (1-to-1), Scale (1-to-few), Programmatic (1-to-many). Each tier has different investment, account count, and personalization depth.
  • TOPO Account-Based Framework — Account selection, insights, plays, metrics. The six roles in an ABM team: ABM lead, account exec, SDR, field marketing, content marketing, marketing ops.
  • Winning by Design Bowtie — ABM lives between marketing (left side) and sales (center), bridging awareness through close and into post-sale expansion.
  • Lars Nilsson — Account-Based Sales Development (ABSD). The SDR execution layer of ABM, created at Cloudera and scaled across 100+ SDRs at Snowflake. Account selection on buying signals (intent surge, job posts, funding) not hunches; SDR + AE + vertical SME co-author 3-email sequences from a use-case library; multi-persona outreach in 50–250 contact chunks; quality of engagement over volume sent (public first-campaign results: ~70% open / ~30% reply vs 5–8% / 2–3% for nurture blasts). Canonical → references/lars-nilsson-absd.md.
  • Sangram Vajre — TEAM and MOVE. Treat account-based work as one GTM motion, not a marketing campaign. TEAM aligns Target, Engage, Activate, and Measure; MOVE diagnoses maturity across Market, Operations, Velocity, and Expansion. Use TEAM to design the account journey and MOVE to identify the operating constraint before adding channels or tools.

Step-by-Step Process

Phase 1: Account Selection

Define the 3-tier account model:

  • Tier 1 (1-to-1): 5-15 accounts. Strategic, $100K+ ACV. Full account intelligence, custom content, executive engagement. C-suite mapping required.
  • Tier 2 (1-to-few): 15-50 accounts. Clustered by industry/use case. Semi-custom campaigns, persona-specific outreach, industry-specific proof points.
  • Tier 3 (1-to-many): 50-200+ accounts. Programmatic. Lookalike from Tier 1-2 wins, automated personalization, scaled outbound.

Selection criteria: ICP fit score (0-100), intent signals (hiring, funding, tech stack), engagement history (website visits, content downloads, event attendance), deal size potential.

Phase 2: Account Intelligence

For each Tier 1/2 account, build an account brief:

  • Company snapshot (revenue, employees, growth, funding)
  • Strategic priorities (earnings calls, annual reports, press)
  • Org chart (decision-maker, champion, economic buyer, influencers, blockers)
  • Tech stack (current tools, gaps, integration points)
  • Relationship map (who knows who, existing connections)
  • Trigger events (new hire, funding, M&A, product launch, earnings miss)
Phase 3: Channel Orchestration

Map channels by tier:

  • Tier 1: Executive mailers, Giftology gifts (strategic-gifting), custom microsites, direct mail, in-person events, executive-to-executive calls
  • Tier 2: Personalized email + LinkedIn, industry roundtables, webinar invites, direct mail, SDR outbound
  • Tier 3: Automated email sequences, LinkedIn ads, content syndication, webinar series, SDR cadences
Phase 4: BDR Alignment

ABM fails without tight sales alignment:

  • BDRs assigned to specific accounts (not territories)
  • Shared account briefs between marketing and BDRs
  • Weekly ABM standups: marketing + BDRs + AEs on target accounts
  • SLAs: contact attempts within 24h of marketing touch

For the full SDR execution layer — signal-based account prioritization, SDR + AE + SME co-authored sequences, multi-persona chunking, and public response benchmarks — run the ABSD playbook: references/lars-nilsson-absd.md.

Phase 5: Measurement Framework

Don't measure ABM on MQLs. Measure:

  • Coverage: % of target accounts with contacts identified
  • Engagement: touches per account per week, depth (C-suite vs end user)
  • Pipeline: opportunities created from target accounts
  • Velocity: days from first touch to opportunity
  • Win rate: target accounts vs non-target
  • Deal size: target account ACV vs non-target

Output Format

ABM strategy document with: tier definitions, account selection criteria and initial list, intelligence template, channel plan by tier, BDR alignment model, measurement dashboard design.

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

  1. 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.
  2. 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.
  3. 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.

Implementation Depth

Use this section when the user asks for a finished asset, not a high-level explanation.

Diagnostic Questions
  1. What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
  2. Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
  3. What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
  4. What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
  5. 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:

  • ITSMA ABM Framework: apply only the part that directly improves the requested deliverable.
  • TOPO Account-Based Framework: apply only the part that directly improves the requested deliverable.
  • WbD Bowtie: apply only the part that directly improves the requested deliverable.
  • John Ruhlin Giftology: apply only the part that directly improves the requested deliverable.
  • Lars Nilsson ABSD: apply only the part that directly improves the requested deliverable.
  • Sangram Vajre TEAM and MOVE: 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.

Execution Artifacts

  • references/framework-notes.md — Named frameworks and reference tables
  • templates/output-template.md — Deliverable shell for agent output
  • scripts/check-output.py — Lightweight deliverable validator
  • references/lars-nilsson-absd.md — Lars Nilsson (Cloudera/Snowflake) ABSD playbook: signal-based selection, SME sequence design, stack, benchmarks
  • abm-1-to-1, abm-1-to-few, abm-1-to-many, account-selection, multi-thread-orchestration
  • icp-scoring, sales-enablement, meeting-prep, pipeline-management, signal-scoring
1---
2name: abm-strategy
3description: >-
4 Designs an account-based marketing program: tier selection, account scoring,
5 channel orchestration, BDR alignment (account-based sales development), and a
6 measurement framework. Use when the user is launching or redesigning ABM,
7 choosing between 1-to-1, 1-to-few, and 1-to-many, or building a target account
8 program. Triggers on: "ABM strategy", "account based marketing", "ABM
9 playbook", "design ABM", "target accounts", "ABSD", "account based sales
10 development", "Lars Nilsson".
11license: MIT
12compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
13metadata:
14 version: "1.2.0"
15 author: LeadMagic
16 category: abm
17 tags: [abm, account-based-marketing, target-accounts, enterprise, b2b, absd]
18 frameworks: [ITSMA ABM Framework, TOPO Account-Based Framework, WbD Bowtie, John Ruhlin Giftology, Sendoso Sending Platform, "Lars Nilsson (Cloudera/Snowflake) — Account-Based Sales Development (ABSD)", "Sangram Vajre — TEAM account-based GTM and MOVE maturity model"]
19---
20 
21# ABM Strategy
22 
23## Overview
24ABM is not "send a gift and call it ABM." It's a systematic approach to treating
25accounts as markets of one — aligned sales and marketing motions against a curated
26set of target accounts. This skill designs the full ABM program: tier selection,
27account intelligence, channel orchestration, and measurement.
28 
29## When to Use
30- "Design our ABM strategy"
31- "Set up account-based marketing"
32- "Build a target account program"
33- "How do we run ABM?"
34- "Account selection for enterprise"
35 
36## Authoritative Foundations
37- **ITSMA ABM Framework** — Three tiers of ABM: Strategic (1-to-1), Scale (1-to-few),
38 Programmatic (1-to-many). Each tier has different investment, account count, and
39 personalization depth.
40- **TOPO Account-Based Framework** — Account selection, insights, plays, metrics.
41 The six roles in an ABM team: ABM lead, account exec, SDR, field marketing,
42 content marketing, marketing ops.
43- **Winning by Design Bowtie** — ABM lives between marketing (left side) and sales
44 (center), bridging awareness through close and into post-sale expansion.
45- **Lars Nilsson — Account-Based Sales Development (ABSD).** The SDR execution layer
46 of ABM, created at Cloudera and scaled across 100+ SDRs at Snowflake. Account
47 selection on **buying signals** (intent surge, job posts, funding) not hunches;
48 SDR + AE + vertical SME co-author 3-email sequences from a use-case library;
49 multi-persona outreach in 50–250 contact chunks; quality of engagement over
50 volume sent (public first-campaign results: ~70% open / ~30% reply vs 5–8% / 2–3%
51 for nurture blasts). Canonical → `references/lars-nilsson-absd.md`.
52- **Sangram Vajre — TEAM and MOVE.** Treat account-based work as one GTM motion,
53 not a marketing campaign. TEAM aligns Target, Engage, Activate, and Measure;
54 MOVE diagnoses maturity across Market, Operations, Velocity, and Expansion.
55 Use TEAM to design the account journey and MOVE to identify the operating
56 constraint before adding channels or tools.
57 
58## Step-by-Step Process
59 
60### Phase 1: Account Selection
61Define the 3-tier account model:
62- **Tier 1 (1-to-1):** 5-15 accounts. Strategic, $100K+ ACV. Full account intelligence,
63 custom content, executive engagement. C-suite mapping required.
64- **Tier 2 (1-to-few):** 15-50 accounts. Clustered by industry/use case. Semi-custom
65 campaigns, persona-specific outreach, industry-specific proof points.
66- **Tier 3 (1-to-many):** 50-200+ accounts. Programmatic. Lookalike from Tier 1-2 wins,
67 automated personalization, scaled outbound.
68 
69Selection criteria: ICP fit score (0-100), intent signals (hiring, funding, tech stack),
70engagement history (website visits, content downloads, event attendance), deal size potential.
71 
72### Phase 2: Account Intelligence
73For each Tier 1/2 account, build an account brief:
74- Company snapshot (revenue, employees, growth, funding)
75- Strategic priorities (earnings calls, annual reports, press)
76- Org chart (decision-maker, champion, economic buyer, influencers, blockers)
77- Tech stack (current tools, gaps, integration points)
78- Relationship map (who knows who, existing connections)
79- Trigger events (new hire, funding, M&A, product launch, earnings miss)
80 
81### Phase 3: Channel Orchestration
82Map channels by tier:
83- **Tier 1:** Executive mailers, Giftology gifts (`strategic-gifting`), custom microsites,
84 direct mail, in-person events, executive-to-executive calls
85- **Tier 2:** Personalized email + LinkedIn, industry roundtables, webinar invites,
86 direct mail, SDR outbound
87- **Tier 3:** Automated email sequences, LinkedIn ads, content syndication,
88 webinar series, SDR cadences
89 
90### Phase 4: BDR Alignment
91ABM fails without tight sales alignment:
92- BDRs assigned to specific accounts (not territories)
93- Shared account briefs between marketing and BDRs
94- Weekly ABM standups: marketing + BDRs + AEs on target accounts
95- SLAs: contact attempts within 24h of marketing touch
96 
97For the full SDR execution layer — signal-based account prioritization, SDR + AE +
98SME co-authored sequences, multi-persona chunking, and public response benchmarks —
99run the ABSD playbook: `references/lars-nilsson-absd.md`.
100 
101### Phase 5: Measurement Framework
102Don't measure ABM on MQLs. Measure:
103- **Coverage:** % of target accounts with contacts identified
104- **Engagement:** touches per account per week, depth (C-suite vs end user)
105- **Pipeline:** opportunities created from target accounts
106- **Velocity:** days from first touch to opportunity
107- **Win rate:** target accounts vs non-target
108- **Deal size:** target account ACV vs non-target
109 
110## Output Format
111ABM strategy document with: tier definitions, account selection criteria and initial
112list, intelligence template, channel plan by tier, BDR alignment model, measurement
113dashboard design.
114 
115 
116 
117## Quality Check
118 
119Before delivering, verify:
120- [ ] All required sections are complete
121- [ ] Output matches the user's stated need
122- [ ] Named frameworks are cited for key recommendations
123- [ ] No vague claims — every recommendation has a specific action
124- [ ] Deliverable is ready for operational use, not just conceptual
125 
126## Common Pitfalls
127 
1281. **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.
1292. **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.
1303. **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.
131 
132## Implementation Depth
133 
134Use this section when the user asks for a finished asset, not a high-level explanation.
135 
136### Diagnostic Questions
137 
1381. What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
1392. Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
1403. What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
1414. What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
1425. What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
143 
144### Framework Application
145 
146Map the recommendation explicitly to the named frameworks in this skill:
147 
148- ITSMA ABM Framework: apply only the part that directly improves the requested deliverable.
149- TOPO Account-Based Framework: apply only the part that directly improves the requested deliverable.
150- WbD Bowtie: apply only the part that directly improves the requested deliverable.
151- John Ruhlin Giftology: apply only the part that directly improves the requested deliverable.
152- Lars Nilsson ABSD: apply only the part that directly improves the requested deliverable.
153- Sangram Vajre TEAM and MOVE: apply only the part that directly improves the requested deliverable.
154 
155### Deliverable Standard
156 
157A strong output from this skill includes:
158 
159- A crisp diagnosis of the current situation
160- A recommended path with tradeoffs, not a generic list
161- A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
162- A measurement plan with leading and lagging indicators
163- Risks and edge cases called out before execution
164 
165### Adaptation Rules
166 
167- For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
168- For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
169- For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
170 
171 
172## Execution Artifacts
173 
174- `references/framework-notes.md` — Named frameworks and reference tables
175- `templates/output-template.md` — Deliverable shell for agent output
176- `scripts/check-output.py` — Lightweight deliverable validator
177- `references/lars-nilsson-absd.md` — Lars Nilsson (Cloudera/Snowflake) ABSD playbook: signal-based selection, SME sequence design, stack, benchmarks
178 
179## Related Skills
180- abm-1-to-1, abm-1-to-few, abm-1-to-many, account-selection, multi-thread-orchestration
181- icp-scoring, sales-enablement, meeting-prep, pipeline-management, signal-scoring
182 

Discussion

Alternatives