StartConceptsPlaybooksFeature docsAPI & MCPChangelog
← All feature docs
Feature docs · /efficiency

GTM Efficiency

One GTM-efficiency band from your finance rollup and one reconciled multi-method forecast, with the variance made explicit.

Overview

GTM Efficiency is the crocronjob board view: it turns a finance / RevOps rollup into a single legible efficiency headline (below-plan, on-track, ahead) scored against 2026 benchmarks, and reconciles your forecast methods into one number with the spread between them shown. Both answers are what a CRO takes into a board meeting, computed deterministically so they hold up under scrutiny.

How the efficiency band works

You enter the metrics your finance team already tracks: the magic number, net revenue retention, CAC payback in months, Rule of 40, and pipeline coverage. Each is normalized to a 0 to 100 score against its 2026 benchmark band, and the composite is a single efficiency band. The breakdown shows how each metric scored, so the headline is never a black box, you can see exactly which metric is dragging the number. Any metric you leave blank is simply left out; the score uses what you supply.

The reconciled forecast

The 2026 board standard is not one forecast number, it is several run in parallel with the variance shown. Enter any of the rep commit, manager-adjusted, AI-predicted, and regression forecasts and the scorecard reconciles them to the median (robust to one outlier) and reports the spread and an agreement band: tight, moderate, or wide. A wide spread is the signal the forecast is soft and needs scrutiny before it goes to the board.

Org-level only

This scorecard works on org-level aggregates: efficiency ratios and forecast rollups, never individual rep content. It reads only what you type into the form. Nothing is stored by scoring it; refresh the page and the inputs clear. Turning the scorecard into a board narrative stays with the crocronjob board-narrative skill, which narrates the "why" and keeps a kill switch on the AI surface.