Home / The Agent Journey

Capability map

This page is a map of a firm's capability, kept for reference. How we deliver every engagement is the FiveForward Framework: Check, Plan, Build, Handover, Run.

The Agent Journey.

The Agent Journey is FiveForward's map of how a firm gets from the Copilot licences it already has to agents running across the business, in five stages: Copilot in your workflows, Cowork and skills, Agents you talk to, Agents that run and A team of agents. Most firms have the licences and a team that can prompt. What they don't have is a route to the value, because nobody has checked what Copilot can see or written down how the firm does things. A Firmwide install makes Copilot safe and useful first, builds the skills stage and the agent stages on it and hands each department over with documentation and training. It is a map of your capability, not our method. The FiveForward Framework (Check, Plan, Build, Handover, Run) 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.

Built in your Microsoft 365

Everything is 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.

Agents you talk to see what you can see

An agent your team talks to only sees what the person using it can already see. The install sets permissions so people only see what they should.

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. Every agent has a kill switch and a named owner.

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 works from 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 firm's capability, starting from the Copilot licences you already have, and you can stop at any of them. Plenty of firms get lasting value from the first two or three alone.

A Firmwide install makes Copilot safe and useful first, builds the skills stage and the agent stages on it and hands each department over on its own data and jobs, by the people who built it. The cards under each stage show what the install builds there and what the handover covers.

The five stages

From the licences you have to a team of agents.

Each stage is small and specific on its own. Together they compound into something bigger: Copilot doing more of the week's work, then agents embedded across the business, each doing one named job.

Stage one uses what the licence already includes. From stage two, some of the work draws Copilot Credits, which Microsoft bills to your firm. We estimate running costs during mapping and keep them low by design.

01

Copilot in your workflows

Skill needed: none beyond writing a prompt
Time: part of each department's handover, then everyday use

Copilot in your workflows is the stage where a firm uses what its Copilot licence already includes, properly, on its real jobs, and saves its way of doing each job as a prompt, an instruction or a skill.

Most firms already have Copilot licences and their team can prompt. What they don't have is a route to the value. It starts with what the licence already includes, used on the jobs the firm does every week.

What makes it last is capturing how the firm does each job as something reusable: a saved prompt, a custom instruction, a Notebook for each client or, where Microsoft has switched skills on for your firm, a skill in Word or PowerPoint. That is the first rung of the same skills idea that stage three builds on and that runs through Cowork and Copilot Studio.

Where Copilot stops is where the next stages begin. Three kinds of job need more than the licence gives you: whole pieces of work done for you (Cowork), routine work done your firm's way every time (a skill) and work that starts on its own when something happens (an agent).

What this looks like

  • A tax senior answers January's client queries from the firm's own guidance, in their own tone.
  • A fee earner turns a new enquiry into intake notes on the firm's template, the same way every time.
  • An adviser prepares for a review meeting from one Notebook holding that client's files, emails and meetings.

02

Cowork and skills

Skill needed: a clear brief and knowing how the job should be done, no code
Time: an afternoon to write a first skill, or a skills pack per department inside a Firmwide install

Cowork and skills is the stage where someone needs whole pieces of work done, with approval before anything is sent, and where the firm's way of doing each recurring job is written down once and built into Copilot, so routine work is done the firm's way by everyone, every time.

Copilot Chat answers a question. Cowork does a whole piece of work: you describe the job and it plans it and does it, then asks for approval before it sends, posts or schedules anything. This is also where Copilot Credits start, which is why the install puts access and spending limits in place before anyone is handed over on it.

A skill is the firm's way of doing one job, saved once and used by everyone: the template, the structure, the checks and the tone. It's the step up from a saved prompt, and the same idea runs through Cowork, Word, Excel, PowerPoint and Copilot Studio. A firm can start small: one person writes a skill for one job, tests it on real examples and shares it. Our free skills library shows the format on typical practice work. The step up is the install: the firm's own procedures mapped with each department and built into a skills pack, with Run keeping them working as Microsoft changes.

Skills are also the groundwork for agents. An agent built on a procedure the firm has already written down is quicker to build and easier to trust, which is why this stage sits before the agent stages.

What this looks like

  • A Monday briefing pulled together from the week's emails and calendar, waiting for approval before it goes.
  • A weekly client-status summary, written the same way each time by a skill.
  • A fee proposal drafted on the firm's template, with the banned words left out.
  • Variance commentary from a management accounts export, with the checks the reviewer expects already done.

03

Agents you talk to

Skill needed: careful writing, no code
Time: about 15 minutes for a first agent, days for a team agent

Agents you talk to is the stage where people use the agents the firm already has, anyone builds a first one in plain English and a team gets an agent with one named job and an owner.

Someone shares an agent with you, or you pick one from the sidebar in Copilot Chat and bring it into the conversation with @. It answers from your firm's own content rather than the open internet and points to the document its answer came from, so you can check it.

Building a first one takes about 15 minutes. In Agent Builder, in Copilot Chat, you describe the job in plain English, point it at a SharePoint site and it writes the instructions for you. Anyone who can write a clear email can do it, and it only works well once that SharePoint site holds something worth asking about.

The step up is a team agent: one named job for one team, with proper instructions, agreed sources and a named owner. This is where content quality starts to matter. An agent that answers from a tidy, current SharePoint site gives answers people trust. An agent pointed at an old file dump does not.

What this looks like

  • Ask a handbook agent how to book annual leave.
  • A personal agent that knows one client folder inside out.
  • A team agent that answers the office's questions about how the firm names and files documents.

04

Agents that run

Skill needed: maker level, trainable
Time: weeks, including proper testing

Agents that run is the stage where agents built in Copilot Studio start on their own when something happens, act and stop for a person to approve.

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, starting a workflow. Each action runs with agreed review points, so a person still approves anything that matters. These agents are built in the install, on a foundation of permissions checked and the firm's procedures in SharePoint and handed to a named owner.

Copilot Studio offers more than one harness, Microsoft's name for the engine around an agent. The choice is made before building starts.

Which Copilot Studio harness should your agent be built on?

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

Skill needed: a capability your team owns
Time: grown over months, one agent at a time

A team of agents is the stage where several teams run agents, each with a named job, an owner and a review rhythm, and someone keeps them running.

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, and they are kept running as Microsoft's tools and the firm's processes change. The skills from stage three sit underneath them, so the agents and the people work from the same procedures.

Everything is built in your own Microsoft 365. Agents people talk to only see what the person using them 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

Three 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 three moves, and each move maps onto the stages above.

Stages 1 to 3

Everyone uses it

The whole team gets more from the licences the firm already pays for: Copilot on their own jobs, with permissions checked and the firm's templates and procedures in SharePoint, Cowork for whole pieces of work, the firm's own skills so routine work is done the same way and agents they talk to for the routine questions. The handover covers each stage on the firm's own work, and the install builds the skills stage.

Stage 4

The first agents are built

The install builds one agent that runs on its own per department, on a foundation of permissions checked and the firm's templates and procedures in SharePoint and hands each one to a named owner with a one-page scope, a kill switch and the documentation.

Stage 5

The firm keeps adding to it

The firm adds departments and agents one named job at a time, and Run keeps everything working as Microsoft changes. Something the firm builds on stage by stage, not a one-off project.

That is what the Agent Journey looks like across the firm: everyone getting more from Copilot, the people who know the work building agents and the firm steadily embedding what works.

Two tools, one path

Copilot agent builder vs Copilot Studio.

Stages one and two need neither tool: they use Copilot, Cowork and skills as they come. From stage three you do not have to choose one. Most firms begin in the agent builder and move to Copilot Studio when an agent needs to act, not just answer.

Stage 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.
  • Answers from 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.
  • 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.
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 everything in your own Microsoft 365, not on our servers, and we don't host your data. An agent your team talks to only sees what the person using it can already see, and the install sets permissions on least privilege. 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, every run is logged and every agent has a kill switch.
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 pointed at a SharePoint site in about 15 minutes. Agents that run need more, which is why the install builds them for you and hands each one to a named owner.
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 the data. Copilot is only as good as what it can see, and in most firms it can see almost nothing, so a Firmwide install makes Copilot safe and useful first and then builds the skills stage and the agent stages on it. A free Copilot Readiness Check tells you where Copilot can and cannot see your data, the two jobs to automate first and a rough install price. Already on licences? Start with Copilot in your workflows.

Next step

Find out where Copilot can and cannot see your data.

A free 30-minute Copilot Readiness Check, online, with James. You leave knowing where Copilot can and cannot see your data, the two jobs to automate first and a rough install price.