How to Build a Pipeline Dashboard

What should a pipeline dashboard answer?

A pipeline dashboard answers whether the quarter will happen and where it breaks, in under a minute of looking.

Most pipeline dashboards answer a different question, which is how much pipeline exists. That number reassures people. It does not predict anything, because two companies with identical pipeline totals can be in completely different positions depending on what the pipeline is made of.

Build the dashboard around four questions. Is there enough. Is it real. Is it moving. Is enough new pipeline arriving. Every panel earns its place by answering one of them.

Which panels belong on the first screen?

Six to eight panels, arranged so the top row carries the answers and the second row carries the reasons. The size gap panel is the one most dashboards omit and the one that changes conversations fastest. A pipeline with an average open deal size of $80,000 that closes at an average of $40,000 is carrying double the revenue it will produce, and no coverage ratio will tell you that.

How do you show coverage without misleading anyone?

Never show a single coverage number on its own. Split it by the dimensions that determine whether it converts.

The standard coverage band runs 3x to 5x. Across ORM's customer base most accounts sit near 3.5x, with real ranges from 1.4x upward. A company at 4x can miss badly if the pipeline is aged, concentrated in a few deals, or owned by reps who have never hit the number. A company with thin coverage can beat the quarter on a strong in-quarter motion. The case against treating the ratio as an answer is in why the 3x pipeline coverage rule is wrong.

Break the coverage panel by segment, by rep tenure band, and by pipeline age. Three small charts beat one large number. Definitions for the ratio itself sit in pipeline coverage.

Add a second line to the same panel showing coverage after aged pipeline is removed. The distance between the two lines is the honest version of the number.

How should the dashboard handle stale pipeline?

Show aged pipeline as a subtraction, not as a separate report nobody opens.

Across ORM's customer base, more than 10 percent of open pipeline has not been touched in twelve months. That value sits inside every ratio on the screen unless the dashboard removes it explicitly.

Define touched as a change in stage, close date, or amount. Logged calls and emails are easy to produce without a deal advancing, so activity-based aging rules get satisfied within a week of being announced and stop measuring anything.

Then show the in-quarter reality check. On the first day of a quarter, about 20 percent of the pipeline carrying close dates inside that quarter actually closes inside it. A panel that displays in-quarter pipeline as though it were near-revenue sets an expectation the quarter will not meet.

Which pipeline metrics do not belong on a dashboard?

Drop anything that goes up when nothing improves.

Total open pipeline with no time bound rises whenever reps stop closing deals as lost. Activity counts rise whenever reps learn the dashboard exists. Rep-assigned confidence percentages restate optimism as a number and then sit next to real conversion rates as though they were the same kind of measure.

Stage-count charts belong in the same category. Ten deals in negotiation means nothing without their value, age, and who owns them.

The metric that creates the most noise is total pipeline coverage without context. It looks like information and behaves like reassurance.

Should the dashboard show weighted pipeline?

Show weighted and unweighted together, and label the probability source.

Weighted pipeline built on committee-assigned stage probabilities produces a different number from weighted pipeline built on historical stage conversion rates, and the gap between them is often larger than the gap people are arguing about in the meeting. Put both on the panel with the source named. Background on the method is in weighted pipeline.

Pair it with a velocity panel. Value, win rate, and cycle length interact, and a pipeline that grew while cycle length grew faster is a pipeline that got worse. The calculation is in sales velocity.

How often should the dashboard refresh?

Daily for open pipeline, weekly for composition, and never mid-meeting.

Real-time refresh sounds better than it works. Numbers that move while a room is discussing them destroy the shared reference point that makes a decision possible. Freeze a snapshot for reviews and let the live view run for everyone else.

Composition metrics like aging, source mix, and the deal size gap move slowly enough that a weekly cut is more readable than a daily one. Recalculating them hourly adds noise without adding a single decision.

How do you know the dashboard is working?

Count the decisions it triggers.

A working pipeline dashboard causes deals to get closed as lost, creation targets to get raised mid-quarter, and coverage claims to get challenged with a specific segment named. If a quarter passes with no action traced back to a panel, that panel is decoration.

Two other tests. Ask three people what the coverage number means and see whether the answers match. Then check whether anyone has opened the dashboard on a day with no meeting scheduled. Both failures point at the same problem, which is a dashboard built to report rather than to decide.