Operations · March 2026
The AI consulting industry is full of technologists selling their favorite tools. That's backwards.
There's a scene that plays out in professional services firms every week. A technology consultant comes in, looks at how things run, and recommends a suite of AI tools. The proposal is impressive. The demos are slick. The tools are genuinely capable.
Six months later, most of those tools are shelfware. The firm paid $15,000-$30,000 for implementation and is paying $500-$1,500/month in subscriptions for tools nobody uses. The office manager went back to doing things the old way because the new tools created more problems than they solved.
I've seen this pattern my entire career — first in investment banking where I evaluated over 100 companies, then as a CFO running a turnaround. The root cause is always the same: the audit started with the technology instead of the business.
When a technologist audits your business, they see the world through the lens of what their tools can do. They look at your intake process and think "this needs a form builder." They look at your scheduling and think "this needs a booking platform."
They're often right about the tools. But they're missing the bigger picture: which of these changes will actually produce enough financial return to justify the disruption of implementing them?
Not every inefficiency is worth fixing. Some processes that look wasteful actually exist for a reason — they ensure compliance, maintain quality, or serve a client relationship function that automation would destroy. A technologist doesn't always see that. A financial operator does.
When I audit a business, I don't start with the technology. I start with three questions:
This is the same analysis I did as an investment banker evaluating companies. The same framework I used as a CFO turning around a company from losing money to $21 million in revenue and profitable. It's not complicated — it's just rigorous.
Even when every recommendation is technically sound, a firm can't implement everything at once. They need to know what to do first, second, and third.
A technical audit typically prioritizes by difficulty: "this one is easy to set up, so do it first." That makes sense from an implementation standpoint, but it ignores the financial reality: the easy fix might save you $200/month while the harder fix saves $3,000/month.
A financial audit prioritizes by impact: highest dollar return first, adjusted for implementation difficulty. Sometimes the right first move is the hard one — because the payoff justifies the effort. Sometimes it's the easy one — because a quick win builds momentum. But you can't make that call without the numbers.
Enterprise companies can afford to experiment. They have IT departments. They can absorb the cost of a failed implementation.
A 5-person law firm can't. A dental practice with 8 employees can't. An insurance agency with 3 agents can't. These businesses need every dollar to count, and they need to know — before they commit — that the investment will pay off.
That's exactly what a financial lens provides. Not "this tool is cool and could theoretically help." Instead: "This specific change will save you $2,400/month based on the hours your team currently spends on this task, at your current labor rates, using a tool that costs $150/month."
That's a financial case. That's something a business owner can evaluate, approve, and act on.
If someone offers to audit your operations, here's what the output should include:
Every RunlightAI audit delivers exactly what's described above. Dollar amounts on every task. Total cost for every recommendation. Priorities ranked by financial impact. A roadmap you can execute yourself — or hand to your team, or bring to any vendor of your choosing. I don't sell tools. I don't earn referral fees. The audit stands on its own.
Fixed price. Clear deliverables. No hourly billing. No hidden fees.
Get my free audit quote →