Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Marketing & sales

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.

YannickMaurice · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add yannickYamo/skills --skill abx-strategy

About this skill


name: abx-strategy description: 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. author: YannickMaurice version: 1.0.0

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 confi
Read the complete source ↗