AI AutomationNo. 08
What is an AI agent? A plain-English guide for business owners
Everyone is selling agents. Here's what the word actually means, where agents earn their keep in a small business, and where they still fall over.
The short answer
- An AI agent is software that uses a language model to decide which steps to take toward a goal, and then takes them using tools like email, a CRM or a calendar.
- A chatbot answers. An automation follows fixed rules. An agent chooses its next action, which makes it flexible but also less predictable.
- Agents are strong at triage, research, drafting and turning messy inputs into structured data. They're weak at long unsupervised tasks and anything needing accountability.
- Start with one narrow, frequent, low-risk task, run it in shadow mode, and keep a person approving anything customer-facing.
The word “agent” is on every product page this year, and it’s doing a lot of work. Some tools that call themselves agents are a chatbot with a new label. Others genuinely act on their own. If you run a business, the difference matters, because it decides what the software can do for you and what it can break.
What an AI agent actually is
An AI agent is a piece of software that uses a language model to decide what to do next in pursuit of a goal, then does it using tools it has been given access to.
Give an agent the goal “follow up with everyone who asked for a quote last week and hasn’t replied”, along with access to your inbox and CRM. It can work out who those people are, read each thread, draft a follow-up that fits the conversation and, if you allow it, send the messages and log them.
Nobody wrote a rule for each of those steps. The agent chose them.
Agents vs chatbots vs automations
It helps to put the three side by side.
| Traditional automation | AI assistant or chatbot | AI agent | |
|---|---|---|---|
| Who decides the steps | You, in advance | Nobody; it answers | The model, at run time |
| Handles messy or unexpected input | Poorly | Yes, in conversation | Yes, and acts on it |
| Takes actions in other tools | Yes, fixed ones | Rarely | Yes, chosen per task |
| Predictability | Very high | Medium | Lower |
| Best for | Repeated, identical tasks | Answering questions | Varied tasks with clear goals |
Traditional automation is still the right answer for a lot of work. If the steps never change, a fixed workflow is cheaper, faster and more reliable. Agents earn their place when the input varies: free-text emails, documents in different formats, customers who describe the same problem ten different ways.
What agents are good at today
In small and mid-sized businesses, these are the jobs where agents reliably save time:
- Triage. Reading incoming emails, forms or tickets and routing, tagging or prioritising them.
- Messy-to-structured. Pulling names, dates, amounts and requests out of emails, PDFs and call transcripts into your systems.
- Research. Gathering and summarising information on a lead, a competitor or a topic before a person makes a decision.
- First drafts. Replies, proposals, reports and briefs, written from your notes and your data.
- Follow-up. Chasing documents, reminding customers and nudging leads, politely and on schedule.
Where agents still fall over
Being honest about the weak spots is how you deploy agents without regret.
- Long, unsupervised chains of steps. Small errors compound. An agent that’s right 95% of the time per step is wrong far more often across twenty steps.
- Confident mistakes. Language models can produce plausible but wrong answers. Anything factual needs a source or a check.
- Arithmetic and exact data. Calculations belong in ordinary code or spreadsheets. Let the agent explain numbers, not produce them.
- Accountability. An agent can’t own a decision. Pricing, refunds, legal or medical questions and anything irreversible need a person.
- Vague goals. “Grow our social media” is not a task. “Draft three posts a week from our blog, for approval” is.
The anatomy of a well-built agent
When I build an agent for a client, it always has the same six parts:
- A narrow goal. One job, clearly described, with a definition of done.
- Written instructions. The same standard operating procedure you’d give a new hire, including what not to do.
- The minimum tools. Access only to the systems and actions the job needs. Read-only wherever possible.
- Context. The customer’s history, your price list, your tone of voice. Agents are only as good as what they can see.
- Guardrails. Limits on what it may send, spend or change, plus rules for when to stop and ask.
- Human checkpoints. A person approves anything customer-facing or irreversible, at least until the track record justifies more freedom. I cover this in detail in how to deploy agents without losing control.
How to try one safely
Pick a task that is narrow, frequent and low-risk, such as sorting inbound enquiries or drafting replies to common questions. Write down how a person does it today. Then run the agent in “shadow mode” for a week or two: it drafts, a person reviews and sends. Track how often the drafts go out unchanged.
When that approval rate is consistently high, let the agent act on routine cases and send only the exceptions to a person. That’s the pattern behind almost every agent I’ve seen succeed. If you want a structured way to choose the first task, start with an AI time audit.
The bottom line
An AI agent is software that decides and acts, not just software that answers. That makes agents powerful for the varied, messy work that fixed automations can’t handle, and it’s also why they need clear goals, limited access and a person in the loop. Start small, measure honestly and expand what works.