Your CRM Is a Black Box
It knows what the customer pays you. It has no idea whether they still use the product.

Tim Burnham
Founder & CEO
October 8, 2026
A RevOps lead told me his CRM shows a lot of summary numbers about the customer's bank account, and almost nothing about how they actually use the product.
I said, so it is a black box.
He said yes. That is where the real value would be. We have just been slow to get to it.
The simple idea
There are two kinds of data about a customer.
Facts. Size, industry, plan, renewal date, how much they pay. These barely change.
Behaviour. Logged in four times this week. Invited three teammates. Used 80% of the allowance with 12 days left in the month. Stopped opening the one feature that made them buy.
Your CRM is full of the first kind and empty of the second.
Facts tell you who someone is. Behaviour tells you what is about to happen.
How it shows up
A rep is prepping a renewal call.
The CRM gives them the contract value, the logo, the industry, and the renewal date.
It does not tell them that the champion stopped logging in six weeks ago.
So the rep opens with some version of just checking in. The customer knows more about their own account than the person selling to them does. Everyone can feel it, and the call goes nowhere.
The same gap shows up on the way in. A trial account that invited five coworkers looks exactly like a trial account that logged in once, because the CRM records both as a trial account.
What we found
The data almost always exists. It is just somewhere nobody can reach.
At one company, a product analytics tool was running and collecting everything. Nobody was sure who owned it. The RevOps lead did not have a license to open it.
So the team did what teams do. They built a fallback.
They estimated a key customer number from public filings, which covered less than a third of their customer base. When that failed, they used whatever the customer had written on their own website. When that failed, they asked a rep to remember.
Four layers of guessing. Still not accurate.
Meanwhile the true number was inside the product the whole time, being written to a database every day.
That is the pattern. Not missing data. Unreachable data, plus an expensive habit built around the gap.
How to close it cheaply
Do not build a data warehouse. That is a six month project and it is not the first step.
Pick one signal, one place, one schedule.
One signal. The one your best rep checks by hand. Usually it is some version of are they still using this. Start with that and nothing else.
One place. A field on the account record in the CRM. Not a dashboard. Nobody opens the dashboard. Put it where the rep is already looking, next to the phone number.
One schedule. Daily or weekly, automatically. This part matters more than it sounds. A one time pull is right on the day you run it and wrong two weeks later. People get burned once by a stale field and then they never trust that field again. A number that refreshes on its own stays true, so it stays used.
Then add one rule. When the signal crosses a line, create a task for the owner. Usage drops by half, someone gets a call this week.
That is a week of work, not a quarter.
And the second signal costs almost nothing, because the hard part was never the signal. The hard part was building the road from the product to the CRM. Once that road exists, everything else is a short drive.
If your reps are preparing for calls by guessing, the fix is smaller than it looks. It usually starts with one field.
Working on something like this? Tell us what's slow and we'll tell you what we'd build.
