Hi there,
For a weekly sales reporting I want to create a dashboard woth the enclosed information. What is the best practise to built this?
for weekly SaaS metrics i’d start with the custom report builder rather than the standard dashboard widgets. create individual reports for each KPI: deals created this week, deals closed this week, MRR added, churn, etc. set the date filter to “this week” on each one.
the trick for week-over-week comparison is to duplicate each report and set the second copy to “last week”, then place them side by side on the dashboard. not as clean as a spreadsheet pivot table but it works.
for pipeline velocity stuff like average deal cycle time, use a calculated property that measures days between create date and close date, then report on the average per week.
Hey @TheoAndela, thanks so much for posting about this, that’s exactly why the HubSpot Community is here for! 
I’d love to put you in touch with our Top Experts: Hi @CHawkins, @Josh and @JWingate2 do you have best practices to share with @TheoAndela, please?
Thanks so much for your help and wishing you all a wonderful day!
Bérangère
Great question. Dashboards like this are often harder to build directly in HubSpot because you’re combining pipeline metrics, deal-level inspection, and weekly comparisons in one view. As mentioned, there are some workarounds like creating duplicate side by side reports in HubSpot, but it won’t be as flexible as a spreadsheet.
The cool thing is you can sync live spreadsheet visualizations into HubSpot dashboards by using the Add External Content feature.
You can automate this all with a tool like Coefficient from HubSpot’s App Marketplace - I do work there, so happy to help if you need!
1. Point and click in Coefficient to pull the raw deal and pipeline data into a spreadsheet (Google Sheets or Excel) and set it on a refresh schedule.
That lets you work with deals, stages, ACV, and dates in a much more flexible way than HubSpot dashboards allow.
2. Build three simple sections in the sheet that mirror your framework. Coefficient actually includes a Sheets Assistant that can help you build all of your formulas and visualizations.
3. Turn the sheet into a simple dashboard. The Sheets Assistant can help you do this too, or just do it for you.
Use:
- KPI cards for headline numbers
- A table for Top 5 deals
- A few summary metrics for pipeline health
4. Use the Add External Content button on a dashboard if you want the visualizations in HubSpot. And/or you can have Coefficient send cadenced Slack or email alerts with your report.
Thousands of RevOps teams levearge Coefficient because it allows cross-object reporting and more flexible analysis than HubSpot dashboards alone.
If you’re doing this every week, connecting HubSpot data directly to Sheets and auto-refreshing it can save a lot of manual exports and keep the dashboard always up to date.
@TheoAndela Your framework is smart — especially the time constraints. Most pipeline reviews balloon to 30+ minutes because there’s no structure. Capping it at 11 minutes forces you to focus on decisions, not discussion.
One thing I’d tweak: in section 2 (Top 5 Deals), sorting by ACV alone can hide the deals that actually need attention. A $15K deal that’s been silent for two weeks is more urgent than a $50K deal that had a meeting yesterday. If you can add “days since last activity” as a column alongside ACV, you get a view that combines value with urgency — and that’s where the real weekly decisions are.
For section 3 (Pipeline Check), “Any Top 5 at risk of slipping?” is the right question but it’s hard to answer from a dashboard. What usually works better: flag any deal where close date is this month AND last activity was 7+ days ago. That’s your “slipping” list — concrete, not subjective.
On the HubSpot build side, alex_m’s approach of duplicating reports with “this week” vs “last week” filters works, but it gets messy fast. An alternative: build one report with the X-axis grouped by week and filter to the rolling last 4 weeks. You get the week-over-week trend in a single chart.
@arttukoo friendly reminder that it is against the community guidelines to use AI without disclosing it.
Ah, thanks for flagging that @karstenkoehler . I used AI to help me resttructure this and should’ve disclosed that. I’ll remember to do that going forward.