revenue-operations_skill

This skill helps SaaS teams optimize revenue operations by analyzing pipeline coverage, forecasting accuracy, and GTM efficiency to drive growth.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill revenue-operations

  • _meta.json474 B
  • SKILL.md9.2 KB

Overview

This skill analyzes pipeline coverage, measures forecast accuracy using MAPE, and calculates GTM efficiency metrics to optimize SaaS revenue performance. It provides actionable indicators like coverage ratios, deal aging flags, forecast bias, and core unit-economics scores to guide weekly, monthly, and quarterly revenue reviews. The outputs support both human-readable reports and JSON for dashboarding or integrations.

How this skill works

You feed the skill structured JSON for deals, forecasts, or financials. The pipeline analyzer computes coverage ratios, stage conversion rates, velocity, aging and concentration risks. The forecast tracker computes MAPE, weighted accuracy, and bias trends. The GTM calculator derives Magic Number, LTV:CAC, CAC payback, Burn Multiple, Rule of 40, and NDR with industry targets and ratings.

When to use it

  • Weekly pipeline reviews to surface aging deals, coverage gaps, and concentration risk.
  • Monthly/quarterly forecast accuracy checks to monitor MAPE and detect systematic bias.
  • Quarterly GTM efficiency audits for board prep and budgeting decisions.
  • Before sales capacity planning or quota setting to validate pipeline coverage.
  • During post-mortems when forecasts missed targets to identify root causes.

Best practices

  • Provide clean, consistent JSON inputs with standardized stage names and dates.
  • Weight forecast accuracy by deal value to focus on material error sources.
  • Use 3–4x pipeline coverage as a working benchmark, then adjust by funnel conversion.
  • Flag deals older than 2x average stage cycle time for immediate review.
  • Combine forward-looking pipeline signals with backward-looking MAPE in QBRs.

Example use cases

  • Generate a weekly pipeline report to identify top 10 at-risk deals and coverage shortfalls.
  • Run forecast accuracy history to calculate MAPE and coach reps with high bias.
  • Compute Magic Number and CAC payback to inform next quarter’s S&M budget.
  • Produce a combined QBR packet showing pipeline health, forecast accuracy, and GTM efficiency.
  • Create JSON outputs for BI dashboards to track trends and automated alerts.

FAQ

The skill expects structured JSON for pipeline, forecast, and GTM data; outputs can be text or JSON for integration.

How is forecast accuracy measured?

MAPE (Mean Absolute Percentage Error) is the primary metric, with optional value-weighted MAPE and bias analysis.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational