Built in your Microsoft 365
Agents are built in your own Microsoft 365, and your own Azure subscription where a job needs it, not on our servers. We don't host your data.
Home / The Agent Journey
Capability map
The Agent Journey.
The Agent Journey is FiveForward's map of Copilot agent capability in five stages: Use an agent, Build your first agent, Team agents, Copilot Studio and A team of agents. It takes a team from never having used an agent to running agents across the business, all inside your own Microsoft 365 tenant. At every stage there are two doors: learn to do it yourself or have us build it for you. It is a map of your capability, not our method. The FiveForward Framework (Discover, Design, Enable, Automate and Embed) is how we deliver each step.
Security first
Are Copilot agents secure?
It is the first question most leaders ask: where does our data go? Agents are built in your own Microsoft 365, not on someone else's servers, and what each one can reach depends on the kind of agent it is. Here is the model we build to at every stage.
Agents you talk to see what you can see
An agent your team talks to only sees what that person can already see.
Agents that run use a service account
Agents that run on their own use a dedicated service account. Its access is limited to the mailboxes, folders and systems the job needs, agreed with you in advance.
Not used to train Microsoft's models
Microsoft doesn't use your Microsoft 365 content to train its foundation models.
UK regions where Microsoft offers them
We build in UK regions wherever Microsoft offers them. Where a service isn't available in the UK, or a build uses a model from another provider, we set out where processing happens so your compliance lead can approve it before anything goes live.
Every run is logged
Every run is logged: what came in, what the agent did and who approved it.
Governance still matters. Loose permissions become visible quickly once an agent starts answering questions. That is a reason to tidy them, not a reason to avoid agents. The Copilot agents guide covers governance in more detail.
A Copilot agent is Copilot given one job, and more and more the ability to do it, not just describe it. You give it a name, instructions written in plain English and a set of knowledge sources, such as a SharePoint site.
There are two kinds of agent. Agents you talk to help people find and draft things, and Microsoft's own Copilot now does a lot of that out of the box. Agents that run start on their own when something happens: an email arrives, a meeting ends, a report is exported, a date comes round. They do the checking, drafting and filing, then stop for one of your team to approve. The second kind is where a firm gets hours back, and it's what we build.
The useful ones have named jobs. An agent that answers questions from the firm's procedures. An agent that files the morning post. An agent that turns a client meeting into a filed note. Not an assistant for everything, but a colleague's worth of help with one thing.
Because the agent is grounded in your own company data, its answers come from your policies, your templates and your files rather than the open internet. For the full picture of where agents fit, what makes a good use case and how to govern them, read the plain-English Copilot agents guide.
The five stages below are not our sales process. They are stages of your team's capability, and you can stop at any of them. Plenty of organisations get lasting value from stage two or three alone.
At every stage there are two doors. Learn this: we train your team to do it themselves. Have it built: we build it for you, document it and hand it over. Most organisations mix the two, learning the early stages and commissioning the later ones.
The five stages
From first agent to a team of agents.
Each stage is small and specific on its own. Together they compound into something bigger: agents embedded across the business, each doing one named job.
01
Use an agent
Build skill needed: none
Time: minutes
Use an agent is the stage where staff ask an existing agent questions and get answers grounded in company content, with nothing to build or install.
Someone shares an agent with you, or you pick one from the sidebar in Copilot Chat. You ask it questions and it answers from your company's own content rather than the open internet. That difference has a name: grounding. A grounded agent points to the document its answer came from, so you can check it.
There is nothing to build and nothing to install. If your organisation runs on Microsoft 365, this is available now.
What this looks like
- Ask an HR agent what the home working policy actually says.
- Ask a handbook agent how to book annual leave.
- Check which version of a process document is current.
02
Build your first agent
Build skill needed: none, plain English only
Time: about 15 minutes
Build your first agent is the stage where anyone describes a personal agent in plain English and has it working in about 15 minutes.
In Copilot Chat, the agent builder lets you describe an agent in plain English. Tell it the job, point it at a SharePoint site and it writes the instructions for you. This kind of agent is called a declarative agent: instructions plus knowledge, no code.
From a standing start to a working agent takes about 15 minutes, and anyone who can write a clear email can do it. It is how we close our agent workshops, because watching your own agent answer from your own documents changes what people think agents are.
What this looks like
- A personal agent that answers from your team's project site.
- An agent that knows one client folder inside out.
- A first pass at an agent that answers from the firm's procedures manual.
03
Team agents
Build skill needed: careful writing, no code
Time: days, mostly agreeing sources and testing
Team agents is the stage where one agent does one named job for a whole team, with agreed sources and a named owner.
The step up from a personal experiment is an agent a whole team relies on. That takes proper instructions, agreed knowledge sources and a named owner. The agent does one job for one team and does it consistently.
This is where content quality starts to matter. An agent grounded on a tidy, current SharePoint site gives answers people trust. An agent grounded on an old file dump does not.
What this looks like
- Answers the office's questions about how the firm names and files documents.
- Drafts replies in the company tone of voice.
- Summarises incoming post for the office team.
04
Copilot Studio
Build skill needed: maker level, trainable
Time: weeks, including proper testing
Copilot Studio is the stage where agents gain triggers, connectors and actions, so they start on their own and carry out steps rather than just answer.
Copilot Studio adds triggers, connectors, workflows and actions. A trigger starts the agent on its own when something happens: an email arrives, a report is exported, a meeting ends. An action is a step the agent carries out rather than just describes, so agents stop only answering questions and start doing the next step.
Raising a ticket, updating a record, moving a file, triggering a Power Automate flow. Each action runs with agreed review points, so a person still approves anything that matters.
What this looks like
- WIP exceptions pushed to each manager in Teams, with the decision buttons built in.
- A client meeting filed and actioned: the note, the tasks and the record updates, once the adviser approves.
- A new client checked and onboarded, with one partner approval before anything goes out.
- A VAT return reviewed before filing, with every flag ranked and sourced.
05
A team of agents
Build skill needed: a capability your team owns
Time: grown over months, one agent at a time
A team of agents is the stage where each department runs agents with named jobs, owners and a review rhythm, embedded across the business.
Each agent owns one job. The office has the post agent, managers have the WIP agent, the client team has the onboarding agent. They take the admin off your team, each with a named owner and a review rhythm.
Everything is built in your own Microsoft 365. Agents people talk to only see what that person can already see, agents that run on their own use a service account limited to their job, and every run is logged.
What this looks like
- A dozen agents, each with one job, one owner and one set of knowledge sources.
- New agent ideas come from your own team, because by now they know what a good one looks like.
- A review rhythm keeps agents current as policies and processes change.
The whole firm
Two moves, five stages.
Seen from the leadership side, the five stages are also the firm's route from Copilot licences to agents in the work. It happens in two moves, and each move maps onto the stages above.
Stages 1 to 4
Some learn to build
A builder group works up the stages through our agent workshops: using agents, building a first one, then team agents, Copilot Studio, workflows and automation. Some of the firm, not every member of staff.
Stage 5
The firm embeds it
The business begins embedding agents and automation into its actual processes, one named job at a time. Something the firm builds on stage by stage, not a one-off project.
That is what the Agent Journey looks like across the firm: the people who know the work building agents, and the firm steadily embedding what works.
What this looks like in an accountancy firm
Stages four and five, ready-made.
Six agents that start on their own, do the checking, drafting and filing, then stop for one of your team to approve.
See the six accountancy agents- WIP and billing agent Starts when your practice system emails its scheduled WIP report.
- Adverse media and conflict checks Starts when a new client record is created.
- Client meeting agent Starts when a meeting carries your Client meeting category.
- PBC and records chaser Starts when a job is created in your practice system.
- Client onboarding agent Starts when a new client's intake form is submitted.
- VAT return review agent Starts when the VAT return detail export lands in the quarter folder.
Two tools, one path
Copilot agent builder vs Copilot Studio.
You do not have to choose one. Most firms start in the agent builder and move to Copilot Studio when an agent needs to act, not just answer.
In September 2026 Microsoft announced Autopilot (previously Scout) and Code in Copilot. We'll update this comparison as they roll out.
Stages 1 to 3
Copilot Chat agent builder
- Built inside Copilot Chat in plain English.
- Declarative agents: instructions plus knowledge sources.
- Answers questions and drafts text. It does not take actions.
- Grounded on SharePoint sites and Microsoft 365 content.
- The right tool for a first agent and for most team agents.
Stages 4 and 5
Copilot Studio
- A full build environment for agents, licensed separately.
- Adds connectors, workflows and actions.
- Agents can raise tickets, update records and trigger Power Automate flows.
- Needs maker-level skills, which teams learn or bring in.
- The right tool once an agent needs to do things, not just answer.
Where to go next
The map is here. These are the transport.
Plain English guide
Microsoft Copilot agents
The companion guide: what agents are, where they fit, good and poor use cases and how to govern them.
Have it built
Copilot Studio consultancy
The build service behind the second door: scoping, grounding, testing, rollout and handover.
Learn to build
Agent workshops
One workshop offer for your builder group, sized by the roadmap, from first agent to Copilot Studio.
Keep it running
Embed
Agent operations, optimisation and async support on a monthly retainer once agents are live.
How we deliver
The FiveForward Framework
The Agent Journey is your capability map. The framework is how we deliver each step: Discover, Design, Enable, Automate and Embed.
Fixed prices
Pricing
Fixed prices for Discover, agent builds, workshops and Embed, all in one place.
What is a Copilot agent?
Copilot given one job, and more and more the ability to do it, not just describe it. Agents you talk to answer questions about that job from named sources, such as a SharePoint site. Agents that run start on their own when something happens, do the checking, drafting and filing, then stop for a person to approve. Either way they take admin off people; they don't replace them.
Are Copilot agents secure?
We build agents in your own Microsoft 365, not on our servers, and we don't host your data. Agents your team talks to only see what that person can already see. Agents that run on their own use a dedicated service account, limited to the mailboxes, folders and systems the job needs, agreed with you in advance. We build in UK regions wherever Microsoft offers them, and anything that has to run elsewhere is set out for your compliance lead to approve before go-live. Microsoft doesn't use your Microsoft 365 content to train its foundation models, and every run is logged.
What is the difference between the Copilot agent builder and Copilot Studio?
The agent builder in Copilot Chat creates declarative agents in plain English: instructions plus knowledge, good for answering questions from your own content. Copilot Studio adds connectors, workflows and actions, so an agent can raise tickets, update records and trigger Power Automate flows.
Do we need to be technical to build an agent?
No. A first declarative agent is described in plain English and grounded on a SharePoint site in about 15 minutes. Copilot Studio work needs more skill, which teams either learn in our agent workshops or hand to us to build.
Do Copilot agents replace staff?
No. Agents take on defined jobs such as answering policy questions or preparing drafts, and they run with agreed human review points. The aim is fewer repeated interruptions and less manual admin, not fewer people.
Where should we start with Copilot agents?
Use an agent, then build one. The first two stages need nothing bought and nothing built beyond the Copilot access most Microsoft 365 organisations already have. When a team wants a shared agent doing a named job, choose a door: learn to build it yourselves or have it built for you.
Next step
Work out which stage you are at.
A short call is usually enough to place your team on the Agent Journey and pick the right door for the next stage: learn it or have it built.