Copilot Adoption Framework · Microsoft 365 Copilot

From first prompt to everyday agents, at every level.

Licences don't change how people work. Confidence does. Our framework starts from your teams' own use cases and context: how Copilot can help in their day-to-day work, and what that work needs. From there it takes them from the basics of large language models to working with agents every day, measured, so the new way of working actually sticks.

A hands-on AI training session, colleagues helping each other (AI-generated image)See how we use AI
The pathway

Four levels. Everyone starts where they are.

Some people have never written a prompt. Others are ready to build agents. The pathway meets each of them at their level and moves them on, one step at a time.
Level 1 · Everyone

Foundations

What large language models are, what Copilot can and can't do, and how to use it safely with your data.

  • How AI works, in plain words
  • Your first useful prompts
  • What to share and what not to
Level 2 · Every role

Everyday use

Copilot in the work people already do, with prompts tailored to their role, not a generic demo.

  • Prompts built around real tasks and challenges
  • Copilot in Outlook, Teams, Word and Excel
  • A take-home cheat sheet
Level 3 · Teams

Working with agents

Knowing when a prompt is enough, when an agent helps, and when to ask for something to be built.

  • Prompt, agent or build: a simple decision tree
  • Using and sharing ready-made agents
  • Your first agent in Agent Builder
Level 4 · Champions

Champions and builders

The people who keep it going: they spot use cases, build agents and help colleagues.

  • Use case discovery with their teams
  • Copilot Studio agents on governed data
  • A champions network that carries it on
From use case to the right tool

Not every idea needs an agent.

Every use case your teams find goes through the same simple decision tree. Some are best as a prompt they reuse, some as a personal agent, and a few deserve a governed solution your IT team owns. Choosing well keeps costs down and gets value sooner.

A use case from your team
Quick win

A reusable prompt

Microsoft 365 Copilot Chat

A well-written prompt the person saves and reuses, right inside Outlook, Teams, Word or Excel.

For example: summarise a long email thread and draft the reply.

Personal helper

A personal agent

Agent Builder in Microsoft 365 Copilot

A small agent someone builds for their own repeat task, grounded on the files and sites they already use.

For example: an agent that answers questions from the team handbook.

Team solution

A Copilot Studio solution

Microsoft Copilot Studio

A governed agent for a whole team or process, built and supported with your IT and AI teams.

For example: intake and triage of internal requests across a business unit.

One safe foundation under all three

Each person's own sign-in and permissions, your data policies and admin controls
Knowledge sourcesSharePoint, files and sites people already have access to
Microsoft DataverseBusiness data, governed by your existing security roles
ConnectorsApproved links to your other systems, within your data policies
Skills and workflowsTasks and flows agents can run for you, with a person approving what matters
Product names and icons belong to Microsoft and are shown to explain how the options fit together.
How we run it

Five steps for every team we work with.

Each team or business unit goes through the same proven cycle. The first three steps take one to three weeks.
  1. Prepare

    We meet the team lead, pick the roles to start with and agree what success looks like.

  2. Listen to experts

    Short conversations with the people who do the work, to capture their real tasks and language.

  3. Tailor

    We shape the workshop and prompts around those roles, so every example feels familiar.

  4. Deliver

    A hands-on workshop. People try it live and capture their own use cases as they go.

  5. Reinforce and measure

    A take-home pack, then an impact check about a month later, so you see what changed.

What your team keeps

Built once, used again and again

  • A role-based library of use cases and tested prompts
  • A simple decision tree: prompt, agent, or ask for a build
  • Prompt cheat sheets and a take-home pack for every workshop
  • An impact template, so each team measures what changed
  • A champions network that keeps it going after we leave
People first

Why adoption stalls, and how we avoid it

Most rollouts give everyone the same generic training and hope for the best. People try it once, don't see their own work in it, and stop. We start from each role's real tasks, let people practise on them, and measure the result. Good ideas that need more than a prompt go to your IT or AI team in a form they can act on.

Case · Assento

Copilot adoption at a leading bank in South Africa

Through Assento, on behalf of Microsoft, we rolled out our framework at a leading bank in South Africa: a stepped pathway from first prompts to working with agents every day, run business unit by business unit. The bank continues to scale our framework as we work alongside their key subject-matter experts and Microsoft on their Copilot adoption strategy and drive for 2026 and 2027.

Full case study coming soon
The offer

Copilot Adoption Framework

From€7,500excl. BTW · 6–12 weeks
  • The pathway for your first one or two teams
  • Tailored workshops, prompts and take-home packs
  • Champions trained and an impact check after a month

Works with Microsoft 365 Copilot licences and with Copilot Chat. The from-price covers one or two teams, up to 25 people in total, with hands-on sessions in small groups. Scale to more teams at your own pace, with a lower price for every further rollout.

Book a call about adoption (opens in a new tab)