How to create a custom dashboard in HubSpot CRM for tracking sales performance in 2027?

The scenario that forces the build

A 12-rep team runs one pipeline in HubSpot CRM with eight deal stages, and every Monday the VP of Sales pastes numbers into a spreadsheet because nobody trusts the out-of-the-box "Sales Dashboard." The stock dashboard ships with reports like deal forecast, deals created by owner, and activity totals — useful, but they answer HubSpot's questions, not this team's. The VP wants four things on one screen: coverage ratio against quota, stage conversion by rep, days-in-stage for anything currently open, and outbound activity volume normalized per rep per day. None of those exist as a default report card.

The reason the spreadsheet keeps winning is that the team never defined what "sales performance" means as a set of countable objects. Coverage ratio needs open pipeline amount divided by a quota number, and quota is not a native property on the deal record — it lives in a spreadsheet or in HubSpot's Forecast tool depending on the seat tier. Stage conversion by rep needs deal stage history, which HubSpot exposes through the deal stage timestamp properties (Date entered <stage> and Date exited <stage>) that the system writes automatically once a deal moves through a pipeline. Days-in-stage needs those same timestamps compared to today. Activity volume per rep per day needs the Activities object with a calls-and-emails filter and a rolling date frame.

So the build order is not "make a dashboard." It is: define the four questions, confirm each one maps to properties that already exist or can be created, build one report per question, then assemble those reports onto a canvas. Teams that skip the mapping step end up with a dashboard of pretty charts that quietly measure the wrong denominator — for example, counting deals created rather than deals worked, which flatters a rep who opens 40 junk records a month and punishes the one who works 6 real ones.

Set a concrete target before touching the software: a dashboard the VP can open at 8:00 a.m. Monday, read in under 90 seconds, and act on without exporting anything. That constraint caps the build at roughly 8–10 report cards. Anything past 12 cards on a single dashboard forces scrolling, and a dashboard that requires scrolling becomes a report library nobody reads.

How the dashboard actually gets assembled

The mechanical path in HubSpot CRM is short, and knowing the exact clicks removes most of the friction. From the main navigation, go to Reporting → Reports → Dashboards, then click Create dashboard in the upper right. HubSpot offers a template gallery (Sales, Marketing, Service, plus role-specific ones like Sales Manager) and a Start from scratch option. For a genuinely custom sales performance dashboard, start from scratch — templates pre-load reports you will delete anyway, and each deletion is a separate confirmation.

Name the dashboard something a stranger could parse six months later: "Sales Performance — New Business Pipeline" beats "VP Dashboard." Then set access. HubSpot gives three sharing modes: private to you, shared with everyone (view or edit), or shared with specific users and teams. For a performance dashboard, "shared with everyone, edit restricted to the owner" is the safe default — reps need to see it, and one accidental filter change by a rep should not alter what the VP sees.

Reports are built either from the dashboard ("Add report" → Create custom report) or from the Reports home. The custom report builder asks for a data source first. The three that matter for sales performance are:

• Single object → Deals for pipeline value, deal counts, average deal size, and stage timestamps.
• Single object → Activities for calls, emails, meetings, and tasks logged.
• Custom report builder (cross-object) when you need Contacts joined to Deals joined to Companies — for example, "closed-won deals by original source," which pulls a contact property onto a deal-level chart.

Once the data source is chosen, the builder is a drag-and-drop grid: fields go into the left panel, then you pick the visualization (vertical bar, horizontal bar, line, area, pie, donut, gauge, KPI number, table, or pivot table). The two shapes that carry a performance dashboard are the KPI number card for a single headline figure and the stacked bar for composition by rep or stage.

Filtering is where a report becomes trustworthy. Every performance report needs at minimum three filters: pipeline (so a Renewals pipeline does not contaminate New Business), deal owner or team (so the chart can be broken out by rep), and a rolling date range rather than a fixed one. Use "Close date is this quarter" or "is in the last 30 days" instead of typing explicit dates — a hard-coded range silently goes stale and produces a dashboard that looks fine and is wrong.

Dashboard-level filters sit above the cards and apply to every report that contains the filtered property. This is the highest-leverage feature on the whole surface: one dashboard with an owner filter replaces twelve per-rep dashboards. Add filters for deal owner, pipeline, and close date at the dashboard level, then save the default filter state as the view everyone lands on.

Finally, set delivery. Each dashboard supports recurring email on a daily, weekly, or monthly cadence to selected users. A Monday 7:30 a.m. weekly email to the sales team, with the dashboard image inline, means the review starts before the meeting rather than during it.

The numbers that make the cards worth reading

A dashboard is only as useful as the thresholds attached to each number. Build the cards with an explicit "good/bad" line in the title or description so nobody has to remember the benchmark.

Pipeline coverage. Open pipeline amount divided by the quota for the period. The widely used working range is 3x to 4x for a team closing roughly 25–33% of qualified pipeline; a team that wins closer to 20% needs 5x. Build this as a KPI card showing open deal amount filtered to the current quarter's close dates, and put the quota in the card description ("Target: $1.2M open against $300K quota = 4x"). HubSpot does not compute the ratio natively on a standard deal report, so either state the quota in the description or store quota as a custom property and use a calculated property to divide.

Stage conversion. Use the Deals funnel report, which lets you select an ordered set of stages and returns both count and conversion percentage between each pair. Break it down by deal owner. What you are hunting for is a rep whose stage-2-to-stage-3 rate diverges from team median by more than about 15 percentage points — that gap is a coaching signal, not noise. With 12 reps and a quarter of data, roughly 40–60 deals per rep gives conversion percentages stable enough to act on; below about 20 deals per rep, single-deal swings dominate and the chart will mislead.

Days in stage. Deal stage timestamp properties let you build a report on "Days to close" or on a calculated property like today − Date entered Proposal. Show it as a horizontal bar by rep or as a table of open deals sorted descending. The actionable threshold is usually 1.5x to 2x the historical median for that stage — if proposals normally close in 14 days, anything sitting past 25 days goes on the review list. Compute the historical median once from a closed-won report, then hard-code that threshold into the card description and revisit it quarterly.

Activity volume, normalized. Raw call counts reward whoever dials the most. Normalize instead: calls per working day per rep, and meetings booked per 100 outbound touches. Build the Activities report filtered to activity type = Call and Email, grouped by activity assigned-to, over a rolling 30 days, then divide by ~21 working days in the card description. Connection rate and meetings-per-touch vary enormously by segment, so derive your own baseline from the first 60 days of data rather than importing a number from a blog post.

Average deal size and cycle length. Two KPI cards, both filtered to closed-won in the trailing 90 days. Watching these together catches the classic distortion where a rep hits a revenue number by closing one outlier while their cycle length balloons. If average deal size moves more than about 20% quarter over quarter without a pricing change, the mix shifted and the coverage ratio target needs rebuilding.

Card count and load. Practical limits matter for tracking that people actually do: keep a performance dashboard to 8–12 reports. HubSpot's dashboard limits depend on subscription tier, and heavy cross-object reports with wide date ranges render noticeably slower than single-object ones — if a dashboard takes more than a few seconds to paint, split historical trend cards onto a second dashboard and keep the primary one on rolling 30/90-day windows.

Where custom reports stop and other tooling starts

Not every performance question belongs on a HubSpot dashboard, and knowing the boundary saves weeks. The custom report builder handles cross-object joins across the standard CRM objects and, on higher tiers, custom objects — but it is still a reporting layer over the CRM's own data model. Three limits recur.

Quota and target data. Unless you use HubSpot's Forecast tools or store quota as a property, there is no native place for a per-rep monthly target. The workaround that holds up is a custom property on the Owner-adjacent record (or a small custom object for "Quota by rep by period") populated once a quarter, then referenced in a calculated property. The workaround that fails is typing quota into report descriptions and forgetting to update it — six weeks later every coverage card is measuring against last quarter's number.

Historical snapshots. Most deal reports show current state. If a deal moved from Proposal back to Discovery, a "deals by stage" report shows it in Discovery, and last month's pipeline as it looked last month is not recoverable from a standard report. HubSpot's deal stage timestamp properties partially solve this, and snapshot-style reporting exists on higher tiers, but if board-level "pipeline as of the first of each month" is required, the durable answer is a warehouse sync — pipe deals into a data warehouse nightly and build the trend there.

Blended data. Revenue attribution that spans product usage, billing, and CRM is not a HubSpot dashboard job. Once you need CRM data joined to invoice data joined to product events, a BI tool sitting on a warehouse is the right software, and the HubSpot dashboard becomes the operational surface reps look at daily while the BI layer answers the strategic questions monthly. Trying to force both onto one dashboard produces a slow page that satisfies neither audience.

The build-vs-template trade-off. Templates get a working dashboard in under five minutes and are genuinely correct for a small team on a single pipeline. Custom reports take 15–40 minutes each once you are fluent, plus the upstream property hygiene work. The honest rule: start with a template for the first 30 days while data volume is low, and rebuild custom only when you can name the specific decision a stock report failed to support. Building custom first, on a CRM with three weeks of messy data, produces precise charts of garbage.

Dashboard sprawl. Every new question tempts a new dashboard. Cap the org at a small number of named dashboards with owners — one per operating rhythm (daily rep view, weekly manager review, monthly leadership) rather than one per curiosity. An unowned dashboard drifts within a quarter, and the second nobody trusts it, the spreadsheet comes back.

The failure modes that quietly break the numbers

Fixed date ranges. The single most common defect. A report filtered to "Close date between Jan 1 and Mar 31" keeps rendering happily in Q2 while showing stale data. Audit every card for rolling ranges — "this quarter," "last 30 days," "this month so far" — and treat any absolute date as a bug unless the card is explicitly a historical archive.

Deal amount without currency or line items. If the team uses multiple currencies, confirm reports use the company-currency amount property rather than raw amount, or the pipeline total is meaningless. If deals get their value from line items, verify the deal amount actually syncs from line items — a deal with $80K of products and a blank amount field contributes zero to coverage.

Owner versus creator. Reports grouped by "created by" measure who typed the record; reports grouped by "deal owner" measure who owns the outcome. Performance tracking almost always wants owner. Check every grouped card, because the builder offers both and the labels look similar.

Unworked deals inflating coverage. A pipeline padded with deals that have no activity in 45 days shows 5x coverage and forecasts like 2x. Add a "last activity date" filter or a companion card counting open deals with no activity in 30+ days. That second card is often the most valuable thing on the dashboard.

Stage definitions drifting between reps. Conversion rates are only comparable if "Proposal" means the same thing to everyone. Write one-sentence exit criteria for each stage into HubSpot's stage settings and review them quarterly. Without that, a stage conversion chart is comparing twelve different private definitions.

Deleted or renamed properties. Renaming a property in HubSpot generally keeps reports intact, but deleting one breaks every report referencing it, and archived properties disappear from the builder. Before any property cleanup, search which reports use it. Keep a short changelog of property changes next to the dashboard's documentation.

Permissions confusion. A rep with restricted CRM access sees a dashboard rendered against their own visible records, so their number and the VP's number differ for the same card. That is correct behavior and a constant source of "the dashboard is wrong" tickets. Either grant read access to team-level records for the reporting scope, or state plainly on the dashboard description that rep views are filtered to owned records.

No pruning ritual. Dashboards accumulate. Put a recurring 30-minute calendar block at the end of each quarter to delete any card nobody referenced in a decision. A tight 8-card dashboard that gets read beats a 20-card dashboard that gets ignored, and the whole point of tracking sales performance is that somebody acts on what the tracking shows.

Related questions

How many reports can one HubSpot dashboard hold?

Limits vary by subscription tier, and the practical ceiling is lower than the technical one. Keep performance dashboards to 8–12 cards so the whole view fits one screen. Push historical trend reports to a separate dashboard rather than scrolling.

Can I report on deal stage history rather than current stage?

Partially. HubSpot writes Date entered <stage> and Date exited <stage> timestamp properties automatically as deals move, which supports days-in-stage and velocity reporting. True point-in-time pipeline snapshots across past months generally require higher tiers or a warehouse sync.

Should each rep get their own dashboard?

No. Build one dashboard with a dashboard-level deal owner filter. Reps filter to themselves, managers filter to the team. Twelve near-identical dashboards drift apart within a quarter and multiply the maintenance cost of every change.

What is the fastest way to share the dashboard with the team?

Set sharing to everyone with view access and edit restricted to the owner, then enable recurring email delivery on a weekly cadence timed just before the pipeline review. The email carries the dashboard inline so the discussion starts from the same numbers.

Do I need custom properties before building reports?

Often yes for quota, target, and any team-specific segmentation. Create and populate those properties first — building charts on properties that are 40% blank produces confident-looking bars that mostly measure who remembered to fill in a field.

FAQ

Where exactly is the create-dashboard button in HubSpot CRM?

Navigate to Reporting → Reports, then select the Dashboards tab, and click Create dashboard in the top right. You will be offered a template gallery or a blank canvas. Choose the blank canvas for a genuinely custom sales performance dashboard, name it descriptively, and set sharing before you add the first report.

What data source should I pick for a sales performance report?

Start with the single-object Deals source for anything about pipeline value, stage, or close date, and the Activities source for call, email, meeting, and task volume. Reach for the cross-object custom report builder only when a chart genuinely needs a property from a different object, since cross-object reports render more slowly.

How do I make one dashboard work for both reps and managers?

Use dashboard-level filters. Add deal owner, pipeline, and close date as filters at the top of the dashboard; they cascade to every card containing those properties. Reps set the owner filter to themselves, managers clear it. Save the cleared state as the default so the dashboard opens on the full team view.

Why do two people see different numbers on the same card?

Almost always CRM permissions. HubSpot renders reports against the records each user is allowed to see, so a rep restricted to owned records sees a smaller pipeline than a manager with team-wide access. Fix it by widening read access for reporting purposes or by documenting the behavior directly in the dashboard description.

How often should the dashboard be rebuilt or pruned?

Review quarterly. Delete any card that has not driven a decision, re-derive threshold numbers like median days-in-stage from the latest closed-won data, and re-check every date filter for hard-coded ranges. Thirty minutes a quarter prevents the slow decay that sends the team back to spreadsheets.

Can the dashboard replace a forecast?

It supports one but does not replace it. A dashboard shows coverage, conversion, velocity, and activity — the inputs. A forecast is a judgment applied to those inputs, usually with rep-level commit categories. Keep the forecast as its own artifact and use the dashboard to argue about whether the forecast is credible.

Sources

• https://knowledge.hubspot.com/reports/create-dashboards
• https://knowledge.hubspot.com/reports/create-custom-reports
• https://knowledge.hubspot.com/reports/create-and-manage-reports
• https://knowledge.hubspot.com/records/hubspots-default-deal-properties
• https://knowledge.hubspot.com/deals/set-up-and-customize-your-deal-pipelines-and-deal-stages
• https://knowledge.hubspot.com/reports/use-funnel-reports
• https://knowledge.hubspot.com/properties/create-calculation-properties
• https://developers.hubspot.com/docs/api/crm/deals
• https://knowledge.hubspot.com/user-management/hubspot-user-permissions-guide
• https://knowledge.hubspot.com/reports/filter-your-dashboards

Related on PULSE

• How to clean up a messy HubSpot deal pipeline before reporting on it
• What pipeline coverage ratio should a B2B sales team target
• How to define deal stage exit criteria your whole team applies the same way
• When to move CRM reporting into a data warehouse and BI tool
• How to build a weekly pipeline review agenda from CRM data
• How to normalize sales activity metrics so volume does not beat quality