The Second Wave: A Copilot Adoption Workshop
for rollouts that stalled.
Bottom line: The Second Wave is a copilot adoption workshop for teams whose Microsoft 365 rollout already happened and mostly went quiet. 4 sessions over 4 weeks, up to 20 people, from $8,440 / €7,280.
You already paid for the licences. This is not a second launch event and it is not the same slide deck with a new date on it. It starts with a licence audit, it gives people homework between sessions, and it ends with an actual usage number (not a sentence that says engagement is improving, an actual number).
Built for the second wave, not the first
Most Copilot training gets written for the first wave: the week after licences go out, when everyone is at least curious. This copilot adoption workshop is built for a different room. The one where the launch already happened, the novelty already wore off, and someone in finance is now asking why 500 licences look like 150 people who ever opened the app.
(If that sentence made you wince a little, you are the audience for this page.)
Gartner surveyed 187 IT leaders in 2025 and found 40% of organisations were piloting Copilot, but only 5% of the ones that finished a pilot actually scaled it. That gap, between a pilot that looked fine and a rollout that never became a habit, is where most Copilot budgets quietly go to die.
What the Second Wave actually is
A 4-week, 4-session copilot adoption workshop (2 hours each), for teams whose first Copilot rollout stalled, up to 20 people, from $8,440 / €7,280. If you want the full diagnosis of why rollouts go quiet in the first place, that lives on its own page: why Copilot rollouts stall. This page is the fix, not the post-mortem.
Week by week: audit, 4 sessions, homework
Every copilot adoption training programme I run for a second wave starts before session one, with a licence audit. Who actually has a Copilot licence. Who has opened it in the last 28 days, which is Microsoft's own default definition of an active user. Where the real gap sits, as opposed to where everyone assumes it sits.
(In one recent audit, the department everyone had quietly blamed turned out to be the heaviest user in the building. The team nobody suspected was the actual gap. Guessing is not a strategy.)
01The audit, before week one
A short review of licence assignment against actual usage, so the 4 sessions are built around your real numbers, not a generic curriculum written for nobody in particular.
024 working sessions, 2 hours each
Every session runs on your team's own files and real recurring tasks, not a fictional demo scenario. That is the difference between a session people remember and one they sit through.
03Homework in between
Each session ends with 2 or 3 specific things to try before the next one. What people actually did (or did not) becomes the opening 5 minutes of the next session, which is where the honest conversation happens.
What changes in 4 weeks
I have no commercial interest in Microsoft. I get paid the same whether your organisation ends up genuinely using Copilot or decides it is not worth the licence fee for part of the team. I just want you to know which one is true before the next renewal.
What usually changes over 4 weeks is not enthusiasm, that was already there after the first launch. What changes is habit: whether Copilot becomes something people reach for on a task they already do every week. That shift is the real copilot rollout training outcome, not a slide of feature names.
01From a feature list to a repeating task
We do not tour features. We build the habit around 2 or 3 tasks each participant already does every week, because a habit only forms on something that repeats.
A usage number at the end (a measurement, not a guarantee)
I will not promise you a specific adoption percentage. Anyone who does is guessing, and it is your organisation's culture, permissions and manager habits that decide the ceiling, not 4 sessions with me. What I will do is measure it properly: Microsoft's own default adoption metric is one use in 28 days, and that is the number we track before, during and after the programme.
A measurement tells you where you actually stand. A guarantee is a sales line. This page only offers the first one. If you want to see how that number then connects to actual business impact, that is a separate conversation, covered on the Copilot ROI measurement page.
Price and how to book
Last updated September 2026. The Second Wave runs from $8,440 / €7,280, up to $12,660 / €10,920 depending on customisation and group size, for the 4 sessions, live online, up to 20 people, 2 hours per session across 4 weeks, including the licence audit up front. Sessions are scheduled for Europe and US East afternoons, 15:00 to 19:00 Israel time. Leave your details below and I will call you back to talk through your current usage numbers before we set a date.
Questions I get about this copilot adoption workshop
Why does Copilot adoption stall after rollout?
There is a whole page built to answer that in full, so I will keep it short here: the first wave usually taught features instead of habits, and nobody came back a few weeks later to check what people actually kept using. See why Copilot rollouts stall for the complete picture.
How do you measure Copilot adoption success?
By tracking active use against Microsoft's own default metric, one use in 28 days, before and after the programme, at the team level rather than as an organisation-wide average that hides which groups are actually using it.
What is the Second Wave programme?
A 4-week, 4-session copilot adoption training programme (2 hours each) for teams whose first Copilot rollout stalled, up to 20 people, from $8,440 / €7,280, starting with a licence audit.
How long does it run?
4 weeks, one 2-hour session per week, plus the licence audit that happens before session 1.
What happens before the first session?
A licence audit: who has a Copilot licence, who has actually opened it recently, and where the real gap sits. The 4 sessions get built around that, not around a generic curriculum.
What should we expect to measure by the end?
A usage number for the group, tracked against Microsoft's one-use-in-28-days benchmark. It is a measurement of where you landed, not a guarantee of where you will land.
Tell me what your usage numbers actually look like.
Leave your details and I will call you back. A first call takes 30 to 45 minutes, and by the end you will know whether the Second Wave is the right next step or whether the issue sits somewhere else entirely. No deck, no obligation.