Home / The FiveForward Framework

Adoption framework

The FiveForward Framework

A five-stage method for turning Microsoft Copilot from a licence into a working habit.

Book a free consultation Explore the services

6 min read Updated 7 July 2026

Jump to section

Why most Copilot rollouts stall

Most Copilot rollouts do not fail because the tool is weak. They stall because access arrives before people know what to do differently on Monday morning.

The licence is bought, the announcement goes out and a training session is booked. A few people find useful habits. Others try it once, get an average answer and go back to the familiar way of working.

The missing piece is not another feature demo. Staff need clear use cases, real examples, safe-use rules, follow-up support and a route for the repeated work that should be automated rather than prompted each time.

The FiveForward Framework is a practical way to create that route: Discover, Design, Enable, Automate and Embed.

The five stages, at a glance

The framework follows five stages in sequence. Each can be scoped as a standalone engagement or run as part of a wider programme.

Discover

Discover is a fixed £1,500 assessment that maps how your teams work and produces a prioritised, costed roadmap of Copilot opportunities, credited back once follow-on work passes £3,500.

Design

Design is a one-day workshop, included with every engagement after a paid Discover, that sets the pilot team, targets and build route and fixes the price of the chosen route in a plan on a page.

Enable

Enable is the training and support stage, built around real emails, meetings, files and decisions, and every session ends with a real agent built and running in your tenant.

Automate

Automate is the build stage, where FiveForward delivers Copilot Studio agents, Power Automate flows and Microsoft 365 automations for work that repeats, from £5,000 fixed at Design.

Embed

Embed is the ongoing stage that keeps adoption alive after launch, with a supported champions network, office hours and a monthly retainer from £750.

Discover

What happens

We talk to the people doing the work, map repeated tasks and find the places where Copilot could reduce friction without creating avoidable risk. We also note the early adopters who volunteer experiments, the people who often become champions later.

Why it matters

Most rollouts stall because the training starts before anyone knows what staff should use Copilot for. Discover gives the rollout a useful target.

What you get

A workflow map, a prioritised set of use cases and a costed roadmap of what is worth doing and in what order, plus the blockers that need attention.

Examples

Interview tax, audit or operations teams about repeated admin and handovers.
Review where important files, meeting notes and templates actually live.
Separate good Copilot candidates from tasks that need SharePoint cleanup or a human review step first.

Explore Discover services

The first paid step

Discover is the stage. It is also how engagements are designed to begin: a fixed £1,500 piece of work, credited back in full once follow-on work passes £3,500. You come away with a workflow map, a prioritised set of use cases and a costed roadmap of what is worth doing and in what order, whether or not you carry on with us.

The free consultation comes first. Discover is what we recommend on that call when the fit is right.

See what Discover covers

Design

What happens

Design is a one-day workshop. The morning covers the pilot team, the rollout sequence and the 30, 60 and 90 day targets, plus the build route decision on agents and automations: we build them, or we train your team to build them in-house. The afternoon produces the plan on a page.

Why it matters

A rollout cannot cover everything at once. Design keeps the first wave focused enough for people to understand and leaders to measure.

What you get

The plan on a page, produced in the afternoon as the proposal, with the price of the chosen route fixed in it. Design is included with every engagement that follows a paid Discover and never separately charged.

Examples

Choose client meeting follow-up before more complex client drafting.
Sequence the champions' teams first so their workflows become the pilot examples.
Create separate training paths for partners, managers and support teams.
Define what good usage should look like after 30, 60 and 90 days.

Explore Design services

Enable

What happens

We deliver practical training, office hours and role-based examples so staff can try Copilot in the work they already recognise.

Why it matters

People do not change habits because they saw a feature demo. They change when they can practise a useful task, get help and see managers reinforce the behaviour.

What you get

Training sessions, role examples, prompt guidance, follow-up actions and support for the first real questions after launch.

Examples

Train fee earners on meeting summaries, follow-up emails and document preparation.
Show finance teams how to draft commentary without treating AI output as final analysis.
Run office hours where staff bring failed prompts and live workflow questions.

Explore Enable services

Automate

What happens

We build or improve the workflows where automation is a better answer than asking a person to prompt Copilot every time. This is the stage the earlier work builds towards: Copilot agents and automations taking on repeated steps while your team keeps the agreed review points.

Why it matters

Some work should not depend on memory, chasing or copy-paste. Automation helps when the process is clear enough to run safely in the background.

What you get

Documented Power Automate flows, Microsoft 365 workflow improvements, agent scope or build work, plus handover notes.

Examples

Route training bookings, reminders, feedback and certificates from one form response.
Move document approvals through SharePoint and Teams without manual chasing.
Build a narrow Copilot Studio agent for internal knowledge or intake once the source content is ready.

Explore Automate services

Embed

What happens

We help the change continue after the launch with champions, office hours, prompt libraries, usage reviews and small improvements. That includes any agents you now run. Owners stay named, knowledge sources stay current and new agent ideas come from your own team.

Why it matters

Copilot habits fade when the support fades. Embed gives people somewhere to take questions and gives leaders a clearer view of what is improving.

What you get

A support rhythm, champion guidance, reusable examples, review points and a backlog of the next use cases worth developing.

Examples

Set up monthly office hours for awkward prompts and real workflow blockers.
Give champions examples they can share inside their own teams.
Review usage themes and decide whether the next step is training, SharePoint work, automation or an agent.

Explore Embed services

How the stages connect

The stages are flexible, but the order matters when the work is unclear.

Discover before Design. If you do not know where time is being lost, the plan will be based on guesses.

Design before Enable. Training works better when the first teams, examples and success measures have already been chosen.

Discover before Automate. A workflow that looks simple often contains exceptions, handovers and judgement calls. Those need to be visible before anything is built.

Enable before Embed. Champions and office hours work best once people have tried Copilot against real tasks and have real questions to bring back.

Champions run through all five. They are spotted in Discover, sequenced first in Design, trained early in Enable, drive the agent ideas in Automate and are formalised into a supported network in Embed.

You do not have to buy all five stages. The point is to choose the right starting point with the dependencies in view.

Who the framework is for

The FiveForward Framework is designed for UK organisations where Copilot has been purchased and the next question is what to actually do with it. It works for any knowledge-led team, and fits professional services particularly well, where the work is knowledge-heavy, the Microsoft 365 dependency is high and the risks of poor adoption are well-understood once named.

The framework applies across sectors. Use the sector pages for more specific examples of where Copilot, automation and Microsoft 365 adoption fit the work.

Accountancy firms Client reports, engagement letters and knowledge retrieval. Law firms Controlled drafting, research and matter preparation. Finance teams Reporting packs, commentary and forecasting workflows. HR and people teams Policy, onboarding and internal communications. Marketing teams Campaign planning, drafting and review workflows. Sales teams Account planning, follow-up and proposals. Retail teams Store communication, task follow-up and knowledge bases. Businesses and SMEs Broader operational adoption across Microsoft 365.

We are based in Essex and work across the UK, online or on site. See where we deliver Copilot training:

Essex Colchester Chelmsford Ipswich Cambridge London All locations

Worked examples: how the stages are designed to run

The worked examples below show how the stages are designed to translate into decisions, training and workflow work.

Worked example: accountancy firm, roughly 120 staff

Picture a firm that has purchased Copilot licences across the organisation but has not yet started training. Rather than begin with training, a firm like this would commission Discover first.

Discover typically runs about three weeks at this size. It involves structured interviews with fee earners across tax, audit and advisory, mapping the tasks that consume the most unrecoverable time each week. Three workflows would emerge as clear priorities. The first is the monthly client management report: a recurring task that can take a team six hours per cycle, drawing on meeting notes, emails and spreadsheet commentary. The second is the preparation of engagement letters, drafted largely from scratch despite following predictable patterns. The third is internal knowledge retrieval: junior staff spending time searching for precedent documents and past advice scattered across a fragmented SharePoint structure.

None of those three workflows tends to come up in the initial licence conversation. Two would be invisible to management, because the time cost is distributed across junior staff who have not been asked about their workload.

The Design stage takes those three use cases and builds the executable programme: which team first, which Copilot features to cover, what success looks like for each workflow and in what order the rollout runs. The Enable stage then builds specific training sessions around each workflow rather than running generic feature demos.

Worked example: professional services firm, roughly 200 staff

Now picture a consultancy that has completed its own Discover and Design work internally and needs Automate support alone. The specific need: a Copilot Studio agent to handle the initial briefing and intake process for new client engagements, reducing the time partners spend on administrative coordination.

The Automate engagement begins with a process review, which exists to surface the edge cases in the intake workflow that would break the agent if they were not accounted for. A build like this typically takes about four weeks including testing. The agent goes live with clear governance: a defined scope, a human review step and a documented process for handling exceptions.

Where to go from here

If you are thinking about how the framework applies to your organisation, the most useful next step is a conversation. Not a sales call. A working conversation about where you are now, what adoption looks like today and which stage of the framework would move things forward most quickly.

Book a free consultation to talk it through with someone who has seen a lot of Copilot adoption work. Or if you want to understand the individual services first, explore the service map.

Engagements are designed to begin with Discover, a fixed £1,500 that is credited back in full once follow-on work passes £3,500. Fixed prices are on the pricing page.

Next step

Start with a free consultation.

A short, no-obligation call is enough to work out where the framework fits your organisation and what a sensible next move looks like.

Book a free consultation Explore the services