RevenueOps KPI tree (what must be owned)
Most RevenueOps JDs fail because they list “responsibilities” without specifying the KPI tree.
If you cannot name the KPIs and their upstream inputs, you cannot define ownership.
Example measures to define for your own model
There is no universal minimum KPI tree. Definitions, segments, and reporting windows depend on the business model and source data. These are examples to consider, not a benchmark:
Revenue layer
- Bookings / ARR / MRR
- Win rate
- Sales cycle length
Pipeline layer
- Pipeline created
- Pipeline coverage
- Pipeline velocity
Conversion layer
- Lead → SQL
- SQL → Opportunity
- Opportunity → Closed won
Quality layer
- Stage conversion integrity (definitions + enforcement)
- Duplicate / routing / attribution hygiene
The instrumentation implication
If the tools cannot measure the inputs, the KPI tree is fiction.
For a cross-functional issue, the Growth Team Audit can clarify which measures, owners, and instrumentation questions belong in scope.