Data and RevOps
HubSpot dashboards for leadership: what to measure and how to build
Five questions a leadership dashboard should answer, the HubSpot reports that cover them and the data you need to get right for the numbers to add up.
A HubSpot dashboard for leadership should answer five questions in two minutes: how much will we sell this quarter, is the pipeline enough to cover the next ones, where do opportunities come from, where do they get stuck and which customers are at risk. If it answers more, something is surplus; if it answers fewer, a piece of data is missing from the CRM.
We explain which reports to build for each question, which data needs to be right in HubSpot for them to be reliable and which tools you need depending on your edition.
Start with the questions, not the charts
HubSpot comes with a report library and dashboard templates you can create in seconds. The result is usually a screen with fifteen charts that nobody in leadership opens twice. Better to do it the other way round: write down the questions asked in the Monday meeting and design one report per question.
| Leadership question | Report | Data it needs in HubSpot |
|---|---|---|
| How much will we close this quarter? | Forecast by category and rep | Amount, close date and forecast category kept up to date |
| Do we have enough pipeline? | Weighted pipeline by close month against target | Realistic stage probabilities and goals loaded |
| Where do opportunities come from? | Deals created by original source | Contacts associated with deals and sources properly recorded |
| Where do they get stuck? | Stage-to-stage conversion and time in each stage | Stages with clear criteria and no skipping |
| Which customers are at risk? | Upcoming renewals, open tickets, accounts with no activity | Renewal dates and tickets associated with companies |
- 01Leadership question
- 02Data in the CRM
- 03Report
- 04Dashboard
- 05Decision in the meeting
Dashboard 1: sales and forecast
This is the one people check most. Four or five reports are enough:
- Closed-won revenue against target for the period, by team. Goals are loaded in HubSpot per rep or per team.
- Forecast from the Sales Hub forecasting tool, with the categories the team uses, or as a weighted pipeline if your edition does not include it in full.
- Open pipeline by stage and close month, to see whether the coming quarters are covered.
- Stalled deals: open with a close date in the past or with no activity in recent weeks.
- Win rate and average sales cycle by business line.
Stage conversion and time-in-stage reports rely on the dates HubSpot records when a deal enters and leaves each stage. That is why changing stages lightly breaks the history; we explain it in how to design sales pipelines in HubSpot.
How to make the forecast credible
A forecast that changes every week without explanation stops being looked at. For leadership to trust it, the sales team has to review its deals on a fixed cadence (for example, the Friday before the meeting) and the close date has to mean the same thing to everyone: when we expect the signature, not when we would like it.
It helps a lot to separate two figures on the dashboard: the weighted pipeline, which comes from the stage probabilities, and the forecast each rep submits using their categories. When the two drift far apart, there is a conversation waiting to happen in the sales meeting. Over time, comparing forecast against closed for each quarter tells you which reps and which stages are optimistic.
Dashboard 2: acquisition and marketing
- New contacts and MQLs by source and by month.
- Funnel conversion by lifecycle stage: lead, MQL, SQL, opportunity, customer.
- Deals and revenue by the contact's original source.
- Time from MQL to first sales contact.
To know which campaign or channel generates revenue, and not just contacts, you need the attribution reports, which have edition requirements of their own. Check them against your subscription before promising leadership a revenue-by-channel view.
Dashboard 3: customers and retention
In companies with recurring revenue or a lot of repeat business, leadership needs to see the customer base and not just the pipeline: renewals in the next 90 days, customers with high-priority open tickets, satisfaction from surveys and customers with no recent sales activity. At a SaaS company we migrated from Salesforce, for example, ARR and account type are calculated daily and stored in HubSpot precisely so they can be reported here.
If invoicing lives in an ERP, this dashboard improves a great deal when invoices and payments flow back into the CRM. That is what we do in our HubSpot integrations with tools such as Holded or Stripe: the invoice number, the PDF and the payment status sit on the deal or on an object of their own.
How to build them in HubSpot
Templates and the report library cover many cases. The custom report builder, which is essential for combining objects (deals with companies and contacts, tickets with companies), is documented for the Professional and Enterprise editions, and the number of reports you can create depends on the subscription. Some practical tips:
- Use dashboard filters (period, team, owner) instead of duplicating reports for each rep.
- Name reports after the question they answer. "Do we have pipeline for next quarter?" is clearer than "Deals by close date v2".
- Schedule the dashboard email to leadership for Monday morning. It arrives before the request for the spreadsheet.
- Control who edits the leadership dashboard: let the right people view it, but only the CRM administrator change it.
- Add a line of context to each report: what it includes and what it does not, for example "excludes renewals".
Before
- Spreadsheet built by hand every Monday
- Different figures depending on who prepares it
- Deals with no close date
After
- Dashboard emailed every Monday
- One definition per KPI
- Amount and date required on qualification
Why don't the numbers add up?
The first dashboard almost always uncovers data problems: deals with no amount, close dates in the past, contacts not associated with their company, two pipelines whose stages mean different things. It is not a fault in the report; it is what was already there. Before presenting it to leadership:
- Make amount and close date required from the stage at which the deal counts as qualified.
- Review open deals with a close date in the past and ask each rep to update or close them.
- Write down the definition of each KPI (what counts as a new customer, which date is used for revenue) and put it on the dashboard itself.
- Compare total closed-won revenue with the finance figures at least once. Differences usually come from won deals that were never invoiced or invoices with no deal behind them.
What not to put on a leadership dashboard
Activity metrics without context (emails sent, calls made), email opens, website visits unrelated to revenue and any chart nobody can explain. Their place is on each team's dashboards, where they do help manage the day to day.
The leadership dashboard should fit on one screen and help people decide. A useful test: cover the title of each report and ask someone on the leadership team what decision they would make with it. If they cannot answer, that report is surplus or badly framed.
A living dashboard, not a finished project
Leadership's questions change with the company: a new business line, a new country, a shift towards recurring revenue. Review the dashboard every quarter with the people who use it, remove what nobody looks at and add what is missing. And every time a stage, a property or a definition changes, check which reports depend on it.
Designing these dashboards is part of every implementation we do at Vexco and of our HubSpot and RevOps support, because it is almost never a chart problem: it is a problem of definitions and data.
