Home/ Skills/ hubspot-reports-dashboards

general hubspot-reports-dashboards

hubspot-reports-dashboards

This skill should be used when the user asks to "build HubSpot reports", "design a HubSpot dashboard", "create reports in HubSpot", "set up HubSpot reporting", "HubSpot dashboard best practices", "build a sales dashboard in HubSpot", "create a pipeline report in HubSpot", "HubSpot custom reports", "design a marketing dashboard in HubSpot", or any variation of building reports and dashboards in HubSpot for B2B SaaS.

Download .md

HubSpot Reports and Dashboards

HubSpot reports turn your CRM data into answers. Dashboards organize those answers into views that different teams check daily. A good dashboard surfaces the 5-8 metrics that drive action. A bad dashboard has 30 charts nobody reads.

The principle: every report on a dashboard must answer a question someone asks at least weekly. "How much pipeline did we create this month?" is a valid question. "What's the average deal size by industry sub-segment by quarter?" is a one-time analysis, not a dashboard metric. Dashboards are for recurring questions. Ad-hoc analysis lives in reports.

Dashboard Architecture

The three dashboards every B2B SaaS team needs

Dashboard	Audience	Purpose	Review cadence
Pipeline Dashboard	Sales leadership, RevOps	Pipeline health, coverage, velocity	Weekly (Monday)
Activity Dashboard	SDR manager, sales ops	Rep activity, outreach metrics	Daily
Marketing Dashboard	Marketing leadership, demand gen	Lead volume, MQL conversion, attribution	Weekly

Dashboard rules

5-8 reports per dashboard. More than 8 and the dashboard becomes a wall of charts. Nobody reads past 8. Prioritize the metrics that drive decisions
One dashboard per audience. The VP of Sales and the SDR manager need different views. Don't force them to share one dashboard with 20 reports. Build separate dashboards
Every report must drive action. "Pipeline coverage is 2.5x" drives the action: "accelerate pipeline generation." If a report doesn't drive a clear action, remove it
Order by priority. The most important metric is top-left. The least important is bottom-right. Users read dashboards like pages: top-left to bottom-right

Pipeline Dashboard

Reports to include

Report	Type	What it shows	Action it drives
Pipeline by stage	Bar chart	$ value per deal stage	Identify stage bottlenecks
Pipeline coverage ratio	Single number	Current pipeline / quarterly target	Trigger pipeline generation if low
New pipeline created (this month)	Line chart or number	Pipeline created this period	Track pipeline generation pace
Pipeline by source	Pie chart	% from inbound, outbound, partner	Source health check
Deals closing this quarter	Table	Top deals with stage, amount, close date	Focus closing effort
Average deal size trend	Line chart	ACV over last 6 months	Detect ACV drift
Win rate trend	Line chart	% of opps closing won, last 6 months	Early warning for quality issues
Stale deals	Table	Deals with no activity in 30+ days	Pipeline cleanup trigger

Pipeline report configuration

Pipeline Coverage Ratio:
  Report type: Single number
  Measure: Sum of deal amounts (open, stages 2-6)
  Divide by: Quarterly revenue target (manual input or property)
  Display: "4.2x" with color coding (green > 3.5x, yellow 2-3.5x, red < 2x)

New Pipeline Created:
  Report type: Line chart
  Data source: Deals
  Filter: Create date is this month
  Measure: Sum of deal amounts
  Group by: Week
  Compare to: Same period last month

Activity Dashboard

Reports to include

Report	Type	What it shows	Action it drives
Emails sent (by rep)	Bar chart	Volume per rep this week	Spot low-activity reps
Meetings booked (by rep)	Bar chart	Meetings booked per rep	Track output metric
Reply rate (by rep)	Bar chart	Reply rate per rep	Identify email quality issues
Activities by type	Pie chart	Email, call, LinkedIn, meeting breakdown	Channel mix check
Meetings booked trend	Line chart	Weekly meetings booked, last 8 weeks	Trend detection
Sequence enrollment	Number	Prospects enrolled in sequences this week	Volume tracking
Response time	Number	Average time to respond to inbound leads	Speed-to-lead check

Marketing Dashboard

Reports to include

Report	Type	What it shows	Action it drives
Leads created (this month)	Line chart	New leads by week	Lead volume tracking
MQL volume	Line chart	MQLs by week, last 12 weeks	Pipeline input tracking
Lead-to-MQL conversion	Number	% of leads becoming MQLs	Quality check
MQL-to-SQL conversion	Number	% of MQLs accepted by sales	Alignment check
Leads by source	Bar chart	Lead volume by source channel	Channel performance
Self-reported attribution	Pie chart	"How did you hear about us?" distribution	Dark funnel visibility
Pipeline from marketing	Number	Pipeline $ from marketing-sourced leads	Revenue contribution
Cost per MQL by channel	Bar chart	CAC per MQL per channel	Budget allocation

Building Custom Reports

Report types in HubSpot

Type	When to use	Example
Single object	Simple counts or sums on one object	"Total deals in pipeline"
Cross-object	Data spanning contacts + companies + deals	"Pipeline by company industry"
Funnel	Stage-to-stage conversion	"MQL → SQL → Opp → Won conversion"
Attribution	Multi-touch attribution	"Revenue by first touch source"

Report building rules

Start with the question. "What % of MQLs from organic search become SQLs?" Then build the report. Not "let me see what reports I can build"
Filter to relevant data. Always filter by date range (this quarter, last 90 days). Unfiltered reports include stale data from 2 years ago
Use comparison periods. Show this month vs last month. This quarter vs last quarter. Without comparison, you can't tell if a number is good or bad
Name reports descriptively. "Pipeline Coverage Ratio - Q2 2025" not "Report 1" or "New Report." Future-you will thank present-you

Report Permissions and Sharing

Who sees what

Role	Dashboard access	Why
CEO / CRO	Pipeline dashboard + marketing dashboard	Revenue-level view
VP Sales	Pipeline dashboard + activity dashboard	Pipeline health + team performance
SDR Manager	Activity dashboard	Rep-level tracking
Marketing Director	Marketing dashboard	Lead and MQL tracking
Individual SDR	Personal activity dashboard (filtered to their data)	Self-monitoring
RevOps	All dashboards	Operations and data quality

Sharing rules

Reps see their own data. An SDR dashboard filtered to their records. They don't need to see other reps' numbers (unless the manager chooses to share for motivation)
Managers see team aggregates and individual breakdowns. Both the total and per-rep views
Leadership sees trends and ratios, not individual activities. The VP doesn't need to see how many emails Rep A sent. They need pipeline coverage, win rate, and forecast

Measurement

Metric	Definition	Target	Frequency
Dashboard usage	How often each dashboard is viewed	Weekly views by intended audience	Monthly
Report accuracy	Do reports match reality? Spot-check against raw data	100% accurate	Quarterly
Stale reports	Reports nobody has viewed in 90 days	0 (archive them)	Quarterly
Dashboard load time	How fast dashboards render	< 5 seconds	Monthly
Data freshness	Time lag between activity and appearance in reports	< 1 hour for most data	Monthly

Pre-Build Checklist

[ ] Dashboard audience defined (who will view this?)
[ ] 5-8 reports selected (each answers a weekly question)
[ ] Each report has a clear action it drives
[ ] Reports ordered by priority (top-left = most important)
[ ] Date filters applied to all reports
[ ] Comparison periods configured (vs last period)
[ ] Report names are descriptive
[ ] Permissions set (who can view, who can edit)
[ ] Dashboard tested with sample data
[ ] Reviewed with the intended audience before sharing widely

Anti-Pattern Check

25 reports on one dashboard. Nobody reads past 8. The dashboard becomes a wall of noise. Cut to the 5-8 metrics that actually drive decisions. Put the rest in an "Analysis" folder for ad-hoc use
Reports without date filters. A pipeline report showing data from 2022 mixed with 2025. Filter to relevant time periods. "This quarter" or "last 90 days" for most reports
Beautiful dashboards nobody uses. Spent 2 weeks building a dashboard. It's never opened after the first demo. Before building, confirm the audience will use it. Build the top 3 reports first. Add more only if the audience asks
Same dashboard for VP and SDR. The VP wants pipeline coverage and win rate trends. The SDR wants their personal meetings and reply rates. These are different audiences with different needs. Build separate dashboards
Reports that nobody acts on. "Average deal size by company sub-industry by quarter" is interesting once. It doesn't drive a weekly action. Remove it from the dashboard. Put it in an analysis report
Never cleaning up. 50 reports created over 2 years. 30 are outdated or unused. They clutter the report library and make finding the right report harder. Archive unused reports quarterly
No comparison periods. "We created $200K in pipeline this month." Is that good? Without comparing to last month ($180K or $250K), the number has no context. Always show vs previous period

Want agents that use skill files like this?

We customize skill files for your brand voice and methodology, then run content agents against them.

Book a call

# HubSpot Reports and Dashboards

## Dashboard Architecture

### The three dashboards every B2B SaaS team needs

| Dashboard | Audience | Purpose | Review cadence |
|-----------|---------|---------|---------------|
| Pipeline Dashboard | Sales leadership, RevOps | Pipeline health, coverage, velocity | Weekly (Monday) |
| Activity Dashboard | SDR manager, sales ops | Rep activity, outreach metrics | Daily |
| Marketing Dashboard | Marketing leadership, demand gen | Lead volume, MQL conversion, attribution | Weekly |

### Dashboard rules

- **5-8 reports per dashboard.** More than 8 and the dashboard becomes a wall of charts. Nobody reads past 8. Prioritize the metrics that drive decisions
- **One dashboard per audience.** The VP of Sales and the SDR manager need different views. Don't force them to share one dashboard with 20 reports. Build separate dashboards
- **Every report must drive action.** "Pipeline coverage is 2.5x" drives the action: "accelerate pipeline generation." If a report doesn't drive a clear action, remove it
- **Order by priority.** The most important metric is top-left. The least important is bottom-right. Users read dashboards like pages: top-left to bottom-right

---

## Pipeline Dashboard

### Reports to include

| Report | Type | What it shows | Action it drives |
|--------|------|-------------|-----------------|
| Pipeline by stage | Bar chart | $ value per deal stage | Identify stage bottlenecks |
| Pipeline coverage ratio | Single number | Current pipeline / quarterly target | Trigger pipeline generation if low |
| New pipeline created (this month) | Line chart or number | Pipeline created this period | Track pipeline generation pace |
| Pipeline by source | Pie chart | % from inbound, outbound, partner | Source health check |
| Deals closing this quarter | Table | Top deals with stage, amount, close date | Focus closing effort |
| Average deal size trend | Line chart | ACV over last 6 months | Detect ACV drift |
| Win rate trend | Line chart | % of opps closing won, last 6 months | Early warning for quality issues |
| Stale deals | Table | Deals with no activity in 30+ days | Pipeline cleanup trigger |

### Pipeline report configuration

```
Pipeline Coverage Ratio:
  Report type: Single number
  Measure: Sum of deal amounts (open, stages 2-6)
  Divide by: Quarterly revenue target (manual input or property)
  Display: "4.2x" with color coding (green > 3.5x, yellow 2-3.5x, red < 2x)

New Pipeline Created:
  Report type: Line chart
  Data source: Deals
  Filter: Create date is this month
  Measure: Sum of deal amounts
  Group by: Week
  Compare to: Same period last month
```

---

## Activity Dashboard

### Reports to include

| Report | Type | What it shows | Action it drives |
|--------|------|-------------|-----------------|
| Emails sent (by rep) | Bar chart | Volume per rep this week | Spot low-activity reps |
| Meetings booked (by rep) | Bar chart | Meetings booked per rep | Track output metric |
| Reply rate (by rep) | Bar chart | Reply rate per rep | Identify email quality issues |
| Activities by type | Pie chart | Email, call, LinkedIn, meeting breakdown | Channel mix check |
| Meetings booked trend | Line chart | Weekly meetings booked, last 8 weeks | Trend detection |
| Sequence enrollment | Number | Prospects enrolled in sequences this week | Volume tracking |
| Response time | Number | Average time to respond to inbound leads | Speed-to-lead check |

---

## Marketing Dashboard

### Reports to include

| Report | Type | What it shows | Action it drives |
|--------|------|-------------|-----------------|
| Leads created (this month) | Line chart | New leads by week | Lead volume tracking |
| MQL volume | Line chart | MQLs by week, last 12 weeks | Pipeline input tracking |
| Lead-to-MQL conversion | Number | % of leads becoming MQLs | Quality check |
| MQL-to-SQL conversion | Number | % of MQLs accepted by sales | Alignment check |
| Leads by source | Bar chart | Lead volume by source channel | Channel performance |
| Self-reported attribution | Pie chart | "How did you hear about us?" distribution | Dark funnel visibility |
| Pipeline from marketing | Number | Pipeline $ from marketing-sourced leads | Revenue contribution |
| Cost per MQL by channel | Bar chart | CAC per MQL per channel | Budget allocation |

---

## Building Custom Reports

### Report types in HubSpot

| Type | When to use | Example |
|------|------------|---------|
| Single object | Simple counts or sums on one object | "Total deals in pipeline" |
| Cross-object | Data spanning contacts + companies + deals | "Pipeline by company industry" |
| Funnel | Stage-to-stage conversion | "MQL → SQL → Opp → Won conversion" |
| Attribution | Multi-touch attribution | "Revenue by first touch source" |

### Report building rules

- **Start with the question.** "What % of MQLs from organic search become SQLs?" Then build the report. Not "let me see what reports I can build"
- **Filter to relevant data.** Always filter by date range (this quarter, last 90 days). Unfiltered reports include stale data from 2 years ago
- **Use comparison periods.** Show this month vs last month. This quarter vs last quarter. Without comparison, you can't tell if a number is good or bad
- **Name reports descriptively.** "Pipeline Coverage Ratio - Q2 2025" not "Report 1" or "New Report." Future-you will thank present-you

---

## Report Permissions and Sharing

### Who sees what

| Role | Dashboard access | Why |
|------|-----------------|-----|
| CEO / CRO | Pipeline dashboard + marketing dashboard | Revenue-level view |
| VP Sales | Pipeline dashboard + activity dashboard | Pipeline health + team performance |
| SDR Manager | Activity dashboard | Rep-level tracking |
| Marketing Director | Marketing dashboard | Lead and MQL tracking |
| Individual SDR | Personal activity dashboard (filtered to their data) | Self-monitoring |
| RevOps | All dashboards | Operations and data quality |

### Sharing rules

- **Reps see their own data.** An SDR dashboard filtered to their records. They don't need to see other reps' numbers (unless the manager chooses to share for motivation)
- **Managers see team aggregates and individual breakdowns.** Both the total and per-rep views
- **Leadership sees trends and ratios, not individual activities.** The VP doesn't need to see how many emails Rep A sent. They need pipeline coverage, win rate, and forecast

---

## Measurement

| Metric | Definition | Target | Frequency |
|--------|-----------|--------|-----------|
| Dashboard usage | How often each dashboard is viewed | Weekly views by intended audience | Monthly |
| Report accuracy | Do reports match reality? Spot-check against raw data | 100% accurate | Quarterly |
| Stale reports | Reports nobody has viewed in 90 days | 0 (archive them) | Quarterly |
| Dashboard load time | How fast dashboards render | < 5 seconds | Monthly |
| Data freshness | Time lag between activity and appearance in reports | < 1 hour for most data | Monthly |

---

## Pre-Build Checklist

- [ ] Dashboard audience defined (who will view this?)
- [ ] 5-8 reports selected (each answers a weekly question)
- [ ] Each report has a clear action it drives
- [ ] Reports ordered by priority (top-left = most important)
- [ ] Date filters applied to all reports
- [ ] Comparison periods configured (vs last period)
- [ ] Report names are descriptive
- [ ] Permissions set (who can view, who can edit)
- [ ] Dashboard tested with sample data
- [ ] Reviewed with the intended audience before sharing widely

---

## Anti-Pattern Check

- 25 reports on one dashboard. Nobody reads past 8. The dashboard becomes a wall of noise. Cut to the 5-8 metrics that actually drive decisions. Put the rest in an "Analysis" folder for ad-hoc use
- Reports without date filters. A pipeline report showing data from 2022 mixed with 2025. Filter to relevant time periods. "This quarter" or "last 90 days" for most reports
- Beautiful dashboards nobody uses. Spent 2 weeks building a dashboard. It's never opened after the first demo. Before building, confirm the audience will use it. Build the top 3 reports first. Add more only if the audience asks
- Same dashboard for VP and SDR. The VP wants pipeline coverage and win rate trends. The SDR wants their personal meetings and reply rates. These are different audiences with different needs. Build separate dashboards
- Reports that nobody acts on. "Average deal size by company sub-industry by quarter" is interesting once. It doesn't drive a weekly action. Remove it from the dashboard. Put it in an analysis report
- Never cleaning up. 50 reports created over 2 years. 30 are outdated or unused. They clutter the report library and make finding the right report harder. Archive unused reports quarterly
- No comparison periods. "We created $200K in pipeline this month." Is that good? Without comparing to last month ($180K or $250K), the number has no context. Always show vs previous period