Chart choice on a sales dashboard is a reading-speed decision. A sales leader looks at a tile for a few seconds and either extracts a fact or moves on. The wrong chart type does not hide the data, it slows down the read enough that nobody bothers, and the number stops influencing anything.
Which chart should you use for each sales metric?
Match the chart to the question rather than to the metric. The same number needs a different visual depending on whether the reader is asking about level, change, composition, or distribution.| What you are showing | Chart type | Why it works | Common mistake |
|---|---|---|---|
| Current pipeline by stage | Stacked column across periods | Shows level and composition together | Using a pie, which loses the time axis |
| Pipeline movement over a quarter | Waterfall | Separates additions, closures, and losses | Showing only start and end totals |
| Cumulative bookings against plan | Two lines across the period | Makes the pace gap readable at a glance | Bar-versus-bar, which hides timing |
| Conversion between stages | Horizontal funnel bars | Shows drop-off at each step | Percentages without the underlying counts |
| Coverage or win rate over time | Single value with sparkline | Level plus direction in minimal space | A full line chart for one number |
| Deal size distribution | Histogram or box plot | Exposes concentration in a few large deals | An average, which hides the shape entirely |
| Rep performance comparison | Sorted horizontal bars | Rank is immediately readable | Radar charts, which nobody can compare |
How do you visualize pipeline movement over a quarter?
Use a waterfall, because the total at each end tells you nothing about how it got there. Pipeline that started at one level and ended at the same level might have been completely replaced or completely static, and those are different businesses.The bars that matter are pipeline created, pipeline closed-won, pipeline closed-lost, pipeline pushed to a future period, and amount changes on existing deals. That last bar is the one most teams omit, and it explains a large share of unexpected movement given how often deals get revalued downward before close.
The same chart form carries the revenue view. ORM structures monthly ARR movement as beginning ARR, churned customer ARR, churned product ARR, product decrease ARR, new customer ARR, new product ARR, increased product ARR, and ending ARR, with beginning ARR always equal to the prior month's ending ARR. That reconciliation reads naturally as a waterfall and makes net revenue retention traceable to specific rows.
What is the right way to chart forecast versus actual?
Plot cumulative actual against plan pace across the period, with markers where each forecast was submitted. Forecast error is a timing problem as much as a magnitude problem, and only a time-based chart surfaces that.The markers matter. A team that called the number correctly in week eleven and badly in week two has a different problem from a team that was wrong throughout. Getting the forecast right in the last week of a quarter helps nobody, because by then the quarter has already happened. Charting when the call changed is what makes that distinction visible.
Seasonality belongs in the plan pace line rather than in a footnote. Most B2B businesses run stronger Q2 and Q4 than Q1 and Q3, and the third month of a quarter outperforms the first two. A flat plan line makes every early-quarter reading look like a miss. Scoring the result over time gives you a real forecast accuracy trend rather than a single quarterly verdict.
How should you show pipeline composition?
Stacked columns across periods, never a pie. Composition questions are almost always comparative, meaning the reader wants to know how this quarter's mix differs from last quarter's, and a pie chart has no way to express that.Three composition cuts earn dashboard space. Stage, which shows whether pipeline is concentrated early. Age, which shows how much of the total is inert. And deal size distribution, which shows whether the quarter depends on a handful of large deals.
The age cut is the one most often missing. ORM sees 10% or more of pipeline sitting untouched for a full 12 months across most customer bases, and on a standard stage chart that inventory is indistinguishable from active pipeline.
Deal size distribution deserves a histogram rather than an average. A pipeline averaging $80,000 per deal that produces closed-won deals averaging $40,000 is a distribution problem the average actively conceals.
How should coverage appear on a dashboard?
As a single value with a sparkline, sitting directly above the composition charts that qualify it. Coverage plotted alone as a trend line invites a conclusion the composition would contradict.The standard coverage range is 3x to 5x. Across ORM customers, coverage clusters near 3.5x. A team inside the standard range can still miss when the pipeline is concentrated in a few deals, aged, owned by reps who have not closed at that size, or carrying close dates that keep moving. The visual layout should force the eye from the ratio down to those qualifiers rather than letting the ratio stand alone. The reasoning behind that is covered in the definition of pipeline coverage.
If you weight the pipeline before charting it, weight on your own stage conversion history rather than default CRM probabilities, and show the unweighted value alongside so the adjustment is visible. The mechanics are in weighted pipeline.
Which chart types should you avoid?
Pie charts, radar charts, dual-axis combinations, and any 3D rendering. Each one costs reading speed without adding information.Dual-axis charts deserve specific attention because they look sophisticated and mislead reliably. Two series on different scales can be made to appear correlated or divergent depending entirely on where the axes are set, and readers have no way to detect the manipulation. Split them into two stacked charts sharing an x-axis instead.
Gauges and speedometers waste more space than any other chart form. They present one number using the area of a full chart, and a single value with a sparkline conveys more in a quarter of the room.
How many charts should one dashboard hold?
Three or four charts on the main view, with single-value tiles above them. Beyond roughly six, readers scan instead of read, and the dashboard's influence on decisions drops to zero regardless of how good the underlying data is.Put the headline numbers in a top strip, the three charts that explain movement underneath, and everything else on a diagnostics view that opens when a headline number moves the wrong way. That structure gives each chart a job, and any chart without one gets removed at the next review.
Frequently Asked Questions
What is the best chart type for pipeline data?
A stacked column by stage across time for composition, and a waterfall for movement between two points. The stacked column shows where pipeline sits, and the waterfall shows what added to it and what left. Together they answer most pipeline questions a sales leader asks.
Should a sales dashboard use pie charts?
Almost never. People read angles poorly, and pipeline composition usually has more categories than a pie can carry legibly. A horizontal bar chart sorted by value communicates the same split faster and supports comparison across periods, which a pie cannot do.
How do you chart forecast versus actual?
Use a line for cumulative actual against a line for the plan pace, both running across the period. Add a marker where each forecast was submitted so the reader can see how the call changed over time. Bar-versus-bar comparisons hide the timing that makes forecast error diagnosable.
What is the right way to show pipeline coverage on a chart?
Show the ratio as a single value with a trend sparkline, and put a composition chart directly beneath it broken out by age, segment, and owner. Coverage plotted alone as a line invites conclusions that the composition would contradict.
How many charts should one dashboard have?
Three or four on the main view, with single-value tiles above them. Every additional chart reduces the attention each one receives, and dashboards past roughly six charts get scanned rather than read. Diagnostic charts belong on a second view that opens when a headline number moves.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo