Where your revenue data lives, and why the CRM is last to know

Ask most mid-sized businesses what their CRM knows and the honest answer is short: the contact, the company, and a deal value from the day it was won.

Almost everything else that decides whether revenue actually arrives is held somewhere else.

At our stand this year, we heard it put two ways. One visitor: "We push data from HubSpot to NetSuite, manually reconcile back into HubSpot, then manually notify implementation team when payment is received." Another, more bluntly: "It takes two days to assemble a single sales report."

Neither of them was describing a crisis, but worryingly, both were describing a normal Tuesday.

How revenue data usually travels

The route looks much the same in most businesses we work with. A deal is won in the CRM and from there, the numbers that matter move into the systems where the work happens. Invoices and renewal dates go to billing and orders, stock and costs go to the ERP. Hours go into a timesheet tool and somewhere there's key information held informally by one person — as one visitor to our stand put it:

"sometimes held informally by staff (e.g., on Post-it notes) rather than in systems."

During a HubSpot partner session, a software company mentioned that when quoting:

"Our price logic lives in our ERP system, so HubSpot doesn't have the logic in place."

Their quote flow ran through four separate systems; CRM for customer info, ERP for pricing, a spreadsheet to actually build the quote, then back to the CRM just to attach the file.

Those systems are usually good at their own jobs, but what they rarely do is report back. The CRM keeps the deal value from the day it closed while the real figures change elsewhere, and sales or account management find out what happened from a finance report at month end, when it's too late to act on.

This isn't an article shaming these companies, it's here to help you understand is it's also you...

Where it shows up

The effects tend to surface in the same places:

• Renewals and repeat orders get noticed late, because the dates and the usage sit outside the record the account manager works from. One analysis of stalled pipelines found healthy-looking forecasts hiding deals stuck for eight to ten months, because the CRM's own forecasting logic treated old and new deals the same way.
• Marketing can't show what it produced, because the revenue that would prove it lands in a finance system the CRM never hears from. One unified-data case study showed what's possible when the gap closes: a company unified 123 fragmented records and uncovered a multimillion-dollar cross-sell opportunity that had been invisible until then.
• Forecasts get argued about in meetings, because each team is working from a different source. "Sales team doesn't trust the current data; sales pipeline is seen as unreliable" was how one client described it. New Breed's 2026 State of HubSpot report, based on interviews with over 1,200 revenue leaders, found only 5% expressed confidence in hitting their revenue targets for the year.
• Quotes get rebuilt by hand, because the pricing, stock or cost data the salesperson needs is in another system,"A broken quoting process is chaos with a good CRM wrapped around it. The CRM isn't the problem. What breaks quoting is complexity: the configuration one person carries in their head, the price pulled from a spreadsheet that's three weeks out of date, the approval living in a Slack thread, the margin math no template can hold." One sales leader at a steel products company summed up the trap: "The more you build into Excel, the longer you stay in Excel forever."

Each system here is usually doing what it was set up to do. The trouble is what doesn't move between them.

An example

Before we worked together, Indeemo ran its business across six platforms: Close CRM, SendGrid, Freshdesk, a separate signing tool and several spreadsheets, with handoffs between teams happening in Slack. Every one of those tools worked, but none of them held the whole picture, and each participant support ticket took 10 to 15 minutes of someone's time.

Over five sprints, all of it moved into HubSpot. Their AI support agent, Erin, now resolves 77% of participant tickets, and Indeemo handles more research than a year ago with the same size team. As Indeemo's CXO Will Plummer put it:

"Erin went from zero to resolving 70% of participant support tickets the moment she went live and we really don't think about it anymore. She just handles it."

Read the Indeemo case study

Three questions that show where it stops

You can find where revenue data stops in your own business with three questions.

1. Where is the number created? Pick the figure that most affects revenue in your business, and name the system where it first appears.
2. Who needs it to make a decision? Name the person, and the decision.
3. How long does it take to reach them? If the answer is "at month end" or "when they ask," you've found the gap.

Most teams answer the first two quickly. The third is where the room goes quiet or, as one prospect admitted,  "it takes two days to assemble a single sales report."

What to do with the answer

If the number reaches the right person in time, leave it alone but if it arrives at month end, or only when somebody asks, now is your time to act. 

The fix is usually one of three things: an integration that brings the number into the CRM on a schedule, a field that gives it a proper home on the record, or an agreed definition so everyone means the same thing by it.

It rarely means buying new software. One CRO put it well: low CRM adoption "rarely stems from the CRM platform itself", the real problem is usually a mismatch between how the business actually works and how the CRM is configured, which is exactly what drives the workarounds in the first place.

If you can't find where your number is recorded at all, that's worth knowing too. It usually means it never was.