Circulos AI

Finance AI Skill

Revenue Forecasting

Generate accurate revenue forecasts using historical data, seasonality patterns, market trends, and predictive analytics. Use when building revenue models, creating quarterly/annual forecasts, generating best/worst/likely scenarios, calculating confidence intervals, or monitoring forecast accuracy. Triggers on phrases like "revenue forecast", "predict revenue", "forecast model", "revenue projection", "top-line forecast", "ARR forecast", "MRR forecast", "seasonal adjustment".

Revenue Forecasting

Generate data-driven revenue forecasts with scenario modeling and confidence intervals.

Workflow

  1. Aggregate historical revenue data (minimum 3 years, monthly granularity) — total revenue by product, region, segment, channel.
  2. Incorporate pipeline data from CRM: weighted pipeline by stage, rep close rates, deal cycle, win rates.
  3. Integrate external factors: economic indicators, industry benchmarks, competitor activity, product launches.
  4. Engineer features: YoY growth rates, rolling averages, cohort retention curves, channel attribution.
  5. Run parallel models: time-series (ARIMA, Prophet), ML (Random Forest, XGBoost), driver-based (leads × conversion × ACV).
  6. Generate scenario variants: base case (60%), upside (20%), downside (20%).
  7. Calculate confidence intervals: 80% and 95% prediction bands with historical accuracy metrics.
  8. Produce deliverables: monthly/quarterly forecast, executive summary, scenario charts, variance drivers.
  9. Set up monitoring: actuals vs. forecast, accuracy tracking (target <5% MAPE), deviation alerts.
  10. Monthly refresh: update assumptions, re-run models, adjust forecast, document changes.

Forecast Methodologies

Methodology by Revenue Type

REVENUE FORECASTING BY BUSINESS MODEL
=======================================

SaaS / Subscription Revenue:
  Formula: ARR = (Beginning ARR + New Logos + Expansion) − (Gross Churn + Logo Churn)
  Components:
    New Logo ARR: Pipeline × Win Rate × ACV × Sales Cycle Adjustment
    Expansion ARR: Existing ARR × Net Expansion Rate (typically 10–30%)
    Gross Churn: Existing ARR × Gross Churn Rate (typically 3–10% annual)
    Logo Churn: % of customers lost × average contract value

  Forecasting approach:
    - Cohort-based: Track each quarterly cohort's revenue over lifetime
    - Pipeline-weighted: Stage-based probability (Prospecting 10%, Qualification 25%, Proposal 50%, Negotiation 75%, Closed 100%)
    - Run-rate: Current MRR × 12 (simple but ignores seasonality and churn)
    - Best practice: Combine cohort analysis + pipeline weighting + expansion trends

  Key metrics to forecast:
    - MRR/ARR growth rate: 20–50% for high-growth, 5–15% for mature
    - Net Revenue Retention (NRR): 100–130%+ for healthy SaaS
    - Gross Revenue Retention (GRR): 85–95% for healthy SaaS
    - Sales velocity: Deal cycle × win rate × ACV
    - CAC payback: CAC / (Monthly revenue per customer × Gross margin)
    - Target payback: < 12 months (growth), < 18 months (mature)

Transaction / E-commerce Revenue:
  Formula: Revenue = Traffic × Conversion Rate × Average Order Value (AOV)
  Components:
    Traffic: Organic + Paid + Direct + Referral + Social (by channel)
    Conversion Rate: 1–3% (typical e-commerce), 2–5% (best-in-class)
    AOV: Average order value by product category and channel
    Repeat Purchase Rate: 20–40% for e-commerce within 90 days

  Forecasting approach:
    - Channel-based: Forecast traffic and conversion by channel separately
    - Seasonality: Apply monthly seasonality indices (e.g., November = 2.5x baseline)
    - Campaign-driven: Model specific marketing campaign impacts
    - Product mix: Category-level revenue forecasts rolled up

  Key metrics:
    - Customer Acquisition Cost (CAC): $50–$500 (varies by industry)
    - Lifetime Value (LTV): Target LTV:CAC > 3:1
    - Return customer rate: > 40% for healthy e-commerce
    - Cart abandonment rate: 60–80% (industry standard)

Professional Services / Project Revenue:
  Formula: Revenue = Billable Hours × Rate + Fixed-Fee Projects
  Components:
    Utilization Rate: % of available time billed to clients (target 70–85%)
    Billing Rate: Average hourly rate by consultant level ($100–$500/hr)
    Project Pipeline: Committed + In Negotiation + Prospecting (weighted)
    Headcount: Billable staff count with ramp-up curves for new hires

  Forecasting approach:
    - Project-based: Top-down from committed project backlog
    - Utilization-based: Headcount × target utilization × billing rate × hours/month
    - Pipeline-weighted: Similar to SaaS but with longer sales cycles (3–12 months)
    - Blend: Weighted average of project commitments (70%) + utilization model (30%)

  Key metrics:
    - Bench rate: Non-billable cost per consultant ($5K–$15K/month)
    - Project gross margin: 25–45%
    - Sell-through rate: Committed revenue / available capacity (target > 1.2x)
    - Backlog: Committed but undelivered revenue (target 3–6 months of quarterly run rate)

Manufacturing / Product Revenue:
  Formula: Revenue = Units Sold × Price (by product/SKU)
  Components:
    Unit demand forecast: Historical sales + new orders + market intelligence
    Price changes: Planned price increases, discounts, promotions
    Product mix: Revenue contribution by product line/SKU
    Channel distribution: Direct, distributor, retail by volume

  Forecasting approach:
    - SKU-level: Bottom-up from individual product forecasts
    - Demand planning: Statistical forecast + sales input + market intelligence
    - Rolling 13-week: Near-term accuracy critical for production planning
    - Annual: Strategic forecast for capacity and procurement planning

  Key metrics:
    - Forecast accuracy: Target > 80% at SKU level, > 90% at category
    - Sell-through rate: Units sold / units shipped to channel
    - Inventory turns: COGS / average inventory (target 4–8x annually)
    - Fill rate: % of demand met from stock (target > 95%)

Forecast Model Comparison

FORECAST MODEL PERFORMANCE BY SCENARIO
========================================

Time-Series Models:
  Simple Moving Average:
    - Use case: Stable revenue, no trend, minimal seasonality
    - Accuracy: MAPE 8–15%
    - Window: 3-month (volatile), 6-month (moderate), 12-month (stable)
    - Limitation: Ignores trend and seasonality; lagging indicator

  Exponential Smoothing (Holt-Winters):
    - Use case: Revenue with trend and seasonality
    - Accuracy: MAPE 5–10%
    - Parameters: Alpha (level 0.1–0.3), Beta (trend 0.01–0.1), Gamma (seasonality 0.01–0.1)
    - Handles: Monthly, weekly, and daily seasonality patterns
    - Best for: 3–12 month forecasts with established patterns

  ARIMA / SARIMA:
    - Use case: Complex time-series with multiple seasonal patterns
    - Accuracy: MAPE 3–8%
    - Parameters: p (autoregressive), d (differencing), q (moving average)
    - SARIMA adds: P (seasonal AR), D (seasonal differencing), Q (seasonal MA), s (seasonal period)
    - Best for: Monthly data with clear seasonal patterns; requires 24+ data points
    - Limitation: Extrapolates past patterns; blind to structural changes

  Prophet (Meta/Facebook):
    - Use case: Revenue with strong seasonality, holidays, and structural changes
    - Accuracy: MAPE 4–9%
    - Features: Handles missing data, shifts trend automatically, supports custom holidays
    - Parameters: Changepoint prior (0.05–0.5), seasonality prior (5–10), holidays
    - Best for: Business time-series with known holidays and events
    - Limitation: Less accurate for very short series (< 2 years)

Machine Learning Models:
  Random Forest / XGBoost:
    - Use case: Multiple revenue drivers, non-linear relationships
    - Accuracy: MAPE 3–7%
    - Features: Incorporates 10–50+ variables (pipeline, marketing spend, economic data)
    - Feature importance: Identifies key revenue drivers
    - Best for: 1–6 month forecasts with rich feature sets
    - Limitation: Requires training data; less interpretable than time-series

  LSTM (Deep Learning):
    - Use case: Long-term patterns, complex temporal dependencies
    - Accuracy: MAPE 2–6% (with sufficient data)
    - Requirements: 5+ years of data, GPU computation, ML engineering expertise
    - Best for: Enterprise with dedicated ML team and rich data
    - Limitation: Overkill for simple revenue patterns; hard to explain to business users

Driver-Based Models:
  Formula models:
    - Revenue = Leads × Conversion Rate × ACV × (1 + Growth Rate)
    - SaaS: MRR = Σ(customer MRR) adjusted for churn and expansion
    - E-commerce: Revenue = Traffic × CR × AOV × (1 + Seasonality)
    - Accuracy: MAPE 5–15% (depends on driver accuracy)
    - Best for: Strategic planning, scenario analysis, explaining "why"
    - Advantage: Transparent, intuitive, easily communicated to leadership

Scenario Planning

Three-Scenario Framework

THREE-SCENARIO REVENUE FORECAST
=================================

Base Case (60% probability):
  Assumptions:
    - Economic conditions: Stable GDP growth 2–3%, no recession
    - Market: Industry growth at historical average (e.g., 8–12% for SaaS)
    - Execution: Plan achieves on target; no major setbacks
    - Competitive: Stable market share; no disruptive competitor moves
    - Product: Roadmap delivered on schedule
    - Headcount: Hiring plan executed as planned

  Revenue projection: $XXXM
  Growth rate: X.X%
  Margin: X.X%

Upside Case (20% probability):
  Assumptions:
    - Economic conditions: GDP growth 3–4%, consumer confidence high
    - Market: Industry outperforms expectations (+2–4% above average)
    - Execution: Key deals closed early; conversion rates 10–20% above plan
    - Competitive: Market share gains; competitor weakness
    - Product: Early product launches exceed adoption targets
    - Additional: M&A opportunity realized; new channel partnership

  Revenue projection: $XXXM (+15–25% vs. base)
  Growth rate: X.X%
  Margin: X.X%

Downside Case (20% probability):
  Assumptions:
    - Economic conditions: GDP growth 0–1%, mild recession indicators
    - Market: Industry slows; budget cuts in key segments
    - Execution: Key deals delayed; sales cycle extends 20–30%
    - Competitive: Aggressive competitor pricing; market share pressure
    - Product: Launch delays; adoption slower than expected
    - Additional: Key customer loss; regulatory headwinds

  Revenue projection: $XXXM (-10–20% vs. base)
  Growth rate: X.X%
  Margin: X.X%
  Contingency: Cost reduction plan triggered at < 80% of base revenue

Sensitivity Analysis

REVENUE SENSITIVITY ANALYSIS
=============================

Variable              | Base | -10% Impact | +10% Impact
----------------------|------|-------------|------------
New Logo Deals        | $X.XM | -$X.XX M    | +$X.XX M
Win Rate              | XX%  | -$X.XX M    | +$X.XX M
Average Deal Size     | $XXK  | -$X.XX M    | +$X.XX M
Churn Rate            | X.X% | +$X.XX M    | -$X.XX M
Expansion Revenue     | $X.XM | -$X.XX M    | +$X.XX M
Sales Headcount       | XX   | -$X.XX M    | +$X.XX M
Sales Cycle Length    | XX d | -$X.XX M    | +$X.XX M
Pricing               | $XX  | -$X.XX M    | +$X.XX M

Key insight: Revenue most sensitive to [variable] — a 10% change impacts revenue by $X.XM
  → Focus improvement efforts here for maximum impact
  → Monitor this variable weekly for early warning signals

Forecast Accuracy Monitoring

Accuracy Scorecard

FORECAST ACCURACY SCORECARD
============================

Metric                          | Target     | Current    | Trend
--------------------------------|------------|------------|------
MAPE (Mean Absolute % Error)    | < 5%       | X.X%       | →
RMSE (Root Mean Square Error)   | Track      | $XXXK      | →
Directional Accuracy            | > 80%      | XX%        | →
Bias (Systematic Over/Under)    | < ±1%      | +X.X%      | →
Month-1 Forecast Accuracy       | > 95%      | XX%        | →
Month-3 Forecast Accuracy       | > 85%      | XX%        | →
Quarter-End Forecast Accuracy   | > 90%      | XX%        | →
Annual Forecast Accuracy        | > 80%      | XX%        | →

MAPE Calculation:
  MAPE = (1/n) × Σ(|Actual − Forecast| / Actual) × 100
  By month: Track monthly MAPE for trend analysis
  By segment: Identify which product/region has worst accuracy
  By model: Compare model performance for continuous improvement

Common accuracy patterns:
  - First quarter after budget: MAPE typically 8–15% (biggest changes)
  - Mid-year quarters: MAPE typically 3–7% (refined assumptions)
  - Fourth quarter: MAPE can spike if year-end push varies
  - SaaS revenue: MAPE typically 2–5% (stable recurring)
  - Project revenue: MAPE typically 10–20% (lumpy, deal-dependent)

Edge Cases

Integration Points

Disclaimer: All rights reserved by Circulos AI. These skills are specifically designed for Claude Code, Claude Cowork, Codex, and OpenClaw. When using or referencing any skill, please provide proper attribution to Circulos AI.