Read the recap

Back to Hubsessed Office Hours: Reporting & Dashboards
Hubsessed Office Hours: Reporting & Dashboards

Hubsessed Office Hours - Reporting and Dashboards - Oct 28, 2026

  • Joshua OakesHost
  • Madelyn DonovanHost

Wednesday, October 28, 2026

Sign in to watch the full replay and read the transcript.

Sign inSubscribe free
SharePost on X (opens in a new tab)Share on LinkedIn (opens in a new tab)

Madelyn Donovan and Joshua Oakes on reporting the process, not only the outcome: a data set built live in a sandbox, yes-or-no steps turned into numbers, meeting outcomes, forecast categories, and why adoption is usually the hard part.

Key takeaways

Reporting on outcomes and reporting on process compliance are different jobs; the second asks what happened in a stage, not only what the rate was.

Before you build a process, pin down what is true; even the deal amount needs a definition, and a calculated amount can surface a flaw in the pricing behind it.

A date-entered field or a checkbox can become a one or a zero that you can add up and divide, so a process step becomes something you can measure.

Put calculated columns in a Data Hub data set instead of adding properties to every object; it keeps helper fields out of other places.

Breeze can write a formula, but check which property it picked; how well your properties are named may affect which one it picks.

A data set can bring in data from an external system by a join key, without integrating that system into HubSpot.

Data has to describe reality: meetings with no outcome set can't tell you how many meetings happened, and a lapsed status makes the gap visible.

For forecast categories, start with the defaults and keep them simple; the hard part is the months of adoption that follow.

Know whether you have an implementation challenge or an adoption challenge, and bring the right tools to each.

Questions answered

  1. 00:45Knowing whether your process is finished, and how reporting helps you reverse engineer itTopic
  2. 01:22An outcomes dashboard and a process-variance dashboardTopic
  3. 06:13Grounding the deal amount in what is trueTopic
  4. 07:26A calculated amount that surfaced a bug in a pricing formulaTopic
  5. 12:22How far have you gotten? Have you built out a version of this?Question
  6. 13:28A one-or-zero default property you can sum and divideTopic
  7. 14:56Building a data set from scratch in a sandboxTopic
  8. 18:39Letting Breeze write the formula, and checking which property it pickedTopic
  9. 20:40Property names, and new stages that show up as numbersTopic
  10. 23:51A rate that spans stages, including administrative onesTopic
  11. 25:20Process compliance: turning a skipped review into a yes or noTopic
  12. 28:49A legal-review status, and joining outside data into a data setTopic
  13. 31:19Getting something quantitative out of qualitative dataTopic
  14. 32:43Math isn't real: making the data describe realityTopic
  15. 33:57Meeting outcomes, and a lapsed status for meetings nobody closed outTopic
  16. 36:45Forecasting: the dashboard everyone wants and the category nobody fills inTopic
  17. 38:39A new source or campaign: rates against history and against goalTopic
  18. 41:44Have you come up with any best practices for deciding what your forecast categories are?Question
  19. 45:26Go with the basics: the hard part of forecasting is adoptionTopic
  20. 47:30Takeaways: Data Hub, and data sets instead of more propertiesTopic
  21. 49:16Keeping metadata properties out of people's work zonesTopic
  22. 51:10Start with the defaults, and tell an implementation challenge from an adoption challengeTopic

Related episodes