In short
Source: Sales Surge, dashboard project methodAs of: 16 November 2026
In this article
- Does Pipedrive have sales forecasting and customizable dashboards?
- Five mistakes that make your dashboard useless
- Which KPIs belong on a sales dashboard?
- Four layers: from data to a decision
- How do you build a sales rep performance dashboard in Pipedrive?
- How many KPIs should a dashboard show?
- Once the basics work: threshold alerts
- When do you need Looker Studio or Power BI?
- How to build it, step by step
- What a dashboard project with Sales Surge includes
- Frequently asked questions
You have dashboards full of numbers, but cannot explain why you missed last quarter's target. Your team looks at different metrics and nobody agrees on what a good quarter looks like. A dashboard should drive a decision and show a problem in time, not just report what already happened. This piece covers which KPIs that takes, and how to build them in Pipedrive.

Does Pipedrive have sales forecasting and customizable dashboards?
Yes. Pipedrive Insights is the reporting module of Pipedrive. You build your own reports on deals, activities and revenue, and combine them on dashboards you share with the team. Pipedrive also has a forecast view that shows expected revenue per period, based on deal value and expected close date. Which report types you get depends on your plan.
What Pipedrive does not do on its own: report across objects, follow cohorts over time, and combine numbers from several accounts or sources. That is why we built Surge Reports, a reporting layer on top of Pipedrive for funnel health, deal risk and forecast across sources.
Five mistakes that make your dashboard useless
#1: Too many metrics
Why it fails: 'We had 10,000 website visitors.' But how many became customers? On a crowded screen the team picks the number with the best story and celebrates a peak while revenue stands still
Fix: Five to seven metrics per dashboard. Further down you see how to split them per audience.
#2: Metrics without context
Why it fails: 'Conversion is 3%.' Is that good? Better than last month? Without a reference point nobody knows whether things are getting better or worse
Fix: Always show the previous period and the target next to it
#3: One dashboard for everyone
Why it fails: The CEO, the sales manager and the SDR get the same screen. Nobody sees what they can act on, so decisions go back to gut feel
Fix: One dashboard per audience, with the layer that fits that role
#4: No owner
Why it fails: If nobody is responsible for a metric, that metric drifts
Fix: Put one name next to every metric, not the name of a department
#5: Build and forget
Why it fails: The business changes and the dashboard stays where it was
Fix: Review it every quarter: is it still right, does anyone still use it, can you still act on it
Which KPIs belong on a sales dashboard?
Start with the six numbers we use as the base set in every dashboard project: lead-to-first-contact time, lead-to-deal cycle time, conversion per stage, response time on new leads, cost per won customer per campaign, and the trend in customer satisfaction. Add win rate and pipeline coverage as soon as you steer on a target.
The target values are a rule of thumb, not a promise. They vary by market, deal size and sales cycle. Replace them with your own numbers after a quarter.
| KPI | Definition | Formula | Target (rule of thumb) | Layer |
|---|---|---|---|---|
| Lead-to-first-contact time | How long a new lead waits for the first call or email | First contact date field minus lead creation time. An automation fills that field, Insights does not have it by default | Under 5 minutes for a hot lead | L4 |
| Lead-to-deal cycle time | How long it takes from lead to won deal | Average of close date minus creation date | Falling or stable per quarter | L3 |
| Conversion per stage | Share of deals that move to the next stage | Deals moved on divided by deals in the stage | Find the lowest and work there first | L3 |
| Win rate | Share of qualified deals you win | Won divided by won plus lost | Above 25% on qualified deals | L2 |
| Pipeline coverage | Open pipeline against your target | Open deal value in the period divided by target | 3 to 4 times the target | L2 |
| Cost per customer per campaign | What a campaign costs per won customer | Campaign cost divided by customers won from it | Lower than the margin on the first deal | L1 |
| Customer satisfaction | The trend in CSAT or NPS after delivery | Average score per quarter | Rising or stable | L1 |
Four layers: from data to a decision
Build your dashboards in these four layers, from the boardroom down to daily follow-up. Each layer shows where you build it in Pipedrive, which fields you need and what Pipedrive cannot do on its own. The targets are rules of thumb from the market, not a promise and not our own benchmark.
L1 North Star Metrics
Leadership and board
Annual Recurring Revenue (ARR) / MRR
The temperature of your business in one number
A growth rate you see every quarter, for example 20% a year
Net Revenue Retention (NRR)
Shows whether existing customers buy more over time or less
Above 110%, so you grow without a single new customer
CAC payback period
The number of months until a customer's gross margin covers the cost of acquiring them
Within 12 months
LTV to CAC ratio
Whether a customer earns more than it cost to win them
At least 3 to 1
In Pipedrive: An Insights report on revenue or won deals per month, on a separate dashboard for leadership.
Fields you need: Deal value, close date, a field for recurring revenue and a field for the customer's source.
What Pipedrive cannot do on its own: Recurring revenue and retention over several years. That needs cohorts or accounting as a source.
L2 Revenue Engine Metrics
VP Sales, CMO and RevOps
Pipeline Velocity
How fast deals move through your funnel
A rising trend, checked per stage
Average Deal Size
Whether deals are getting bigger or smaller
Rising or stable, never quietly falling
In Pipedrive: An Insights forecast or deals report with goals per team, plus the forecast view in the pipeline.
Fields you need: Deal value, expected close date, probability per stage and an owner on every deal.
What Pipedrive cannot do on its own: Velocity across several pipelines or accounts in one view.
L3 Conversion Funnel Metrics
Sales managers and marketing managers
MQL to SQL
Whether marketing delivers leads sales can work with
Above 40%, though it varies a lot per market
SQL to opportunity
Whether sales turns those leads into real opportunities
Above 60%
In Pipedrive: An Insights deals report with conversion per stage, and a report on time spent per stage.
Fields you need: Clearly defined stages, a required lost reason and a source field on every lead.
What Pipedrive cannot do on its own: Marketing-to-sales conversion when your leads come from another system.
L4 Activity & Efficiency Metrics
AEs, SDRs and everyone who makes their own calls
Outbound activity: calls, emails and LinkedIn
Whether the team keeps the agreed rhythm
Depends on how your prospecting works
Response time on a new lead
How long a new lead waits. Insights only measures this with a First contact date field that a Pipedrive automation or a Make.com workflow fills
Under 5 minutes for a hot lead
Meeting Set Rate
How much of your outreach turns into a meeting
Above 2% cold, above 15% warm
Touches per deal, per stage
How many touches it takes to close
Look at what your best people do and teach the rest
In Pipedrive: An Insights activities report grouped per user, on a dashboard per rep.
Fields you need: Activity types you actually use, and a next activity on every open deal.
What Pipedrive cannot do on its own: Linking activity to revenue per deal and per product in one report.
How do you build a sales rep performance dashboard in Pipedrive?
Create six reports in Insights, put them on one dashboard and filter it per user. Each rep sees their own numbers, and the manager sees the whole team on the same screen. Plan an afternoon of work if the fields are in order.
Response time on new leads is left out of this list on purpose. Insights does not measure it by default. You need a First contact date field that a Pipedrive automation or a Make.com workflow fills, or you take the number from Surge Reports.
Show the previous period next to every report and, where you can, a goal. A dashboard per rep is a tool for the weekly one-to-one, not a leaderboard. Once it is used as a leaderboard, people log activities to score instead of to sell.
- Step 1: check that every open deal has an owner, a value and a next activity. Without those three the reports are wrong.
- Step 2: create a new dashboard in Insights and name it after the role, for example Rep weekly view.
- Step 3: add the six reports below, each set to this week or this month.
- Step 4: add a filter on user, so everyone opens the same dashboard for themselves.
- Step 5: set goals per user for won deals and activities, so the report shows the distance to the goal.
- Step 6: review the dashboard every week in a ten-minute one-to-one, from the screen.
The six widgets:
- Activities completed this week, per type.
- Deals won this month, against the goal.
- Open deals without a next activity.
- Conversion per stage over the last three months.
- Average time a deal spends per stage.
- New deals this month, per source.
How many KPIs should a dashboard show?
Five to seven per dashboard. With twenty numbers nobody looks at any of them, and with three you miss the link between activity and outcome.
If you need more numbers, build more dashboards per audience instead of one full screen. Leadership looks at layers one and two. The sales manager at layers two and three. The rep at layer four and their own conversion. Anything that does not lead to a decision every week belongs in a report you open when you need it.
Once the basics work: threshold alerts
Threshold alerts
Problem: Nobody opens a dashboard every day, and then it is too late
Approach: Let the system raise the alarm as soon as a number crosses a line
Example: Pipeline coverage drops below 3 times the target and the VP Sales gets a message. Win rate drops more than 10 percent and someone looks at it the same day.
How to build it: Set the red line per metric, send a Slack or email message when it is crossed, for example with a workflow in Make.com, and name one person who responds
When do you need Looker Studio or Power BI?
When your data comes from more than one system, or when your questions run across time and objects. Pipedrive Insights is strong as long as everything sits in one Pipedrive account and your questions are about deals and activities.
Once revenue comes from accounting, leads from a marketing platform or retention from a subscription system, you need a place where those sources meet: Looker Studio, Power BI or a reporting layer on Pipedrive. The downside: a BI tool needs maintenance, because someone has to keep the connections and calculation rules up to date. Take that step only when a concrete question cannot be answered in Insights.
How to build it, step by step
For a dashboard in Pipedrive Insights this takes one to two weeks. Add several sources or Looker Studio and plan on four to six weeks, because most of the work then sits in the data model and the connections.
Phase 1: Find out what the question is (days 1 and 2)
- Talk to the people who will use the dashboard and ask what they are trying to answer
- Write down which decisions this dashboard should drive
- Decide per dashboard who it is for, from L1 to L4
Phase 2: Check and clean the data (week 1)
- Check whether the data in your CRM is correct
- Find out what you cannot measure today, and why
- Remove duplicates and half-filled records
- Set validation rules so it stays clean
Phase 3: Build the dashboards (weeks 1 and 2)
- Start with the L1 dashboard for leadership
- Then build L2 for management
- Create L3 and L4 for teams and individuals
Phase 4: Explain and train (week 2)
- Walk through the dashboards with the people who asked for them and collect their reactions
- Teach teams how to read them and what to do with them on Monday
- Put a fixed review moment in the calendar, weekly or monthly
- Write down what each metric means and how it is calculated
Phase 5: Monitor and adjust (ongoing)
- Check whether the dashboards are actually opened
- Ask what is missing and what is noise
- Remove what nobody uses and add what people ask for
What a dashboard project with Sales Surge includes
A dashboard in Pipedrive Insights starts from €1,500 with us and is live in one to two weeks. That covers the base set of KPIs, the reports per layer, goals per user and a walkthrough for the people who will work with it. If your data comes from several sources, we build in Looker Studio or add Surge Reports. That costs more, and the quote says how much.
The page on revenue dashboards shows how such a project runs. If you want the definitions of every metric first, they are in our KPI glossary. How dashboards fit into a complete Pipedrive setup is covered in the Pipedrive RevOps stack.
Frequently asked questions
Does Pipedrive have sales forecasting and customizable dashboards?
Yes. Pipedrive Insights lets you build your own reports on deals, activities and revenue, and combine them on dashboards you can share with the team. There is also a forecast view of expected revenue per period. What Pipedrive does not do on its own is report across objects in one view, or across several accounts or sources. For that you need an extra reporting layer.
Which KPIs belong on a rep performance dashboard in Pipedrive?
Six widgets cover most teams: activities completed per rep this week, deals won this month against the goal, open deals without a next activity, conversion per stage, average time a deal spends per stage, and new deals per source. Build them as Insights reports filtered per user. Response time on new leads needs a First contact date field that an automation fills, because Insights does not measure it by default.
When do you need Looker Studio or Power BI instead of Pipedrive Insights?
When your data comes from more than one system, such as the CRM plus accounting or a marketing platform, or when you need cohorts and history that Insights cannot hold. For a single Pipedrive account with standard sales questions, Insights is enough and cheaper to maintain. Start there and move only when a concrete question cannot be answered.
What does a dashboard project cost?
At Sales Surge a dashboard in Pipedrive Insights starts from €1,500 and is live in one to two weeks. A setup with several sources, for example in Looker Studio, costs more, and the quote says how much. If the data underneath is not clean yet, we start there, because a dashboard on dirty data shows the wrong numbers very neatly.
Can a dashboard fix bad CRM data?
No, it only shows what is in the CRM. Start by making three fields required: deal value, expected close date and a lost reason. Then remove the duplicates and agree per stage when a deal leaves it. Only then does a conversion number mean something, and you do not have to touch a single widget.


