ANSWERS · COMPARISON
AI agents vs Copilot: what's the difference?
Written by the Forth Systems team · Last updated
The short answer
A copilot assists a person who is already doing the work — it drafts, summarises and answers, and a human presses send. An agent owns a process: it is triggered by an event, decides what to do, acts across your systems and only escalates the exceptions. Copilots make individuals faster. Agents remove whole steps from the working day.
What is an AI copilot?
A copilot is an assistant that sits inside a tool a person is already using — an inbox, a document, a CRM record — and responds when asked. It drafts, summarises, explains and answers questions, usually grounded in the company's own documents and data.
Microsoft Copilot, and the copilot features now built into most business software, all work this way: the human stays in the driving seat and presses send. Nothing happens unless someone asks for it.
What is an AI agent?
An agent is triggered by an event rather than a person: an email arrives, a job completes, an invoice ages past thirty days. It then decides what should happen, acts across your systems through their APIs, and escalates only the exceptions to a human.
That changes where the value comes from. A copilot's benefit is capped by how much time the person using it already spends in that tool. An agent's benefit is the whole process it takes over, including the waiting time between people.
AI agents vs Copilot: side by side
| Copilot | Agent | |
|---|---|---|
| Started by | A person, in the moment | An event, a schedule or a rule |
| Scope | One task inside one tool | A process across several systems |
| Output | A suggestion, draft or answer | Records updated, messages sent, work moved on |
| Human role | Reviews and sends every time | Approves exceptions and consequential steps |
| Runs when | You are at your desk | Overnight, weekends, whenever the trigger fires |
| Fails by | Being ignored | Acting confidently on a bad read |
| Typical win | Faster writing, faster search | Hours of coordination removed |
How is an AI agent different from a chatbot?
A chatbot answers in a conversation window. Its output is text; the work still has to be done by somebody afterwards. An agent's output is a change in your systems: a record created, a stage moved, a quote drafted and queued, a supplier chased.
The practical test is simple. If switching it off only means people have to write their own replies, it is a chatbot or a copilot. If switching it off means work stops moving, it is an agent.
Microsoft Copilot vs a custom AI agent
Microsoft Copilot is excellent inside the Microsoft 365 estate: your email, files, meetings and Teams threads. If your problem is people writing and searching too slowly, buy the licences before you build anything.
A custom agent is what you build when the process crosses systems Microsoft does not own — your job management platform, accounting package, telephony, supplier portals and website enquiries — and when you need it to act rather than suggest. Most UK operators we work with end up with both: Copilot licences for the desk work, custom agents for the operational spine.
What a copilot is genuinely good at
- Answering internal questions from your own procedures, jobs and documents.
- Drafting a reply, a quote or a job note the person then edits.
- Summarising long threads, call transcripts and reports.
- Onboarding: new staff asking the system how things are done here.
What an agent is genuinely good at
- Triaging every inbound enquiry, scoring it and putting it in the pipeline with a first reply out.
- Chasing invoices and quotes on a schedule, escalating only what stalls.
- Reading supplier documents, extracting the numbers and updating the job.
- Watching for exceptions — an overdue job, a missed SLA, a margin dropping — and telling the right person.
Keeping control of an agent
Every agent we build has three non-negotiables: a clear trigger, a full log of what it did and why, and a human approval gate on anything touching money, safety, legal exposure or a customer relationship.
In practice that means an agent can draft and queue a quote, chase a payment, or move a deal stage on its own — and it cannot issue a credit note, sign anything, or contact a client outside the templates you approved. Full manual override is the default, not a feature request.
What each costs
Copilot-style licences are priced per user per month, so the cost scales with headcount and the benefit scales with how much each person writes and searches.
A first production agent typically costs £6,000 to £25,000 to build depending on how many systems it touches, plus roughly £150 to £600 a month to run. The cost is fixed against the process rather than the headcount, which is why agents tend to look better the larger the volume of work they absorb.
Agent build cost by sector in the UK
Agent pricing follows the sector's paperwork, not its size. These are the fixed-price bands Forth Systems quotes against in the UK, with the monthly figure covering hosting, model usage, monitoring and support.
| Sector | First production build | Bespoke agent | Monthly running cost |
|---|---|---|---|
| Construction & contracting | £8,000–£18,000 | £18,000–£40,000 | £250–£750 |
| Landscaping & grounds maintenance | £6,000–£12,000 | £12,000–£26,000 | £150–£450 |
| Plant hire & equipment | £7,000–£15,000 | £15,000–£32,000 | £200–£600 |
| Logistics & haulage | £8,000–£18,000 | £16,000–£35,000 | £250–£800 |
| Property & facilities management | £7,000–£16,000 | £15,000–£34,000 | £200–£650 |
| Professional services | £7,000–£16,000 | £16,000–£38,000 | £200–£700 |
Which should you build first?
If your problem is 'our people spend too long writing and searching', start with a copilot grounded in your own content. It is quicker to stand up and easy to withdraw if nobody uses it.
If your problem is 'things sit waiting for someone to pick them up', build an agent. The measurable win is the waiting time, and it shows up in the first week rather than the first quarter.
Most operators end up with both: an agent running the process and a copilot for the humans handling the exceptions it raises.
Frequently asked questions
- What is the difference between an AI agent and a copilot?
- A copilot is prompted by a person and produces a suggestion the person acts on. An agent is triggered by an event, decides what to do and carries out the action in your systems, escalating only exceptions. Copilots speed up individuals; agents remove steps from a process.
- Is Microsoft Copilot an AI agent?
- Not in its standard form. Microsoft Copilot assists a person inside an application — answering, drafting and summarising on request. Microsoft does offer agent-building tools such as Copilot Studio, but the licensed Copilot experience most people use is an assistant, not an unattended agent.
- What is the difference between an AI agent and a chatbot?
- A chatbot's output is a conversation; an agent's output is a change in your systems. If turning it off just means staff write their own replies, it is a chatbot. If turning it off means work stops progressing, it is an agent.
- Do we need Copilot licences if we build custom agents?
- Often yes, for different reasons. Copilot licences help the individuals doing desk work in Microsoft 365; custom agents handle the cross-system operational process. They are complementary purchases, not alternatives.
- Are AI agents safe to let loose on customer communication?
- Only with guardrails. We keep agents inside approved templates, log every action, and require human approval before anything consequential leaves the business. The agent's job is to remove waiting and re-keying, not to improvise with your customers.
- Do agents replace our CRM or job system?
- No. Agents work inside the software you already run — CRM, accounting, email, telephony, job management — reading and writing through their APIs. Replacing your stack is rarely necessary and always more expensive.
- What does an AI agent cost to build?
- A first production agent typically costs between £6,000 and £25,000 depending on how many systems it touches, plus a monthly running cost of around £150 to £600 for hosting, model usage and support. A grounded copilot is usually at the lower end of that range.
- How long does it take to deploy an AI agent?
- A single well-scoped agent takes four to eight weeks from discovery to production, most of which is integration and testing rather than model work. Broader multi-process rollouts run over several months, one workflow at a time.
- How do we know it's actually working?
- Instrument it before you launch: time from enquiry to first reply, percentage handled without a human, exceptions raised, and hours released. If a system cannot show those numbers, it cannot be defended at the next budget review.
Keep reading
- AI automation vs RPARules-based robots versus interpreting systems.
- AI automation cost in the UKBuild and running cost ranges.
- AI automation hubThe systems we build and how to start.
- AI by industryWhere agents pay off in construction, landscaping and plant hire.
- 2-minute AI scanSee which processes to hand to an agent first.
- ROI calculatorModel savings and payback for your team.
Ask us about your own setup
Tell us what is slowing the business down. We reply with a straight answer on what can be automated, what should stay human, and what it would cost.
