Your operations might not be.
The short version
I've spent my career inside large, complex operations, the kind where the systems have to work every day, for every client, with very little margin for error.
The best solutions are almost always already in the room and they just need someone to pull them out. I work by listening first, asking the questions most people skip, and bringing examples from what I've seen break and what actually fixed it. I care about making your job easier, not just delivering a plan. And I've found that the best work happens when there's enough trust in the room to be honest and occasionally laugh at the problem so we can actually solve it.
ideaFlows is what I'm doing next. The specifics are below.
The specifics
Most consultants write vague summaries of their past roles. Here's what the work actually looked like.
Spent ten years on a five-person operations team supporting a business that grew relentlessly, month after month, for a decade — where every workflow either got rebuilt ahead of the growth or broke underneath it, and "it broke" was never an acceptable answer
Led cross-functional coordination across investment management, distribution, legal, technology, and client service — the kind of coordination work most small businesses never see until they try to build it themselves
Partnered with client-facing teams to launch new products — working directly with sales and client relationship teams so operations enabled growth instead of chasing it
Piloted the team's first automation — a bot that took over manual validation work the team had been doing by hand for years
Designed automation for task routing, reporting, and oversight — one initiative alone gave the team back more than eight hours a week, every week, permanently; another took real regulatory and operational risk off the table
The common thread: operational systems that actually work, that reduce risk, that scale, and that don't fall apart under pressure. That's the work.
The origin
After two decades inside a large institution, I noticed something every time I stepped outside of it. The operational discipline that kept my firm running (the systems, the documentation, the clear ownership, the design rigor) was almost entirely absent in the small service businesses I encountered.
Not because the owners were bad at operations. Because they never had time to build what they needed.
Running a growing service business is a different job than optimizing one. The owner is selling, delivering, hiring, managing, worrying about cash, chasing follow-ups, and trying to hold the whole thing together. Building proper operational systems while doing all of that is close to impossible. Something has to give, and what gives is always the operational work — until the operational work becomes the reason the business stops growing.
That's the gap ideaFlows is built to close.
Working style
If your process is broken, I'll say so. If a tool you're using is wrong for the job, I'll say that too. I'd rather be useful than comfortable.
The goal is systems that work, not systems that look sophisticated. A one-page process that everyone follows beats a 50-page SOP that nobody reads. Every time.
I work in short sprints with clear deliverables at each stage. You see progress in weeks, not months. If something isn't working, we adjust before it compounds.
I don't hand off a deck and disappear. Implementation is where most of the value lives, and most engagements continue into that work.