Sales reporting, dashboards & forecasting
A free sales dashboard template. Five panels, real formulas, no analyst required.
I'm Lauren Pearson, and most founder-led teams asking for a sales dashboard template do not need a new tool. They need to know exactly which five things to build and what formula sits behind each one, so they can put it together in the CRM they already pay for. That is what this template gives you, panel by panel.
What the template covers. Five panels, one page.
| Panel | Formula / definition | Data source | Refresh |
|---|---|---|---|
| Pipeline by stage | Sum of open deal value, grouped by stage | CRM deal records | Live |
| Weighted forecast | Sum of (deal value × stage win probability), split into commit and best case | CRM deal records & stage probabilities | Live |
| Win rate, trailing 90 days | Closed-won ÷ (closed-won + closed-lost) | CRM closed deals, by rep and source | Daily |
| Average deal size & cycle length | Mean deal value; mean days from creation to close | CRM deal records, trailing 90 days | Weekly |
| Rep activity | Calls, emails and meetings logged per rep | CRM activity log or connected phone/email tool | Weekly |
Five panels is deliberate, not a minimum you build towards a bigger version. A dashboard that starts with forty widgets rarely gets looked at properly by anyone; one that starts with five gets checked every Monday, which is the entire point of building it.
How to use it. Build order, and where teams get the formulas wrong.
Build pipeline by stage first. It needs no historical data, just accurate stage names and deal values, and it is usually the fastest panel to get live. Weighted forecast comes second, and it depends entirely on stage probabilities being set honestly. If your CRM ships with default probabilities nobody has ever reviewed, replace them with numbers based on your last two or three closed quarters before trusting this panel for anything.
Win rate and cycle length need real trailing data, so build them once you have at least twenty to thirty closed deals to average across; below that, the percentage swings too much on a single deal to mean anything. When you do turn them on, define win rate correctly: closed-won divided by all closed deals, won plus lost, in the period, never divided by every deal ever created. Ebsta and Pavilion's 2025 GTM Benchmarks report, drawn from more than 440,000 opportunities and $43 billion in pipeline data, found win rates falling to 19% in 2025, down from 29% the year before, a reminder that this number is worth tracking precisely rather than estimating from memory.
Pipeline coverage is the check most teams skip. Once the forecast panel is live, compare total open pipeline against the quota still open for the quarter. Most B2B teams aim for three to four times coverage; below that, the weighted forecast is optimistic no matter how clean the maths behind it looks, and above it the real bottleneck is usually deals stalling mid-pipeline rather than a lead generation problem.
The rep activity panel is the one teams most often build wrong, usually by counting everything a CRM can log rather than what actually predicts a healthy pipeline. Logging every email open or link click produces a noisy panel nobody reads twice. Count the activities a rep actually controls and that correlate with deals moving, calls made, meetings booked, proposals sent, and leave passive tracking data out of this panel entirely. It is a leading indicator, not a surveillance tool, and it should read that way to the team seeing it.
A worked example. An eight-person B2B services team.
An eight-person B2B services firm I worked with had never built a dashboard, running the pipeline entirely from memory and a founder's mental tally. Building the five panels above took an afternoon inside their existing CRM, since every field the template needed already existed, it had simply never been reported on.
The pipeline-by-stage panel surfaced the first surprise: nearly 40% of open value was sitting in a stage called "in discussion" that had no defined exit criteria, deals could sit there indefinitely with no trigger to move them forward or mark them lost. The weighted forecast panel, once built on that same stage, was accordingly generous, since a vague stage with no time pressure attracted an optimistic default probability nobody had actually challenged.
The fix was not a new tool, it was renaming that stage into two clearer ones, "proposal sent" and "verbal commitment", each with its own probability and a defined maximum time a deal could sit there before a rep had to update it or mark it stalled. Once that split went live, the same five panels told a noticeably more honest story within a single closed quarter: coverage dropped from an apparent 4.2x to a real 2.6x, uncomfortable to see, but the kind of number a founder can act on three weeks before quarter end rather than discover in the final week. That is the judgement call I make on nearly every dashboard build: fix what the pipeline stages actually mean before trusting a single formula built on top of them.
It is worth being honest about what a dashboard cannot do, too. The five panels above will tell that same eight-person firm precisely where pipeline is thin or where a stage is quietly hiding stalled deals, but they will not tell anyone why a particular prospect went quiet, or whether a discount is the right call on a specific deal. Treat the template as the thing that tells you where to look, not the thing that makes the call for you. The founder still ran the actual conversation with the two reps whose deals had been sitting untouched in "verbal commitment" for six weeks; the dashboard only made it obvious that conversation was overdue.
Once your five panels are live and trusted, the natural next step for a growing team is a version built specifically for what leadership needs to see rather than the full operational detail here; our piece on the executive sales dashboard covers that layer. For the wider reporting build this template feeds into, see our approach to sales reporting, dashboards and forecasting.
Common questions.
Do I need a BI tool to build this template, or can I use my CRM?
Start in your CRM's native reporting. Pipedrive, HubSpot and Salesforce all support every panel in this template out of the box, and building there means the dashboard updates automatically as deals move. Move to a dedicated BI tool only once you need to blend CRM data with finance or marketing data on the same screen.
What if my CRM does not have stage probabilities set up yet?
Set them before building the weighted forecast panel, not after. Use your last two to three closed quarters to estimate a rough win probability per stage, even a simple 20/40/60/80% split by stage is far more honest than an unweighted total, and refine the numbers once a full quarter of new data confirms or corrects them.
How many deals do I need before this template is worth building?
There is no hard minimum, but win rate and cycle length panels get more reliable once you have at least twenty or thirty closed deals to average across. Below that, build the pipeline-by-stage and forecast panels first, since those are useful with even a handful of open deals, and add the trailing metrics once more history exists.
Should each rep see the full dashboard or just their own numbers?
Most CRMs let you filter the same underlying panels by owner, so a rep sees their own pipeline and activity while a manager sees the rolled-up version. Build one dashboard definition and apply role-based filters rather than maintaining two separate dashboards that can quietly drift apart.
How often should I update the template once it is built?
The panels themselves should refresh live or daily from the CRM without manual work. What needs a human check is the underlying data behind them, stage probabilities, won and lost reasons, roughly once a quarter, so the template keeps describing how the business actually sells rather than how it sold a year ago.
Want this template built around how your team actually sells? Let's set it up properly.
Get in touch and we'll build the five panels around your real pipeline stages, fix the ones that need renaming, and hand over a dashboard your team will actually check.
Let's talk ↑