A quarterly business review. The VP of Marketing presents pipeline numbers — healthy growth, good conversion from campaign to opportunity. The slide looks clean.

Then the VP of Sales speaks. “I don’t recognize these numbers. Half of what marketing calls pipeline, my team wouldn’t touch.” Finance asks which number is right. Nobody can answer, because both are technically correct. They’re just not measuring the same thing.

I’ve sat in this meeting more than once. Every time, the instinct is the same: “We need better dashboards.” The dashboards aren’t the problem. The problem is that when marketing says “qualified lead,” they mean something different than when sales says it.

flowchart TD
    L[Lead submits form] --> MK["<b>Marketing</b><br/>scores against threshold"] & SL["<b>Sales</b><br/>assesses buying intent"]
    MK --> MN["200 MQLs"]
    SL --> SN["30 SQLs"]
    MN & SN --> QBR["QBR: which number is right?"]
    QBR --> FIX["<b>Fix:</b> align definitions<br/>before building the dashboard"]

Same words, different meanings

The most dangerous terms in revenue operations are the ones everyone thinks they agree on. MQL. SQL. Active customer. Churn. Pipeline.

Take “qualified lead.” Marketing defines it as a lead that hits a scoring threshold: right industry, right company size, attended a webinar. That’s an MQL. Sales looks at the same lead and sees someone with no buying intent, no budget conversation, no timeline. To sales, that lead isn’t qualified. It’s a name.

“Active customer” works the same way. For CS it’s someone who logged in this month. For finance it’s someone with a current contract. For sales it’s someone responsive to outreach. Three teams, three numbers, all defensible, none comparable. Churn is worse — logo vs revenue, gross vs net, does a downgrade count? I’ve seen CS report 5% while finance reports 12%.

Why definitions drift

This isn’t malice. Incentives create exactly the outcome without any intent.

Marketing is measured on pipeline generation, so they define “qualified” in a way that maximizes the count. Sales is measured on closed revenue, so they define it as “ready to buy.” Each team owns their own definitions, and nobody owns the definitions across teams. There’s no single person responsible for saying: when we use this word in a report, this is what it means, everywhere, for everyone.

What a shared metric vocabulary looks like

Every metric that crosses a team boundary needs a written definition that specifies what is counted, how, and when. Not “MQL = qualified lead from marketing.” That’s a label. An operational definition: “MQL = a lead with a fit score above 60 and a behavior score above 40, calculated from industry, company size, role match, website visits, content downloads, and event attendance within the last 90 days.”

That’s specific enough that two people can independently look at the same lead and arrive at the same classification. That’s the test. If your definition doesn’t pass it, it’s not a definition yet.

The definition also has to live in the CRM, not in a slide deck. It needs an owner — one function responsible for the cross-team vocabulary, with the authority to say what terms mean and the responsibility to update them when the business changes. Revenue operations is the natural home. And definitions need quarterly review; the scoring model that worked at 50 customers often doesn’t at 500.

The conversation that should happen before the dashboard

When leadership asks for a new dashboard, the first question shouldn’t be “what do you want to see?” It should be “what do these terms mean to you?”

Build a list of ten or fifteen terms that show up in your reporting. Go around the room and ask each function to define them. You will find disagreements. Those disagreements are currently invisible, buried inside dashboards that look precise but aren’t comparable.

The output is a metric dictionary: a single document, maintained by rev ops, with the operational definition of every cross-functional term, linked to the system field that produces it, with a version number and a review date. Nobody gets promoted for writing it. But the organizations where reporting actually drives decisions are the ones where this boring work got done.

Every reporting complaint I’ve encountered can be traced to one of two root causes: the data isn’t there, or the definitions aren’t aligned. The first is a data problem. The second is a conversation that never happened.

Sit in a room. Define your terms. Write them down. Put them in the system. Assign an owner. Review them quarterly.

Then build the dashboard.