Skip to main content
command CX Codex

forecast-renewals — Claude Code command: renewal forecasting

forecast-renewals — a command that builds segmented renewal forecasts with account health signals, variance analysis, and executive reporting. Combines ARR, NRR, and risk data into a single view.

Apache-2.0 ★ 450 updated 2026-04-03

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

What forecast-renewals does

forecast-renewals merges contract data, product usage, account health scores, and support signals, then segments them by tier, region, or vertical (enterprise, midmarket, SMB). The command runs three scenarios—base, upside, downside—with optional upsell overlays.

Output includes a forecast table with ARR, NRR, churn rate, and confidence per segment, plus a commentary deck covering drivers, blockers, and next actions. Data is stored in .claude/plans for audit trails. The command coordinates with renewal-director and cs-ops-partner agents to validate assumptions and data quality.

Forecast window is set in days or quarters (30d, 60d, 90d, quarter); detail level ranges from summary to full. If accuracy or confidence falls below threshold twice in a row, escalation triggers to Renewal Director and finance leadership.

What it helps with

  • Build segmented renewal forecast with risk scoring
  • Model base, upside and downside scenarios
  • Identify drivers and blockers per segment
  • Generate executive summary and finance report
  • Maintain forecast assumption audit trail

Example prompts for the agent

  • /renewal-orchestration:forecast-renewals --window 90d --segment enterprise --detail full
  • 60-day forecast by region with expansion scenarios: /renewal-orchestration:forecast-renewals --window 60d --segment region --include-expansion true
  • Quick SMB overview with confidence above 75%: /renewal-orchestration:forecast-renewals --segment smb --detail summary --confidence-threshold 75

How to install forecast-renewals

Manually: put the files in place

.claude/commands/forecast-renewals.md

Call it with /forecast-renewals. For all projects use ~/.claude/commands/

Questions about forecast-renewals

How do I install forecast-renewals in Claude Code?

Copy forecast-renewals.md into the .claude/commands/ directory of your project. The command will be available in Claude Code under the renewal-orchestration namespace.

What does forecast-renewals do?

The command builds segmented renewal forecasts from ARR, account health, product usage, and risk data. It models three scenarios, adds variance commentary, and produces reports for leadership.

What data does forecast-renewals require?

The command needs access to ARR, contract terms, product usage metrics, CS health scores, support tickets, and sentiment analysis. Data must be available through CS Ops and Finance integrations.

Source text

forecast-renewals.md · Apache-2.0
---
name: forecast-renewals
description: Builds segmented renewal forecasts with health signals, variance commentary, and executive-ready views.
usage: /renewal-orchestration:forecast-renewals --window 90d --segment enterprise --detail full
---

# Command: forecast-renewals

## Inputs
- **window** – time horizon (30d, 60d, 90d, quarter) to include in the forecast.
- **segment** – optional filters (enterprise, midmarket, smb, region, vertical).
- **detail** – summary | full (controls depth of commentary and tables).
- **include-expansion** – true/false toggle to incorporate upsell scenarios.
- **confidence-threshold** – percentage for highlighting low-confidence projections.

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

- **Pattern selection**: Forecast builds usually run **pipeline** (data → segmentation → scenarios → commentary → packaging). If segmentation + scenario modeling can parallelize, note a **diamond** segment and merge gate in the plan header.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing objective, filters, task IDs, parallel groups, dependency graph (CS Ops, Finance, Product), error handling, and success metrics (forecast accuracy, coverage %, confidence spread).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for data model diffs, Context7 for product/support doc pulls, Sequential Thinking for scenario retros, Playwright for dashboard QA if embedded.
- **Guardrails**: Default retry limit = 2 for failed data pulls or scenario jobs; escalation ladder = CS Ops Partner → Renewal Director → Finance lead.
- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` checklist before execution to confirm agents, dependencies, deliverables.

## Workflow
1. **Data Pull** – combine ARR, contract terms, product usage, CS health, support tickets, and sentiment data.
2. **Segmentation** – bucket accounts by tier, segment, and renewal phase; calculate coverage ratios.
3. **Scenario Modeling** – run base, upside, downside scenarios with expansion overlays.
4. **Variance Commentary** – note drivers (product adoption, exec engagement, risk flags) per segment.
5. **Package Deliverables** – produce dashboards + slides for CS leadership and finance.

## Outputs
- Renewal forecast table with ARR, NRR, churn %, and confidence per segment.
- Commentary deck with drivers, blockers, and next steps.
- Data extract for RevOps/finance to ingest into planning tools.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.

## Agent/Skill Invocations
- `renewal-director` – validates scenario assumptions and narratives.
- `cs-ops-partner` – ensures data integrity + automation hooks.
- `renewal-playbooks` skill – maps forecast insights to plays.

## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., Exec Sponsor covering Renewal Director commentary) when specialists unavailable.
- **Escalation triggers**: if accuracy or confidence guardrails fall below thresholds twice in a row, escalate to Renewal Director + Finance leadership per GTM Agents rip-cord.
- **Plan maintenance**: update plan JSON/change log whenever segments, scenario assumptions, or deliverables change to maintain GTM Agents audit parity.

---

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

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set224

The whole set →
map-journey map-journey — a Claude Code command that runs a structured journey mapping workshop, from research compilation to a gap log with assigned owners. Takes persona, scope, and time horizon as inputs. CX Codex +1 ★ 450repo stars plan-community-calendar plan-community-calendar builds a community programming calendar spanning 8 weeks or a quarter, with themes, formats, owners and dependencies. CX Codex +1 ★ 450repo stars run-survey run-survey orchestrates customer surveys with target sampling, structured question banks, and distribution steps. CX Codex +1 ★ 450repo stars configure-rules The configure-rules command takes personalization rules through data checks, decision setup, variant mapping, QA, and deployment. Use it to prepare changes for web and in-app channels. CX Codex +1 ★ 450repo stars experiment-design-kit experiment-design-kit structures product and growth hypotheses into test briefs with guardrails, variant catalogs, and rollback plans. CX Codex +1 ★ 450repo stars run-community-event run-community-event is a Claude Code command that drafts an agenda, moderation plan, and follow-up tasks for a community session or livestream. CX Codex +1 ★ 450repo stars cold-email-personalization cold-email-personalization turns a prospect brief into a cold email and a follow-up series: research first, a 60-120 word draft, then a scored QA pass. CX Codex +1 ★ 450repo stars run-retro run-retro orchestrates renewal cycle retrospectives to analyze ARR shifts, review churn patterns, and generate action trackers. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open