Build better Quarterly Business Review (QBR) reports with Hubspot + Databox

Create a single executive view of sessions, leads, MQLs, deals, and revenue to anchor quarterly business reviews.

Author:
Cameron Collins, from RevPartners

Integrations: HubSpot CRM

Departments: Marketing, Operations and Sales

Pricing Plans: Professional

Features: Calculated Metrics and Dashboards

Summary

Quarterly Business Reviews often fail because performance data is fragmented across HubSpot objects. Sessions, leads, MQLs, deals, and revenue live in separate reports, forcing executives to interpret multiple charts that tell pieces of the same story. This makes it difficult to see where revenue leaks occur or why performance changes quarter over quarter.

This use case shows how Cameron Collins builds a single Databox dashboard that combines cross-object HubSpot metrics into one narrative view. By layering calculated conversion rates and average deal size on top of core funnel metrics, teams gain clearer visibility into what is working, where drop-offs happen, and which questions to ask next during QBRs.

Cameron’s tips and best practices

“Cross-object reports are really hard to not only create, but also to display.” 

When metrics are split across multiple HubSpot reports, interpretation becomes the bottleneck. The signal to watch for is when teams need four to six separate reports to explain one performance story. The action is to consolidate those metrics into a single cross-object dashboard so executives see the full picture at once.

“This setup gives you answers, but more importantly, it helps you ask better questions.”

The value of the dashboard is not just visibility but interrogation. Sudden changes in average deal size or conversion rates become diagnostic cues. When those metrics shift quarter over quarter, teams can immediately ask why and investigate the underlying funnel stage.

“One report, cross-object, actionable”

The key indicator of effectiveness is whether a single report can replace multiple disconnected views. If leaders can switch between table and funnel views to spot drop-offs without exporting data or rebuilding reports, the setup is doing its job.

Explore similar use cases

Prove Marketing Impact across every Location

Read more

Improve Monthly Revenue Outcomes by Spotting Sales Gaps Early

Read more

Understand how marketing influences pipeline across the full funnel

Read more

View all companies exposed to your ads on LinkedIn (not just the top 25)

Read more

FAQ

Can Databox replace HubSpot reporting for executive dashboards?

Yes – with caveats. Databox is ideal when you need to combine data from multiple sources or want better visualization options. However, for simpler reports that live entirely in HubSpot, native reporting tools may suffice.

What are the limitations of HubSpot’s reporting when it comes to cross-object or multi-stage funnels?

Users frequently report difficulties combining properties across objects (e.g. contacts + deals), inflated counts due to associations, and limited capabilities for custom calculations or visualizations.

What should I check when using Databox to ensure the metrics I need are available and reliable?

Always review the Metric Library for each data source. Pay attention to sync limitations, filtering options, and visualization compatibility – especially for advanced calculated metrics or segmenting.

How can I track drop-off between funnel stages like sessions → leads → closed won?

Use calculated metrics to track stage-to-stage conversion rates, and visualize them in both funnel and table formats. Include time comparisons (QoQ, YoY) and segment filters to pinpoint performance issues.

Can I segment metrics by campaign, region, or lead source?

Yes. Databox allows filtering at the dataset, dashboard, or individual chart level. Use UTM parameters and property-based filters to break down performance by source.

 

What are common workarounds when HubSpot reporting doesn’t support the views I need?

Export data to a BI tool (like Databox), use custom properties/workflows to bridge gaps, or rely on APIs to prep data externally before visualizing. These approaches help create the cross-object views HubSpot can’t support native.