When you need an operations consultant — and when you're just avoiding a hard conversation

An operations consultant is the right answer to a specific shape of problem. The reason we say no to roughly a third of the inbound we get is that the asking team has a different shape of problem — usually a people problem dressed up in a process costume.

This is the diagnostic we use ourselves before taking on an engagement.

When you genuinely need an operations consultant

You need outside operations help when at least two of these are true:

1. The same problem has recurred three times and the team has tried to fix it twice
2. The fix requires changes that span more than one team, and no one internally has the political room to drive across teams
3. The founder/CEO is the bottleneck for the fix, and explicitly does not have the bandwidth
4. The cost of the problem is measurable in dollars, hours, or churn — not just frustration

If you can check two of these, an external operator can unlock the situation in 4–8 weeks. If you can check all four, you should have called someone last quarter.

When you don't actually need a consultant

You don't need an ops consultant — even though you think you might — if:

1. You haven't had the hard conversation with the person responsible. If the real fix is "tell X they need to ship or leave," a consultant cannot do that for you. They can give you cover, but the cost of that cover is higher than the cost of just having the conversation.
2. The problem is one team's. Single-team problems are almost always solved by the manager of that team, plus a deadline. An outside consultant in this situation is theater.
3. You haven't written down what "fixed" looks like. If you can't describe the end state in two sentences, no consultant can deliver it. They will deliver a state — but you won't know if it's the right one.
4. You're hoping it will validate a decision you've already made. This is the most expensive reason to hire a consultant. The work happens; the validation arrives; the underlying issue does not move. Just make the decision.

The honest test

Ask yourself: "if a great operator joined my team full-time tomorrow, would they see this problem in their first week?"

If yes — the problem is real, visible, and external help can compress the timeline. Hire the consultant.

If no — the problem may be more about you than about operations. That's not a judgment; it's just a different kind of work, and ops consulting is the wrong tool.

What good engagements look like

The engagements that work — for our clients and for us — share three traits:

• A written scope under two pages, with a measurable end state
• An internal owner with authority, not just a sponsor
• A defined ending, with a transition plan to whoever runs it after

If any of those three is missing at the contract stage, the engagement will either over-run or under-deliver. We'd rather walk away than start.

Where to start

Before you take a sales call with anyone (us included), spend an hour writing down:

1. The problem, in one sentence, in the language a customer would use
2. The cost of the problem this quarter, in numbers
3. The person internally who will own the fix and have authority to make changes
4. The end state, in two sentences

If you can fill those in, the conversation about whether to bring in outside help becomes ten minutes long. If you can't, that hour was the most valuable hour of the week — regardless of who you hire next.

---

Related reading:

• Fractional COO or full-time COO? A decision framework with real cost math
• The 5-day SOP playbook: documenting your business so it can run without you
• When to scale: the boring signal that beats every gut check

If the diagnostic above lands cleanly, the next step is usually a scoped engagement. See our Business Operations Consulting page or book an intro call.