What "AI-Powered" Actually Means (And How to Tell When It's Just a Label)

"AI-powered" is on your email platform, your CRM, your website builder and the proposal from the agency pitching you. It's on the software you bought last year and on the software trying to replace it.

The label tells you almost nothing. It says AI is in there somewhere. It doesn't say what the AI does, what it's connected to, what it's allowed to decide or who checks its work. Those four things are the difference between a feature you'll forget about and a system that changes how your business runs.

I build and run AI agents in healthcare. At Solve Sleep Apnea, the nationwide sleep apnea network I co-founded, AI agents, including voice agents, handle patient calls, texts and email, set and reschedule appointments, and qualify and route patients 24/7, with HIPAA compliance built in and people in charge of anything that needs judgment. I've also built multiple medical businesses and spent more than 11 years building businesses, websites and systems from scratch. That work has taught me to judge AI by what happens to the work, not by the label.

Here's the framework I use, and the questions I'd ask anyone selling you something AI-powered.

"AI-powered" describes an ingredient, not a result

When a restaurant says "made with fresh ingredients," you still want to know what's on the plate. AI is the same. It's an ingredient. The useful question is what your business can do with it that it couldn't do before.

Compare two descriptions:

• "Our platform uses AI to enhance customer engagement."
• "When a patient calls at night, an agent answers, asks the qualifying questions, books or reschedules the appointment and routes the patient to the next step. Anything it shouldn't decide goes to a person."

The second one you can check. It names the job, the action and the boundary. The first one could describe almost any product sold in the last few years.

So before anything else, translate every AI claim into a plain sentence with a verb and an object. The AI answers the after-hours calls. The AI sorts incoming messages by what the person needs. The AI drafts a reply that a person approves. If no one can give you that sentence, there's nothing yet to evaluate.

If someone can't tell you what the AI does in one plain sentence, they're selling the label, not the work.

The four levels of AI in a business

Most confusion about AI comes from lumping very different things together. I sort them into four levels by one question: how much is the AI allowed to do on its own?

Level 1: AI as an assistant

A person asks, the AI drafts, the person decides. A first draft of an email, a summary of a long document, a list of ideas, cleaned-up notes. This is where most people start, and it's genuinely useful. The risk is low because a person reviews everything before it goes anywhere. The limit is that nothing happens unless someone sits down and asks.

Level 2: AI built into your software

The features your existing tools have added: suggested replies, call summaries, lead scores, generated reports. Often worth turning on. But they're built for every customer of that software, so they know nothing about your rules unless you configure them, and they stop at the edge of that one tool.

Level 3: Automation with AI in one step

A workflow where rules do most of the work and AI handles the one step that needs language. A message comes in, the AI reads it and labels what the person needs, and the rules send it to the right place. A call ends, the AI summarizes it, and the summary lands in the CRM. The AI has a narrow job, and everything around it is predictable.

Level 4: AI agents that act

Software that holds a real conversation by phone, text or email and takes action: answers the question, qualifies the lead, books or reschedules the appointment, routes the person, updates the record. This level has the most leverage, and it's where the rules, the connections and the oversight matter most, because the agent is talking to your customers in real time.

Solve Sleep Apnea runs at level 4, and that's the right level for that business: patients can reach out by phone, text or email at any hour, and every one of them needs an answer and a next step. Most businesses don't need to start there.

The point of the levels isn't that higher is better. It's that you should know which one you're paying for, and that every level up needs more groundwork underneath it.

Most of what you need isn't AI at all

Here's something that rarely makes the pitch: a lot of the most valuable automation in a small business has no AI in it. It's rules. Something happens, something else follows, every time.

• A call is missed, so a text goes out.
• A form comes in, so the lead lands in the CRM and gets a reply.
• An appointment is booked, so a confirmation and reminders go out.
• A payment clears, so the order is confirmed.

Buon Cibo, the Italian deli and catering business in Scripps Ranch that I built from the ground up through my restaurant consulting company, Clear the Plate, is a good example. The website was built for ordering: prepaid preorders for dinners, weekly specials and heat-and-eat meals, plus tickets for wine nights and events. It brings in about $20,000 a month in prepaid orders, separate from the counter. What makes that work is an ordering flow built around how the deli actually sells. Nobody needs AI to take a prepaid order.

Here's a simple way to decide where AI belongs in any process:

• Predictable input: use rules. Form fields, payments, calendar events, status changes. Rules do the same thing every time and never improvise.
• Messy input: consider AI. Phone calls, free-text questions, conversations that wander, documents that need reading. That's where language models earn their place.
• Judgment: keep a person. Exceptions, complaints, high-stakes decisions, anything where being wrong costs more than being slow.

When someone proposes an "AI solution" for a step with predictable input, ask why. Sometimes there's a good reason. Often the label came first and the problem came second.

What a real AI system has underneath it

The agent is the part people see. Most of the work is underneath it. At Solve Sleep Apnea, the agents sit on top of a CRM, an automation system, HIPAA compliance, human oversight and escalation, and a team that runs the consultations and routes each patient to the right partner provider. Without those, the agents could only talk.

When I look at any AI system, mine or someone else's, I check for seven things:

1. Approved knowledge. What the AI knows about your business, written down and approved by you: services, process, locations, policies and the questions your team answers every day. Not whatever it can find.
2. Connections. The CRM, the calendar, the phone line, the inbox. An agent that can't see the calendar can't book. One that can't write to the CRM leaves your team guessing.
3. Rules. Who qualifies, where each person goes, and what the AI is never allowed to say or decide.
4. Escalation. When a person takes over, who it goes to, how fast, and what context comes with it.
5. Records. Every conversation logged where your team can see it.
6. Review. Someone reading real conversations on a schedule and tightening the rules.
7. Protection. If you handle sensitive information, the system is designed around it from the start. In healthcare, compliance decides which tools you can use and what an agent is allowed to do.

If a pitch only talks about the model, ask about these seven. That's where AI systems succeed or fail.

The agent is the part people see. Most of the work is underneath it.

Where "AI-powered" goes wrong

The mistakes I see most aren't about choosing the wrong model. They're about skipping the groundwork.

• Automating a process nobody has written down. AI makes a messy process faster, not better. Map it first.
• Letting it improvise where you need a policy. Prices, guarantees, refunds, medical or legal questions. Write the approved answer, or route it to a person.
• Generic output. Pages, emails and posts that could belong to any business in your category. AI makes generic easy. The value is in the specific: your market, your customers, your voice.
• Nobody reading the conversations. Without review, small problems repeat quietly until a customer points them out.
• Compliance as an afterthought. If you handle health, financial or other sensitive information, build the protection in from the start instead of patching it on later.
• Locking yourself in. Models keep improving. If your knowledge, rules and data are tangled up inside one vendor's tool, you can't move when something better arrives. Keep the parts that are yours, yours: the approved knowledge, the rules and the data in your CRM.
• Using AI to cover a weak foundation. An agent can't fix an unclear offer or a website that doesn't convert. It just sends more people to it faster. That's why the blueprint comes before the website, and before the automation too.

Questions to ask before you pay for anything AI-powered

Bring these to any vendor, agency or freelancer who uses the label. They work whether you're buying software, a service or a custom build.

1. What exactly does the AI do, step by step, in plain sentences?
2. Which level is it: assisting a person, a feature inside a tool, one step in a workflow, or an agent that acts on its own?
3. What is it connected to: the CRM, the calendar, the phone, email?
4. What is it allowed to decide on its own, and what does it never decide?
5. When does a person take over, and what does that person see when they do?
6. Where are the conversations stored, and who reviews them?
7. What happens when it gets something wrong, and how would we find out?
8. How is sensitive information protected?
9. If a better model comes out, can it be swapped in without rebuilding everything?
10. What does this remove from my team's day, and how will we measure it?

Good answers about AI are specific and a little boring. Vague answers are the label talking.

How to use AI well, starting this week

You don't need to start with an agent. Here's the sequence I'd recommend to most small businesses:

1. Use AI as an assistant for your own work. Drafts, summaries and research, with you reviewing everything. You'll learn quickly what it's good at and where it's confidently wrong. If you're planning a launch, use it to research your market before you spend on anything else.
2. Map how customers reach you and what happens next. Every call, text, form and email. Mark each step as predictable (rules), messy (a candidate for AI) or judgment (a person).
3. Fix the predictable steps with plain automation. Missed-call texts, form replies, confirmations and reminders, with everything landing in one CRM.
4. Pick one messy, high-volume job for AI. After-hours calls, the same ten questions every day, rescheduling. One job, clear rules, a clear handoff to a person.
5. Measure it, read the conversations, then expand. Add the next job only when the first one is working and you can show it.

That's also the order I build in. Because I do the strategy, the website, the marketing and the automations myself, nothing gets lost between vendors, and the AI is designed around how your business actually runs, not bolted on afterward. For a closer look at what a level 4 system does day to day, read How AI Agents Can Handle Your Follow-Up (Without Sounding Like Robots).

The bottom line

"AI-powered" should mean that specific work gets done, every time, with clear rules and a person in charge of judgment. If you can't point to the work, it's a label.

If you want help sorting out what's worth automating in your business and what should stay with people, that's where my Business Automations work begins, with Scalable Systems underneath when the CRM and integrations need to be built first. It starts with a free conversation, then a Strategic Blueprint that maps the work before anything is built. Start the conversation here.