Opens in a new tab
needsahuman.

AI agents for business: from chatbot to agent

AI agents for business are the next step after chat assistants: AI that does things, not just writes them. This lesson explains what an agent is, how much freedom to give one, and where a person must stay in charge. In this lesson The difference between an assistant that answers and an agent that acts.…

AI agents for business are the next step after chat assistants: AI that does things, not just writes them. This lesson explains what an agent is, how much freedom to give one, and where a person must stay in charge.

In this lesson

  • The difference between an assistant that answers and an agent that acts.
  • The parts of an agent: a goal, a model, tools, memory and a loop.
  • Five levels of autonomy, from “answers questions” to “acts alone inside set limits”, with a small-business example of each.
  • How agents connect to your software, including the Model Context Protocol, in one paragraph.
  • What agents are good at today, where they stumble, and how to start safely.

What is an AI agent? Chat answers, agents act

Everything in Lessons 1 to 6 was mostly about AI that answers: you ask, it drafts, you decide what to do with the draft. An agent goes a step further. It is given a goal, access to tools, and permission to take several steps on its own to reach that goal, checking its progress as it goes.

Ask a chat assistant “find me a time next week for a call with Sam,” and it might suggest how to word an email. Ask an agent the same thing, with access to your calendar and email, and it can look at your diary, write to Sam, read the reply, and put the call in both calendars.

That is the whole difference, and it matters for one reason: chat mistakes stay on the screen until a person acts on them; agent mistakes have effects. A wrong draft is a nuisance. A wrong email sent, payment made or record deleted is a real problem. Everything in this lesson follows from that.

The anatomy of an agent

Every agent, however it is sold, has the same parts.

You give the agent a goal and instructions. The model works in a loop: plan the next step, act with a tool, check the result, and repeat. It ends either done, reporting back to you, or by asking a person when it is stuck or unsure. Its tools are email, calendar, web browser, spreadsheet and accounting software; reading and looking up go straight through, but an approval gate means a person approves any action that sends, pays or deletes. Memory sits underneath: notes it keeps between steps and files you let it read.

Goal and instructionswhat to do, and the limitswritten by you
The agent loop The model at the centre, with a loop around it: plan the next step, act with a tool, check the result, then plan again. Model Plan next step Act with a tool Check the result
Donereports back to you
Asks a personstuck, unsure or out of limits
Approval gateA person approves anything that sends, pays or deletes.
ToolsEmailCalendarWeb browserSpreadsheetAccounting softwareReading and looking up go straight through.
Memorynotes it keeps between steps, earlier conversations, files you let it read
Chat answers; agents act. Because an agent's mistakes have effects, the amber gate sits in front of every action that sends, pays or deletes. Start with approval on everything, then loosen.
  • A goal and instructions. What you want done, and the rules: what it may and may not do, when to stop, when to ask.
  • A model. The same kind of model as in a chat assistant (Lesson 1), doing the thinking: working out the next step.
  • Tools. The software it can use: email, calendar, a web browser, a spreadsheet, your accounting or booking system. Using them is called tool use. An agent can only do what its tools let it do.
  • A loop. Plan a step, act with a tool, check the result, then plan the next step, until the goal is met or it gets stuck.
  • Memory. Notes on what it has done so far in this task, and sometimes what it has learned from earlier tasks.
  • A person. At the points that matter, it stops and asks. In the diagram, the amber gate before anything that sends, pays or deletes is where your approval goes.

Agents use more computing than chat, because each step is another round with the model. Anthropic, which makes Claude, reported that “agents typically use about 4× more tokens than chat interactions” in its data (Anthropic). That shows up in price, especially on usage-based plans (Lesson 11).

How agents connect to your software

To act, an agent needs a way into your systems. Some products build those connections themselves: an assistant inside your email or accounts can already see them. Others use a shared standard. The best known is the Model Context Protocol (MCP), which its own site describes as “an open-source standard for connecting AI applications to external systems,” adding: “Think of MCP like a USB-C port for AI applications” (modelcontextprotocol.io). Anthropic introduced it in November 2024 (Anthropic) and in December 2025 gave it to the Agentic AI Foundation, “a directed fund under the Linux Foundation, co-founded by Anthropic, Block and OpenAI” (Anthropic). For a business owner, the point is simple: if your software offers an MCP connector, many different AI tools can use it, and you decide which ones and with what permissions.

Five levels of autonomy

How much freedom to give an agent is your choice, and it should depend on the task, not on what the product can do. A useful way to think about it is a ladder.

  1. 0Answers questions"What is our refund policy?" answered from the staff handbook.Youask, then decide what to use.
  2. 1Drafts for you to sendWrites replies to online reviews.Youedit and press send.
  3. 2Acts after you approveBooks a supplier delivery once you click approve.Youapprove each action.
  4. 3Acts and tells youFiles receipts into the accounts and sends a daily summary.Youreview what it did and undo mistakes.
  5. 4Acts alone inside set limitsReorders stock under a set amount from approved suppliers.Youset the limits and check its record regularly.
Climb one rung at a time. At every rung a person has a job: asking, sending, approving, reviewing or setting limits. Most small-business agents should start at rung 2.
  • Level 0: answers questions. It can look things up in your information and answer, but takes no action. Example: a staff assistant that answers “what’s our refund policy?” from the handbook. The person does everything.
  • Level 1: drafts for you to send. It prepares the email, quote or invoice; you review and send it yourself. Example: an agent that reads a customer enquiry and drafts a quote from your price list. The person checks and acts.
  • Level 2: acts after you approve. It proposes an action and does it once you click yes. Example: a scheduling agent that proposes tomorrow’s rota and sends it to staff when the manager approves. The person approves each action.
  • Level 3: acts and tells you. It acts on its own and reports what it did, so you can step in. Example: an agent that sends appointment reminders and tells you who has not confirmed. The person reviews afterwards and spot-checks.
  • Level 4: acts alone inside set limits. It acts without reporting each step, within firm limits: a spending cap, a list of allowed actions, certain customers only. Example: an agent that reorders stock automatically below a set level, up to a set amount per week. The person sets the limits and audits regularly.

Most small businesses should start every agent at Level 1 or 2 and move up only when the logs show it gets the task right, reliably, over weeks. Anything that sends money, signs, deletes or speaks for the business publicly should stay at Level 2 unless there is a very good reason.

What agents are good at today, and where they stumble

Good fits are multi-step tasks that follow a pattern and happen in software:

  • admin across several systems, such as copying details from emails into your customer records and booking system;
  • research, such as gathering information on a list of suppliers or prospects and summarizing it;
  • data entry and tidying, such as matching invoices to orders and flagging the ones that do not match;
  • routine follow-ups, such as chasing missing documents or confirming appointments.

Where they stumble:

  • Long tasks. The more steps, the more chances to go wrong, and an early mistake can carry through.
  • Unclear instructions. People fill gaps with common sense; agents fill them with guesses.
  • Unexpected screens. A changed website, a pop-up or a login can throw an agent that works in a browser.
  • Being tricked by what they read. An email or web page can contain hidden instructions that the agent follows. This is called prompt injection, and Lesson 10 explains how to guard against it: limit what the agent can do, and approve actions.
  • Knowing when to stop. Agents can keep going when a person would have stopped and asked.

AI agents for business: where you’ll meet them

You may never build an agent. More likely, you will meet them inside products you already use or are offered: assistants that can now take actions, and agent features in office, accounting, help desk and booking software. The main AI makers’ agent features, as each describes them on its own pages, with the date we read them:

AI makers’ agent features, as each describes them on its own pages, with the date we read them. Alphabetical; not a ranking.
MakerAssistantAgent features, as the maker describes themDate read
Alibaba (Qwen)Qwen ChatNot stated on the pages we read.October 6, 2026
AnthropicClaude
  • Research (multi-agent research system): A lead agent plans the research, then starts several sub-agents that search in parallel and report back; a separate agent adds citations. Anthropic says this uses far more tokens than chat: about 4 times for a single agent and about 15 times for a multi-agent system.
  • Research: token use versus chat: Anthropic's figure for the cost of agents and multi-agent systems compared with chat (engineering post published Jun 13, 2025).
  • Research (in the Claude apps): Claude runs several searches that build on each other across the web and connected work apps, and returns an answer with citations. The pricing page lists Research on Pro, Max and paid business plans, not on Free.
  • Claude Cowork (now merging into Claude): Hand Claude a goal and it works across your files and tools, splits big projects into parts that run at the same time, can run on a schedule while your laptop is closed, and asks before taking an action by default. Anthropic says Cowork and chat are merging into one Claude, rolling out to Pro and Max first; the Team plan lists 'Claude Code and Claude Cowork'.
  • Claude in Chrome: A browser extension that reads the page you are signed in to and clicks, types and fills forms, while you approve what happens.
  • Claude Code subagents: In Claude Code, the coding agent, Claude can hand a side task to a specialised subagent that works in its own context with its own tools and permissions and returns a summary; the docs also describe agent teams, a coordinated team of sessions that Claude starts and supervises.
October 6, 2026
DeepSeekDeepSeek (chat at chat.deepseek.com)DeepSeek Harness: An agent harness for developers, in developer preview; the API docs also list guides for running DeepSeek models inside other makers' coding agents.October 6, 2026
GoogleGemini (Gemini app; Gemini Enterprise app for business)October 6, 2026
MetaMeta AI
  • Meta Business Agent: An AI agent that answers a business's customers in chat in their language and tone, lets the business decide when a person steps in, and can give the owner a morning briefing on overnight chats.
  • Meta Business Agent Platform: A platform for larger businesses to build, customise and deploy their Business Agent and connect it to systems such as Shopify and Zendesk so it can take actions.
  • Muse Code: A coding tool for the terminal that uses several agents, built for Muse Spark.
  • Muse Glimmer (open model for local agents): An open model meant for always-on agents that run on your own computer, tuned for tool use, long tasks and recovering from failures.
October 6, 2026
MicrosoftMicrosoft Copilot (formerly Microsoft 365 Copilot); Microsoft Copilot Chat (formerly Microsoft 365 Copilot Chat)
  • Prebuilt Microsoft agents: Researcher and Analyst for research and data analysis with advanced reasoning, and Facilitator for meetings; listed on Microsoft 365 Copilot Business and enterprise plans, with an Agent Store for Microsoft and third-party agents.
  • Agent Builder and Copilot Studio: Agent Builder inside Microsoft Copilot makes quick, simple agents; Copilot Studio builds custom agents, workflows and apps without code, including agents that run tasks or business processes on their own and escalate when needed.
  • Copilot Studio multi-agent orchestration: Connects agents, from Microsoft or partners, so a complex process is routed to the agent with the right knowledge or actions.
October 6, 2026
Mistral AIMistral Vibe (formerly Le Chat)
  • Vibe (assistant and agent): Mistral's assistant now presents itself as an agent for long tasks that uses your knowledge and tools; plans add scheduled prompts, agents or workflows, connectors and custom MCP connectors.
  • Remote coding agents (Vibe for code): Coding agents that run in isolated sandboxes so several tasks run in parallel, with a terminal agent (Vibe CLI) and IDE plugins.
  • Agents and Conversations API: For developers: agents that plan, use built-in tools (code execution, web search, image generation, document library) and hand off to other agents in a workflow.
October 6, 2026
OpenAIChatGPT
  • ChatGPT Work: Give ChatGPT a goal and it gathers context from your apps, files, tools and browser, makes a plan, does the work and checks in for approval; it can also run scheduled and team tasks. Available on all plans on desktop, and on Plus, Pro, Business, Enterprise and Edu on web and mobile.
  • Dots: Always-on agents that keep working between conversations; listed on Pro and on ChatGPT Business Premium seats.
  • Agents SDK and Agents API (developers): Developer tools for building agents that use tools, work with other agents and keep context across steps; the Agents API runs the Codex harness with multi-agent orchestration and MCP support.
October 6, 2026
xAIGrok
  • Multi-agent mode (Grok app): Several agents work on parts of a hard question at the same time, each shows its reasoning, and the results are merged into one cited answer. The page ties multi-agent reasoning to SuperGrok.
  • Grok 4 Heavy / SuperGrok Heavy: xAI described Grok 4 Heavy (July 2025) as using parallel test-time compute to weigh several hypotheses at once, sold through a SuperGrok Heavy tier. The current pricing page lists SuperGrok Heavy as a plan but its text does not describe Heavy as multi-agent.
  • Realtime Multi-agent Research (API, beta): For developers: one request launches 4 or 16 agents that discuss the query, and a leader agent combines their findings into the answer; more agents means deeper research at higher token use and latency.
  • Grok Bot: Always-on agents with their own cloud computer that sign into your tools, finish jobs end to end and come back when something needs your approval; in beta for SuperGrok plans and some Cursor plans, and for enterprises.
  • Workflows in Grok Build: Grok Build, the coding agent, can write and run scripts that split a task across many parallel agents, check the results and report back.
October 6, 2026
Where you’ll meet agents. AI makers’ agent features, as each describes them on its own pages, with the date we read them. Alphabetical; not a ranking. Prices and features change often: check the maker’s page before you buy.

Features change quickly. Treat this as a snapshot and check the vendor’s own page.

How to start

  1. One agent, one task. Pick a task from your Lesson 4 list that is frequent, in software and easy to check.
  2. Write the goal and rules down: what it may do, what it must never do, when to stop and ask.
  3. Give it only the access it needs. A read-only connection where possible; no payment or delete permission unless the task requires it.
  4. Approve every action at first (Level 2), and keep the log.
  5. Loosen slowly. After a few weeks without mistakes, let it act and tell you (Level 3) for the lowest-risk part of the task. Keep the approval gate for anything that sends, pays or deletes.
  6. Name the person responsible, on your team chart from Lesson 5, and in your AI use policy from Lesson 10.

Key terms

Every term is explained in the glossary.

Try this

Take one multi-step task from your list, such as booking a new customer’s first appointment. Write down every step a person takes, every piece of software they touch, and every point where they make a decision. Then mark which steps an agent could do, which need a person’s approval, and which should stay with a person. That is the design for your first agent, and you can hand it to any vendor or developer.

Sources