Weekly lead management dashboard

Smart CRM & Sales Hub Dashboards & Reporting
1

Hi Community,

I’m looking for best practices on building a weekly lead management dashboard in HubSpot.

Our current process looks like this:

  • Marketing generates leads (excluding offline sources).

  • Qualified leads become MQLs.

  • Sales then works these leads and updates the Lead Status (Assigned, Contacted, Qualified Working, Do Not Contact, Disqualified, Bad Contact, etc.).

  • Once qualification criteria are met, the SQL Date is populated, and the lead progresses further into the pipeline.

The dashboard requirement is to report weekly on:

  • Total Leads

  • Total Workable Leads (MQLs)

  • Channel-wise performance (excluding offline sources)

  • Sales progression after MQL (Assigned → Contacted → Qualified Working → Meeting → SQL)

The biggest challenge is identifying which MQLs did not convert into SQLs and why.

I’m considering reports that show:

  • MQLs without an SQL Date

  • Breakdown by Lead Status

  • Sales owner performance

  • Time between MQL and first sales activity

  • Time from MQL to SQL

  • MQL aging (e.g., 7, 14, 30+ days)

  • MQLs with no assigned owner or no sales activity

Has anyone built a similar dashboard? I’m particularly interested in:

  1. The key reports and KPIs you include.

  2. Whether you rely primarily on Lead Status or lifecycle date properties for reporting.

  3. Any best practices for identifying leakage between MQL and SQL without creating overly complex reports.

I’d appreciate any recommendations or examples of dashboards that have worked well for your teams.

3

Hey @Deep_Kwatra,

Welcome to the Community! :partying_face:

Great breakdown and great question!! This may be best answered my folks in the community who have hands-on experience with this, but in here are a few threads that might help you get started:

Tagging in a few folks who may be able to chime in here! Hey @danmoyle, @Josh, @Alex_Boissonneault – do you have any suggestions for @Deep_Kwatra on this?

Thank you!

Sam, Community Manager

4

Hi @stassey , thanks for the tag! Happy to share what has worked well.

@Deep_Kwatra, I’d keep it as simple as possible by using lifecycle stage dates for conversion metrics and Lead Status for sales execution.

A dashboard I commonly build includes:

  • Leads > MQL > SQL funnel (using lifecycle date properties)

  • MQLs without an SQL Date (your primary leakage report)

  • MQLs grouped by Lead Status to understand why they haven’t progressed

  • MQL aging (7/14/30+ days since MQL Date)

  • Time from MQL > SQL and MQL > first sales activity

  • MQLs with no owner or no logged sales activity

  • Channel performance filtered to exclude offline sources

One best practice is to treat Lifecycle Stages as your source of truth for progression, while Lead Status explains what’s happening now. That combination makes it much easier to identify where leads are getting stuck without creating overly complex reports.

If your sales team updates Lead Status consistently, you’ll have a very actionable weekly dashboard.

5

Hey @Deep_Kwatra. Looks like you’ve got some good advice, but I’ll go ahead and share my perspective as well. More ideas and voices may help find new paths. :slightly_smiling_face: I’d keep this pretty simple and focus on making the handoff visible, not trying to report on every possible variation of the funnel. In HubSpot, I’d use lifecycle stage and the associated date properties for the actual funnel progression, and use Lead Status as the operational view of what sales is doing with those MQLs. Lifecycle stage tells you where the record is in the process, while Lead Status tells you what’s happening right now.

For the dashboard, I’d include weekly totals for Leads, Workable Leads/MQLs, and conversion from MQL to SQL. I’d also break MQLs down by source or channel, excluding offline sources, so you can see which inbound channels are producing real sales opportunities. Then I’d add a report for MQLs with no SQL date, segmented by Lead Status, owner, and age bucket. That’s usually where the leakage becomes obvious.

The reports that tend to be most useful are the ones that answer a few very specific questions: how long does it take sales to act on an MQL, how long does it take for an MQL to become SQL, and where do leads stall if they never convert? Time from MQL to first sales activity is especially important, because slow follow-up often looks like lead quality issues until you dig in. I’d also include MQL aging buckets like 7, 14, and 30+ days, plus a report for MQLs with no owner or no activity so you can catch process gaps early.

If you want the dashboard to stay useful, I’d avoid overbuilding it. My usual approach is one dashboard for weekly leadership reporting and one for sales ops/working the queue. Leadership gets volume, channel performance, and conversion; sales ops gets aging, owner performance, Lead Status movement, and stalled MQLs.

One thing I’d strongly recommend is requiring a reason when a lead is disqualified or never progresses. Otherwise, the dashboard tells you that something leaked, but not why it leaked. That’s the difference between a report and something the team can actually act on.

My general rule is: use lifecycle stage for the story of progression, Lead Status for the story of activity, and a reason field for the story of failure. That combination usually gives you enough visibility without making the reporting messy. Hope that helps!

6

Hi @Deep_Kwatra

That looks like a solid reporting framework. One approach I’ve found helpful is to separate funnel progression from pipeline health so each report answers a specific question rather than trying to capture everything in one view.

For identifying leakage between MQL and SQL, I’d consider including reports such as:

  • MQLs with no SQL Date (your current backlog)
  • MQLs grouped by Lead Status to understand where they’re stalling
  • MQL aging (for example, 7, 14, and 30+ days) to identify leads that may need attention
  • MQLs with no owner and MQLs with no recent sales activity to surface operational gaps
  • Average time from MQL to SQL to monitor qualification efficiency over time

Personally, I’d also be interested in comparing Lead Status with the corresponding lifecycle date properties rather than relying on only one. The lifecycle dates can help measure progression over time, while Lead Status provides additional context about where and why leads are being held.

Out of curiosity, are you planning to build this using standard single-object reports, or are you considering custom reports that combine contact activities, owners, and lifecycle information?