Your board sees a pipeline number nobody can define
The pipeline number your board sees probably can't be defended, because marketing and sales are using different definitions of the same word.
Ask your CMO what pipeline is. Then ask your CRO. Then ask your CFO. You will get three different answers. Possibly four.
This is not a technology problem. It is not a reporting problem. It is a language problem, and it is so common in B2B SaaS companies that most leadership teams have stopped noticing it, because they have never experienced anything different.
How it happens
Marketing counts marketing-qualified leads as pipeline contributions. In their view, every MQL that passes qualification criteria has entered the pipeline. The number looks strong because the threshold was designed to be achievable.
Sales counts opportunities, deals that have been accepted by an AE, had a discovery call, and meet some basic qualification bar. In their view, pipeline is what they are actively working. MQLs that have not yet converted to conversations are not pipeline; they are leads.
Finance counts weighted pipeline, opportunities adjusted for stage probability, with a bias toward late-stage deals that are more likely to close this quarter. In their view, the top of the funnel barely exists in the number they care about.
None of them are wrong within their own frame. But none of them are looking at the same thing.
The board sees a composite. A slide that says "pipeline: $X." Nobody in the room knows exactly what is in that number, how it was built, or whether it will produce the revenue growth it implies. Decisions get made on it anyway.
What it costs
The cost of this misalignment is not just confusion. It is active misallocation.
When marketing is optimizing for a pipeline number that sales does not recognize as meaningful, marketing invests in volume. More leads, broader reach, lower qualification thresholds. The number goes up. The CRO remains unimpressed, because from where they sit, the quality has not improved.
When sales is calling pipeline what marketing would call mid-funnel, the forecast is chronically optimistic. Deals that have barely been qualified are treated as real opportunities. The gap between pipeline and closed revenue grows. Finance discounts the marketing number, which leads to budget pressure, which leads to marketing cutting programs that were actually working.
When nobody agrees on what an MQL is, the SDR team is in an impossible position. They are qualifying against their own judgment. Some pass everything. Some kill deals before they start. There is no shared standard to coach against and no way to tell whether the function is working at all.
The fix is not a new CRM
Companies often try to solve this with technology. A new attribution tool. A better dashboard. A unified data platform. These things can help, but only if the definitions are agreed upon first. Technology does not resolve a language problem. It amplifies it.
The fix starts with a conversation that most leadership teams have never had explicitly: what do we mean, as a company, by each stage of the funnel? What exactly is an MQL? What makes something a sales-qualified opportunity? What moves a deal forward, and what disqualifies it?
That conversation is uncomfortable because it requires sales and marketing to negotiate, and both functions have an incentive to define stages in ways that make their own numbers look better. Running the conversation well requires a facilitator with no stake in either function's numbers, someone whose only interest is in the revenue outcome.
Once the definitions exist, the targets follow. And once the targets exist, the operating cadence, the weekly pipeline reviews, the conversion analysis, the quarterly planning, can actually be built on something real.
One question to settle it
When your board sees the pipeline number next quarter, can you explain in one sentence what is in it, how it was built, what qualifies for inclusion, and what conversion rate is embedded in the forecast?
If the answer is “it depends on who you ask,” you do not have a reporting problem. You have a funnel definition problem, and the board is making decisions on a number nobody can fully defend.
If you cannot answer that question cleanly, the problem is not the dashboard. It is the absence of a shared funnel definition underneath it.
A Funnel Framework engagement builds the shared model underneath the number: agreed stage definitions, handoff standards, conversion expectations, and pipeline accountability across marketing, business development, and sales.
See how Build works →