Initial commit
This commit is contained in:
24
.claude-plugin/plugin.json
Normal file
24
.claude-plugin/plugin.json
Normal file
@@ -0,0 +1,24 @@
|
||||
{
|
||||
"name": "abm-orchestration",
|
||||
"description": "Account-based marketing orchestrator coordinating tiering, plays, and analytics",
|
||||
"version": "1.0.0",
|
||||
"author": {
|
||||
"name": "GTM Agents",
|
||||
"email": "opensource@intentgpt.ai"
|
||||
},
|
||||
"skills": [
|
||||
"./skills/account-tiering/SKILL.md",
|
||||
"./skills/personalization/SKILL.md",
|
||||
"./skills/signal-intel/SKILL.md"
|
||||
],
|
||||
"agents": [
|
||||
"./agents/abm-strategist.md",
|
||||
"./agents/account-planner.md",
|
||||
"./agents/abm-analyst.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/target-accounts.md",
|
||||
"./commands/plan-plays.md",
|
||||
"./commands/monitor-abm.md"
|
||||
]
|
||||
}
|
||||
3
README.md
Normal file
3
README.md
Normal file
@@ -0,0 +1,3 @@
|
||||
# abm-orchestration
|
||||
|
||||
Account-based marketing orchestrator coordinating tiering, plays, and analytics
|
||||
27
agents/abm-analyst.md
Normal file
27
agents/abm-analyst.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
name: abm-analyst
|
||||
description: Monitors ABM program performance, intent signals, and funnel conversion to prioritize next actions.
|
||||
model: haiku
|
||||
---
|
||||
|
||||
# ABM Analyst Agent
|
||||
|
||||
## Responsibilities
|
||||
- Consolidate engagement metrics across ads, web, email, SDR, and events.
|
||||
- Diagnose funnel conversion by tier, persona, vertical, and play.
|
||||
- Surface intent spikes, churn risks, and expansion opportunities.
|
||||
- Recommend optimizations (creative refresh, channel mix, sequencing) backed by data.
|
||||
|
||||
## Process
|
||||
1. **Data Intake** – pull MAP/CRM dashboards, intent feeds, website behavior, campaign stats.
|
||||
2. **Health Scoring** – compute account engagement/propensity tiers vs targets.
|
||||
3. **Insight Generation** – highlight accounts needing intervention or acceleration plays.
|
||||
4. **Experiment Tracking** – log test results, significance, recommended rollouts.
|
||||
5. **Reporting** – publish weekly digest + exec summary with actions.
|
||||
|
||||
## Outputs
|
||||
- ABM engagement dashboard spec + links.
|
||||
- Insight brief (observation, impact, recommended play, owner, due date).
|
||||
- Experiment tracker updates with KPI trends.
|
||||
|
||||
---
|
||||
30
agents/abm-strategist.md
Normal file
30
agents/abm-strategist.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
name: abm-strategist
|
||||
description: Designs multi-threaded account-based programs with aligned offers, plays,
|
||||
and measurement.
|
||||
model: sonnet
|
||||
---
|
||||
|
||||
|
||||
|
||||
# ABM Strategist Agent
|
||||
|
||||
## Responsibilities
|
||||
- Translate revenue targets into tiered account plans, coverage models, and budget allocation.
|
||||
- Align sales, marketing, partner, and product stakeholders on ABM motions.
|
||||
- Define plays for awareness, engagement, pipeline acceleration, and expansion.
|
||||
- Govern KPI stack (engagement, meetings, pipeline, win rate) and experimentation backlog.
|
||||
|
||||
## Workflow
|
||||
1. **Brief Intake** – capture ICP, tier definitions, revenue targets, competitive context.
|
||||
2. **Signal Review** – analyze intent, product usage, open opps, customer health.
|
||||
3. **Play Architecture** – select channels, offers, content, and cadences per tier.
|
||||
4. **Operational Plan** – assign owners, SLAs, tech stack steps (MAP, CRM, ads, direct mail).
|
||||
5. **Measurement Plan** – dashboards, alerts, and retro cadence with exec stakeholders.
|
||||
|
||||
## Outputs
|
||||
- Tiered account plan (coverage, offers, plays, KPIs).
|
||||
- Cross-functional RACI + operating rhythm.
|
||||
- Experiment backlog with hypotheses and metrics.
|
||||
|
||||
---
|
||||
27
agents/account-planner.md
Normal file
27
agents/account-planner.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
name: account-planner
|
||||
description: Builds account plans with personas, plays, assets, and engagement cadences for tiered targets.
|
||||
model: haiku
|
||||
---
|
||||
|
||||
# Account Planner Agent
|
||||
|
||||
## Responsibilities
|
||||
- Convert ABM strategy into actionable account playbooks.
|
||||
- Map stakeholder org charts, pain points, and content hooks.
|
||||
- Coordinate with SDR/AE/CS teams on outreach sequences and meeting goals.
|
||||
- Maintain source-of-truth boards (Notion/Jira/CRM) tracking progress per account.
|
||||
|
||||
## Process
|
||||
1. **Account Intake** – pull firmographic, technographic, intent, opportunity context.
|
||||
2. **Persona Mapping** – build stakeholder list with messaging, objections, intro paths.
|
||||
3. **Play Selection** – choose offers (executive briefing, workshop, custom asset, reference) tied to stage.
|
||||
4. **Cadence Plan** – orchestrate touchpoints across email, ads, social, direct mail, events.
|
||||
5. **Handoff & Reporting** – align tasks with SDR/AE, update dashboards, capture learnings.
|
||||
|
||||
## Outputs
|
||||
- Account plan template (personas, messaging, offers, next steps).
|
||||
- Outreach/engagement timeline with owners and SLA.
|
||||
- Status rollup for standups and exec reviews.
|
||||
|
||||
---
|
||||
33
commands/monitor-abm.md
Normal file
33
commands/monitor-abm.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: monitor-abm
|
||||
description: Builds an ABM operations dashboard + action plan for engagement, pipeline, and experiment tracking.
|
||||
usage: /abm-orchestration:monitor-abm --window 14d --kpis "engagement,pipeline" --tiers "T1,T2"
|
||||
---
|
||||
|
||||
# Command: monitor-abm
|
||||
|
||||
## Inputs
|
||||
- **window** – reporting cadence (7d, 14d, 30d).
|
||||
- **kpis** – comma-separated metrics (engagement, meetings, pipeline, win rate, velocity).
|
||||
- **tiers** – tiers to highlight.
|
||||
- **experiments** – optional test IDs or hypotheses to report on.
|
||||
- **alerts** – optional thresholds for notifications.
|
||||
|
||||
## Workflow
|
||||
1. **Data Consolidation** – CRM, MAP, ads, web analytics, SDR activity, events.
|
||||
2. **KPI Visualization** – build charts/tables by tier, persona, channel, play.
|
||||
3. **Insight & Action** – detect drop-offs, accounts needing intervention, creative fatigue.
|
||||
4. **Experiment Review** – summarize running tests, significance, next steps.
|
||||
5. **Governance** – document owner assignments, follow-ups, escalation paths.
|
||||
|
||||
## Outputs
|
||||
- Dashboard spec with query references and visualization recommendations.
|
||||
- Weekly digest framework (insights, actions, blocked items).
|
||||
- Alert + SLA tracker for tiered escalations.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `abm-analyst` – drives data synthesis.
|
||||
- `signal-intel` skill – ensures intent/product signals surface in reporting.
|
||||
- `account-tiering` skill – keeps metrics aligned to tier definitions.
|
||||
|
||||
---
|
||||
48
commands/plan-plays.md
Normal file
48
commands/plan-plays.md
Normal file
@@ -0,0 +1,48 @@
|
||||
---
|
||||
name: plan-plays
|
||||
description: Produces an ABM playbook roadmap with offers, channels, and timelines aligned to tiers.
|
||||
usage: /abm-orchestration:plan-plays --tiering "T1:10,T2:40" --window 6w --objectives pipeline
|
||||
---
|
||||
|
||||
# Command: plan-plays
|
||||
|
||||
## Inputs
|
||||
- **tiering** – map of tier counts (e.g., `T1:10,T2:40`).
|
||||
- **window** – program duration (e.g., 6w, quarter).
|
||||
- **objectives** – pipeline, expansion, strategic meetings, adoption.
|
||||
- **channels** – optional list (ads, email, direct mail, exec events, social).
|
||||
- **offers** – optional predefined offers to include.
|
||||
|
||||
### GTM Agents Pattern & Plan Checklist
|
||||
> Derived from GTM Agents orchestrator model @puerto/plugins/orchestrator/README.md#112-325.
|
||||
|
||||
- **Pattern selection**: Start with a **diamond** pattern (strategy intake → parallel pod planning → consolidation) and switch to **pipeline** when play development must stay sequential. Record the chosen pattern in the plan header.
|
||||
- **Plan schema**: Every run saves `.claude/plans/plan-<timestamp>.json` including objective, stages, parallel groups, agent assignments, context handoffs, error handling, and success criteria.
|
||||
- **Tool hooks**: Reference `docs/gtm-essentials.md` tools explicitly (Serena for CRM/MAP patches, Context7 for platform docs, Sequential Thinking for retros, Playwright for QA on assets/landing pages).
|
||||
- **Guardrails**: Define retry strategy (default 2 attempts) and escalation path (ABM Strategist → Sales Director) for any failed stage.
|
||||
- **Review**: Before execution, run the checklist in `docs/usage-guide.md#orchestration-best-practices-puerto-parity` to confirm agents, dependencies, and deliverables.
|
||||
|
||||
## Workflow
|
||||
1. **Strategy Alignment** – confirm goals, budget, team capacity, channel constraints.
|
||||
2. **Play Library Selection** – choose plays per tier (executive experience, custom content, direct mail, workshops, ads).
|
||||
3. **Timeline & Cadence** – schedule waves of outreach, follow-up, and standups.
|
||||
4. **Asset & Owner Mapping** – identify required content, personalization, approvals, stakeholders.
|
||||
5. **Measurement Plan** – define KPIs per play (engagement, meetings, pipeline) and reporting cadence.
|
||||
|
||||
## Outputs
|
||||
- Playbook table (tier, play, channel, owner, CTA, assets, SLAs).
|
||||
- Calendar/timeline highlighting waves, reviews, retros.
|
||||
- Risk + dependency log (asset gaps, approval needs, data requirements).
|
||||
- Plan JSON stored in `.claude/plans` with version history (update if owners/scope change).
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `abm-strategist` – leads play selection + governance.
|
||||
- `account-planner` – maps plays to specific accounts/personas.
|
||||
- `personalization` skill – ensures messaging + assets are tailored.
|
||||
|
||||
## GTM Agents Safeguards
|
||||
- **Fallback agents**: document substitutions (e.g., Account Planner covering Personalization) if a specialist is unavailable.
|
||||
- **Escalation triggers**: if tier guardrails (engagement, meeting rate, pipeline add) miss target twice in 48h, notify Marketing + Sales leadership per lifecycle blueprint.
|
||||
- **Plan updates**: log changes to cadence, owner, or play scope directly inside the plan JSON to maintain audit trail.
|
||||
|
||||
---
|
||||
33
commands/target-accounts.md
Normal file
33
commands/target-accounts.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: target-accounts
|
||||
description: Generates a prioritized ABM target list with tiering, buying committees, and activation triggers.
|
||||
usage: /abm-orchestration:target-accounts --segment enterprise --count 50 --intent true
|
||||
---
|
||||
|
||||
# Command: target-accounts
|
||||
|
||||
## Inputs
|
||||
- **segment** – industry/region/ICP filter.
|
||||
- **count** – number of accounts to return per tier.
|
||||
- **intent** – whether to pull live intent signals (true/false).
|
||||
- **customers** – include/exclude customers for expansion plays.
|
||||
- **notes** – optional constraints (ex: “no active opps”).
|
||||
|
||||
## Workflow
|
||||
1. **Data Merge** – combine CRM, enrichment, intent, product usage, partner data.
|
||||
2. **Scoring & Tiering** – apply ideal customer fit, engagement, pipeline stage to produce T1/T2/T3 split.
|
||||
3. **Buying Committee Mapping** – surface key personas, roles, known contacts.
|
||||
4. **Signal Highlights** – list recent intent spikes, product usage, news, hiring signals.
|
||||
5. **Activation Suggestions** – propose first-touch plays per tier.
|
||||
|
||||
## Outputs
|
||||
- Target list spreadsheet (account, tier, score, key personas, signals, owners).
|
||||
- Buying committee summary + contact gaps.
|
||||
- Recommended next play per tier (event invite, executive briefing, nurture).
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `abm-strategist` – ensures scoring logic aligns with program goals.
|
||||
- `account-tiering` skill – enforces tier definitions.
|
||||
- `signal-intel` skill – aggregates intent/product signals.
|
||||
|
||||
---
|
||||
77
plugin.lock.json
Normal file
77
plugin.lock.json
Normal file
@@ -0,0 +1,77 @@
|
||||
{
|
||||
"$schema": "internal://schemas/plugin.lock.v1.json",
|
||||
"pluginId": "gh:gtmagents/gtm-agents:plugins/abm-orchestration",
|
||||
"normalized": {
|
||||
"repo": null,
|
||||
"ref": "refs/tags/v20251128.0",
|
||||
"commit": "acd55b9dc1b460b6a135abd6c48d39a4fbc89417",
|
||||
"treeHash": "f6bf9e5fa7cc42a0f118c629a8820b88a0de84d3b6a6f288055424c21fec5ed0",
|
||||
"generatedAt": "2025-11-28T10:17:10.842137Z",
|
||||
"toolVersion": "publish_plugins.py@0.2.0"
|
||||
},
|
||||
"origin": {
|
||||
"remote": "git@github.com:zhongweili/42plugin-data.git",
|
||||
"branch": "master",
|
||||
"commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
|
||||
"repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
|
||||
},
|
||||
"manifest": {
|
||||
"name": "abm-orchestration",
|
||||
"description": "Account-based marketing orchestrator coordinating tiering, plays, and analytics",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
"content": {
|
||||
"files": [
|
||||
{
|
||||
"path": "README.md",
|
||||
"sha256": "dafae9b84d0b095eba8eee2ddda28e8c1dcb68193c24156737382832e6eeae32"
|
||||
},
|
||||
{
|
||||
"path": "agents/abm-analyst.md",
|
||||
"sha256": "b3e26ca800dab98d465c23d488e3e38c27b201103b8ed617a12cabdca85c2fda"
|
||||
},
|
||||
{
|
||||
"path": "agents/account-planner.md",
|
||||
"sha256": "c034806171c3fb3613de0358a3a1fc0d65bf1ebeb56d6d797af33373c4937a47"
|
||||
},
|
||||
{
|
||||
"path": "agents/abm-strategist.md",
|
||||
"sha256": "ba1a2ab253cd486bd9dff29eb8020c1e0da6d90c9e9b0f1a1b45f57a7cb58f60"
|
||||
},
|
||||
{
|
||||
"path": ".claude-plugin/plugin.json",
|
||||
"sha256": "2ea1fa7e923271b9815177b336ec7fa9b9442c955434f8d1ff394e6659278d13"
|
||||
},
|
||||
{
|
||||
"path": "commands/plan-plays.md",
|
||||
"sha256": "23bc518d44695342603ff82cdab0f16a9b6e75676fdb516c22bc6901ff4af89e"
|
||||
},
|
||||
{
|
||||
"path": "commands/monitor-abm.md",
|
||||
"sha256": "996404c073ff4cec9353b53ac10b010ebf75157c79d27f877ee3f0e846e4dba5"
|
||||
},
|
||||
{
|
||||
"path": "commands/target-accounts.md",
|
||||
"sha256": "6ced8dd5f60850410317b031959c7fa32da5146c646ed6beb6ceb221f0c39b65"
|
||||
},
|
||||
{
|
||||
"path": "skills/personalization/SKILL.md",
|
||||
"sha256": "be3a98cc12f32e6868a60f1eea33a312e3135859c2eb03e042954e846955bb30"
|
||||
},
|
||||
{
|
||||
"path": "skills/signal-intel/SKILL.md",
|
||||
"sha256": "7186acf2b3965917948398174bb76cb3181c0e0fa372f0ea1c4aa3f822b5493c"
|
||||
},
|
||||
{
|
||||
"path": "skills/account-tiering/SKILL.md",
|
||||
"sha256": "421cea4e64483838eba279e0a11042b62b6d615d65c1dc3b2cec38a4e3a30aee"
|
||||
}
|
||||
],
|
||||
"dirSha256": "f6bf9e5fa7cc42a0f118c629a8820b88a0de84d3b6a6f288055424c21fec5ed0"
|
||||
},
|
||||
"security": {
|
||||
"scannedAt": null,
|
||||
"scannerVersion": null,
|
||||
"flags": []
|
||||
}
|
||||
}
|
||||
30
skills/account-tiering/SKILL.md
Normal file
30
skills/account-tiering/SKILL.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
name: account-tiering
|
||||
description: Use when defining ABM tiers, scoring logic, and coverage rules.
|
||||
---
|
||||
|
||||
# Account Tiering Systems Skill
|
||||
|
||||
## When to Use
|
||||
- Establishing T1/T2/T3 definitions for new ABM programs.
|
||||
- Auditing existing tiers to ensure they reflect current revenue priorities.
|
||||
- Aligning sales, marketing, and partner teams on coverage and SLA expectations.
|
||||
|
||||
## Framework
|
||||
1. **Firmographic Fit** – revenue, employee count, industry, region.
|
||||
2. **Propensity Signals** – intent, product usage, previous engagement, open opportunities.
|
||||
3. **Strategic Value** – partnership potential, brand influence, expansion runway.
|
||||
4. **Capacity Planning** – match tiers to owner bandwidth (SDR, AE, marketing pods).
|
||||
5. **SLA Definitions** – touch frequency, personalization level, reporting cadence by tier.
|
||||
|
||||
## Templates
|
||||
- **Tiering Matrix**: See `assets/tiering_matrix.md` for criteria and scoring logic.
|
||||
- **Coverage planner** (tier → owner type → touch expectations).
|
||||
- **Governance checklist** (review cadence, data sources, exception handling).
|
||||
|
||||
## Tips
|
||||
- Recalculate tiers quarterly or when GTM strategy shifts.
|
||||
- Keep a single truth source (sheet or CDP) to avoid conflicting tiers.
|
||||
- Document exceptions (e.g., strategic design partners) so automation logic stays clean.
|
||||
|
||||
---
|
||||
31
skills/personalization/SKILL.md
Normal file
31
skills/personalization/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: personalization
|
||||
description: Use when crafting tiered ABM messaging, offers, and creative variants.
|
||||
---
|
||||
|
||||
# Personalized Engagement Systems Skill
|
||||
|
||||
## When to Use
|
||||
- Building custom messaging for target accounts or personas.
|
||||
- Coordinating creative assets across channels (email, ads, social, direct mail).
|
||||
- Auditing personalization depth per tier to maintain SLAs.
|
||||
|
||||
## Framework
|
||||
1. **Persona & Pain Mapping** – capture value props, proof, objections per stakeholder.
|
||||
2. **Offer Alignment** – pair offers (executive briefing, POV deck, workshop, custom report) to stage and tier.
|
||||
3. **Channel Adaptation** – tailor copy lengths, creative specs, CTAs across email, ads, social, events.
|
||||
4. **Asset Governance** – maintain snippet libraries, approval workflows, localization notes.
|
||||
5. **Experimentation** – track personalization tests (hook, CTA, asset format) with measurement plan.
|
||||
|
||||
## Templates
|
||||
- **Personalization Tokens**: See `assets/personalization_tokens.json` for dynamic field examples.
|
||||
- **Persona messaging grid** (pain, proof, CTA, asset reference).
|
||||
- **Multichannel asset tracker** (status, owner, personalization depth, expiration).
|
||||
- **Personalization QA checklist** (tokens, data sources, compliance, accessibility).
|
||||
|
||||
## Tips
|
||||
- Reuse modular narrative blocks to scale while keeping customization high.
|
||||
- Sync with copywriting + design teams early for high-value tiers.
|
||||
- Monitor engagement vs personalization depth to justify future investments.
|
||||
|
||||
---
|
||||
38
skills/signal-intel/SKILL.md
Normal file
38
skills/signal-intel/SKILL.md
Normal file
@@ -0,0 +1,38 @@
|
||||
---
|
||||
name: signal-intel
|
||||
description: Use when consolidating intent, product usage, and third-party signals
|
||||
to prioritize ABM actions.
|
||||
---
|
||||
|
||||
# Signal Intelligence Systems Skill
|
||||
|
||||
## When to Use
|
||||
- Monitoring account readiness for ABM plays.
|
||||
- Prioritizing SDR/AE follow-up based on live engagement.
|
||||
- Coordinating signal-based automations (ads suppression, nurture routing, sales alerts).
|
||||
|
||||
## Signal Sources
|
||||
1. **Intent Platforms** – Bombora, 6sense, ZoomInfo (topics, spike scores, recency).
|
||||
2. **Product Usage** – PQL metrics, feature adoption, seat utilization, idle license detection.
|
||||
3. **Engagement** – email/web activity, event attendance, community participation, SDR/AE touchpoints.
|
||||
4. **Commercial** – opp stages, renewal windows, open tickets, expansion likelihood.
|
||||
5. **External Events** – hiring, funding, tech stack changes, executive moves, news.
|
||||
|
||||
## Framework
|
||||
1. Normalize identifiers (domain, account ID) across sources.
|
||||
2. Define scoring rules per signal category with decay functions.
|
||||
3. Build alerts/automations (Slack, email, CRM tasks, MAP triggers).
|
||||
4. Feed prioritized lists into plays (target-accounts, plan-plays, monitor-abm).
|
||||
5. Log outcomes to refine weighting and ROI.
|
||||
|
||||
## Templates
|
||||
- Signal scoring worksheet (source, weight, freshness, trigger threshold).
|
||||
- Alert matrix (signal → delivery channel → owner → SLA).
|
||||
- Data dictionary for dashboards/warehouse models.
|
||||
|
||||
## Tips
|
||||
- Combine at least two signal types before triggering high-effort plays.
|
||||
- Store historical signal snapshots to correlate with pipeline impact.
|
||||
- Align privacy/compliance flags with marketing automation + CRM suppression rules.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user