HubSpot sales KPI dashboard examples: 12 reports that drive action

Who this guide is for

• Sales managers preparing weekly pipeline reviews.
• Revenue operations teams standardizing KPI definitions.
• Founders who currently combine CRM exports in spreadsheets.
• Administrators deciding whether HubSpot reporting depth fits the process.

Symptoms of the problem

Common mistakes

• Putting total open pipeline at the top without age, next activity, or close-date quality.
• Comparing raw activity volume across different roles or territories.
• Mixing creation date and close date in the same narrative.
• Using average values when a few very large deals distort the result.
• Ignoring records behind a chart instead of drilling into exceptions.
• Giving every user edit access to shared dashboards.

Recommended process

1. Step 1

   Write the management questions the dashboard must answer.

2. Step 2

   Define each KPI, date property, denominator, filter, and owner.

3. Step 3

   Audit required deal and activity properties.

4. Step 4

   Build one report per decision, starting with standard reports.

5. Step 5

   Add global filters only where they preserve comparable definitions.

6. Step 6

   Test chart totals against a record-level view.

7. Step 7

   Run the dashboard in a weekly review and remove unused reports.

8. Step 8

   Document data-quality actions alongside performance actions.

HubSpot features that may help

• Sales analytics provides prebuilt reports that can be filtered and saved to dashboards in eligible Sales Hub subscriptions.
• Dashboards can group reports by audience and support filtering, access control, sharing, and record-level drill-down.
• Custom reporting depth, report limits, and sales workspace dashboard options vary by product, plan, seat, and permissions.
• Forecast reporting becomes useful only when stages, categories, close dates, and amounts are maintained.
• Saved views and workflows can turn dashboard exceptions into operating queues where available.

Data and configuration blueprint

• Outcome: closed-won amount by close date versus goal, win rate, median deal size, and sales-cycle length.
• Pipeline creation: qualified pipeline created by create date, source, segment, and owner.
• Coverage: open eligible pipeline divided by the remaining goal; keep the numerator rules written beside the report.
• Movement: stage-entry cohort conversion and median time in stage, separated by pipeline and segment.
• Execution: deals without a future next activity, overdue tasks, and records not updated within the agreed review window.
• Forecast: amount by forecast category, close-date slippage, and movement into or out of Commit.
• Source quality: qualified pipeline and closed-won amount by agreed attribution field, not raw lead count.
• Data quality: missing owner, amount, close date, source, associated company, or required stage evidence.

Step-by-step setup

1. Step 1

   Create an outcome band: closed revenue versus goal, win rate, and average or median deal size.

2. Step 2

   Create a pipeline band: new qualified pipeline, pipeline coverage, stage conversion, and pipeline velocity.

3. Step 3

   Create an execution band: deals without next activity, overdue tasks, and time in stage.

4. Step 4

   Create a forecast band: amount by forecast category and close-date slippage.

5. Step 5

   Create a source band: qualified pipeline and closed revenue by original or agreed attribution field.

6. Step 6

   Create a quality band: missing owner, missing amount, overdue close date, and invalid stage.

7. Step 7

   Apply a consistent pipeline, team, currency, and reporting-period definition.

8. Step 8

   Validate twelve reports on sample records before publishing the dashboard.

First 30 days

1. Step 1

   Days 1–5: agree on questions, KPI definitions, date properties, currencies, filters, and the owner of each response.

2. Step 2

   Days 6–10: audit deal data and create saved views for missing fields, stale close dates, and absent next activities.

3. Step 3

   Days 11–17: build the outcome, pipeline, execution, forecast, source, and quality bands using the simplest valid report type.

4. Step 4

   Days 18–24: reconcile every total against sample records, test permissions, and run two review meetings using the dashboard.

5. Step 5

   Days 25–30: remove unused charts, document definitions, assign data-quality ownership, and schedule the review cadence.

Decision criteria

• Use standard reports when they answer the question without custom joins.
• Use custom reporting only when the required objects and definitions justify the added maintenance.
• Separate executive, manager, and seller dashboards when each audience needs different actions.
• Do not add a KPI unless someone owns the response to a bad result.

When HubSpot is not needed

• A very small team has a handful of active deals and can review every record directly.
• Stages and required fields are not yet agreed.
• The source systems cannot provide reliable identifiers or outcomes.
• A lightweight CRM already answers the same management questions without manual consolidation.

Alternatives

• A governed spreadsheet for a low-volume pipeline.
• A lightweight CRM with standard pipeline reports.
• A business intelligence layer when data from many systems must be modeled centrally.
• Direct record views and a short weekly exception review before introducing more charts.

Practical checklist

• Every report answers one management question.
• Dates, denominators, currencies, and filters are documented.
• Outcome, pipeline, execution, and quality views are separated.
• Totals reconcile with sample records.
• Permissions match the dashboard audience.
• Exceptions can be assigned to an owner.
• Unused charts are removed.
• Plan and seat requirements are checked.

Related problems and use cases

Related features

Related tool

FAQ