Skip to main content
command CX Codex

prioritize-accounts — Claude Code command: account prioritization

The prioritize-accounts command ranks target accounts by composite intent score, identifies coverage gaps, and recommends plays for each segment.

Apache-2.0 ★ 450 updated 2026-04-03

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/prioritize-accounts.md
Open on GitHub

What prioritize-accounts does

The command refreshes scores from intent-analyst datasets, buckets accounts into tiers based on fit and intent, and summarizes top topics and key events per tier. It then flags gaps — missing personas, conflicting signals, active suppression rules — and maps activation plays (ads, SDR outreach, executive programs) with owners. Output includes a tiered account list, a coverage gap report, and export-ready CSV/JSON for CRM or engagement platforms.

Results are stored in .claude/plans/plan-<timestamp>.json with a dependency graph, scoring weights, success metrics (coverage percentage, activation lift, follow-up SLA), and an escalation ladder (Intent Analyst → Sales Ops → Exec sponsor). When segmentation and narrative analysis run in parallel, the command documents a diamond block with a merge gate.

Accepts --segment filter (industry, region, ARR band), --tiers (number of tiers, default 3), --min-score (minimum composite score), --include-customers (toggle for expansion plays), and --signals (subset of signal types to prioritize).

What it helps with

  • rank target accounts by fit and intent
  • surface coverage gaps in personas and data
  • generate activation play recommendations per segment
  • build a plan with dependency graph and success metrics
  • prepare export-ready lists for CRM or engagement platforms

Example prompts for the agent

  • Rank accounts in the fintech segment, three tiers, minimum score 65
  • Refresh prioritization for the enterprise segment, include customers, minimum score 70
  • Build an account list for the SaaS segment, two tiers, weigh product-interest signals heavily

How to install prioritize-accounts

Manually: put the files in place

.claude/commands/prioritize-accounts.md

Call it with /prioritize-accounts. For all projects use ~/.claude/commands/

Questions about prioritize-accounts

How to install prioritize-accounts in Claude Code?

Place the command file at .claude/commands/prioritize-accounts.md.

What does the prioritize-accounts command do?

It ranks target accounts by intent score, identifies coverage gaps in personas and data, recommends plays for each segment, and stores a plan with a dependency graph.

What parameters does prioritize-accounts accept?

Filter --segment (industry, region, ARR band), --tiers (number of tiers, default 3), --min-score (score threshold), --include-customers (include customers), --signals (prioritized signal types).

Source text

prioritize-accounts.md · Apache-2.0
---
name: prioritize-accounts
description: Produces ranked account lists with signal context, coverage gaps, and play recommendations.
usage: /intent-signal-orchestration:prioritize-accounts --segment fintech --tiers 3 --min-score 65
---

# Command: prioritize-accounts

## Inputs
- **segment** – optional ICP filter (industry, region, ARR band).
- **tiers** – number of tiers to output (default 3).
- **min-score** – minimum composite signal score required for inclusion.
- **include-customers** – true/false toggle for expansion plays.
- **signals** – optional subset of signal types to weigh heavily.

### GTM Agents Pattern & Plan Checklist
> Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.

- **Pattern selection**: Prioritization typically runs **pipeline** (score refresh → segmentation → narrative → gap check → activation mapping); if segmentation + narrative analysis run in parallel, document a **diamond** block with merge gate in the plan header.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing segments, scoring weights, dependency graph (RevOps, sales, automation), error handling, and success metrics (coverage %, activation lift, SLA on follow-ups).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for scoring template diffs, Context7 for ICP documentation, Sequential Thinking for review cadence, Playwright for CRM view QA if applicable.
- **Guardrails**: Default retry limit = 2 for scoring refresh failures; escalation ladder = Intent Analyst → Sales Ops → Exec sponsor.
- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before exporting lists to confirm dependencies + approvals.

## Workflow
1. **Score Refresh** – pull latest composite scores from `intent-analyst` datasets and apply decay.
2. **Segmentation & Tiering** – bucket accounts by fit + intent score; highlight data sufficiency.
3. **Signal Narrative** – summarize top topics, key events, and recency for each tier.
4. **Gap & Risk Check** – flag missing personas, conflicting signals, or active suppression rules.
5. **Activation Mapping** – recommend plays (ads, SDR outreach, executive program) with owners.

## Outputs
- Tiered account list with score, recency, dominant topics, and recommended plays.
- Coverage gap report (missing contacts, stale data, disqualified signals).
- Export-ready CSV/JSON for CRM or engagement platforms.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.

## Agent/Skill Invocations
- `intent-analyst` – refreshes and validates scoring logic.
- `sales-liaison` – reviews activation suggestions and persona coverage.
- `signal-scoring` skill – documents weighting logic per tier.
- `suppression-logic` skill – ensures risky accounts remain parked.

## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., Sales Ops covering Analyst) when owners unavailable.
- **Escalation triggers**: escalate if coverage gaps exceed threshold twice or suppression logic conflicts; log remediation in plan JSON.
- **Plan maintenance**: update plan JSON/change log when tiers, thresholds, or weighting methodology change.

---

© gtmagents · Apache-2.0 · gtmagents/gtm-agents

Similar slash commands

All slash commands for Marketing and content →

From the same set224

The whole set →
define-profiles The define-profiles command maps audience profile schemas, data sources, and activation needs. Use it to plan personalization across selected channels. CX Codex +1 ★ 450repo stars optimize-nurture optimize-nurture is a Claude Code command that turns nurture metrics and test results into an optimization plan. It flags weak stages and assigns follow-up work with owners and due dates. CX Codex +1 ★ 450repo stars co-plan-campaign co-plan-campaign builds a structured co-marketing campaign brief covering joint messaging, target audiences, asset ownership, and governance rules. CX Codex +1 ★ 450repo stars implement-actions implement-actions is a Claude Code command that turns a prioritized customer-journey initiative into coordinated workstreams, ownership, and measurement. CX Codex +1 ★ 450repo stars configure-rewards configure-rewards orchestrates reward catalog setup, fulfillment workflows, and QA verification prior to a loyalty program launch. CX Codex +1 ★ 450repo stars configure-branches The configure-branches command for Claude Code generates step-by-step instructions for configuring branching, personalization, and automations in nurture campaigns. CX Codex +1 ★ 450repo stars run-standups run-standups runs a daily MQL→SQL pipeline standup, pulling routing metrics, logging blockers and assigning follow-up actions. CX Codex +1 ★ 450repo stars connect-signals connect-signals sets up data connections, schema alignment, and monitoring for B2B intent, product, and engagement feeds. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open