Your CRM cannot report on a business it cannot see

A company asks why their HubSpot reporting does not reflect what is really happening in the business. Someone rebuilds the dashboards. It does not help. Someone rebuilds them again with different filters. Still wrong.

The dashboards were never the problem.

The actual shape of it

The CRM is being asked to report on a business it cannot see.

The real work is happening in source systems that never feed it. A property management system. An ecommerce back end. A billing platform. A scheduling tool. A comms system. A spreadsheet that one person maintains and everyone quietly depends on.

The CRM knows about leads and it knows about deals. It does not know about the delivery, the revenue, the renewals, the support load, or the churn signals, because those live in systems that were never connected to it.

So the reports it can produce are technically accurate and describe a fraction of the business. Which is worse than being wrong, because being wrong is at least detectable.

Why this keeps happening

It is not incompetence. It is the order things get bought in.

Companies buy a CRM to fix a sales problem, so the CRM is set up around sales. The other systems came earlier, or came later for different reasons, bought by different people to solve different problems. Nobody made a decision to leave them disconnected. There was simply never a moment where connecting them was anyone's job.

Then somebody senior asks a question that spans two systems, and everyone discovers at once that the answer requires a person, a Friday afternoon, and two exports.

Why this is good news

Because it is an integration and data-model problem, not a strategy problem.

Strategy problems are genuinely hard. There is no correct answer, the feedback loop is measured in quarters, and reasonable people disagree. Integration problems have answers. You can enumerate the systems, name the records that have to move, decide which system owns each field, and build it. It is work, but it is bounded and it is checkable.

The most common outcome of a proper discovery phase is that a problem which felt strategic turns out to be structural. That is the cheaper diagnosis, and it is usually the true one.

The move

Get your first-party data into one system that can see all of it.

Note what that does and does not say. It does not say replace your source systems. Your billing platform is good at billing and your scheduling tool is good at scheduling. Replacing working software to get reporting is an expensive way to solve a reporting problem.

It says the data has to arrive somewhere it can be seen together. That is usually ETL or a sync layer, and it is frequently the single highest-leverage piece of work available in an engagement, because everything downstream depends on it. Attribution, forecasting, lifecycle definitions, churn prediction. None of them work on a partial view, and all of them work once the view is complete.

A test you can run this week

Pick a question that spans two systems. Something like: which marketing channel produces customers who are still customers a year later?

If answering it takes a person and two exports, you have found the gap. That question should be a report.