Skip to main content
Generalgtmagents

variance-analysis

Use to attribute forecast vs actual deltas and recommend remediation

Stars
259
Source
gtmagents/gtm-agents
Updated
2026-04-03
Slug
gtmagents--gtm-agents--variance-analysis
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/gtmagents/gtm-agents/HEAD/plugins/revenue-forecasting-pipeline/skills/variance-analysis/SKILL.md -o .claude/skills/variance-analysis.md

Drops the SKILL.md into .claude/skills/variance-analysis.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Revenue Variance Analysis Skill

When to Use

  • Preparing forecast reviews or board updates that require variance explanations.
  • Investigating misses/exceeds across segments, products, or channels.
  • Prioritizing remediation plays tied to specific variance drivers.

Framework

  1. Driver Taxonomy – classify deltas into volume, conversion, price/mix, churn, expansion, currency.
  2. Attribution Logic – define formulas for each driver and maintain consistent baselines.
  3. Root Cause Layer – connect drivers to operational issues (pipeline quality, capacity, enablement, macro).
  4. Action Mapping – translate each root cause into specific plays with owners and expected impact.
  5. Feedback Loop – update forecasting assumptions once variance is understood.

Templates

  • Variance waterfall chart setup instructions.
  • Driver worksheet (metric → delta → driver → root cause → owner → due date).
  • Remediation tracker with status and forecast impact.

Tips

  • Keep a glossary so stakeholders interpret drivers consistently.
  • Combine quantitative attribution with qualitative context from GTM leaders.
  • Feed learnings back to forecast-modeling to tighten assumptions next cycle.