Alignment, signed
Every number in the plan traces to a definition somebody signed. Lifecycles, handoffs, metrics, offerings and goals — defined once, signed by each function, published as one versioned document.
Create your workspaceSee how it works
Definitions signed by every function · one versioned document
Revenue operations charter
| Qualified opportunity A deal with a named economic buyer, a written need and a date — created only after the S2 → S3 handoff is accepted. | PNMT |
| Pipeline coverage Open pipeline in the quarter divided by the quarter’s committed revenue goal. | DRF |
The loop
None of this is a workshop artefact. Every move leaves a record in the document — a definition, a signature, a version number — and the next move builds on the last.
Deal and customer lifecycles, the handoffs between your five functions, and what every metric actually counts.
Each function signs only what binds it — a face on every definition, a date on every signature.
One score: what share of your definitions carry current signatures. Edit one and it goes stale by itself.
Goals exist only through campaigns — each tied to a metric, a window, and the function that owns it.
A versioned, redlined document with your logo on it, ratified by the owner and shareable by link.
Sign-off
Change one clause and every signature on it goes stale — visibly, in the document, with the name of whoever has to look again.
From the document · § 4 metric definitions
| Qualified opportunity | PN |
| Pipeline coverage | DR |
| Activation, day 30 | CS |
| Net revenue retention | AS |
These three states are the whole of the alignment score — 86% of this charter’s definitions carry a current signature.
Substance
Six things the charter does that a deck cannot. Each one is a mechanism in the product — enforced by it — rather than a line on a slide.
Each function signs only what binds it. A signature pins to the exact wording — edit a signed definition and it reads stale until re-approved. The owner alone ratifies.
A single number for the whole org: what share of your definitions carry current signatures. It sits on the charter's cover, where nobody can miss it.
Your logo, a table of contents, semver versions (major = ratified), tracked-changes redlines between any two versions, print-ready as it stands.
What you sell, its value, its nature and its margin — with the talk track written in markdown and versioned alongside everything else.
A goal is a claim: this intervention, this window, this metric, this owner. The charter's goal inventory derives from them — nobody edits a goal cell.
Monthly actuals, computed baselines, self-explaining forecasts and an honest prediction scoreboard — parked one tab away until you want them. API and MCP included.
Measurement
Actuals, a computed baseline, the goal line you committed to, and a forecast frozen before the month it predicts.
Live component, not a mockup — hover any month for its exact values; every series is labelled at its right end, and on a narrow screen the panel scrolls sideways to reach them.
The funnel
Stages are yours: rename them, add them, reorder them. All three metric families regenerate against whatever shape your lifecycle actually has.
The lifecycle boundaries your team argues about — TOFU, MOFU, BOFU — stay where the product puts them: on hover, not in the headline.