Legal
Revenue Visibility That Won't Break When You Update It
Simple Strat replaced a 99-step HubSpot workflow with rollup and calculated properties, giving a legal services client reliable purchase volume and revenue reporting across four time windows they can actually maintain.
The Challenge
The client needed visibility into customer purchase volume and revenue across four specific time windows: the last 14, 90, 180, and 365 days. A solution was already in place. The problem was what that solution had become.
Over time, the workflow handling this reporting had grown into 99 steps of looping and branching logic. It was difficult to follow, harder to update, and increasingly risky to touch as the business scaled. When data inconsistencies came up, tracing them back to their source inside that workflow was its own project. The system was technically doing the job, but the cost of maintaining it was rising and the confidence in it was quietly eroding.
The goal wasn't just better reporting. It was reporting that someone could actually understand and own going forward.
The Solution
Rather than untangling the existing workflow step by step, the team looked at whether the same visibility could be achieved without the workflow complexity at all. Rollup and calculated properties can pull data directly from associated deals, which meant the logic could live in the properties themselves rather than inside a workflow that had to be actively monitored and maintained.
The Setup
Rollup properties were built to aggregate deal data across each of the four time windows. Calculated properties then do the math on top, combining volume and revenue figures into the reporting format the client needed. The logic sits at the property level, visible and auditable, rather than buried inside branching workflow conditions.
The Engine
One workflow stayed in place, but was reduced to three steps: a time delay that fires when a deal closes and tags it with the appropriate time window. That tag is what the rollups and calculations reference. Everything else that used to live in 99 workflow steps now lives in the properties themselves, running automatically without branching logic, looping, or manual oversight.
The Impact
The 99-step workflow is gone. What replaced it is something the team can actually own.
The client now has purchase volume and revenue data across all four time windows pulling directly from associated deals, without a workflow that needs to be monitored or maintained. When data inconsistencies come up, the source is visible in the properties themselves rather than buried inside branching logic. And because the solution doesn't rely on workflow timing or sequencing, it avoids the delays that came with the original approach. The reporting is faster, cleaner, and far easier to audit.
FAQ
When should you use rollup and calculated properties instead of a workflow for reporting?
When the data you need already lives on associated records, properties can often do the job more reliably than a workflow built to move that data around.
Workflows are powerful for automating actions and triggering sequences, but they can become fragile when they're doing the work of aggregating and calculating data. Every branch adds complexity, every loop adds risk, and debugging a 99-step workflow when something goes wrong is a significant time investment. Rollup properties aggregate data from associated records automatically and update in real time, and calculated properties can do math on top of that without any workflow logic involved. The result is reporting that's transparent, auditable, and doesn't require anyone to understand a branching logic tree to troubleshoot it. As a HubSpot Diamond Solutions Partner, Simple Strat evaluates both approaches for clients and recommends properties when the data is already there and the workflow is only moving it around.
How do you simplify a HubSpot workflow that's grown too complex to maintain?
Start by asking what the workflow is actually doing, and whether any of those steps could be replaced by a property that updates automatically instead.
Overgrown workflows often signal a deeper architectural question: is a workflow actually the right tool for this job? Data that's being moved or calculated is often better handled by rollup or calculated properties. A property you're building to surface a data point might actually be a report. A report you're planning to build might be better accomplished in an index view. Working through that hierarchy (goal, tools, plan, test, implement, document) before touching the workflow keeps solutions simpler, easier to audit, and easier to hand off to whoever manages it next. Simple Strat approaches workflow audits by solving for the right architecture first, not just a working one.
How do you report on revenue across multiple time windows in HubSpot without complex workflow logic?
A rollup property with a date-based condition can aggregate deal data within a specific time window, and a calculated property can do the math on top of it.
Reporting on revenue over the last 14, 90, 180, or 365 days requires filtering associated deal data by close date and then summing or counting within that range. Rollup properties support date-based conditions, so you can build a separate rollup for each time window that only counts deals closed within the relevant period. Calculated properties can then reference those rollups to derive totals, averages, or combined figures. The one piece that still benefits from a workflow is tagging deals with the appropriate time window at close, which keeps the rollup logic simple. Beyond that three-step workflow, the properties handle everything else automatically. Simple Strat builds this kind of reporting architecture for clients who need time-based revenue visibility without the maintenance overhead of a workflow doing all the work.