AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

revenue-operations

Use for pipeline coverage, forecast accuracy or GTM efficiency (magic number, CAC payback). Runs pipeline_analyzer.py, forecast_accuracy_tracker.py and gtm_efficiency_calculator.py.

Original source
alirezarezvani
License
MIT
Pinned revision
e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read alirezarezvani--revenue-operations at revision e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 7

assets/forecast_report_template.md

Forecast Accuracy Report - [Period]

Report Details

  • Prepared By: [Name]
  • Report Date: [YYYY-MM-DD]
  • Period Analyzed: [Start Period] to [End Period]
  • Periods Covered: [N] periods

Executive Summary

| Metric | Value | Rating | Trend | |--------|-------|--------|-------| | MAPE | _% | | | | Weighted MAPE | _% | | | | Forecast Bias | _% | | | | Bias Direction | | | |

Accuracy Rating:

  • Excellent (<10%) / Good (10-15%) / Fair (15-25%) / Poor (>25%)

Key Finding: [1-2 sentence summary of forecast accuracy status]


Period-by-Period Analysis

| Period | Forecast | Actual | Variance | Error % | Bias | |--------|----------|--------|----------|---------|------| | | $_ | $_ | $_ | % | Over/Under | | | $ | $_ | $_ | % | Over/Under | | | $ | $_ | $_ | % | Over/Under | | | $ | $_ | $_ | % | Over/Under | | | $ | $_ | $_ | % | Over/Under | | | $ | $_ | $_ | _% | Over/Under |


Bias Analysis

Overall Bias

  • Direction: [Over-forecasting / Under-forecasting / Balanced]
  • Bias Magnitude: _%
  • Over-forecast Periods: _ of _
  • Under-forecast Periods: _ of _
  • Bias Ratio: _ (1.0 = always over, 0.0 = always under, 0.5 = balanced)

Interpretation

[What does the bias pattern tell us about our forecasting process? Is it systematic or random?]

Root Cause

[Identify the primary drivers of bias: optimistic deal assessment, poor stage qualification, sandbagging, late-arriving deals, etc.]


Trend Analysis

Accuracy Trend

  • Direction: [Improving / Stable / Declining]
  • Early Period MAPE: _%
  • Recent Period MAPE: _%
  • MAPE Change: _% (positive = worsening, negative = improving)

Trend Chart (Text)

Period    Error%    Trend
Q1        __%      ████████
Q2        __%      ██████████
Q3        __%      ██████
Q4        __%      ████████████

Category Breakdown

By Rep

| Rep | Forecast | Actual | Error % | Bias | Rating | |-----|----------|--------|---------|------|--------| | | $_ | $_ | % | | | | | $ | $_ | % | | | | | $ | $_ | % | | | | | $ | $_ | _% | | |

Overall Rep MAPE: _%

By Segment

| Segment | Forecast | Actual | Error % | Bias | Rating | |---------|----------|--------|---------|------|--------| | Enterprise | $_ | $_ | % | | | | Mid-Market | $ | $_ | % | | | | SMB | $ | $_ | _% | | |

Overall Segment MAPE: _%

By Product (if applicable)

| Product | Forecast | Actual | Error % | Bias | Rating | |---------|----------|--------|---------|------|--------| | | $_ | $_ | % | | | | | $ | $_ | _% | | |


Recommendations

Immediate Actions (This Quarter)

  1. [Action] -- [Why and expected impact]
  2. [Action] -- [Why and expected impact]
  3. [Action] -- [Why and expected impact]

Process Improvements (Next Quarter)

  1. [Improvement] -- [Implementation plan]
  2. [Improvement] -- [Implementation plan]

Coaching Focus Areas

| Rep/Team | Issue | Coaching Action | Target | |----------|-------|-----------------|--------| | | | | | | | | | |


Forecast Methodology Notes

Current Methodology

[Describe the current forecasting methodology: weighted pipeline, commit/upside categories, AI-assisted, etc.]

Methodology Changes This Period

[Any changes to the forecasting process or methodology during the reporting period]

Data Quality Issues

[Note any data quality issues that may affect accuracy: missing close dates, inconsistent stage definitions, CRM hygiene gaps]


Next Steps

| # | Action | Owner | Due Date | |---|--------|-------|----------| | 1 | | | | | 2 | | | | | 3 | | | |