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
.claude/commands/build-capacity-plan.mdWhat 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-planfor the smb segment over rolling-12 and add a scenario with heavier attrition. - Run
/sales-operations:build-capacity-plan --target 220M --horizon FY26and 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.mdCall it with /build-capacity-plan. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/build-capacity-plan.mdCall it with /prompts:build-capacity-plan. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/build-capacity-plan.prompt.mdManually: put the files in place
.gemini/commands/build-capacity-plan.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
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