Run Forecast

Generates revenue forecast scenarios, compares to targets, and highlights risks/opportunities.

Published by @gtmagents·0 agent reads / 30d·0 saves·

Command: run-forecast

Inputs

  • timeframe – period to forecast (Q1, Q2, FY, rolling-90).
  • scenario – base | upside | downside | custom.
  • confidence – numeric (0-1) to tune risk weighting.
  • drivers – optional overrides for win rates, ASP, capacity, churn, expansion.
  • notes – optional context for scenario assumptions.

Workflow

  1. Input Gathering – pull pipeline snapshot, bookings actuals, macro assumptions, and overrides.
  2. Driver Application – adjust conversion rates, stage weightings, and coverage multipliers per scenario.
  3. Model Execution – compute bookings forecast, ARR impact, cash flow pacing, and contribution by segment.
  4. Variance Comparison – benchmark vs targets, prior forecast, and budget.
  5. Insights & Actions – flag risk areas, required pipeline creation, and mitigation plays.

Outputs

  • Scenario forecast table (segment → commit/upside/downside → delta vs goal).
  • Driver sheet summarizing assumptions and overrides.
  • Action plan for pipeline creation or acceleration.

Agent/Skill Invocations

  • forecast-architect – owns methodology and interpretation.
  • forecast-modeling skill – provides model templates + sensitivity analysis.
  • revops-analyst – validates inputs and risk tags.

More on the bench

SKILL0

Vendor Management

Evaluate, compare, and manage vendor relationships. Trigger with "evaluate this vendor", "compare vendors", "vendor review", "should we renew", "RFP", or when the user is making procurement or vendor decisions.

sales-gtm-revops+1
0
SKILL0

Qbr Builder

Create Quarterly Business Reviews with account health scores, usage analytics, ROI analysis, expansion opportunities, and risk mitigation

customer-success+1
0
SKILL0

Escalation

Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.

customer-success+2
0