THE ANSWERS ARE
ALREADY IN YOUR DATA
This is the story of how I learned to find them.
The businesses I find most interesting are the ones that have outgrown their own visibility. Revenue is real. Customers are real. Something is clearly working — but nobody can see the whole picture clearly enough to know what to do next. The data is there. It's always there. It's just not saying anything useful yet.
That's not a failure.
That's actually the most interesting moment in the life of a growing business — the point where the next level of clarity is sitting just underneath the surface, waiting for someone willing to dig for it. I've spent my career figuring out how to get there. And I've never stopped finding it fascinating.
At a fast moving SaaS company generating more data than anyone had time to make sense of, every corner of the business had questions worth asking, but not the visibility to answer them. The first time a department head walked into my office with a problem that stretched beyond my skill set, I said yes anyway and learned whatever needed to get it done. Then it happened again. Then it became the job — not because I had it all figured out in advance, but because I couldn't stop being interested in the questions. Nobody called it consulting then. It was just Tuesday. These days, the questions have evolved — and so have the tools. AI and automation let me build systems that don't just answer the question once, but keep answering it every time the data changes.
Over seven years, the projects kept getting bigger. A subscription model that needed to be rebuilt from the ground up. ETL pipelines replacing hours of manual work across every department. Datasets the C-suite used to close a $20M recapitalization and a $90M growth round. Fifty million rows of customer data validated, cleaned, and made useful. A customer health score that could predict churn before it showed up in revenue.
None of it came with instructions. Each problem arrived as a question someone needed answered, and the answer required building something that hadn't existed before. Sales needed visibility into their pipeline. Marketing needed to know what was actually working. Legal needed numbers they could defend in a room. Every department spoke a different language, and every deliverable had to work for the person receiving it — not just the person who built it.
That last part turned out to matter more than I expected. The technical work was never really the hard part. The hard part was understanding what someone actually needed versus what they thought they were asking for — and then making it clear enough that they could act on it with confidence. That's a skill that has nothing to do with SQL.
That skill set came from somewhere most people don't expect. Before data analytics, I spent fourteen years in pastoral ministry. Fundamentally it's a listening profession — listening in study, listening spiritually, listening in counseling. You sit across from people at complicated moments in their lives and your job is to understand what they actually need, not just what they're saying.
You learn to ask better questions.
You learn that clarity is an act of respect. You learn that the most sophisticated thinking in the world is worthless if it can't serve the person in the room you're there to help.
I didn't know it at the time, but I was building exactly the muscle I'd need later — sitting across from a VP who needed to understand their pipeline, or a COO who needed numbers they could stake a funding round on. Different room. Different language. Same discipline.
Perelux exists because I love what I do.
Businesses with data they have no idea how to leverage. Leaders making consequential decisions on instinct because nothing in their stack was telling them anything useful. Disconnected systems, exported spreadsheets everywhere, broken reports — the data is there. The visibility isn't.
That's who Perelux is built for.
If any of this resonates, I'd genuinely enjoy a conversation. Not a sales call — just two people figuring out whether there's something worth working on together. That's usually where the most interesting problems start.
Let's Talk