The Dashboard Nobody Opens

Think back to the dashboard you were proudest of. The one a vendor walked you through, all clean charts and your numbers finally in one place. For a few weeks you opened it every morning. Then a rep left, a new lead source came online, you added a location, and one number stopped looking right. You stopped trusting it. Then you stopped opening it. Now it sits in a browser tab nobody clicks, and you are back to running the business on feel.

That is not a story about a bad dashboard. It is the normal life of a dashboard that nobody kept wired. And it is the single biggest reason owners ask the fair question at the heart of this: if the build is done, why would I pay anyone monthly?

I Have Been on the Other Side of That Screen

I learned this the hard way, long before there was a CDA. Two weeks into my first job as a data analyst, my boss handed me the assignment every new analyst dreams of: can you build us a marketing metrics dashboard? I went all in. I talked to every marketer, wrote down every wish, mocked it up, and got a standing ovation. Launch day was beautiful. There was a scoreboard across the top. This is going to be a game changer, they said.

Two months later, usage was zero. I assumed the tracking was broken. It was not. When I finally asked why nobody opened it, the answer gutted me: oh, I already know those numbers, I do not really need to look at it.

That was the day a lesson stuck that still shapes how we build at CDA. The dashboard was not the problem. The problem was two questions I never asked before building it: what are we actually trying to achieve, and how will we know if we did it. Skip those, and even a flawless dashboard goes straight to the data graveyard. Most of the dashboards gathering dust in home services businesses died of the exact same thing, just slower.

Why Dashboards Go Unused: They Rot

This is not a you problem. By BARC’s long running survey of business intelligence users, fewer than a quarter of the people a reporting tool is bought for ever actually use it, and at large companies it is closer to one in six. Most dashboards, in other words, are not killed by bad math on day one. They are abandoned, because the wiring underneath them quietly rotted while nobody was watching. (We dug into the broader version of that adoption problem in You Probably Don’t Need the Expensive Model.)

Here is what “rotting” actually means, in concrete terms. These are the failure modes that turn a trusted dashboard into a tab nobody opens, and not one of them trips an alarm when it happens:

• A data connection silently expires. A login or an API token behind one of your sources lapses, that feed stops updating, and the dashboard keeps showing last month’s number as if it were today’s.
• A field gets renamed upstream. Someone changes a lead source label or a stage name in your CRM, and a whole channel quietly falls out of the report, because the dashboard is still looking for the old name.
• Something new is never mapped in. You add a location, a service line, or a rep, and their jobs land in an “other” bucket or nowhere at all, so every total that should include them now reads low.
• A definition drifts. Marketing counts a sale at the signed contract, the office counts it at collected payment, an ad platform counts it on its own window, and over time those quietly diverge until no two reports agree.

Each one is small. Each one is invisible until you are staring at a number that does not match your gut. By then the trust is already gone, and trust is the only thing that makes a dashboard worth opening.

The Build Was Never the Deliverable

Here is the reframe that changes the monthly question, and it is the same lesson from that first dashboard that died. You never actually wanted a dashboard. You wanted to answer two questions, every week, as the business keeps moving: what are we trying to achieve, and are we doing it. The dashboard is just where the answer is supposed to show up. The day it stops answering truthfully, it is worthless, no matter how good it looked at launch.

So the real deliverable was never the screen. It was a trustworthy answer, kept trustworthy. A one time build gives you that answer for the few weeks before the business moves out from under it. Keeping it true as reps, channels, and locations change is not a maintenance chore bolted onto the build. It is the actual product. The monthly fee is not paying to keep a screen alive. It is paying for the only thing you were ever buying: numbers you can still bet a decision on six months from now.

What Actually Keeps It Alive

Keeping analytics wired is real, ongoing work, and it is the work most one time builds never include:

• Keeping the source of truth connected. Pipelines break. Connectors change. When they do, someone has to notice and fix it before you make a call on a stale number.
• Evolving the views as the business changes. New reps, lead sources, products, and locations need to show up correctly, not silently distort the old report.
• Answering the new question without a new project. The question you have in August was not on the dashboard built in March. A living function answers it. A finished build sends you back out to procure another one.
• Catching drift before you do. A number going wrong should be flagged by the people who maintain it, not discovered by you at the worst moment.

None of that is glamorous. All of it is the difference between a dashboard you run the business on and a tab you stopped opening.

What It Looks Like When It Stays Wired

All States Home Improvement, a home services contractor, did not just get a dashboard. CDA built them a command center the owner could run without a technical team, wired speed to lead through to booked revenue, and the build traced to about $650,000 in attributable sales in the first seven weeks, roughly 25 times what the work cost. The work was priced with a cap, and CDA billed under it. The owner, Cris Keeter, put it plainly: “I know it’s making a difference.” The reason that number was real, and not a screenshot, is that the command center reflected how the business actually ran and stayed that way.

The pattern holds over years, across industries. One analytics relationship we have maintained for four years, with a client well outside home services, has more than doubled in scope and value over that time. Not because the first build was incomplete, but because the work kept growing with the business and one team kept it current the whole way. A finished build cannot do that. A living function does it by design.

So, Why Pay Monthly When the Build Is Done?

Because the build is never done, the business is not done, and a dashboard that is not kept wired becomes the expensive screen nobody opens. The monthly relationship is not a maintenance fee on a finished object. It is the part that keeps your numbers worth trusting as everything around them changes. This is the same one time versus ongoing question that decides how you should buy analytics in the first place. If you do not need that every month, an honest partner will tell you, and there are lighter ways to buy it. But the work itself does not stop just because the build shipped.

See Whether Your Numbers Still Hold

A free Profit Leak Audit reads your own numbers as they are today and shows you where they have already drifted, what it is costing you, and the smallest thing worth fixing first. Read only, no obligation, and the findings are yours to keep.