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
.claude/commands/prioritize-accounts.mdWhat 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.mdCall it with /prioritize-accounts. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/prioritize-accounts.mdCall it with /prompts:prioritize-accounts. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/prioritize-accounts.prompt.mdManually: put the files in place
.gemini/commands/prioritize-accounts.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
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