revenue-kpi-framework — Analytics, an agent skill published by mbfinotti/revops-skills
Analyticsmbfinotti/revops-skillsskills.sh ↗
Installs
27,718
deduplicated, at the last sync
Since we started
+480%
24 readings, about 2 days apart. Not a live curve.
Our category
Analytics
ours
Last read
Nov 22, 2026
from the directory
Our brief
oursThe revenue‑kpi‑framework skill designs the org‑wide revenue KPI framework at the macro level, deciding which metrics matter at each org level and how they roll up through a reconciling metric tree with explicit math. It assigns owners, pairs guardrail counter‑metrics, and gates the set by company stage and business model. Use it when users ask about revenue KPI frameworks, metric hierarchies, North Star metrics, driver metrics, guardrail counter‑metrics, NRR, or which revenue metrics each org level should track.
- Metric tree artifact
- Owner assignments list
- Guardrail pair mapping
- Altitude/cadence map
- Interview responses
- Company stage
- Revenue model
- Org level list
- Existing metric definitions
not detected
The evidence contains no mention of required paid services, accounts, or credentials.
not detected
The evidence contains no mention of registration requirements.
It cannot write board reports, dashboards, or SQL; those tasks are delegated to other skills. It also does not define metric definitions or encode them into a metric dictionary; those are handled by governance skills. The skill only designs the macro framework, not the final reporting artifacts.
Evidencestatic findingsskills/revenue-kpi-framework/references/guardrail-pairs.md:1-36skills/revenue-kpi-framework/references/stage-and-model-gating.md:1-29skills/revenue-kpi-framework/references/worked-metric-trees.md:1-45+1
[{"code":"payment","match":"subscription","path":"SKILL.md"},{"code":"payment","match":"subscription","path":"references/stage-and-model-gating.md"},{"code":"payment","match":"subscription","path":"references/worked-metric-trees.md"},{"code":"payment","match":"pricing","path":"references/worked-metric-trees.md"}]# Guardrail and Counter-Metric Design The mechanism behind the "one paired counter-metric per owned metric" ground rule. ## The two laws a guardrail defends against - **Goodhart's Law** (Charles Goodhart, 1975; generalized by Marilyn Strathern): "When a measure becomes a target, it ceases to be a good measure." - **Campbell's Law** (Donald Campbell, 1979): the more a quantitative indicator is used for decision-making, the more subject it becomes to corruption pressures. Manheim and Garrabrant (2018) decompose Goodhart failures into four modes, useful vocabulary for diagnosing _which way_ a metric is being gamed, not just that it is: - regressive - extremal - causal - adversarial ## Grove's paired indicators - the durable defense Andy Grove, _High Output Management_ (1983), two decades before "Goodhart's Law" became common vocabulary: indicators direct attention toward what they monitor, so guard against overreacting "by pairing indicators, so that together both effect and counter-effect are measured." His quantity/output measures each get a quality-side pair: - inventory levels with incidence of shortages - vouchers processed with errors found - square feet cleaned with a q
# Stage and Business-Model Gating The two gates every candidate metric passes before entering the framework, plus published examples and the rules for citing benchmark figures. ## Stage gate - what appears, what recedes Governing rule: - early-stage: a pass on efficiency metrics, not on retention - late-stage: a pass on growth rate, not on efficiency | Stage | Metrics that appear | Metrics that recede / premature | | ------------------ | -------------------------------------------------------------------------- | ------------------------------------------------- | | Pre-seed / Seed | Activation, engagement, early retention (Day 7/30), qualitative PMF signal | Rule of 40, burn multiple, unit-economics theater | | Series A | Growth rate, logo churn, early CAC payback, LTV:CAC baseline | Profitability | | Series B | NRR, fully-loaded LTV:CAC, gross margin by segment | Pure activation as a headline | | Series C+ / Growth | Rule of 40, burn multiple, FCF margin, magic number
# Worked Metric Trees Three worked trees and one negative example. Use the one matching the user's model as the shape to imitate - the specific metrics and owners always come from the Interview, never copied wholesale. ## Table of Contents - [Tree 1 - B2B subscription SaaS (sales-led, Series B)](#tree-1---b2b-subscription-saas-sales-led-series-b) - [Tree 2 - B2C subscription (D2C, repeat-revenue weighted)](#tree-2---b2c-subscription-d2c-repeat-revenue-weighted) - [Tree 3 - usage-based variant (what changes from Tree 1)](#tree-3---usage-based-variant-what-changes-from-tree-1) - [Negative example - a "tree" that isn't one](#negative-example---a-tree-that-isnt-one) ## Tree 1 - B2B subscription SaaS (sales-led, Series B) Top metric: **Net New ARR** (additive decomposition). NRR is reviewed beside it as the exec-level retention composite. ``` Net New ARR [owner: CRO | additive] = New Logo ARR + Expansion ARR − Churned ARR − Contraction ARR ├── New Logo ARR [owner: VP Sales | multiplicative] │ = Leads × Lead-to-Opp Conversion × Win Rate × Avg Deal Size │ ├── Qualified Pipeline [owner: VP Marketing] │ │ guardrail: SQL-to-opportunity conversion │ │ └── activity leaves
--- name: revenue-kpi-framework description: Design the org-wide revenue KPI framework at the macro level - which metrics matter at each org level from board to IC, how they roll up through a reconciling metric tree with explicit math, who owns each branch, which guardrail counter-metrics ride alongside each owned number, and how the set is gated by company stage and business model. Use whenever the user mentions a revenue KPI framework, a metric hierarchy, a KPI tree, a North Star metric, driver metrics, guardrail counter-metrics, NRR, or which revenue metrics each org level should track - even if they never say "framework". Covers B2B and B2C. Do NOT use for writing the board report itself - use mbfinotti/revops-skills@revenue-reporting instead. license: MIT metadata: author: Maya-Beth Finotti version: "1.3.2" --- # Revenue KPI Framework You are the strategic partner to revenue leadership designing the company's KPI framework: which metrics matter at which org level, and how they roll up. The deliverable is a reconciling metric tree with named owners, paired guardrails, and an altitude/cadence map - a causal model of how this business makes money, not a longer list of numbe
Read 5 of 5 text files in the skill.
Installfrom the directory
npx skills add https://github.com/mbfinotti/revops-skillsInstalling happens there, not here. We are an index with an opinion, not a mirror.
What is inside itfrom the directory
5 files — names only. The directory does not report sizes.
What the auditors foundfrom the directory
A skill is instructions your agent will follow and scripts it may run, so who checked it matters as much as how many people installed it.
Installs, reading by readingours
Axis starts at 4.8k, not zero — the range is 4.8k to 27.7k.
Asked out loudspoken, not typed
The same skill in the words people use speaking to an assistant rather than typing into a box. Each one carries the situation it came from, and each answer says only what the skill's own files support.
The evidence does not mention any payment or subscription requirement, so no paid service is needed. It is a design skill that you can use without a license or credential.
The evidence describes a design skill that only creates KPI frameworks and does not modify code or repositories. It will not touch your repo.
There is no mention of account registration in the evidence, so no account is required to use the skill.