Upsell Strategy Coach

Expansion selling

by LeadMagic · MIT license · ★ 62 on GitHub

Expansion selling cover

Complete expansion and upsell playbook for B2B SaaS — consumption-based upsell triggers, cross-sell identification, seat expansion, tier upgrades, NRR growth strategies, land-and-expand motions, expansion propensity scoring, and…

---
name: expansion-selling
description: >-
  Complete expansion and upsell playbook for B2B SaaS — consumption-based
  upsell triggers, cross-sell identification, seat expansion, tier upgrades,
  NRR growth strategies, land-and-expand motions, expansion propensity scoring,
  and measuring expansion revenue. Use when designing expansion motions,
  identifying upsell opportunities, or growing NRR. Triggers on: "expansion
  selling", "upsell strategy", "NRR growth", "land and expand", "cross-sell",
  "expansion revenue", "seat expansion".
license: MIT
compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
metadata:
  version: "2.1.0"
  author: LeadMagic
  category: growth
  tags: [expansion, upsell, cross-sell, nrr, land-expand, revenue-growth]
  related_skills: [churn-prevention, cs-playbooks, cs-analytics-dashboards, pricing-strategy, customer-onboarding, saas-metrics-calculator, saas-outcomes]

Overview

The most profitable revenue doesn't come from new customers — it comes from existing ones. New customer acquisition costs 5-7x more than expanding an existing account. Yet most companies treat expansion as an afterthought. The mistake: waiting for customers to ask for more instead of systematically identifying and executing expansion opportunities. This skill covers the complete expansion playbook: triggers, scoring, execution, and measurement.

Manual install (npx, ZIP)
Claude Codenpx skills add LeadMagic/gtm-skills --skill expansion-selling -g -a claude-code
Claude Code (degit)npx degit LeadMagic/gtm-skills/skills/growth/expansion-selling#main ~/.claude/skills/expansion-selling
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md10.0 KB
Read SKILL.md here
LeadMagic/main1 file shown
SKILL.md
Show the full text205 lines

Expansion Selling

Overview

The most profitable revenue doesn't come from new customers — it comes from existing ones. New customer acquisition costs 5-7x more than expanding an existing account. Yet most companies treat expansion as an afterthought. The mistake: waiting for customers to ask for more instead of systematically identifying and executing expansion opportunities. This skill covers the complete expansion playbook: triggers, scoring, execution, and measurement.

Frameworks Referenced

  • Winning by Design — Bowtie Funnel — Post-sale expansion as revenue system
  • Jason Lemkin (SaaStr) — NRR drives exit multiples (PE/strategic)
  • Marc Benioff — Land-and-expand enterprise motion
  • Randy Seidl — Relationship-led expansion: map stakeholders beyond the original champion; score trust before upsell. Load sales-coaching → references/randy-seidl-relationship-selling.md. Complements Benioff CRM land-expand structure (crm-toolkit → land-expand-account-plan).
  • Snowflake consumption model (Slootman, Degnan). Land with paid pilot (low ACV entry); expand via use cases tracked in CRM; rep comp on booking and consumption so hit-and-run deals are penalized. Slootman aligned entire exec team to usage metrics. See gtm-leadership/references/cro-enterprise-strategy.md.
  • Databricks DBU expansion. Revenue grows with data volume and query analysis — expansion triggers are workload adoption, not seat adds. Technical sellers drive POC → production workloads. Gabrisko: structure field vs inside by ACV and buyer complexity.

When to Use

Trigger phrases: "expansion strategy", "upsell playbook", "NRR growth", "land and expand", "cross-sell identification", "seat expansion triggers", "tier upgrade strategy", "expansion revenue playbook"

Expansion Triggers (Ranked by Conversion Rate)

Trigger Signal Conversion Rate Action
Usage approaching limit "You've used 85% of your plan" 25-35% Proactive upgrade offer + migration support
Feature request for higher tier "Can we get SSO?" 40-60% "That's in Growth tier. Here's an instant upgrade path."
Multi-team adoption Multiple departments using product 20-30% Enterprise upsell with centralized billing
New hire at customer Customer adds headcount 15-25% Seat expansion + training for new team
QBR uncovers new use case Customer articulates expansion use case 30-50% Proposal within 1 week of QBR
Champion requests API access Building on your platform 50%+ Platform/Enterprise tier with API + support
Positive NPS + healthy usage Happy, active customer 15-25% Case study ask, then expansion conversation

Step-by-Step Process

Phase 1: Identify Expansion Opportunities

Expansion Propensity Score:

Score = (Usage approaching limit: +30) +
        (Multi-team adoption: +25) +
        (Requested higher-tier feature: +25) +
        (NPS Promoter: +10) +
        (QBR attendance: +10)

Score > 70: Expansion playbook NOW
Score 40-69: Nurture — showcase advanced features
Score < 40: Focus on adoption before expansion
Phase 2: Expansion Plays

Play 1: Seat Expansion

  • Trigger: Customer adds team members. Usage per seat increasing.
  • Play: "Your team has grown. 5 new team members will benefit from [product]. Here's a prorated seat expansion for this month."
  • Economics: ACV increases linearly with seats. Simple. Predictable.

Play 2: Tier Upgrade

  • Trigger: Customer requests feature in higher tier, or usage exceeds plan limits.
  • Play: "All the features you've asked for are in Growth. Here's a side-by-side of what you get. First month at current rate to make the transition easy."
  • Economics: ARPU increases. Margin typically improves at higher tiers.

Play 3: Cross-Sell

  • Trigger: Customer buys Product A. Complementary Product B solves adjacent need.
  • Play: "Customers who use [Product A] typically add [Product B] within 6 months. Here's how they work together. Bundled pricing for existing customers."
  • Economics: New product line revenue without new logo acquisition cost.

Play 4: Enterprise Expansion

  • Trigger: Multi-team usage, SSO request, API access, security review.
  • Play: Enterprise tier with dedicated CSM, SSO, API access, custom SLA, volume pricing. "You've outgrown self-serve. Here's the enterprise experience."
  • Economics: 3-10x ACV increase. Stickier customer. Higher retention.
Phase 3: Expansion Economics

NRR Formula: NRR = (Starting MRR + Expansion - Contraction - Churn) / Starting MRR

Target NRR by stage (reconcile with references/benchmark-reconciliation.md):

  • Seed: 100%+ (aspirational)
  • Series A: 105%+
  • Series B: 110%+
  • Growth: 115%+
  • Public-company comp (Meritech): median ~108–111%; leaders 120%+

Flywheel note (Dharmesh Shah / HubSpot): Expansion + advocacy = Delight stage fuel. See references/dharmesh-shah-hubspot-inbound.md.

Expansion as % of New Revenue: Best-in-class SaaS: 30-40% of net new ARR comes from expansion Median SaaS: 15-25%

Phase 4: Expansion Playbook Execution

CSM expansion cadence:

  • Month 1-2: Onboarding. No expansion talk. Deliver value first.
  • Month 3: Identify expansion triggers. Document use cases.
  • Month 4-6: First expansion conversation. Plant the seed.
  • Month 6-12: Execute expansion. Close upgrade or cross-sell.

Implementation Checklist

  • Expansion triggers automated (usage approaching limit = alert)
  • Expansion propensity scored for every account
  • NRR tracked monthly with target by customer segment
  • CSM comp tied to NRR (not just retention)
  • Expansion plays documented for each trigger type

Common Pitfalls

  1. Expanding too early. Asking for upsell during onboarding = churn risk. Fix: Deliver value first. Expand after month 3+.
  2. No expansion comp for CSMs. CSMs comped on retention only = no expansion. Fix: Variable comp tied to NRR. 50% base, 50% variable on NRR target.
  3. Missing consumption triggers. Customer usage spikes. Nobody notices. Fix: Automated alerts when usage hits 80% of plan limit.
  4. One-size expansion play. Seat expansion for every customer ignores cross-sell and tier upgrade opportunities. Fix: Multiple playbooks.

Output Format

Expansion playbook containing: (1) expansion propensity score formula with threshold bands (expand now / nurture / focus on adoption) applied to the target account set; (2) trigger table — each expansion signal mapped to the corresponding play, conversion rate benchmark, and recommended action with timing; (3) NRR formula with stage-appropriate targets (Seed through Growth) and expansion-as-percentage-of-new-ARR benchmarks; (4) four named expansion plays (Seat Expansion, Tier Upgrade, Cross-Sell, Enterprise Expansion) with trigger conditions, talk-track outline, and economics per play; (5) CSM expansion cadence by month (1-2 onboarding, 3 trigger identification, 4-6 first conversation, 6-12 close); (6) implementation checklist with automated trigger alerts, comp structure tied to NRR, and monthly measurement cadence.

Quality Check

Before delivering, verify:

  • All required sections complete
  • Output matches the user's stated need
  • No vague or unsupported claims
  • Frameworks cited where applicable

Execution Artifacts

  • references/framework-notes.md — Bowtie expansion, propensity score, NRR benchmarks
  • templates/output-template.md — Deliverable shell for agent output
  • scripts/check-output.py — Lightweight deliverable validator
  • references/cro-enterprise-strategy.md — Snowflake consumption + Databricks workload expansion (Pattern 31)
  • sales-coaching/references/randy-seidl-relationship-selling.md — Stakeholder trust map for expansion (canonical) Lifecycle (Revenue stage): references/gtm-lifecycle-stages.md · references/lifecycle-skill-index.md · Pattern 18 in using-gtm-skills
    Cross-skill: saas-metrics-calculator/references/metric-definitions-exit-weight.md (NRR exit weight) · references/saas-metrics-reference.md Canonical lifecycle: references/gtm-lifecycle-stages.md (Revenue) · references/lifecycle-metrics-by-stage.md · the gtm-metrics skill (stage-health-scorecard.md)
  • churn-prevention — Retention is the foundation of expansion
  • cs-playbooks — Customer success framework
  • cs-analytics-dashboards — Health scores, expansion propensity
  • pricing-strategy — Tier design that enables expansion
  • customer-onboarding — Onboarding that sets up expansion
1---
2name: expansion-selling
3description: >-
4 Complete expansion and upsell playbook for B2B SaaS — consumption-based
5 upsell triggers, cross-sell identification, seat expansion, tier upgrades,
6 NRR growth strategies, land-and-expand motions, expansion propensity scoring,
7 and measuring expansion revenue. Use when designing expansion motions,
8 identifying upsell opportunities, or growing NRR. Triggers on: "expansion
9 selling", "upsell strategy", "NRR growth", "land and expand", "cross-sell",
10 "expansion revenue", "seat expansion".
11license: MIT
12compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
13metadata:
14 version: "2.1.0"
15 author: LeadMagic
16 category: growth
17 tags: [expansion, upsell, cross-sell, nrr, land-expand, revenue-growth]
18 related_skills: [churn-prevention, cs-playbooks, cs-analytics-dashboards, pricing-strategy, customer-onboarding, saas-metrics-calculator, saas-outcomes]
19 frameworks:
20 - "Winning by Design — Bowtie Funnel (post-sale expansion)"
21 - "Reforge — Expansion Revenue and Product-Qualified Accounts"
22 - "Gainsight — Expansion Selling Framework"
23 - "Jason Lemkin (SaaStr) — NRR as the ultimate SaaS metric"
24 - "Marc Benioff — Land-and-expand enterprise motion"
25 - "Randy Seidl (Sales Community) — Relationship-led expansion, stakeholder trust"
26 - "Frank Slootman / Snowflake — Consumption land-expand, use-case tracking, rep usage incentive"
27 - "Databricks — DBU consumption expansion, workload-based growth"
28---
29 
30# Expansion Selling
31 
32## Overview
33 
34The most profitable revenue doesn't come from new customers — it comes from
35existing ones. New customer acquisition costs 5-7x more than expanding an
36existing account. Yet most companies treat expansion as an afterthought. The
37mistake: waiting for customers to ask for more instead of systematically
38identifying and executing expansion opportunities. This skill covers the
39complete expansion playbook: triggers, scoring, execution, and measurement.
40 
41## Frameworks Referenced
42 
43- **Winning by Design — Bowtie Funnel** — Post-sale expansion as revenue system
44- **Jason Lemkin (SaaStr)** — NRR drives exit multiples (PE/strategic)
45- **Marc Benioff** — Land-and-expand enterprise motion
46- **Randy Seidl** — Relationship-led expansion: map stakeholders beyond the
47 original champion; score trust before upsell. Load `sales-coaching` →
48 `references/randy-seidl-relationship-selling.md`. Complements Benioff CRM
49 land-expand structure (`crm-toolkit` → land-expand-account-plan).
50- **Snowflake consumption model (Slootman, Degnan).** Land with **paid pilot**
51 (low ACV entry); expand via **use cases** tracked in CRM; rep comp on booking
52 **and** consumption so hit-and-run deals are penalized. Slootman aligned entire
53 exec team to usage metrics. See `gtm-leadership/references/cro-enterprise-strategy.md`.
54- **Databricks DBU expansion.** Revenue grows with data volume and query
55 analysis — expansion triggers are **workload adoption**, not seat adds.
56 Technical sellers drive POC → production workloads. Gabrisko: structure field
57 vs inside by ACV and buyer complexity.
58 
59## When to Use
60 
61Trigger phrases: "expansion strategy", "upsell playbook", "NRR growth",
62"land and expand", "cross-sell identification", "seat expansion triggers",
63"tier upgrade strategy", "expansion revenue playbook"
64 
65## Expansion Triggers (Ranked by Conversion Rate)
66 
67| Trigger | Signal | Conversion Rate | Action |
68|---|---|---|---|
69| Usage approaching limit | "You've used 85% of your plan" | 25-35% | Proactive upgrade offer + migration support |
70| Feature request for higher tier | "Can we get SSO?" | 40-60% | "That's in Growth tier. Here's an instant upgrade path." |
71| Multi-team adoption | Multiple departments using product | 20-30% | Enterprise upsell with centralized billing |
72| New hire at customer | Customer adds headcount | 15-25% | Seat expansion + training for new team |
73| QBR uncovers new use case | Customer articulates expansion use case | 30-50% | Proposal within 1 week of QBR |
74| Champion requests API access | Building on your platform | 50%+ | Platform/Enterprise tier with API + support |
75| Positive NPS + healthy usage | Happy, active customer | 15-25% | Case study ask, then expansion conversation |
76 
77## Step-by-Step Process
78 
79### Phase 1: Identify Expansion Opportunities
80 
81**Expansion Propensity Score:**
82```
83Score = (Usage approaching limit: +30) +
84 (Multi-team adoption: +25) +
85 (Requested higher-tier feature: +25) +
86 (NPS Promoter: +10) +
87 (QBR attendance: +10)
88 
89Score > 70: Expansion playbook NOW
90Score 40-69: Nurture — showcase advanced features
91Score < 40: Focus on adoption before expansion
92```
93 
94### Phase 2: Expansion Plays
95 
96**Play 1: Seat Expansion**
97- Trigger: Customer adds team members. Usage per seat increasing.
98- Play: "Your team has grown. 5 new team members will benefit from [product].
99 Here's a prorated seat expansion for this month."
100- Economics: ACV increases linearly with seats. Simple. Predictable.
101 
102**Play 2: Tier Upgrade**
103- Trigger: Customer requests feature in higher tier, or usage exceeds plan limits.
104- Play: "All the features you've asked for are in Growth. Here's a side-by-side
105 of what you get. First month at current rate to make the transition easy."
106- Economics: ARPU increases. Margin typically improves at higher tiers.
107 
108**Play 3: Cross-Sell**
109- Trigger: Customer buys Product A. Complementary Product B solves adjacent need.
110- Play: "Customers who use [Product A] typically add [Product B] within 6 months.
111 Here's how they work together. Bundled pricing for existing customers."
112- Economics: New product line revenue without new logo acquisition cost.
113 
114**Play 4: Enterprise Expansion**
115- Trigger: Multi-team usage, SSO request, API access, security review.
116- Play: Enterprise tier with dedicated CSM, SSO, API access, custom SLA, volume
117 pricing. "You've outgrown self-serve. Here's the enterprise experience."
118- Economics: 3-10x ACV increase. Stickier customer. Higher retention.
119 
120### Phase 3: Expansion Economics
121 
122**NRR Formula:**
123NRR = (Starting MRR + Expansion - Contraction - Churn) / Starting MRR
124 
125**Target NRR by stage** (reconcile with `references/benchmark-reconciliation.md`):
126- Seed: 100%+ (aspirational)
127- Series A: 105%+
128- Series B: 110%+
129- Growth: 115%+
130- Public-company comp (Meritech): median ~108–111%; leaders 120%+
131 
132**Flywheel note (Dharmesh Shah / HubSpot):** Expansion + advocacy = Delight stage fuel. See `references/dharmesh-shah-hubspot-inbound.md`.
133 
134**Expansion as % of New Revenue:**
135Best-in-class SaaS: 30-40% of net new ARR comes from expansion
136Median SaaS: 15-25%
137 
138### Phase 4: Expansion Playbook Execution
139 
140**CSM expansion cadence:**
141- Month 1-2: Onboarding. No expansion talk. Deliver value first.
142- Month 3: Identify expansion triggers. Document use cases.
143- Month 4-6: First expansion conversation. Plant the seed.
144- Month 6-12: Execute expansion. Close upgrade or cross-sell.
145 
146## Implementation Checklist
147 
148- [ ] Expansion triggers automated (usage approaching limit = alert)
149- [ ] Expansion propensity scored for every account
150- [ ] NRR tracked monthly with target by customer segment
151- [ ] CSM comp tied to NRR (not just retention)
152- [ ] Expansion plays documented for each trigger type
153 
154## Common Pitfalls
155 
1561. **Expanding too early.** Asking for upsell during onboarding = churn risk.
157 Fix: Deliver value first. Expand after month 3+.
1582. **No expansion comp for CSMs.** CSMs comped on retention only = no expansion.
159 Fix: Variable comp tied to NRR. 50% base, 50% variable on NRR target.
1603. **Missing consumption triggers.** Customer usage spikes. Nobody notices.
161 Fix: Automated alerts when usage hits 80% of plan limit.
1624. **One-size expansion play.** Seat expansion for every customer ignores
163 cross-sell and tier upgrade opportunities. Fix: Multiple playbooks.
164 
165 
166## Output Format
167 
168Expansion playbook containing: (1) expansion propensity score formula with
169threshold bands (expand now / nurture / focus on adoption) applied to the
170target account set; (2) trigger table — each expansion signal mapped to the
171corresponding play, conversion rate benchmark, and recommended action with
172timing; (3) NRR formula with stage-appropriate targets (Seed through Growth)
173and expansion-as-percentage-of-new-ARR benchmarks; (4) four named expansion
174plays (Seat Expansion, Tier Upgrade, Cross-Sell, Enterprise Expansion) with
175trigger conditions, talk-track outline, and economics per play; (5) CSM
176expansion cadence by month (1-2 onboarding, 3 trigger identification, 4-6
177first conversation, 6-12 close); (6) implementation checklist with automated
178trigger alerts, comp structure tied to NRR, and monthly measurement cadence.
179 
180## Quality Check
181 
182Before delivering, verify:
183- [ ] All required sections complete
184- [ ] Output matches the user's stated need
185- [ ] No vague or unsupported claims
186- [ ] Frameworks cited where applicable
187 
188## Execution Artifacts
189 
190- `references/framework-notes.md` — Bowtie expansion, propensity score, NRR benchmarks
191- `templates/output-template.md` — Deliverable shell for agent output
192- `scripts/check-output.py` — Lightweight deliverable validator
193- `references/cro-enterprise-strategy.md` — Snowflake consumption + Databricks workload expansion (Pattern 31)
194- `sales-coaching/references/randy-seidl-relationship-selling.md` — Stakeholder trust map for expansion (canonical)
195**Lifecycle (Revenue stage):** `references/gtm-lifecycle-stages.md` · `references/lifecycle-skill-index.md` · Pattern 18 in `using-gtm-skills`
196**Cross-skill:** `saas-metrics-calculator/references/metric-definitions-exit-weight.md` (NRR exit weight) · `references/saas-metrics-reference.md`
197**Canonical lifecycle:** `references/gtm-lifecycle-stages.md` (Revenue) · `references/lifecycle-metrics-by-stage.md` · the `gtm-metrics` skill (stage-health-scorecard.md)
198 
199## Related Skills
200 
201- `churn-prevention` — Retention is the foundation of expansion
202- `cs-playbooks` — Customer success framework
203- `cs-analytics-dashboards` — Health scores, expansion propensity
204- `pricing-strategy` — Tier design that enables expansion
205- `customer-onboarding` — Onboarding that sets up expansion
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 62
Checked
Source
LeadMagic/gtm-skills ↗
Creator
LeadMagic · 129 listings
View creator

Similar skills

See all →
SkillMobile App Pricing Advisorappeeky/aso-skills · by appeekyWhen the user wants to design or optimize their app's monetization — pricing, paywalls, subscriptions, or in-app purchases. Also use when the user mentions "pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", or "conversion to paid". For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.★ 2.2k GitHub starsSkillPaywall Optimization Specialistappeeky/aso-skills · by appeekyWhen the user wants to design, test, or optimize their app's paywall — layout, copy, pricing display, trial offers, plan structure, hard vs soft paywall, paywall placement, or paywall A/B tests. Use when the user mentions "paywall", "paywall design", "paywall conversion", "trial-to-paid", "soft paywall", "hard paywall", "paywall A/B test", "paywall copy", "plan picker", "annual vs monthly display", "best paywall", "RevenueCat paywall", "Superwall", "Adapty", or "my paywall isn't converting". For overall pricing strategy and monetization model choice, see monetization-strategy. For trial nurture, dunning, and churn, see subscription-lifecycle. For where in the onboarding the paywall fires, see onboarding-optimization.★ 2.2k GitHub starsSkillPricing and Packagingcbrock84/headcount · by cbrock84Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction. Use this to set or change pricing, design or restructure tiers, choose a pricing metric, build an offer, design upgrade prompts and paywalls, or evaluate whether a pricing change is safe to make.★ 2k GitHub starsSkillWillingness-to-Pay AnalyzerRefoundAI/lenny-skills · by RefoundAIHelp users validate willingness-to-pay, select the right value metrics, and continuously optimize pricing and packaging to drive growth.★ 1.4k GitHub starsSkill100M Money Modelsgetagentseal/founder-playbook · by getagentsealDesigns a deliberate sequence of offers (attraction, upsell, downsell, continuity) so a new customer generates enough cash within ~30 days to fund acquiring the next one - Alex Hormozi's client-financed acquisition. Use when customers buy once and never again, when CAC eats all the profit, when you can't afford to advertise profitably, when the business grows but cash shrinks, when you sell one product at one price, when deciding what to sell first or next, or when structuring upsells, downsells, payment plans, trials, and continuity. Covers the 30-day payback rule, attraction/upsell/downsell/continuity offer types, and cash-flow sequencing for validated markets.★ 729 GitHub starsSkillGrand Slam Offer Designergetagentseal/founder-playbook · by getagentsealDesigns irresistible Grand Slam Offers using Alex Hormozi's value equation, obstacle-solution mapping, value-cost trim/stack, and offer-naming patterns. Use when fixing low conversion rates, packaging products, pricing services, designing high-converting offers, or when prospects browse but don't buy. Covers value stacking, guarantees, scarcity, urgency, and pricing psychology for validated markets.★ 729 GitHub stars

More from LeadMagic

SkillFirst-Party Analytics SetupLeadMagic/gtm-skills · by LeadMagicSet up first-party tracking and analytics — website pixels, conversion tracking, UTM architecture, cookie consent, server-side tagging vs client-side, 1P vs 3P data strategy, and identity resolution. Use when setting up tracking, implementing pixels, building attribution, or preparing for privacy-first measurement. Triggers on: "pixel", "tracking", "conversion tracking", "first-party data", server-side tagging", "UTM", "cookie consent", "1P vs 3P", "identity resolution", or any tracking implementation request.★ 62 GitHub starsSkillStrategic Account MarketingLeadMagic/gtm-skills · by LeadMagicRuns strategic 1-to-1 ABM for 5-15 high-value accounts: account plans, custom microsites, executive engagement, direct mail, and board-level connections. Use when a named enterprise account justifies bespoke content and executive time, or when the user needs a strategic account plan. Triggers on: "1-to-1 ABM", "strategic ABM", "custom ABM", "key account marketing", "named account".★ 62 GitHub starsSkillCluster Account MarketingLeadMagic/gtm-skills · by LeadMagicRuns ABM at scale (1-to-few) for 15-50 clustered accounts: industry or persona clusters, semi-custom campaigns, and cluster-level content. Use when named-account ABM needs to reach more accounts without bespoke work per account. Triggers on: "1-to-few ABM", "ABM scale", "cluster ABM", "industry ABM".★ 62 GitHub starsSkillProgrammatic Account TargetingLeadMagic/gtm-skills · by LeadMagicRuns programmatic 1-to-many ABM for 50-200+ accounts: automated personalization, scaled outbound, intent-based targeting, and lookalike expansion. Use when ABM coverage must grow without adding headcount or when the user wants automated account-based outreach. Triggers on: "1-to-many ABM", programmatic ABM", "scaled ABM", "automated ABM".★ 62 GitHub starsSkillAccount Strategy DesignerLeadMagic/gtm-skills · by LeadMagicDesigns an account-based marketing program: tier selection, account scoring, channel orchestration, BDR alignment (account-based sales development), and a measurement framework. Use when the user is launching or redesigning ABM, choosing between 1-to-1, 1-to-few, and 1-to-many, or building a target account program. Triggers on: "ABM strategy", "account based marketing", "ABM playbook", "design ABM", "target accounts", "ABSD", "account based sales development", "Lars Nilsson".★ 62 GitHub starsSkillTarget Account SelectorLeadMagic/gtm-skills · by LeadMagicBuilds and tiers a target account list: fit and intent scoring models, tier assignment, and TAM segmentation. Use when the user needs to decide which accounts to target, score or tier an account list, or prioritize a TAM for ABM or outbound. Triggers on: "account selection", "target account list", "tier accounts", "prioritize accounts", "TAM segmentation".★ 62 GitHub stars