The business has data everywhere. The accounting software has reports. The project tool has dashboards. There’s a spreadsheet somebody built that tracks sales by month. The CRM has charts. Someone even set up a reporting tool last year.
And the owner asks a simple question: “Which of our clients are actually worth the effort?”
Silence. Then, “We could probably pull that together.” Then a week of somebody exporting things into a spreadsheet, and the answer still feels shaky.
What the owner thinks
“We need a better dashboard.” Or a new reporting tool, or someone who’s good with data.
Having the data and being able to use the data are two different things. Another dashboard on top of disconnected data is still disconnected data, just prettier.
What I’d investigate
I’d start with the question, not the reports. “Which clients are worth the effort?” sounds simple, but to answer it you need, for each client:
- What we billed them
- What it cost us to serve them: time, and any direct costs
- How much of our time was never billed
- How often they pay late or dispute invoices
- How much non-billable hassle they create: revisions, extra calls, scope creep
Then I’d check which of those the business actually captures, and whether it’s connected to the client. Usually billing is there. Time is partly there. Unbilled time and hassle are almost never there. Cost to serve is the big gap.
What’s underneath it
The reports were built around what was easy to pull, not around the decisions the owner needs to make. So there’s a lot of information about activity and very little about the questions that matter. And the key links, like time tied to clients, or costs tied to projects, were never captured consistently.
If I need five documents and three messages to answer a normal question, I’m looking at the process too.
What I’d change
- Pick three decision questions. Not thirty. The three the owner most wants answered. “Which clients are worth it?” “Which type of work makes us the most?” “Where is our time going?”
- Map each question to the data it needs. And mark what’s missing or disconnected.
- Fix capture for the missing pieces. If time isn’t tied to clients and services consistently, that’s the first fix.
- Build one simple report per question. Something the owner can look at monthly, in a few minutes, that actually answers it.
For a contractor, the same idea applies to jobs instead of clients: which type of job, which size, which kind of customer actually earns what the estimate said it would? The questions change a little by business. The fix doesn’t. Decide what you need to know, then make sure the information that answers it gets captured on the way through.
What I’d leave alone
Reports people use. If the bookkeeper relies on a certain report, or the team checks a dashboard daily, leave it. I’m not trying to replace everything. I’m trying to add the answers that are missing.
Be wary of reports that answer “how busy were we?” when the question is “was it worth it?” Hours logged, jobs completed and invoices sent all measure activity. Useful, but they can’t tell you which work deserves more of your time.
The tradeoff
Capturing the missing data usually means small new habits, like tagging time to a service, or logging extra client requests. That’s a bit more effort every day. And the answer won’t appear overnight. You need a few months of clean data before patterns show up. But a shaky answer you rebuild every quarter is worse than a real one you wait for.
The pattern
Most small businesses don’t have a data shortage. They have a question shortage. Nobody decided which questions the data should answer, so it answers whatever was easiest.
Start reporting from the question, not the data.
So try this: write down the three questions you most wish you could answer about your business. For each, ask who could answer it today, and how long it would take. The ones that take a week are where your reporting is breaking.
If you want help turning those questions into answers you can trust, bring them to a Systems Fit Call.
