The data is there. The systems are running. But when you actually need to know something — really know it — you end up in a spreadsheet at 10pm making your best guess.
I co-ran a manufacturing business as a second-generation owner. I know what that feels like. And I know what changed when someone finally showed me what my own data was actually saying — not just cleaner reports, but a completely different understanding of what the real problem was.
That's what I do for operators now.
Different words, same situation. I've heard some version of each of these in almost every first conversation.
You see everything before I move forward. Fixed fees — if it takes longer than I estimated, that's on me, not you. I work with a small number of clients at a time so the work actually gets my attention.
Whatever system is trapping it — legacy ERP, practice management software, a patchwork of spreadsheets — we get the data out, clean it, and make sure the foundation is actually solid before we build anything on top of it.
Dashboards, tools, pipelines — whatever the business actually needs to see what's happening in real time. I start with prototypes so you can react before I build the full thing. You tell me what's right, we lock it in.
The manual work goes away. The data flows without anyone copying numbers between screens. You get a written SOP so you can keep the system running without calling me every time something changes.
Too much going on for a freelancer to handle. Not the right size for a Big 4 engagement. The kind of business where one person who can go from the technical layer all the way to the strategic conversation is exactly what's needed.
Every engagement is different in its technical specifics. The through-line is always the same: operational data that exists but can't be read clearly — and someone who needs to understand it before they can act.
The reason I do this work isn't that I'm good at data. It's that I know what it changed for me — and I've spent the last several years trying to create that same moment for other operators.
Most operators I work with are running on instinct — not because they're not smart, but because nobody has ever sat down with their data and shown them what it's actually saying. The answers are almost always already there. The work is learning to read them. My PhD research focused on how practitioners create and understand ineffable experiences — the kind of knowing that lives below language. How people sense something is true before they can prove it. That research is directly applicable to every engagement where a client says "something is off" but can't say what. They're usually right. The data almost always confirms it. I think in systems and I see in patterns. When I get into a business's data I'm not just looking at numbers — I'm reading the relationships between them. Where a pattern breaks unexpectedly. Where the data points at something nobody has named yet. The 5 Whys isn't a technique I apply — it's closer to how I naturally move through a problem. Operator background, technical depth, pattern recognition, a research foundation in how people understand complex systems. I'm not bringing a framework. I'm bringing a way of seeing.
The first conversation is just that — a conversation. I want to understand your situation before either of us decides if it's a fit. No pitch, no pressure. If it's not the right match, I'll tell you that too.