Five HubSpot Reports to Build Before Any Dashboard

Five reports earn their place before anyone builds a dashboard. Stage conversion, pipeline created against the gap, time in current stage on open deals, closed lost reason by value, and a data integrity report covering the properties the other four depend on. All five are native HubSpot report types. None of them need a custom object, an integration or a data warehouse.

The request almost always arrives the other way round. A board meeting goes badly, someone asks for a revenue dashboard, and two weeks later the portal holds a twenty-tile screen that nobody opens after the first Monday. The tiles are not wrong. They answer questions nobody was asking, built on properties nobody was filling in.

Why build reports before a dashboard?

A dashboard is a distribution format. A report is a question with a defensible answer. Building the second first is the only order that produces something people use.

The practical test is whether a tile would change a decision in the next fortnight. Most tiles on most dashboards fail it. Total contacts, email open rate and deals created this month are measurements, and measurement without a decision attached is decoration. Five reports that each drive a specific action beat twenty that describe the business back to itself.

HubSpot documents its report types under create custom reports. Two matter here. Funnel reports measure conversion between stages. The custom report builder analyses a primary data source alongside related objects and adds calculations, which is why we build four of the five below in it as standard. Stage conversion stays a funnel report. Both report types need a Professional or Enterprise subscription.

Which report shows you where deals are lost?

A funnel report on the deal pipeline, stage by stage, over a rolling two quarters.

Stage conversion is the report everything else hangs off. It tells you which transition leaks, and the leak is rarely where people assume. Teams who believe they have a closing problem usually have a qualification problem showing up three stages later. The funnel makes that argument settleable rather than repeatable.

Read it as a sequence of pairs rather than a single number. Discovery to qualified tells you about lead quality. Qualified to proposal tells you about discovery depth. Proposal to closed won tells you about pricing, competition and whether your champion was ever real. One headline win rate blends all three into a figure that cannot be acted on.

Note the behaviour of funnel reports when deals skip stages, because a pipeline where reps routinely jump from discovery to proposal produces conversion rates that look better than reality. If that is happening, fix the pipeline rules before you trust the report.

Which report tells you whether you will hit next quarter?

A deals report in the custom report builder, showing sum of Amount by Create date, segmented by source, with your required pipeline overlaid.

Pipeline created in a month is the earliest number you have about a quarter that has not started. Closed won tells you about work finished months ago. New pipeline tells you whether the engine is still feeding.

Segment it by source from the start. Total pipeline created looking flat while inbound falls and outbound rises is a different business to one where both hold steady, and the aggregate hides it. Overlay the pipeline you need rather than the pipeline you want, derived from your own conversion rates in the first report rather than a coverage ratio borrowed from a blog.

This is also the report that catches sandbagging and deal stuffing, both of which show up as unusual shapes in create date rather than as anything visible on a board.

Which report finds deals that stopped moving?

A deals report in the custom report builder, filtered to open deals and using Time in current stage against a threshold you set per stage.

The property matters. HubSpot's stage calculated properties include Latest time in and Cumulative time in, and neither returns a value while a deal is still sitting in the stage. Build this report on Time in current stage, or the deals you are hunting will not appear in it.

Set the threshold from your own closed-won median by stage rather than a round number. Review it weekly. Ten minutes in the pipeline meeting on deals past threshold does more for forecast accuracy than any amount of probability tuning, and it is the report that most directly improves the number you take to the board. The wider argument for that sits in what good forecast accuracy looks like.

Which report explains the misses?

A deals report in the custom report builder, sum of Amount rather than deal count, grouped by closed lost reason, over four rolling quarters.

Value lost and deals lost tell different stories, and most teams only ever look at the second. Twelve small losses to went dark is a prospecting quality problem. Two large ones to no decision is a deal strategy problem, and it costs more.

The report only works if the property underneath it does. A closed lost reason picklist with twelve options, left optional, produces sixty per cent Other and no finding. Five to seven options, required on exit to the closed lost stage, gives you something you would defend in a QBR.

Which report tells you whether to believe the other four?

A deals report in the custom report builder, counting open deals where the properties the first four depend on are unknown.

This is the one teams skip and the one that decides whether the other four are worth building. Open deals with no close date, no amount, no next activity date, or an owner who left eight months ago. Each one quietly distorts a report above it. A deal with no amount drops out of your pipeline created figure. A deal with a close date three quarters out inflates coverage. HubSpot's default deal properties documentation is worth reading alongside this, because several properties people report on are set automatically and behave in ways that surprise people.

Run it as a count, watch the trend, and set an internal threshold you would be comfortable stating out loud. If more than a small share of open pipeline is missing a field your forecast depends on, the honest position is that the forecast is an estimate of an estimate. Fixing that is usually a property and permissions exercise rather than a reporting one, which is the argument in why the right fields beat more fields.

Build these five, use them for a quarter, and the dashboard builds itself out of whatever people keep opening. That order also tells you which tiles to leave out, which is the harder half of the job.

Our RevOps Audit covers exactly this ground, your properties, your pipeline rules and your reporting together, and hands back a prioritised plan rather than a screenshot of a dashboard.

FAQs