The 'What Does Revenue Even Mean Here?' Workshop Guide

If your CEO, CFO, CRO, and head of marketing all use the word revenue but mean different things, you do not have a communication problem.

You have an operating problem.

This is one of the most common ways mid-size SaaS companies lose trust in their own reporting. Finance shows net new ARR. Sales talks about bookings. Marketing reports sourced pipeline. The board deck compresses all of it into one chart with a label like “revenue” and everyone leaves the meeting less confident than when it started.

The fix is not another dashboard.

The fix is getting the right people in the room, forcing the definitions into the open, and choosing what each number is actually for.

This guide gives you a practical way to run that workshop.

When You Need This Workshop

Run a revenue-definition workshop when:

• finance and marketing keep bringing different numbers to the same meeting
• pipeline, bookings, ARR, MRR, and revenue are being used interchangeably
• board reporting turns into a caveat recital before anyone can make a decision
• RevOps is expected to be the source of truth without authority over every upstream system
• teams keep asking for a dashboard fix when the real issue is definition drift

If the disagreement is active right now, that is actually a good sign. It means the trust problem is visible enough to solve.

The Goal of the Session

The goal is not to make every metric in the company perfect in 90 minutes.

The goal is to leave with:

1. one explicit definition for the core revenue metric used in leadership reporting
2. a clear distinction between ARR, MRR, bookings, pipeline, and recognized revenue
3. one named system of record for each important number
4. a short list of follow-up fixes for ownership, modeling, and governance

That is enough to stop the meeting chaos and create a real implementation path.

Pre-Work: What to Collect Before Anyone Joins the Room

Do not start the workshop cold. The pre-work is what makes the disagreement visible before the call even begins.

Ask each participating team to submit the following in advance:

• Their current definition of revenue. One sentence, no jargon.
• The report or dashboard they trust most. Link it or attach a screenshot.
• The source system behind that number. CRM, billing platform, warehouse, spreadsheet, board deck, etc.
• What decisions they use the number for. Forecasting, board reporting, compensation, budget allocation, planning.
• What they believe is wrong with the other teams’ number. This is where the useful friction usually lives.

The point is not to collect polished answers. The point is to expose the mismatch early.

Suggested participant list

Keep the room small enough to make a decision:

• RevOps or operations owner
• finance lead or CFO delegate
• sales leader or CRO delegate
• marketing leader or growth lead
• data/analytics owner if they are the team carrying the reconciliation burden

If you invite twelve people, you are running a listening tour. If you invite four to six people, you are running a decision workshop.

The 90-Minute Agenda

Here is the facilitation structure I recommend.

0-10 minutes: Frame the problem

Start with the rule of the meeting:

We are not here to prove one team is right. We are here to decide which number is fit for which decision.

Then show the submitted definitions side by side. Do not summarize them yet. Let the room feel the mismatch.

10-25 minutes: Map the numbers

Put these terms on the board:

• pipeline
• bookings
• ARR
• MRR
• recognized revenue
• expansion revenue
• churn / contraction

For each term, ask:

• what does this mean here?
• who uses it?
• where does it come from?
• where does it break?

You are not trying to clean up every nuance. You are trying to make hidden assumptions obvious.

25-45 minutes: Trace the system of record

Take the most contentious number and map the path backwards:

1. where is it presented?
2. where is it calculated?
3. what upstream systems feed it?
4. where do manual adjustments happen?
5. who owns the definition?

This is usually where you discover that the board metric comes from a spreadsheet maintained by one heroic operator who has been translating three systems by hand.

45-65 minutes: Resolve the critical decisions

Now force the conversation into decisions, not abstractions.

For each major metric, decide:

• Primary use case — board reporting, forecasting, compensation, campaign analysis, etc.
• Canonical definition — the exact business meaning
• System of record — where the number comes from
• Owner — who approves changes to the definition
• Known exclusions — what the number does not include

If the team cannot agree, capture the conflict explicitly. Unresolved conflicts are still progress when they are written down clearly.

65-80 minutes: Choose the operating metric set

Do not leave with twenty metrics.

Pick the two to four numbers that most need shared definitions now. For most SaaS teams, that is some combination of:

• net new ARR
• bookings
• sourced pipeline
• qualified pipeline
• recognized revenue

This becomes the first governance scope.

80-90 minutes: Lock the rollout plan

End the session with three concrete outputs:

1. what definition is now official for leadership reporting
2. what follow-up work is required in CRM / warehouse / reporting
3. how the decision will be communicated to the broader team

If you skip this step, the workshop becomes a smart conversation with no operational afterlife.

How to Handle the Predictable Arguments

Revenue-definition workshops are not hard because the math is hard.

They are hard because each team has a valid reason for using the number they use.

A few facilitation rules help:

Separate “useful” from “universal”

A number can be useful without being universal.

Marketing may need sourced pipeline to evaluate channel quality. Finance may need recognized revenue for external reporting. The mistake is pretending one of those numbers should answer every question.

Do not let labels hide time windows

A lot of disagreement is really a timing disagreement.

If sales talks in bookings, finance talks in recognized revenue, and marketing talks in sourced pipeline, the number mismatch may be less about bad logic and more about different stages of the same commercial motion.

Force exclusions into the definition

A clean definition includes what is left out.

If ARR excludes services revenue, say that. If bookings includes multi-year contracts but board reporting normalizes them, say that. Ambiguity loves omitted edge cases.

Name the temporary workaround

If one number currently depends on spreadsheet adjustments, manual mapping, or a finance-only export, write that down. Temporary duct tape becomes permanent very quickly when nobody names it.

ARR vs. MRR vs. Bookings vs. Recognized Revenue

This is where a lot of teams melt down, so be explicit.

ARR

Use ARR when the goal is to understand the recurring annualized value of contracted revenue. It is useful for board communication, growth planning, and recurring-revenue businesses where annualization clarifies scale.

Do not use ARR as a catch-all stand-in for every revenue conversation. It hides timing and can flatten important differences between signed contracts and recognized revenue.

MRR

Use MRR when the business operates monthly enough that recurring change over time matters operationally. It is useful for understanding expansions, contractions, and monthly movement.

Do not use MRR when leadership is actually asking a quarterly or annual planning question.

Bookings

Use bookings when the question is about what has been sold or contracted, especially in sales forecasting and go-to-market accountability.

Do not present bookings as if it were the same thing as recognized revenue. Finance will stop trusting the conversation immediately.

Recognized revenue

Use recognized revenue when the question is financial reality: what can legitimately be counted in the period under the company’s accounting treatment.

Do not ask marketing to manage campaigns exclusively against recognized revenue if the sales cycle or revenue recognition timing makes that operationally useless.

The answer is usually not choosing one forever. It is assigning each number a job and labeling it correctly.

Decision Framework: How to Pick the Right Definition

When the room gets stuck, use this order of operations:

1. Start with the decision. What decision is this metric supposed to support?
2. Pick the least misleading definition for that decision. Not the most flattering. Not the most familiar.
3. Choose the system that can reproduce it reliably. If the only version lives in one person’s spreadsheet, it is not ready to be canonical.
4. Assign an owner. Definitions without owners drift.
5. Document the caveats. If there are known gaps, write them down instead of pretending the number is cleaner than it is.

This keeps the conversation grounded in business use, not departmental preference.

What the Rollout Message Should Say

After the workshop, send a short written summary to every team using revenue metrics.

Your message should include:

• the official definition for the leadership revenue metric
• the list of related metrics that are still valid for other use cases
• the system of record for each
• what changed from the previous reporting approach
• what follow-up cleanup work is underway
• where questions or definition changes should go

Keep it boring. Precision beats inspiration here.

A Simple Communication Template

You can adapt this directly:

Starting this quarter, the leadership reporting metric for revenue will be [metric name], defined as [definition].

We are using [system of record] as the source for this number.

Related metrics like [ARR / MRR / bookings / sourced pipeline] are still valid for their specific operating use cases, but they should not be substituted for the leadership metric in board, planning, or executive reporting.

The remaining known gaps are [gaps] and the follow-up owners are [owners].

If a team believes the definition should change, route that through [owner/governance process] rather than creating a new local version.

That one message prevents a lot of backsliding.

What Usually Happens Next

Most companies discover that the workshop surfaces one of three underlying realities:

1. The definition problem is real, but solvable with governance. The systems are mostly fine; the team just needs shared ownership and documentation.
2. The definition conflict is hiding data-model or CRM issues. The workshop exposes broken joins, lifecycle confusion, or weak warehouse logic.
3. The company is using one number for too many jobs. The fix is not one metric. It is a cleaner metric system.

That is why this workshop works well as a bridge into larger implementation work.

If you need a real artifact and a fix sequence quickly, start with Three Teams, Three Numbers. If the workshop exposes broader reporting and modeling work, the next step is usually Revenue Analytics. For proof that this kind of finance-marketing alignment can actually stick, read the mid-market SaaS attribution case study.

Download the Facilitation Kit

The PDF version includes the pre-work checklist, agenda, decision worksheet, metric-role prompts, and rollout template in one place.

If your team is already tired of debating which revenue number is real, book the Three Teams, Three Numbers diagnostic. We use this exact structure to turn metric fights into visible decisions and an implementation path.