People ask me this, and they deserve a straight answer.
The problem is that "is it worth it" depends entirely on what's wrong, what it's costing you, and what changes after we fix it. I can't give you a universal ROI number because consulting isn't a product with a fixed return. It's a service applied to a specific situation, and the value depends on the situation.
What I can do is give you a framework for thinking about it. And I can be honest about the cases where it's clearly worth it, the cases where it's probably not, and the gray area in between.
The math side
Start with what the problem is costing you. Not a vague sense that it's expensive, but an actual estimate.
Let's say you're spending 8 hours a week dealing with the consequences of a broken process. Maybe it's rework, maybe it's managing confusion, maybe it's answering questions your team should be able to answer themselves. At whatever your time is worth, say $75 an hour for simplicity, that's $600 a week. Over a year, that's $31,200.
If a consulting engagement costs $5,000 and solves that problem, you're looking at a 6x return in year one alone. The problem was already costing you the money. Fixing it just stops the bleeding.
Now, most situations aren't that clean. You can't always put a precise dollar figure on the cost. But you can usually get in the right neighborhood. How much time is being wasted? How much revenue is being left on the table? What's employee turnover costing you? These aren't abstract questions. They have numbers attached, even if those numbers are estimates.
The exercise of estimating is valuable even if the estimate is rough. It turns "this feels expensive" into "this is costing us roughly X," and that gives you something to compare against the cost of fixing it.
The stuff that's harder to measure
Not everything shows up in a spreadsheet.
How much is it worth to sleep better because you're not worrying about whether things are falling apart when you're not there? What's the value of your best employee staying another two years because the working environment improved? How do you put a number on being able to take a vacation without checking your phone every hour?
You can't, really. But these things are real, and they matter. I've worked with business owners who told me afterward that the biggest change wasn't operational. It was that they enjoyed their business again. They'd been so deep in the weeds for so long that they'd forgotten why they started the thing in the first place.
That's hard to put in an ROI calculation. But if you ask those people whether it was worth it, they don't hesitate.
When the ROI is clear
Certain situations have an obvious return.
You're losing employees and you know it's because of operational dysfunction. Turnover is expensive. Recruiting, training, lost productivity during transitions. If fixing operational problems reduces turnover even modestly, the engagement pays for itself.
You have a growth opportunity that your current operations can't support. You could take on more clients or bigger projects, but your back end can't handle it. The revenue you're leaving on the table dwarfs the cost of getting your operations ready.
You, the owner, are the bottleneck. Every decision runs through you, your days are consumed by operational minutiae, and you can't do the strategic work that would actually grow the business. Freeing up 10 hours a week of your time to focus on high-value work is one of the clearest ROI cases there is.
When it's probably not worth it
Your business is very early stage and you're still finding product-market fit. Optimizing operations on a business that might pivot next month doesn't make sense. Get the fundamentals right first.
The problem is small and contained. If it's a minor annoyance that costs you an hour a week, you can probably fix it yourself with a Saturday morning of focused thought. Don't spend thousands of dollars on something a notebook and a couple hours can handle.
You're looking for a magic fix. If you're hoping a consultant will come in and make everything effortless without any work on your part, you'll be disappointed regardless of the ROI. Consulting requires your participation. The return depends partly on what you put in.
How I think about value
I'll tell you my internal test. Before I take on a project, I ask myself: will this client get back at least three times what they're paying me? If I can't honestly answer yes, I don't take the project.
That might mean I recommend a smaller engagement. Or it might mean I tell you that consulting isn't the right move and suggest something else. I'd rather turn down work than take money I don't think will produce real value.
This isn't altruism. It's practical. A client who gets a poor return doesn't come back, doesn't refer anyone, and rightfully tells people it wasn't worth it. A client who gets a clear return becomes a long-term relationship. The incentives line up.
A way to test it
If you're on the fence, the Flow Check is designed to be a low-risk way to find out. It's a two-week diagnostic engagement at a fraction of the cost of a full project. At the end, you have a clear picture of what's going on in your business and a prioritized plan for fixing it.
If the findings are significant, the ROI case for further work becomes obvious. If the findings are minor, you've spent a modest amount to confirm that your business is running better than you thought. Either way, you're making decisions with information instead of guessing.
That feels like a reasonable bet to me. Here's more about how it works.