Pipedrive Insights is the built-in reporting and analytics module that gives sales managers visibility into pipeline health, team performance, and revenue forecasting — without exporting data to a spreadsheet. For teams that have historically tracked performance via manual pipeline reviews or Excel reports, Insights centralises the data that already exists in Pipedrive deals and activities into dashboards that update in real time. This guide covers what Insights can actually show, how to build useful reports, the key limitations, and fixes for the common problems teams hit when setting up reporting.
That makes the feature set especially useful for managers who want a lighter reporting layer without moving to a heavier business intelligence stack.
Pipedrive Insights exists to make pipeline reporting and analytics easier for teams that want a straightforward sales CRM. The value is not just in charts, but in whether the reporting helps the team understand what is happening in the pipeline and what to do about it.
What Pipedrive Insights Covers
| Report Type | What It Shows | Plan Required |
|---|---|---|
| Deal reports | Deals created, won, lost by rep, stage, time period, and custom filters | Essential ($14/user) |
| Activity reports | Calls, emails, meetings logged by rep; activity completion rates | Essential |
| Revenue reports | Won deal value by period, rep, pipeline, and product | Essential |
| Pipeline velocity | Average deal value, win rate, deal length, and deals in pipeline — combined into velocity metric | Essential |
| Revenue forecast | Weighted revenue forecast based on deal stage probability and expected close dates | Professional ($49/user) |
| Goals tracking | Set targets for deals won, revenue, and activities; track progress vs. goal | Professional |
| Custom dashboards | Build dashboards with multiple reports; share with team or individual managers | Professional |
Building a Deal Performance Report
Navigate to Insights → Reports → Add new report → Deals. Select the metric (deals won count, deals won value, deals lost, deals created). Set the date range, group by (rep, pipeline, stage, or time period), and apply filters (pipeline, label, custom field values). The resulting chart or table updates to show the filtered data. Save the report and add it to a dashboard for quick access.
The most useful standard reports for sales managers:
- Won deals by rep by month: Shows each rep’s closed revenue with monthly trend — the baseline performance tracking report
- Deal age by stage: Shows average time deals spend in each pipeline stage — identifies where deals stall
- Win rate by source: If deals have a lead source field, shows which sources convert at the highest rate
- Activities completed by rep: Shows who is logging the most activities; useful for coaching conversations
Revenue Forecasting
The revenue forecast in Insights (Professional plan) calculates expected revenue by multiplying each open deal’s value by the win probability assigned to its pipeline stage. For example, a £50,000 deal in a stage with 60% probability contributes £30,000 to the forecast. The forecast report shows weighted and unweighted pipeline by time period. To make forecasts reliable, two things must be configured: (1) expected close dates on all open deals — deals without close dates are excluded from time-period forecasts; (2) stage probability percentages calibrated to your actual win rates, not left at Pipedrive defaults.
“Reports show different numbers than I expect when I manually count deals”
The most common cause is the date filter logic. Insights deal reports filter by the date a deal entered a specific state — for won deals, it’s the date the deal was marked won, not the deal’s expected close date. If you’re comparing Insights to a manual count of deals that closed this month, ensure your Insights date filter is set to “Won date” in the current month, not “Created date” or “Expected close date.” These are different fields and produce different numbers.
“Revenue forecast is wildly inaccurate compared to what actually closes”
Forecast accuracy depends entirely on stage probability settings. Pipedrive sets default stage probabilities (e.g., 20% for first stage, 80% for proposal sent). These defaults are almost never accurate for any specific business. Fix: go to Settings → Pipeline and adjust stage probabilities to reflect your actual historical win rates by stage. If you win 40% of deals that reach proposal and 80% of deals that reach verbal agreement, set those stages to 40% and 80% respectively. Recalibrate after each quarter based on actual results.
“I can see the reports but can’t share them with my manager who’s not in Pipedrive”
Insights dashboards can only be shared with other Pipedrive users — there’s no public URL sharing or PDF export directly from the Insights module. Workaround options: (1) take a screenshot of the dashboard for ad-hoc sharing; (2) use the “Export to spreadsheet” option on individual reports, which downloads a CSV; (3) connect Pipedrive to Google Sheets via Zapier or a native integration and build a shared spreadsheet view. For recurring executive reports, many teams build a scheduled CSV export via automation and distribute by email.
“Goals aren’t updating even though deals are being won”
Goals track against specific metrics over specific time periods. If a goal shows zero progress when deals are being closed, check: (1) the goal’s assignee — if a goal is assigned to a specific rep, only that rep’s deals count; (2) the goal’s pipeline filter — goals can be scoped to a specific pipeline, and deals from other pipelines won’t count; (3) the goal metric type — a “deals won count” goal and a “revenue won” goal are different things; (4) the time period — goals with a monthly period reset on the 1st; progress from prior periods doesn’t carry over.
What Insights Doesn’t Do
- No cohort analysis or retention/churn reporting — Pipedrive is a sales CRM, not a customer success tool
- No marketing attribution reporting — there’s no connection between website traffic source and deal outcomes (requires HubSpot-style marketing integration)
- No multi-pipeline consolidated views on Essential — granular cross-pipeline analysis requires Professional
- No scheduled email delivery of reports — reports must be accessed manually in Pipedrive
- No integration with BI tools (Tableau, Looker) natively — requires a third-party data connector or CSV export workflow
Turning Insights into Repeatable Sales Actions
Reports are only valuable when they drive decisions. Bridging the gap between dashboard data and frontline rep behaviour is where most analytics programmes either succeed or stall.
How long does it take to see measurable results after implementing a CRM?
Most teams see initial productivity improvements — reduced manual data entry, better follow-up consistency — within the first 30 days. Measurable impact on pipeline velocity and conversion rates typically emerges after 90 days, once sufficient data has accumulated to surface patterns and the team has moved past the learning curve.
What is the biggest mistake organisations make when adopting a new CRM?
Trying to replicate their old process exactly rather than redesigning for the new tool. The migration from spreadsheets or a legacy system is an opportunity to standardise definitions, eliminate redundant steps, and automate manual work. Teams that migrate as-is lose most of the potential value.
How should we handle contacts who exist in multiple systems?
Designate one system as the master of record for contact identity data. Sync from that master to other systems rather than maintaining parallel copies. Run a deduplication process before and immediately after migration, and configure duplicate detection rules in your CRM to prevent future proliferation.
What is a reasonable CRM adoption rate to target in the first 90 days?
Target 80% of your defined “core actions” being logged in the CRM by 80% of users within 90 days of go-live. Core actions should be limited to 3–5 specific behaviours (e.g., log every call, update deal stage after each meeting, create a contact for every new prospect). Measure completion rates weekly and address laggards individually.
When should a business consider switching CRM platforms?
Consider switching when: the current platform’s limitations are blocking more than one strategic initiative simultaneously; the total cost of workarounds (integrations, manual processes, additional tools) approaches the cost of migration; or the vendor’s roadmap has diverged from your business direction over two or more consecutive product cycles.
The most useful reporting setup is the one that helps the team turn visibility into action. If the reports are easy to build but hard to use, the value drops quickly.
Common Problems and Fixes
Common Problems and Fixes
Problem: Dashboards Show Vanity Metrics That Do Not Drive Decisions
Activity-heavy dashboards full of call counts and email volume create the illusion of productivity without surfacing whether those activities are converting to revenue. Fix: Rebuild your primary dashboard around outcome metrics: conversion rate by stage, average deal velocity, and revenue per rep. Keep activity metrics in a separate operational view for managers.
Problem: Reports Are Manually Rebuilt Each Month, Wasting Time
Sales teams that export CRM data to spreadsheets for manual manipulation each reporting period introduce error risk and lose hours per cycle. Fix: Invest time once to configure saved reports and scheduled email delivery. Most CRM platforms support automatic report distribution — set up weekly and monthly reports to land in stakeholder inboxes without manual intervention.
Problem: Data Gaps in Reports Undermine Confidence in CRM Adoption
When reports show incomplete pipeline data, leadership loses confidence in the CRM and reps lose motivation to maintain records. Fix: Identify the specific fields that are most frequently blank. Make those fields required on the record layout, and run a weekly “data completeness” report that names individual reps with the highest percentage of incomplete records.