Revenue Cockpit
One board composing Efficiency, Attribution, Win/Loss and Forecast Governance into a single revenue-health read.
Included with crocronjob . A seat without it sees an upsell here instead of the page.
Overview
Revenue Cockpit is the CRO's whole-revenue view in one place. Rather than open four surfaces separately, it composes the top-line output of each, Efficiency, Attribution, Win/Loss, and Forecast Governance, into a single revenue-health read and one worklist. It is reuse-first: it re-scores nothing, it blends numbers those surfaces already produce.
What it is for, on the page. Under the headline, this page says what it produces, what makes it run, and where the output lands. Every Work page reads that line from one registry, so the three answers cannot drift from the page.
One number, one risk
The cockpit reads each surface's headline, the efficiency band, NRR and GRR, win rate, forecast reliability, and blends the ones it has into a composite revenue-health score banded strong, watch, or at-risk. It then names the single worst area as the top risk, so the board conversation starts with the one thing to fix rather than a tour of every metric. Attribution is shown as context, the top sourcing channel, rather than scored as health.
Filled in from your own surfaces
Opening the page reads what the four surfaces already know and fills those inputs in for you, each labelled From your data. Six of the seven can come from your stored book: NRR and GRR from the ARR on your accounts, win rate and the top headwind from your closed opps, forecast reliability from the commits that have closed, and the top sourcing channel from the touches on your opps. Every prefilled value stays editable, so a number you disagree with is one you can type over before composing.
An input the product cannot know says why in place of a number. Efficiency band is always one of those: it needs your sales-and-marketing spend and net new ARR, which the product does not store, so you enter it from Efficiency. Where you have nothing stored yet, the page says so plainly rather than showing zeros, and the inputs fill themselves once you connect a CRM or import a CSV.
Honest about what it knows
A surface you have not filled in stays unknown and does not drag the composite down, so a partial cockpit is still useful and never falsely pessimistic. Nothing is invented: every prefilled figure is the underlying surface's own number or straightforward arithmetic on it, never an estimate. Forecast reliability is the one conversion, and it is an identity rather than a guess: governance measures mean absolute error, and reliability is one minus that. A surface that cannot evidence a number leaves the field blank instead of offering a plausible one.
If the prefill read itself fails, the page says the read failed. It does not fall back to empty inputs, because "you have no data" is a claim about your business and a failed request is not evidence for it.
Deterministic
The composition is deterministic: the same top-line numbers always produce the same revenue-health read and the same top risk, so the cockpit holds up as the single slide a CRO opens a board update with.