HubSpot reporting and attribution.
Numbers the board can open. Reporting problems are almost never reporting problems. They are two teams counting the same thing differently, and no dashboard fixes a disagreement about what qualified means.
Three reports. Three answers.
Marketing reports pipeline one way, sales another, and the board deck has a spreadsheet in between with a manual adjustment nobody can fully explain. All three are internally consistent, which is exactly why the argument never resolves.
All three are right. That is the problem.
Reporting — the disagreementDefinitions first, dashboards second.
Definitions written and signed
Qualified, opportunity, pipeline, won, churned. Each written as a testable rule and agreed by the people who argue about them. Everything else is downstream of this.
Reports that reconcile
Built from the agreed definitions so two reports on the same subject cannot disagree, because they inherit the same logic rather than each implementing it.
History the CRM does not keep
Point-in-time pipeline, stage movement and owner changes captured as snapshots, because otherwise you cannot answer what the forecast said in March.
Attribution with its limits stated
First touch, last touch and multi-touch answering different questions, with the assumptions printed. A model you cannot explain will be disbelieved the moment it is inconvenient.
Dashboards per audience
The rep view, the manager view and the board view are different questions. One dashboard for everyone gets opened by nobody.
Knowing when to leave HubSpot reporting
It covers more than most teams use. When the question spans product, billing and the CRM, we will say so rather than contort the report builder into something it is not.
Audit, architect, build, hand over.
Audit
The portal read end to end — objects, properties, automation, permissions, integrations and the reports leadership actually opens.
Architect
The model written down before it is built: objects, lifecycle, ownership and the definitions every report has to agree on.
Build
Configuration, automation and integration built to that model, in a sequence that leaves the team working throughout.
Hand over
Documentation, enablement for the people who run it daily, and a period operating alongside your team until it is genuinely theirs.
Buying a BI tool to settle an argument.
A new dashboard tool produces the same disagreement in a nicer interface, because the disagreement is about definitions. Fix the definitions and almost any tool works. Skip that and you have bought a more expensive way to be wrong.
What people ask before they commit.
Why do our reports disagree?
Nearly always different filters encoding different definitions, or a property written by more than one workflow. We trace it to the record level and show you exactly where the two diverge.
Can HubSpot do the reporting we need?
More often than people assume. The custom report builder is capable and underused. The limit is joining to data that lives in other systems, and that is when a warehouse earns its place.
Can we get historical pipeline?
Going forward, yes, with snapshots. Retrospectively it depends on what was retained, and the honest answer is often that some history cannot be reconstructed.
Which attribution model should we use?
Several, for different questions. First touch for awareness, last touch for conversion, multi-touch for the whole. What matters is stating which one a given number uses.
How long does it take?
Three to eight weeks. Agreeing definitions is the slow part and the part that actually delivers the value.
Where people go from here.
Agree the definition first.
Tell us what you are running
What the system does today, where it breaks, and when it has to work. An engineer reads it — you get an answer inside one business day, not a sequence.