Skip to main content
command CX Codex

build-capacity-plan — Claude Code command: what it does

build-capacity-plan turns a revenue target into headcount, quota and productivity scenarios for base, upside and downside cases, with a hiring plan attached.

Apache-2.0 ★ 450 updated 2026-04-03

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

What build-capacity-plan does

You hand it a bookings or ARR goal through --target, plus a segment, a horizon and the scenarios you want in the output. Ramp months, win rate, ACV and attrition go into an optional JSON block passed as --assumptions. Everything else comes from the pipeline numbers it gathers first.

The workflow runs in stages. Coverage, attainment, win rates and productivity benchmarks get pulled together; ramp curves, hiring plans and attrition are applied per scenario; then it works out rep count, quota per rep and monthly bookings. The closing stages mark the distance to target and name the levers that could close it. Modelling belongs to the capacity-planner subagent, coverage checks to territory-architect, quota design to compensation-architect.

Output is a table that compares scenarios on headcount, quota, bookings and the gap left, a hiring plan with a ramp schedule, and recommendations written for CRO, RevOps and finance. It arrives as a summary deck plus a spreadsheet whose tables are ready to pivot. Segment is optional; the revenue goal is not — drop --target and there is nothing to model.

What it helps with

  • size the rep team needed to hit next year's number
  • compare base, upside and downside hiring scenarios
  • check whether the quota plan survives current attrition
  • build a hiring schedule with ramp timelines
  • show where pipeline coverage falls short of the target

Example prompts for the agent

  • /sales-operations:build-capacity-plan --target 220M --segment enterprise --horizon FY26 --scenarios base,upside,downside
  • Rerun /sales-operations:build-capacity-plan for the smb segment over rolling-12 and add a scenario with heavier attrition.
  • Run /sales-operations:build-capacity-plan --target 220M --horizon FY26 and tell me which month the headcount gap peaks.

How to install build-capacity-plan

Manually: put the files in place

.claude/commands/build-capacity-plan.md

Call it with /build-capacity-plan. For all projects use ~/.claude/commands/

Questions about build-capacity-plan

How do I install build-capacity-plan in Claude Code?

Save the command file as .claude/commands/build-capacity-plan.md. It then runs as /sales-operations:build-capacity-plan.

What does build-capacity-plan do?

It works out the headcount and quota needed to reach a revenue goal, then breaks the result down by scenario, month and segment.

Which arguments does it take?

--target for the revenue goal, optional --segment, --horizon, a comma-separated --scenarios list, and --assumptions as JSON covering ramp, win rate, ACV and attrition.

Source text

build-capacity-plan.md · Apache-2.0
---
name: build-capacity-plan
description: Produces headcount, quota, and productivity scenarios mapped to revenue targets.
usage: /sales-operations:build-capacity-plan --target 220M --segment enterprise --horizon FY26 --scenarios base,upside,downside
---

# Command: build-capacity-plan

## Inputs
- **target** – bookings/ARR goal to model.
- **segment** – optional focus segment(s) (enterprise, commercial, smb, partner).
- **horizon** – time period (quarter, FY, rolling-12).
- **scenarios** – comma-separated list of scenarios to generate.
- **assumptions** – optional JSON (ramp months, win rate, ACV, attrition).

## Workflow
1. **Data Pull** – gather pipeline coverage, quota attainment, win rates, and productivity benchmarks.
2. **Assumption Alignment** – apply ramp curves, hiring plans, and attrition to each scenario.
3. **Capacity Modeling** – calculate required headcount, quota per rep, and bookings contribution by month.
4. **Risk & Sensitivity** – highlight gaps vs target, identify levers (enablement, hiring, pricing).
5. **Deliverables** – assemble summary deck and spreadsheet with pivot-ready tables.

## Outputs
- Scenario comparison table (headcount, quota, bookings, gap).
- Hiring plan + ramp schedule.
- Action recommendations for CRO/RevOps/Finance.

## Agent/Skill Invocations
- `capacity-planner` – runs modeling + analysis.
- `territory-architect` – validates coverage alignment.
- `compensation-architect` – ensures quota design fits incentive plans.
- `capacity-modeling` skill – provides calculators + formulas.
- `quota-health` skill – evaluates attainment distribution + risk.

---

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

Similar slash commands

All slash commands for Finance and business →
capacity-planner claude-code-skills capacity-planner models operations staffing for queued work using demand, utilization and SLA risk. Use it before a headcount budget or a hiring-plan review. CX Codex +1 294installs capacity-plan official anthropics capacity-plan is a Claude Code skill that analyzes workload and forecasts team capacity. It runs for quarterly planning, hiring decisions, or checks on whether upcoming projects fit current staffing. CX Codex +1 3,000installs quota-setting-calculator OneWave-AI quota-setting-calculator — a skill for Claude Code, Codex, Cursor and other platforms that builds top-down or bottom-up sales quota models. Takes historical attainment, market growth, ramp periods and territory complexity into account. CX Codex +1 329installs sales-quota-setting Maya-Beth Finotti sales-quota-setting — a skill that derives sales quotas for a team or company: ramp-adjusted capacity modeling, top-down target reconciled against a bottom-up build, territory allocation. CX Codex +1 33,600installs sales-operations borghei sales-operations — a skill for sales analytics: builds pipeline reports, designs territories, models quotas, and architectures compensation plans. Use it to audit CRM data quality or set evidence-based targets across your team. CX Codex +1 286installs sales-ops-analyst ncklrs sales-ops-analyst hands the agent a sales-ops playbook: pipeline maths, lead routing, territories, comp plans and forecasting. Useful when a number needs to be worked out, not guessed. CX Codex +1 251installs

From the same set224

The whole set →
run-partner-qbr run-partner-qbr builds a partner QBR/EBR packet with metrics, joint programs, and follow-up actions. Use it to prepare a review for executives or partner leadership. CX Codex +1 ★ 450repo stars synthesize-insights synthesize-insights turns scattered customer feedback and usage numbers into one brief for leadership: themes, quotes, metrics and owners. CX Codex +1 ★ 450repo stars audit-provider-health audit-provider-health assesses enrichment provider latency, quality, and credit spend. Useful for reviewing supplier SLAs and cleaning up data pipelines. CX Codex +1 ★ 450repo stars case-studies case-studies — a Claude Code skill that structures customer stories using the CHIC framework: Challenge, Hypothesis, Implementation, Change. Runs whenever sales needs proof points or marketing is building a social-proof campaign. CX Codex +1 ★ 450repo stars inspect-pipeline-levers inspect-pipeline-levers diagnoses sales pipeline coverage, conversion velocity, and deal friction directly inside CRM data. CX Codex +1 ★ 450repo stars activate-program activate-program is a Claude Code command that turns a candidate roster into a live advocacy program by assigning owners, triggering approvals, and starting outreach tracking. CX Codex +1 ★ 450repo stars operationalize-pql-routing operationalize-pql-routing turns product signals into a scoring and routing plan for product-qualified leads, then hands back a spec, an automation checklist and a follow-up playbook. CX Codex +1 ★ 450repo stars build-value-narrative build-value-narrative — a Claude Code command that generates ROI/TCO models, executive storylines, and proof appendices for complex deals. Runs against a named opportunity with industry, scenarios, and target exec roles as inputs. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open