Revenue operations KPIs your CRM cannot calculate.
Most RevOps KPI lists mix three different kinds of number: ones the CRM computes for you, ones it can compute once you add a field, and ones it will never hold the data for. Nobody labels which is which, so teams build dashboards on numbers the system was never able to produce.
Toni MedicSalestructSeptember 9, 20269 min readSales Operations
Every RevOps KPI list looks the same: win rate, sales cycle length, pipeline coverage, CAC, LTV to CAC, forecast accuracy, average deal size, and eight more.
What none of them tells you is that those numbers come from three different places, and only one of the three is inside the CRM you are being asked to report from.
The short version
- A CRM computes some KPIs natively, and the way it does it is worth reading. HubSpot's weighted forecast is "calculated by multiplying the total amount in each stage by the stage probability", so it inherits whatever your stage names mean.
- A second group becomes computable the moment you add one field, usually a source or a date, and most teams never add it.
- A third group needs cost data that lives in your ad accounts and your payroll, and no CRM will ever hold it. CAC is in this group.
- Reporting a KPI from the wrong group is how dashboards end up confidently wrong rather than obviously broken.
- For a small sales team, four numbers are enough, and three of them need the same two fields.
What are revenue operations KPIs?
Revenue operations KPIs are the measures used to judge whether the commercial system is working, as opposed to whether a person is. They cover the pipeline, the conversion between its stages, the time things take, and the money the whole thing costs to run.
The useful way to sort them is not by category. It is by whether your system can actually produce them.
Group one: computed natively, and only as good as its inputs
These your CRM will give you today, without configuration.
Win rate, average deal size, sales cycle length, deal count by stage, weighted pipeline value. They come free because every input is already a field on the deal.
The catch is worth stating precisely. HubSpot documents that its weighted amount is "calculated by multiplying the total amount in each stage by the stage probability." That is a real calculation on real data, and it is only meaningful if the stage a deal sits in means something. When stages are named after seller activity, as most shipped defaults are, the weighted number rises because a rep booked a meeting. The arithmetic is correct and the answer is fiction, which is why what your stages are named is a reporting problem and not just a process one.
Native does not mean trustworthy. It means the system will produce it whether or not it is true.
Group two: one field away
These are computable, and are not being computed at your company, and the reason is almost always a single missing field.
| KPI | Group | What it needs |
|---|---|---|
| Win rate | 1 | Nothing. Already computed |
| Average deal size | 1 | Nothing |
| Sales cycle length | 1 | Nothing, though measured from creation rather than first contact |
| Deal count by stage | 1 | Nothing |
| Weighted pipeline | 1 | Nothing, and it inherits whatever your stage names mean |
| Pipeline created by source | 2 | A source field set at creation, never backfilled |
| Stage conversion rate | 2 | A timestamp when the stage changes, not just the current stage |
| Time in stage | 2 | The same timestamp, read as a duration |
| Speed to first response | 2 | A first-reply timestamp on the contact |
| Win rate by segment | 2 | One segment field, chosen once and required |
| Customer acquisition cost | 3 | Ad spend, tooling, salaries. None of it in the CRM |
| Lifetime value | 3 | Billing and churn history, usually in finance |
| LTV to CAC | 3 | Both of the above, so it inherits both gaps |
| Payback period | 3 | Cost data plus revenue recognition timing |
Every row here is a day of configuration and then it computes forever. That is the highest-return work in most RevOps setups and it is invisible, which is why it does not get done.
The rule to apply: a field that is required at creation produces a KPI, and a field that is backfilled produces a guess. If your source field is filled in at the end of the month by whoever remembers, that column is not data.
Group three: your CRM will never hold this
Customer acquisition cost. Lifetime value. LTV to CAC. Payback period. Blended versus paid CAC. Cost per opportunity.
Every one of these needs money the CRM does not see: ad spend, tool subscriptions, salaries, contractor invoices, the agency retainer. A CRM knows what closed. It does not know what it cost you to be in the room.
This is not an argument against those numbers. They are among the most important a company tracks. It is an argument against expecting them out of the wrong system, and against the dashboard that shows a CAC figure whose cost side was typed in once, six months ago, by somebody who has left.
If you report CAC, report where the cost side came from and when it was last updated, in the same view as the number. A KPI whose inputs nobody can name is a decoration with a decimal point.
The four numbers that are enough for a small team
For a team without a dedicated ops person, these four cover the questions you actually make decisions on.
Win rate, by segment. Group two, one field. Without the segment split it hides the fact that you win one kind of deal and keep bidding for another.
Sales cycle length, measured from first reply. Group two. Measured from creation it tells you about your admin, measured from first contact with the buyer it tells you about your process.
Pipeline created this month, by source. Group two. The only leading indicator on this list, and the first one that moves when something upstream breaks.
Stage conversion, one stage to the next. Group two. The number that tells you where deals stop, which is the only diagnostic that points at a fix rather than at a feeling.
Three of the four need the same thing: a timestamp when a stage changes, and a required field at creation. That's the work. It is not a dashboard project.
Common questions
Sources
HubSpot, Set up and customize your deal pipelines and deal stages. States that the weighted amount in board view is "calculated by multiplying the total amount in each stage by the stage probability". Page states last updated 12 August 2026. Fetched and read 8 September 2026 (2026)
How these were checked
Only the weighted-forecast mechanic above is a vendor claim, and it comes from that HubSpot page opened directly. The three-group split, the field requirements and the four recommended KPIs are method rather than product behaviour, and no vendor is characterised as computing or failing to compute any specific KPI on their behalf.
Read next.
All articlesWhat is revenue operations? RevOps explained
RevOps is what happens when marketing, sales and customer success stop reporting from three different spreadsheets. What it owns, how it differs from sales ops, and the signs a company needs one before it has the headcount to hire one.
Sales infrastructure: the rules layer nobody builds
Companies without a dedicated ops person usually own the tools and improvise everything between them. The list is bought, the CRM is bought, the sending tool is bought, and the rules that connect the three live in someone's head, which is the part that breaks when that person is on holiday.
