abx-strategy

Build Account-Based Everything (ABX) GTM strategies for complex B2B sales. Use when working on ABM strategy, ICP scoring, messaging architecture, product launches, or pipeline acceleration for companies with <500 accounts, $100K+ deals, and 6+ month sales cycles.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "abx-strategy" with this command: npx skills add yannickyamo/skills/yannickyamo-skills-abx-strategy

ABX Strategy Framework

A comprehensive Account-Based Everything (ABX) strategy framework for B2B companies with complex sales cycles, lots of personnas, high-value deals, and limited addressable markets.

When to Use This Skill

Use this skill when:

  • Building GTM strategy for companies with <500 addressable accounts
  • Deal sizes exceed $100K+ with 6+ month sales cycles
  • Buying committees involve 5+ stakeholders
  • Products require technical translation for business buyers
  • You need to prioritize segments with limited resources
  • Marketing must directly influence pipeline, not just generate awareness

This framework is designed for complex B2B sales where traditional demand generation fails and account-based approaches are structurally required.


Core Philosophy: Marketing as Product

Treat every campaign, message, and channel as a hypothesis to validate, not a plan to execute.

Traditional MarketingMarketing as Product
Annual messaging frameworkMessaging backlog with sprint-based testing
Launch plan executed onceLaunch as v1.0, iterated based on field data
Competitive analysis updated quarterlyCompetitive intel as live feed from sales calls
Sales enablement = collateral dumpEnablement = tested talk tracks with win-rate data
Success = assets shippedSuccess = pipeline influenced and deal velocity changed

The Bet Board Methodology

Every initiative is a bet with four components:

┌─────────────────────────────────────────────────────────────┐
│ BET: [Name of initiative]                                   │
├─────────────────────────────────────────────────────────────┤
│ HYPOTHESIS: [What you believe will happen]                  │
│                                                             │
│ TEST: [How you will validate]                               │
│                                                             │
│ SUCCESS CRITERIA: [Measurable outcome that confirms bet]    │
│                                                             │
│ KILL CONDITION: [When to abandon and pivot]                 │
│                                                             │
│ LEARNING OUTPUT: [What you'll know regardless of outcome]   │
└─────────────────────────────────────────────────────────────┘

Example Bet Categories:

  • Messaging bets (which narrative resonates)
  • Channel bets (where to invest)
  • ABM motion bets (what triggers engagement)
  • Product launch bets (what drives conversion)

Framework 1: Segment-Specific vs. Synergy Analysis

Not everything needs to be rebuilt for each segment. This framework identifies what MUST differ vs. what can be REUSED.

Segment-Specific (Must Differ)

DimensionWhy It Must Differ
ICPs & PersonasDifferent buyers, different motivations, different language
Pain PointsEach segment has unique problems driving urgency
Pricing StrategyValue perception varies; commercial vs. government procurement differs
ChannelsWhere buyers gather and consume information varies
Messaging & PositioningSame product, different value narrative per audience
Budget AllocationROI per segment differs; invest proportionally

Synergies (Reusable Across Segments)

DimensionWhy It's Reusable
Education TopicsCore technology/market education applies broadly
Technical CollateralSpecs, datasheets, architecture diagrams are universal
Product RoadmapFeatures serve multiple segments
Strategic PartnersIntegrators, channel partners often span segments
Success StoriesOn-orbit/in-production proof points validate for all
Core NarrativeCategory-level story transcends segments

Template: Segment Analysis Matrix

## Segment: [Name]

### Segment-Specific Elements
- **ICP**: [Description]
- **Primary Personas**: [List with titles]
- **Top 3 Pain Points**: 
  1. [Pain point]
  2. [Pain point]
  3. [Pain point]
- **Pricing Model**: [Approach]
- **Primary Channels**: [List]
- **Key Message**: "[One sentence value prop for this segment]"

### Synergies from Other Segments
- **Reusable Collateral**: [List]
- **Shared Success Stories**: [List]
- **Common Education Topics**: [List]

Framework 2: ABX Account Motions

Replace the linear funnel with signal-driven account motions. Each motion is triggered by observed signals, not assumptions about where accounts "sit" in a journey.

The Five Motions

DETECT ──→ DECODE ──→ ENGAGE ──→ ACCELERATE ──→ EXPAND
   │          │          │            │            │
   ▼          ▼          ▼            ▼            ▼
Signal     Map the    Multi-      Close        Grow the
appears    buying     thread      the deal     account
           committee  engagement

Motion Details

MotionTrigger SignalsMarketing ActionsSuccess Metrics
DETECTPolicy announcement, RFI published, leadership change, contract expiring, funding round, strategic initiative announcedAccount research sprint, buying committee mapping, PURE score assessment, tier assignmentSignal-to-first-touch latency (<72 hrs)
DECODEFirst meeting booked, stakeholder org emerging, champion identifiedDeep committee mapping, personality profiling, custom value narrative per stakeholder# stakeholders mapped, personas engaged (target: 3+)
ENGAGEActive evaluation confirmed, multiple touchpoints, content consumption increasingMulti-channel surround: exec events, site visits, technical deep-dives, personalized content, ABM adsMulti-thread penetration, content engagement depth
ACCELERATEProposal stage, competitive evaluation, procurement initiatedCompetitive battle support, reference activation, custom ROI analysis, executive alignmentPipeline velocity (days), competitive win rate
EXPANDFirst product delivered, performance validated, satisfaction confirmedPerformance reporting, expansion narrative, peer referral program, fleet/portfolio growth pitchExpansion rate (% entering 2nd deal discussion)

Signal Detection Categories

Signal TypeExamplesSourcesResponse Protocol
Policy/RegulatoryNew legislation, budget allocation, mandate announcedGovernment portals, industry news, regulatory filingsResearch sprint: map decision-makers, assess timing
ProcurementRFI/RFP published, contract expiration, vendor reviewProcurement portals, industry contacts, newsImmediate: assemble capture team, prepare response
Leadership ChangeNew CEO/CTO, new program manager, reorg announcedLinkedIn, press releases, job change alertsWelcome outreach with executive briefing offer
CompetitiveCompetitor failure, delay, price increase, service issueIndustry news, sales intelligence, customer networkTargeted outreach to affected customers
StrategicM&A activity, funding round, expansion announcedNews, SEC filings, press releasesAssess fit, prepare relevant value narrative

Framework 3: PURE Problem Scoring

Score ICP tiers using the PURE framework to identify "hair-on-fire" accounts.

The PURE Criteria

CriterionQuestionScore 0-3
PainfulHow acute is the problem? Is it causing real damage today?0=mild, 3=severe
UrgentIs there a forcing function (deadline, mandate, event)?0=no timeline, 3=imminent
RecognizedDoes the buyer know they have this problem?0=unaware, 3=actively seeking solution
ExpensiveWhat's the cost of inaction (financial, strategic, competitive)?0=low, 3=existential

Tier Assignment

Total ScoreTierPriorityResource Allocation
10-12Tier 1: Hair-on-FireHighestDedicated account team, custom everything
7-9Tier 2: Burning PlatformHighProactive outreach, personalized content
4-6Tier 3: Active PainMediumTargeted campaigns, scaled personalization
1-3Tier 4: Emerging NeedLowerNurture programs, educational content
0Tier 5: Future PotentialLowestLight touch, brand awareness only

Template: Account PURE Scorecard

## Account: [Company Name]

### PURE Assessment
| Criterion | Score (0-3) | Evidence |
|-----------|-------------|----------|
| Painful | [X] | [Why this score] |
| Urgent | [X] | [Why this score] |
| Recognized | [X] | [Why this score] |
| Expensive | [X] | [Why this score] |
| **TOTAL** | [X/12] | **Tier: [X]** |

### Buying Committee (Known)
| Name | Title | Role in Decision | Engagement Status |
|------|-------|------------------|-------------------|
| | | Champion / Influencer / Blocker / Decision-maker | Cold / Warm / Engaged |

### Next Actions
1. [Action]
2. [Action]

Framework 4: Message Resonance System

Creating content is not enough. This system ensures messages actually land.

The Five Components

┌─────────────────────────────────────────────────────────────┐
│                   MESSAGE RESONANCE SYSTEM                  │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐         │
│  │PERSONALI-   │  │STORYTELLING │  │ ENGAGEMENT  │         │
│  │ZATION       │  │             │  │ METRICS     │         │
│  │             │  │             │  │             │         │
│  │Tailored     │  │Real examples│  │Track what   │         │
│  │content per  │  │and case     │  │lands via    │         │
│  │persona and  │  │studies that │  │analytics,   │         │
│  │segment      │  │make abstract│  │Gong, email  │         │
│  │             │  │tangible     │  │engagement   │         │
│  └─────────────┘  └─────────────┘  └─────────────┘         │
│                                                             │
│  ┌─────────────┐  ┌─────────────┐                          │
│  │ FEEDBACK    │  │ CONSISTENT  │                          │
│  │ LOOPS       │  │ VOICE       │                          │
│  │             │  │             │                          │
│  │Sales input, │  │Professional │                          │
│  │win/loss     │  │yet human.   │                          │
│  │analysis,    │  │Innovative   │                          │
│  │customer     │  │but proven.  │                          │
│  │interviews   │  │             │                          │
│  └─────────────┘  └─────────────┘                          │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Message Resonance Rate (MRR)

The key leading indicator: % of sales conversations where the prospect uses your language back.

Track via conversation intelligence (Gong, Chorus) by monitoring:

  • Keyword adoption (do they say "dedicated capacity" or "shared bandwidth"?)
  • Objection patterns (are we addressing the right concerns?)
  • Competitive mentions (how are we being compared?)

Target: 40%+ of qualified meetings show message adoption.


Framework 5: Capability-to-Benefit Translation

Technical products require systematic translation from what it does to why it matters.

The Translation Hierarchy

Layer 1: CATEGORY NARRATIVE
         "Why this matters to the world"
              │
              ▼
Layer 2: CAPABILITY → BENEFIT TRANSLATION
         "What it does → So what? → Why you care"
              │
              ▼
Layer 3: PERSONA-SPECIFIC MESSAGES
         "Tailored value prop per buyer type"

Template: Capability Translation Matrix

Technical CapabilitySo What? (Translation)Benefit: Segment ABenefit: Segment B
[Technical feature][Plain language explanation][Value for segment A buyer][Value for segment B buyer]
[Technical feature][Plain language explanation][Value for segment A buyer][Value for segment B buyer]

Template: Persona Message Map

PersonaWhat They Care AboutMessage FrameProof Points
CEO/BoardStrategic positioning, competitive advantage, ROI"[Strategic value prop]"[Evidence]
CTO/TechnicalSpecs, integration, performance, reliability"[Technical value prop]"[Evidence]
CFO/FinanceTCO, payback period, risk mitigation"[Financial value prop]"[Evidence]
Ops/UserEase of use, support, day-to-day experience"[Operational value prop]"[Evidence]
ProcurementCompliance, risk, vendor stability"[Risk mitigation prop]"[Evidence]

Framework 6: Constant Discovery Mindset

Every engagement generates learnings. This framework captures and applies them.

The Four Discovery Questions

Before, during, and after every deal:

┌─────────────────────────────────────────────────────────────┐
│ 1. Do we know and understand the PLAYERS?                   │
│    Who are the real decision-makers vs. influencers?        │
│    Who can kill the deal? Who's the hidden blocker?         │
├─────────────────────────────────────────────────────────────┤
│ 2. Do we understand the RELATIONSHIPS?                      │
│    Internal dynamics? External advisors? Political factors? │
│    Who trusts whom? Who competes internally?                │
├─────────────────────────────────────────────────────────────┤
│ 3. Do we understand the INFLUENCING FACTORS?                │
│    Budget cycles? Regulatory timelines? Competitive moves?  │
│    Internal mandates? Strategic priorities?                 │
├─────────────────────────────────────────────────────────────┤
│ 4. Do we know the DECISION FACTORS?                         │
│    Technical requirements? Commercial terms? Risk tolerance?│
│    Timeline constraints? Evaluation criteria?               │
└─────────────────────────────────────────────────────────────┘

Win/Loss Analysis Framework

DimensionQuestions to AnswerHow to Capture
Decision CriteriaWhat were the top 3 factors? Were these what we expected?Post-decision debrief
Buying ProcessWho was the real decision-maker? Who influenced most?Sales team debrief, call analysis
Messaging EffectivenessWhich messages resonated? Which fell flat?Keyword analysis, champion feedback
Competitive DynamicsWho else considered? What did they say about us?Direct inquiry, third-party research
Timeline & ProcessFaster or slower than expected? What caused delays?CRM tracking, sales input

Framework 7: Learning Loop Architecture

Structured cadence for turning field data into strategy improvements.

CadenceInputsDecisionsOutputs
WeeklyCall summaries, signal alerts, content engagementAdjust messaging, reprioritize accountsUpdated talk tracks, account priority shifts
Bi-weeklyWin/loss patterns, objection frequencyTest new value props, update battle cardsNew messaging variants for testing
MonthlyFull pipeline analysis, content performance, ABM metricsKill underperforming bets, double down on winnersBet board update, resource reallocation
QuarterlyMarket shifts, competitive landscape, customer feedbackStrategy pivots, new bet proposalsUpdated GTM strategy, new hypothesis slate

Framework 8: Budget Allocation by Stage

Marketing investment mix should shift as market position evolves.

StagePrimary InvestmentSecondaryRationale
Early Market (0→1)Branding & Positioning (40%)Sales Enablement (35%)Category creation, message testing, foundational collateral
Scaling (1→10)Demand Generation (40%)Sales Enablement (30%)ABM campaigns, event presence, thought leadership at scale
Market LeaderDemand Generation (45%)Customer Marketing (25%)Expansion, reference program, ecosystem development

Framework 9: Customer Journey Mapping

Map both internal (your team) and external (customer) activities across the journey.

Template: Journey Map

StageCustomer ActivitiesYour Internal ActivitiesKey StakeholdersMarketing Deliverables
IdentificationEvaluating options, initial research, internal alignmentSignal detection, account research, tier assignmentInnovation leads, technical scoutsAccount brief, persona mapping
ConsiderationTechnical evaluation, stakeholder education, vendor comparisonMulti-threading, technical deep-dives, exec engagementCTO, architects, financeTechnical collateral, ROI calculator, battle cards
ValidationPOC/demo, reference checks, contract negotiationReference activation, proposal support, legal/contractCEO, legal, board, implementationCustom business case, exec presentation
ImplementationDeployment, integration, go-liveOnboarding support, success planningOps team, project managerImplementation guides, training
ExpansionPerformance review, additional use cases, renewalPerformance reporting, expansion pitch, reference programExec sponsor, opsPerformance report, expansion narrative, case study

Framework 10: Collaterals with Success Metrics

Every asset should have defined success metrics. Track not just creation, but effectiveness.

Asset TypePurposeSuccess MetricsReview Cadence
ROI/TCO CalculatorSelf-service economic comparison% of meetings where used, conversion rateMonthly
Technical DatasheetsSpec validation for technical buyersTime-on-page, download rate, sales feedbackQuarterly
Case StudiesSocial proof and use case validationCited in sales calls, shared by prospectsMonthly
Battle CardsArm sales for competitive encountersWin rate in competitive deals, objection handle rateMonthly
Executive PresentationC-level storytellingMeeting-to-proposal conversion, exec feedbackQuarterly

KPI Architecture

Tier 1: Leading Indicators (Weekly)

MetricDefinitionTarget
Message Resonance Rate% of conversations where prospect uses your language40%+
Content Engagement DepthTime-on-page for key content by target accounts3+ minutes
Multi-thread PenetrationUnique stakeholders engaged per target account3+ before proposal
Signal-to-Engagement LatencyTime from signal to first personalized touch<72 hours

Tier 2: Core Pipeline Metrics (Monthly)

MetricDefinitionTarget
Marketing-Sourced MeetingsMeetings from marketing-initiated engagement2-3/month from target list
Pipeline VelocityDays from first touch to proposalReduce 15% in 6 months
Deal Influence Rate% of active pipeline with marketing touchpoints80%+
Competitive Win Rate% won when competitor presentTrack QoQ improvement

Tier 3: Lagging Confirmation (Quarterly)

MetricDefinitionTarget
Revenue Influenced$-value where marketing contributed50%+ of bookings
Customer Expansion Rate% entering expansion conversations60%+ within 18 months
Brand Authority IndexUnsolicited inbound citing content/thought leadershipTrack growth

Composable ABX Tech Stack

Best-of-breed tools, orchestrated through CRM as single source of truth.

FunctionRecommended ToolsPurposeEst. Annual Cost
CRM / Source of TruthSalesforce, HubSpotCentral account and deal recordVaries
Conversation IntelligenceGong, Chorus, ClariCapture calls, surface patterns, track competitors$30-50K
Data EnrichmentClay, Apollo, ZoomInfoAccount research, signal monitoring, contact data$10-30K
Website PersonalizationMutiny, DemandbaseAccount-specific landing pages, dynamic content$25-40K
ABM AdvertisingInflu2, ZenABM, LinkedInContact-level targeting, persona-specific creative$20-30K
Workflow AutomationZapier, n8n, MakeConnect tools, trigger motions automatically$5-10K
Buyer IntelligenceHumantic AI, CrystalPersonality profiling, communication preferences$10-15K

Phase 1 Investment: $100-165K for composable stack vs. $150-250K+ for enterprise ABM platforms with less flexibility.


90-Day Implementation Plan

Days 1-30: Listen, Map, Foundation

Listen:

  • Sit in on 10+ sales calls. Document buyer language, objections, competitive mentions.
  • Interview 5+ customers: Why did they choose you? What almost stopped them?
  • Interview 5+ sales reps: What messaging works? What falls flat?

Map:

  • Build target account list with PURE scores
  • Map buying committees for top 10 accounts
  • Audit existing content: What exists? Missing? Stale?
  • Competitive audit: How do competitors position? Where vulnerable?

Foundation:

  • Draft v1 messaging hierarchy
  • Set up conversation intelligence dashboards
  • Establish weekly learning loop cadence

Days 31-60: Build, Test, Launch First Bets

Build:

  • Finalize messaging hierarchy; test with sales + friendly customers
  • ROI/TCO calculator v1
  • First persona-specific content pieces
  • Set up account enrichment for top 30 accounts

Test:

  • Launch 2-3 messaging bets
  • Launch channel bet (e.g., executive LinkedIn content)
  • First warm outbound sequences to signal-showing accounts

Align:

  • Present initial findings to leadership
  • Align with sales on account prioritization

Days 61-90: Iterate, Expand, Prepare

Iterate:

  • First bet review: What's working? Kill or amplify.
  • Update messaging based on call data
  • Refine account tiers based on signals

Expand:

  • Launch additional bets
  • Set up website personalization for top accounts
  • Begin product launch planning if applicable

Prepare:

  • Present 90-day results and updated Bet Board
  • Propose next phase investments

Quick Reference: Power Phrases

Use these frames in strategy discussions:

  • "Hypothesis → Test → Learn → Iterate" — not plan and execute
  • "Learning velocity over planning perfection" — especially at 0→1
  • "The market tells us, we don't tell the market" — ground strategy in signals
  • "Multi-threading is mandatory" — complex deals require parallel engagement
  • "Take the complex and make it simple" — the core PMM challenge
  • "Proven, not promised" — flight heritage / production deployment matters
  • "Every campaign is a bet with a kill condition" — no sacred cows

Using This Skill with Claude

When working on ABX strategy, you can ask Claude to:

  1. Score accounts: "Apply the PURE framework to [company] based on [context]"
  2. Build messaging: "Create a capability-to-benefit translation matrix for [product]"
  3. Design bets: "Propose 5 testable messaging bets for [segment]"
  4. Map journeys: "Build a customer journey map for [persona] buying [product]"
  5. Analyze segments: "Apply the segment-specific vs. synergy framework to [segments]"
  6. Create collaterals: "Draft a battle card for competing against [competitor]"
  7. Build scorecards: "Create a PURE scorecard template for [industry]"
  8. Plan launches: "Design a bet board for launching [product] to [segment]"

License

MIT License. Use freely, adapt to your context, share improvements.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

product-leadership

No summary provided by upstream source.

Repository SourceNeeds Review
General

product-architecture

No summary provided by upstream source.

Repository SourceNeeds Review
General

ai-native-product

No summary provided by upstream source.

Repository SourceNeeds Review
General

product-delivery

No summary provided by upstream source.

Repository SourceNeeds Review