What to Look for in a Business Operations Consultant (Before You Hire One)
I've noticed something about founders who are finally ready to hire outside help.
They don't call because things are falling apart. They call because things are working — a little too well, in places they can't be everywhere at once. The product is solid. The clients are showing up. And somewhere in the back office, the systems that were supposed to hold all of it together are being run entirely from memory.
That's usually the moment someone starts Googling "business operations consultant."
And that's usually the moment they get sold something they don't need.
What people usually think they need is a person who will come in, look impressed by how much they've built, and hand them a framework. Something with a name. A methodology. A slide deck with a pyramid on it. The assumption is that operations expertise looks like credentials — certifications, a big-name former employer, a polished pitch about "unlocking scalable growth."
Here's why that assumption doesn't hold up.
A framework is not the same thing as a system. A framework tells you what good operations look like in theory. A system is the actual, specific, boring set of steps your business runs on every day — who does what, in what order, with what backup plan when the first person is out sick or the software glitches. You can hire someone who's read every operations book written and still walk away without a single document your team can actually follow on a Tuesday.
Here's the reality of what happens inside most businesses that hire the wrong consultant. They get a beautiful audit. A 40-page report identifying every inefficiency in vivid, well-organized detail. And then nothing changes, because a report isn't an SOP, a diagnosis isn't a delegation plan, and nobody was ever handed a document that says: here's exactly how this task gets done, and here's who owns it now.
The businesses that actually shift are the ones where someone rolled up their sleeves and built the thing — the checklist, the handoff, the process — not the ones where someone described what the thing should look like.
So when I say this is a buyer's guide for my own service, I mean it. This is genuinely what I'd tell a friend to ask before they hired anyone, including me.
If I were vetting a consultant, here's what I'd look for:
I'd ask them to describe a system they built, not a strategy they recommended. If the answer stays abstract — "we improved efficiency by 30%" — I'd push further. Improved how? Built what? A real operator can walk you through the actual document, the actual workflow, the actual before-and-after of a task.
I wouldn't hire someone who leads with hustle-culture language. "Scale fast," "10x your output," "unlock your potential" — that's marketing built for people who haven't run anything yet. Founders who've actually operated a business under real constraints tend to talk in specifics: ownership, handoffs, bottlenecks, documentation. Not vibes.
I'd figure out whether they understand my industry's actual constraints before I'd let them touch my systems. Events, hospitality, and service-based businesses don't run like SaaS companies. The operations advice that works for a 12-person software startup can fall apart completely on a live event floor or in a restaurant during a Friday dinner rush. I'd want someone who's stood on that floor, not someone who's only consulted from a spreadsheet.
I wouldn't buy another software tool before I understood the actual process the tool was meant to support. Tools don't fix undocumented workflows. They just make the chaos move faster.
And I wouldn't hire anyone who can't tell me, clearly, what they'd fix first — and why that, and not something else.
The bigger lesson here isn't really about hiring a consultant. It's about recognizing that operations work is infrastructure work, and infrastructure isn't glamorous. Nobody posts about the SOP they finally wrote. Nobody brags about the handoff document that means they can take a weekend off. But that unglamorous work is exactly what determines whether a business can grow past the point where the founder is the only person who knows how anything actually gets done.
The businesses that scale well aren't the ones with the most inspired strategy. They're the ones where someone finally sat down and built the boring, specific, repeatable thing.
If you're evaluating a consultant right now, here's where I'd start:
Ask for one concrete example of a system they built — not a result they claim, a document or workflow they can actually show you.
Ask how they'd approach your specific industry, and listen for whether they understand its actual operational rhythm, or just general business theory.
Ask what they'd tackle first in your business, and press them until the answer is specific enough that you could hand it to an employee tomorrow.
I didn't come into this work through a business degree or a corporate strategy track. I came into it running live events with hundreds of moving pieces and leading hospitality teams across dozens of venues, where the gap between "good idea" and "actually documented and delegated" was the difference between a smooth Saturday and a disaster. That's the eye I bring to a client's backend — not theory, pattern recognition from having actually stood in the mess and built my way out of it.
If your business is ready to grow but your backend is still running on memory, that's exactly the gap I close.
