There's an anti-AI movement building online right now.

You've probably seen it. People saying they tried AI, couldn't find a good use for it, and it doesn't really work. That it's all hype. That it did nothing for their business.

The truth is harder. They have no idea how AI actually works, or how to figure out where it fits into their business. So of course it did nothing for them. They pointed it at the wrong thing and blamed the tool.

That's what I'm going to walk you through now. A short, fast way to make sure the thing you build with AI is actually useful, and not just a fancy demo that impresses you for ten minutes and then sits there doing nothing.

(If you'd rather watch the whole thing, it's all in my free training here: https://training.headcount.so. Otherwise, keep reading.)

What most people actually do with AI

They open ChatGPT and ask it to write an email. Maybe tidy up a message, maybe summarise a document. It does it. Nothing about their business changes. So they shrug and decide AI is overhyped.

The tool's fine. They're just not pointing it at the work that matters.

AI doesn't pay off on small tasks. It pays off when you aim it at the expensive part of your business.

The part costing you the most time and money every single week. The thing someone on your team does by hand, over and over, that a machine should be doing instead.

The question nobody asks

Most people ask "what can AI do?" and get lost, because the answer is "almost anything", which is useless.

The better question is the opposite. Look at your own business and ask: what is the one workflow costing me the most right now?

Not the most annoying. The most expensive. The one eating hours every week, or the one you're paying a salary to do.

Finding that is a skill. It's the thing I do for clients before I build anything. And it has a name: auditing your business for AI.

The bit people miss: that work isn't free while you ignore it

Here's the part that should make you act.

The workflow you haven't automated isn't sitting there costing nothing. You're paying for it. Every month. In hours, or in salary, or in the deals you didn't get to because someone was buried in admin.

Say someone spends ten hours a week chasing invoices and answering the same five questions. That's not a minor irritation. That's most of a working day, every week, that you're paying full price for. Put a number on it and it stops being a chore and starts being a line item.

Every month you don't fix it, you pay it again. That's the real cost of not automating. Not the AI you didn't buy. The work you kept doing the hard way.

If you want to find your number today, the training walks you through it step by step: https://training.headcount.so

How to actually find it

You don't need a consultant for the first pass. Here's the shape of it:

Benchmark it. Pick the workflow and put a real monthly cost on it. Hours times rate, or the salary it eats. A real number, not a feeling.

Match it to the simplest solution that works. Not the most impressive one. Sometimes it's a clever prompt. Sometimes it's a no-code automation. You don't always need an agent.

Work out the payback period. Build cost divided by what it saves you each month. That's the number that turns this from a tech decision into a money decision. If it pays for itself in two months, you stop debating and start building.

Do that honestly and you'll usually find one workflow that's been quietly costing you thousands, sitting in plain sight.

The bit where most people get lazy

Here's the other reason it doesn't work. Even when people pick the right workflow, they're too lazy to actually understand it before they throw AI at it.

They look at the job from a height, go "yeah, AI can do that", and start building. Then they're confused when it half works.

A job is never one thing. It's a stack of small steps and judgement calls, and most of them are invisible until you actually look.

So before you build anything, you unpack the job into its smallest pieces. Every step, every decision, every "well, it depends". For each one you ask:

→ What information does this step need, and can AI get to it?
→ What is the actual decision being made here?
→ What happens if it gets this one wrong?

That last question is the one people skip, and it's the one that matters most. Some steps are safe to hand over completely. Some need a human checking the output. If you don't know which is which, you can't build the thing properly.

Skip this and you get a fancy demo. Do it properly and you get something that actually works.

The honest bit

AI doesn't replace everything, and anyone telling you it does is selling you something.

Part of the audit is working out where AI fits and where a human stays. Some work is too high-stakes to hand over fully, and knowing the difference is the whole point. That honesty is what separates a real audit from "automate everything!" mush.

Where to go deeper

I put the entire method into free training videos. Seven short parts, the exact audit I run with clients, including a company valued at half a billion. The same process scales all the way down to a team of two.

It walks you through finding the workflow, putting a number on it, matching the right solution, and working out the payback, on your own business, this week.

Watch it free here: https://training.headcount.so

Then go run it on your own business. Pick one workflow, put a real monthly cost on it, and see what it's been costing you. That on its own usually changes how people think about this.

Give it a go this week and reply to this if you have any questions.

Cam

P.S. If you'd rather just talk it through, book a call with me here. Fifteen minutes, no pitch: https://cal.com/headcountso/discovery

Keep Reading