"Closed-won" means at least three different things in most owner-led businesses — signed contract, first payment, or delivered work — and when teams mix them, every downstream report is built on sand. Define the exact event once, and your revenue numbers finally line up.
Sales teams lose over 500 hours a year — roughly 27% of selling time — chasing invalid or outdated records (SpurIQ RevOps research, 2026).
If marketing, sales, and finance all use the phrase but mean different events, every downstream report is lying to you. Here's the audit.
In most owner-led businesses we work with, the phrase "closed-won" means at least three different things depending on who you ask.
Marketing counts it when a prospect signs a proposal. Sales counts it when the contract is executed. Finance counts it when the invoice is sent. Operations might count it when the project kicks off.
All four teams are reporting correctly against their own definition. The problem is they're all reporting it to you.
When the same event has four different definitions, your reports show four different numbers for the same thing. And when you try to reconcile them, you get explanations that sound reasonable but don't actually resolve the discrepancy.
"Marketing's numbers are always higher because they count earlier." True — but that truth is covering up a process gap, not explaining it away. The question is not why the numbers differ. The question is which number to use for which decision.
THE DOWNSTREAM COST
When "closed-won" is undefined, every metric downstream from it is unreliable: conversion rate, average deal size, sales cycle length, forecasted revenue, and customer acquisition cost. A 2024 SiriusDecisions (now Forrester) B2B Revenue Alignment study found that organizations with standardized pipeline stage definitions achieved 28% higher revenue attainment against forecast targets than those without. The definition is the infrastructure. Everything else is built on it.
You can run this audit in 30 minutes. Ask these three questions to your marketing lead, your sales lead, and your finance lead — separately, before they can confer:
Question 1: At what point do you count a deal as "closed-won" in your system?
Question 2: What document or event triggers that count — a signed proposal, a countersigned contract, an invoice, or something else?
Question 3: How do you handle deals that are verbally agreed but not yet signed?
If the answers differ — and they will — you now have your definition gap documented. The next step is writing a single shared definition that all three teams can report against.
The resistance to standardizing "closed-won" is almost always political, not technical. Someone's pipeline numbers will go down. Someone's conversion rate will change. Someone will look like they're performing worse on paper, even if nothing in the business has changed.
That resistance is actually useful diagnostic information. The team or metric that is most resistant to aligning the definition is usually the one with the most to reveal.
One question that will tell you everything:
Take your most recent "closed-won" count from your CRM. Now ask your finance team how many new contracts were fully executed in that same period. How large is the gap? That number is the size of your definition problem.
It should mean one specific, agreed event — most often a signed contract. The trouble is teams quietly use it to mean signing, first payment, or delivery, all at once.
Because forecasts, commissions, and cash projections all key off it. If the underlying event is ambiguous, every report downstream inherits the ambiguity.
Ask three questions: what event triggers it, who marks it, and what must be true first. If you get different answers, your definition needs fixing.
Because each team's version feels correct from where they sit. Agreeing on one event means some teams give up the version that flatters their metrics.