Systems Lab

Agent skill

abm-playbook

Account-Based Marketing playbook builder - tiered account list (1:1, 1:few, 1:many), buying-group mapping, coordinated multi-channel plays per account, and pipeline acceleration plays for in-cycle accounts.

slowingSelf-containedInstructions only968 words

Filed under ABM and paid and Team and enablement.

From varunk130/ai-gtm-skill-library · 31 skills · 5 · pushed 2026-07-31

What it does when it runs

Account-Based Marketing playbook builder - tiered account list (1:1, 1:few, 1:many), buying-group mapping, coordinated multi-channel plays per account, and pipeline acceleration plays for in-cycle accounts. Use when: ABM playbook, account-based marketing, target account list, tiered accounts, 1:1 marketing, buying group, named-account strategy, ABM plays, pipeline acceleration, in-cycle account acceleration.

Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about abm-playbook

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/varunk130/ai-gtm-skill-library.git /tmp/ai-gtm-skill-library
git -C /tmp/ai-gtm-skill-library sparse-checkout set "gtm-skills/abm-playbook"
mkdir -p ~/.claude/skills/abm-playbook
cp -R "/tmp/ai-gtm-skill-library/gtm-skills/abm-playbook/." ~/.claude/skills/abm-playbook/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from varunk130/ai-gtm-skill-library/blob/90e878c73a8fbfd1cab864424ccf674fdc889157/gtm-skills/abm-playbook/SKILL.md, which is licensed MIT (repository). 968 words, 12 headings.

ABM Playbook (TIER Framework)

Build a complete Account-Based Marketing playbook - tiered account list, buying-group map per tier, coordinated multi-channel plays, and pipeline acceleration plays for accounts already in cycle. ABM is structurally different from PLG, sales-led, and channel motions; this skill captures that difference rather than bolting it onto a generic GTM template.

Core Principle

ABM is a coordination problem, not a targeting problem. Most failed ABM programs pick the right accounts and then run the same demand-gen plays they always did. The TIER framework forces explicit coordination across channels and across tiers, with different play patterns for different account intimacy levels.

The TIER Framework

LetterStageThe Question
TTier the AccountsWhich accounts get 1:1, which get 1:few, which get 1:many?
IIdentify the Buying GroupWho are the personas in each account, and what's each one's win condition?
EExecute Coordinated PlaysWhat multi-channel plays run per account (not per persona)?
RRe-route on SignalWhen an account hits an in-cycle signal, which acceleration play activates?

Account Tiering

TierAccount CountInvestment per AccountPersonalizationSignal Cadence
1:15-25High (custom content, exec engagement, dedicated SDR)Per-account creativeWeekly
1:few25-150Medium (cluster-level personalization, named SDR pod)Per-cluster (3-8 accounts share)Bi-weekly
1:many150-2000Low (scaled programs with industry/persona personalization)Per-segment creativeMonthly

Buying Group Mapping

Every targeted account has a buying group, not a single buyer. The skill enforces explicit mapping:

RoleWin ConditionCommon Title Patterns
ChampionPersonal outcome (career capital, problem solved)Director / Sr. Manager in problem domain
Economic BuyerBusiness outcome (revenue, cost, risk)VP / SVP, CFO
Technical EvaluatorRisk reduction (architecture, security, fit)Sr. Engineer / Architect / IT Director
End UserDay-to-day usabilityIndividual contributors
Procurement / LegalCompliance, terms, pricing postureProcurement, Legal, Security

A play that engages only the Champion fails because the deal stalls at Economic Buyer or Procurement. The skill enforces multi-role engagement design.

Output

Save to outputs/abm-playbook-[motion]-[YYYY-MM-DD].md

ArtifactDescription
Tiered Account ListAccount names + tier assignment + rationale
Buying Group MapsPer-account (1:1) or per-cluster (1:few) with named roles + engagement state
Play Library6-10 named plays, each tagged by tier + buying-group role + channel mix
Acceleration Plays3-5 plays triggered by in-cycle signals
Coordination CalendarWeekly view across all channels per tier - catches over- and under-engagement
Measurement PlanPer-tier KPIs: account-level engagement, opportunity creation, pipeline velocity, win rate

The Play Library Pattern

Every play follows this structure:

FieldExample
Name"Exec-to-Exec Insight Letter"
TriggerNew 1:1 account assigned, or champion change
Roles EngagedEconomic Buyer, Champion
ChannelsLinkedIn (exec), Email (champion), Direct mail (exec)
SequenceDay 0 LI connect → Day 3 letter delivered → Day 5 champion email → Day 14 ABR follow-up
Personalization LevelPer-account (researched insight specific to stated priorities)
Success SignalExec response or champion-confirmed read
Hand-offSignal → SDR books exec briefing; no signal in 21 days → re-route

Acceleration Play Triggers

SignalAcceleration Play
Intent surge (3rd-party)Account-level ad burst + SDR re-engagement within 48h
Pricing-page or competitor-comparison hitInbound BDR call within 1 business day, deal-context-aware script
Security questionnaire receivedPre-built security artifact pack + named SE engagement
Deal stalled > 21 days in stageChampion enablement kit + multi-thread to EB + Procurement
Champion changes role / leaves"Land the new champion" play within 1 week of signal

Process

  1. Tier the accounts with explicit rationale per tier; cut accounts that don't justify any tier
  2. Map buying groups - full named mapping for 1:1, role patterns for 1:few, persona-level for 1:many
  3. Build the play library - 6-10 plays covering cold start through expansion; every play names a role
  4. Design acceleration plays for each in-cycle signal - trade scale for speed
  5. Build the coordination calendar - weekly view to catch over- and under-engagement
  6. Define per-tier measurement with ABM-friendly metrics (lead-level MQLs are not the right yardstick)

Per-Tier Measurement

TierPrimary KPISecondary KPIs
1:1Pipeline created per accountAccount engagement score, EB meetings booked, deal velocity
1:fewPipeline created per clusterCluster engagement rate, opportunity conversion
1:manyPipeline created per programAccount engagement coverage, MQA rate

Tips

  1. Tier with rationale, not gut feel - every 1:1 is an investment commitment
  2. Plays are per-account, not per-channel - channel-led ABM almost always over-engages
  3. Acceleration > acquisition - in-cycle accounts are 5-10× more efficient than cold ABM
  4. Re-tier quarterly - accounts that don't engage in 1:1 for 2 quarters drop to 1:few
  5. Pair with intent scoring + channel orchestration - ABM consumes those outputs

Pairs With

  • journey-architect - Maps the buyer journey; ABM coordinates above it
  • demand-engine - Channel-level orchestration the calendar consumes
  • enablement-forge - Produces the assets each play needs
  • competitive-battlecard - Per-deal cards that drop into in-cycle acceleration

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what abm-playbook does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.