For revenue operations
Self-service analytics fails when every team computes revenue differently. Covirage puts the definitions in one versioned registry, applies them in code, and lets everyone ask questions that agree with finance.
When a definition changes, every past answer knows which version it used. When a question is asked, the scope gate applies before any row is read.
Net revenue v4 supersedes v3 on a date you choose. Every answer records which one it used.
A rep sees their own accounts. A manager sees their team. Enforced before the query, not in a prompt.
Who asked, what tool ran, which rows. Exportable for finance and compliance.
Three steps, in this order.
From your metrics sheet or dbt models. We keep them versioned.
Warehouse and CRM files on a schedule. Scope derived from your directory.
Every team asks. Every answer agrees with finance.
Short answers. The Help centre has the long ones.
Yes. Metric definitions can be imported from dbt and kept in sync.
Roles you set. Every change is versioned and dated.
Yes, per answer: who, when, which tool, which version, which rows.
Written for this job: the measures, the data you already hold, and the arithmetic.
How to score CRM data quality from the export rather than from complaints: five fields that every coverage and pipeline measure depends on, owner, close date, stage, activity date and account identifier, the check for each, the completeness and validity rate per rep, why the score is reported beside the measures that depend on it, and the rule that a measure computed on data under a stated score is shown greyed.
16 Sept 20263 min readHow to build and use an account hierarchy for sales analytics: the levels that exist in most customers, group, legal entity, site, department, the one level where the buying decision is made and every measure is computed, the levels beneath kept as dimensions, the dated parent mapping that survives acquisitions, the identity that revenue sums identically at every level, and the two mistakes that produce forty customers where there is one and one where there are forty.
16 Sept 20263 min readWhy paying reps on activity measures produces activity and paying them only on outcomes produces sandbagging, the three tests a measure passes before it goes into a plan, the rep controls it, it cannot be gamed by logging, and it reconciles to a ledger, which coverage and outcome measures pass, which fail, the coverage-at-cadence exception that passes all three, and the identity that every credited dollar in a plan is a ledger dollar once.
16 Sept 20263 min readThe seven-part template every measure page on this site follows, and why: the answer in one paragraph, the formula in a line, the rows needed with identifiers only, one worked table, the roll-up and its identity, the four mistakes, and the three questions answered in full. What each part is for, the order and why it is fixed, the length each part gets, and how a company can use the same template for its own definitions document.
16 Sept 20264 min readWhy every effect measured from a company's own history, samples and prescriptions, onboarding milestones and renewals, first-touch latency and first-year revenue, delayed installs and non-renewal, is an association and not a cause, the selection that makes it so, the comparison group that removes most of the noise, the sentence that reports it honestly, associated with rather than caused, why it is still enough to direct effort, and the two claims that are never made from it.
16 Sept 20263 min readThe difference between a baseline, an account's own typical level from its own history, and a norm, what similar accounts do when the relationship is full, why the two answer different questions, has this account changed and how far is it from where it could be, which measures use which, surge and dormancy against baseline, gap and share against norm, the case where an account is at its baseline and far from the norm, and the rule that both are stated on the line that uses them.
16 Sept 20263 min read