A leadership pipeline dashboard needs six metrics, reviewed on three different cadences, because the metrics don't move at the same speed. SLA adherence and stalled deals shift daily; coverage ratio and win rate by source only mean something as a multi-week trend. Reviewing all six weekly, or all six quarterly, is why most dashboards get built once and then ignored.
This is the third piece in our series on marketing-sales alignment at the leadership level. The first piece covers why marketing and sales end up with two different versions of the truth. The second covers the SLA that defines what a qualified lead is and how fast sales has to respond to it. This piece assumes that SLA already exists and answers the question that comes right after it: once marketing and sales agree on the same six numbers, how often does each one actually need to be looked at, and what should the dashboard put in front of leadership first?
Why Two Dashboards Usually Means an Alignment Problem, Not a Reporting Problem
Marketing builds a dashboard showing MQLs, campaign performance, and content downloads. Sales builds one showing pipeline value, forecast, and quota attainment. Both can be accurate and still not answer the one question leadership actually has: is enough qualified pipeline moving through the funnel to hit the number, and if not, where is it breaking down?
Two dashboards, two sets of definitions, two stories. Marketing's numbers say lead volume is up. Sales's numbers say pipeline is flat. Both can be true at once, and a leadership team looking at both in isolation has no way to tell which one is the real signal. The fix isn't a smarter dashboard. It's one dashboard, built on the qualification and handoff definitions both teams already agreed to in the SLA, so there's no separate marketing count and sales count of the same thing.
The 6 Metrics a Leadership Dashboard Actually Needs
Each of these should trace back to a definition your marketing and sales teams have already agreed on. If that agreement doesn't exist yet, the SLA piece linked above is the place to start before any of this.
Pipeline coverage ratio. Total open, qualified pipeline value divided by the revenue target for the period, expressed as a multiple. Stalled deals with no recent activity should be excluded from the numerator, or the ratio overstates how healthy the pipeline actually is. A commonly cited range is roughly 3x quota for teams with a win rate above 30%, and closer to 4-5x for earlier-stage teams or lower win rates, though the right number depends on your specific close rate and cycle length, not a universal benchmark. Match the time window to your sales cycle: a 90-day cycle gets a single-quarter view, a 120-day-plus enterprise cycle needs a rolling two-quarter view or the ratio understates real coverage.
Qualified opportunities created, by source. Opportunities that met the agreed qualification bar and were formally accepted by sales, split by marketing-sourced, sales-sourced, and marketing-influenced where the CRM tracks influence. Not total leads. Without the SLA's definition of "qualified" behind this number, it's just marketing counting its own leads again under a different label.
Stage conversion rate. The percentage of opportunities moving from each pipeline stage to the next: qualified to first meeting, first meeting to proposal, proposal to close. A drop at one specific stage names exactly where the process is breaking, which is more actionable to leadership than a single blended win rate.
SLA adherence. Two percentages tracked together: the share of leads sales responded to within the agreed window, and the share of leads marketing handed off that actually met the qualification bar. This is the metric that keeps the SLA from becoming a document nobody checks after the month it was signed.
Win rate by source. Win rate broken out by where the deal originated, not a single blended figure. This is usually the number that settles disputes about which channel or team is actually contributing to closed revenue, because a source-level win rate is harder to argue with than a volume metric.
Deal age and stalled-deal count. How long open opportunities have sat in their current stage, and how many have crossed a defined threshold (commonly two to three times the average time-in-stage for that stage) without a logged next step. This is the earliest leading indicator of forecast risk on the list. It shows up here before it shows up as a missed quarter.
Six metrics, not twenty. A dashboard that requires scrolling gets summarized verbally in the meeting instead of actually read before it, which defeats the point of building one.
Why Do the Same 6 Metrics Need Three Different Review Speeds?
The mistake most dashboards make isn't picking the wrong metrics. It's reviewing all six at the same frequency. SLA adherence and stalled-deal count change day to day, because they're built from individual events: a lead came in, a rep did or didn't respond, a deal did or didn't get a next step logged. Reviewing those monthly means a broken handoff sits unfixed for weeks before anyone notices. Coverage ratio and win rate by source move the opposite way. A single week of deal activity doesn't shift a coverage multiple in any meaningful sense; the number only becomes signal once you're looking at it across four to six weeks of movement. Reviewing those weekly just adds noise, a leader reacting to a data point that was never meant to be read in isolation. The cadence has to match how fast each metric actually accumulates into something worth a decision, not a single default review rhythm applied to every number on the page.
Weekly: The Metrics That Move Day to Day
Attendees: whoever owns CRM data or revenue operations, plus the sales manager. Thirty minutes, no more.
This is where new pipeline created, SLA response-time adherence, and any deals that have gone quiet get checked, because these are the three numbers on the dashboard that are genuinely different from one week to the next. Nothing here requires a budget call or a change in direction. The purpose is catching a missed follow-up or a broken handoff while it's still a five-minute fix, not letting it compound into a monthly-review problem.
Monthly: The Metrics That Only Mean Something as a Trend
Attendees: CMO or VP Marketing, CRO or VP Sales, and the CEO in companies without a dedicated revenue leader. Sixty minutes.
This is where coverage ratio, stage conversion, and win rate by source get reviewed as trend lines across the last three months, not single numbers pulled from that day. Is coverage improving or slipping? Is one specific stage conversion dropping while the others hold? Is win rate shifting between sources? Real decisions get made here: reallocating spend between channels, tightening the qualification bar if too many "qualified" leads are stalling early, or flagging that the SLA itself needs renegotiating.
Quarterly: Same Numbers, Different Question
Attendees: leadership team, plus board or investors where applicable.
Same six metrics, no new ones introduced at this level, but the question changes from "what do we fix this month" to "what does this mean for hiring, budget, and next quarter's target." A board that sees a differently defined set of numbers every quarter can't actually track whether pipeline generation is working over time. Consistency in what's being measured matters more here than adding sophistication.
What Should a Leadership Dashboard Layout Actually Prioritize?
A dashboard with the right six metrics can still fail if it's laid out like a data export. Three layout choices do more for whether it actually gets used than any additional metric would:
- Trend direction before raw number. A coverage ratio of 2.8x means nothing on its own to someone who doesn't track it weekly. A coverage ratio of 2.8x with an arrow showing it was 3.4x a month ago tells leadership what to ask about in the first three seconds of looking at it.
- One page, ranked by decision urgency, not by funnel order. Put SLA adherence and stalled-deal count at the top if they're currently flagged, because those are the two that can still be fixed this week. A metric that only supports a quarterly conversation doesn't need top placement just because it comes first in the funnel.
- A visible threshold, not just a number. Deal age means little without a stated "stalled" line. Coverage ratio means little without a stated target multiple next to it. A dashboard that shows the number without the threshold it's being judged against forces every viewer to do that math themselves, or skip it.
None of this requires new data. It's the same six numbers, arranged so the person looking at them for thirty seconds before a meeting knows what to react to without asking someone to walk them through it first.
What Doesn't Belong on It
Total MQL volume doesn't belong on a leadership dashboard. It's a marketing operations metric, useful for tuning campaigns, not for a CEO deciding whether pipeline is healthy enough to hit the number. The same goes for website traffic, content downloads, email open rates, and social engagement. None of these are wrong to track. They're the wrong altitude for a dashboard built for resourcing and budget decisions, not campaign-tuning decisions. If a metric doesn't change what leadership does at the next review, it belongs in a departmental report, not the shared one.
You Don't Need a Dashboard Project to Start This
This doesn't require a business intelligence build-out. Most CRMs, including HubSpot, Twenty, Pipedrive, and Salesforce, can generate these six metrics from data that's likely already there, provided qualification status, handoff timestamps, and deal source are being logged consistently. The harder part isn't the dashboard. It's getting marketing and sales to agree on six shared numbers and stop maintaining separate ones. Once that agreement exists, building the dashboard itself is a few hours of setup, not a project with a timeline.
FAQ
How many metrics should a leadership pipeline dashboard have?
Somewhere around five to seven is the practical range. Past that, the dashboard stops getting read before meetings and starts getting summarized verbally instead, which defeats the point of having one.
Should marketing and sales use separate dashboards?
No. Separate dashboards built on separate definitions are usually where reporting disagreements start. One shared dashboard, built on definitions both teams already agreed to in an SLA, removes the argument over whose numbers are right.
Who should own the leadership pipeline dashboard?
Whoever owns the CRM data, a revenue operations function if the company has one, or whoever manages the CRM if it doesn't. Ownership should sit with someone accountable to both marketing and sales, not embedded inside either department.
Why do the weekly, monthly, and quarterly reviews look at the same metrics differently?
Because the metrics move at different speeds. Weekly reviews catch daily-event metrics like SLA adherence and stalled deals while a fix is still cheap. Monthly reviews read coverage ratio and win rate by source as trend lines, since a single week of activity doesn't move them meaningfully. Quarterly reviews use the same numbers again, reframed for board-level questions about hiring and budget rather than this month's fixes.
Do we need a business intelligence tool to build this dashboard?
Not usually. Most CRMs can generate these metrics natively if the underlying data, qualification status, handoff timestamps, deal source, is being logged consistently. The dashboard itself is typically a short setup once marketing and sales agree on the definitions behind it.
If you're not sure whether your current reporting gives you a real read on pipeline health, or whether marketing and sales are quietly working from two different sets of numbers, that's worth a direct look rather than a guess. Request a free audit and we'll tell you what we actually find, including if the answer is that your reporting is fine and the problem is somewhere else.