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.
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 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
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.
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.
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 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.
Microsoft doesn't use your Microsoft 365 content to train its foundation models.
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: 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
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 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
For firms on licences
Copilot in your workflows
Already on Copilot licences and want your team getting more from them? Start here. Most firms go on to a Firmwide install once they can see which jobs Copilot still can't do the firm's way. A hands-on half day or full day on your team's own weekly jobs, with the firm's way saved as prompts, instructions and skills they keep.
In the handover
The handover
Each department is shown what Copilot can do once permissions are checked and the firm's templates and procedures are in SharePoint, on its own weekly jobs, hands-on and follow-along, by the people who built the install.
In the install
The foundation step
Copilot is only as good as what it can see. The foundation step of the install checks permissions and fixes any oversharing, agrees a named owner and simple rules and puts your templates and procedures in SharePoint.
02
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
In the handover
The handover
Where a firm has Cowork, the handover covers handing it a real job from each person's own week, briefing it well, checking its work before approving and keeping the cost down, with the department's skills pack in use.
Free
The free skills library
Shows the format on typical practice work. Download one, read it and change it. Firmwide is the version built from your own procedures, and every install sets the library up in your tenant.
In the install
Firmwide: a skills pack per department
A fixed-price install, typically six to eight weeks: Copilot made safe and useful in your Microsoft 365, an agent and a skills pack for every department, handed over with training. Then Run keeps it working. First department £6,950, each extra department £2,500, whole firm priced on the Readiness Check. Cowork is set up with access and spending limits as part of the foundation.
03
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
In the handover
The handover
Each department is shown how to use its skills pack in Copilot Chat on its own data, and what to ask Copilot now that permissions are checked and the firm's templates and procedures are in SharePoint.
In the install
A skills pack per department in the install
Every department in scope gets a skills pack built from its own templates and procedures, which your team uses in Copilot Chat, Cowork and the department's agent. There is no separate set of assistants on top.
04
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.
What this looks like
In the handover
The handover
The people who will own each agent are shown what starts it, what it does, where it stops and how to approve its work, with a one-page scope and a kill switch.
In the install
One agent per department in the install
Chosen from the six accountancy agents or built bespoke, on the templates and procedures the foundation step put in SharePoint and connected to the systems each one needs, tested on real cases with the people who will use them and handed over with user and technical documentation.
In the install
The six accountancy agents
What starts each one, what it does and where your team approves. Built as part of an install, or added to a Run plan from £2,500.
05
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
In the handover
Champions sessions on Run
On Run Growth, a champions session each quarter with the people who use the agents most, and a handover session for new starters as a fixed-price add-on for Run clients.
In the install
Extra departments and agents
Each extra department is mapped, built, documented and handed over the same way at £2,500, and an extra agent is added to the Run plan from £2,500.
Keep it running
Run: we keep it working
The monthly plan that keeps your agents and skills working, improved a little each month and reported on.
The whole firm
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
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 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 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.
What this looks like in an accountancy firm
Six agents that start on their own, do the checking, drafting and filing, then stop for one of your team to approve. Pick them for your install, or add one later.
See the six accountancy agentsTwo tools, one path
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
Stages 4 and 5
Where to go next
The install
One fixed-price install, priced by department, that makes Copilot safe and useful first and builds the skills stage and the agent stages on it.
Stage three onwards
Each department shown how to use Copilot, the agents and the skills on its own data, by the people who built them.
Plain English guide
The companion guide: what agents are, where they fit, good and poor use cases and how to govern them.
Stage one, for firms on licences
A hands-on half day or full day on your team's own weekly jobs, with the firm's way saved as prompts, instructions and skills they keep.
Keep it running
Keeps the install working after handover, from £750 a month with the first month included.
How we deliver
The Agent Journey is your capability map. The framework is how we deliver each step: Check, Plan, Build, Handover, Run.
Fixed prices
Fixed prices for the Readiness Check, the install priced by department, Run and the add-ons, all in one place.
Next step
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.