The full catalogue
Four tracks, or something entirely your own. Tap any track below to see what's inside it. Start wherever the gap actually is. Most people are already working in the core apps day to day, and Foundations strengthens that before Mastery builds further on top. Teams changes how a whole organisation communicates once it's used properly, and Copilot, the technology of the moment, sits across everything you already have.
Copilot sits across everything you use, and amplifies whatever practice is already there, good habits and bad ones alike.
- 01What it can and cannot doAn honest baseline, so nobody is disappointed or oversold.
- 02Getting usable output first timeAsking well, and recognising when the answer is wrong.
- 03Handing off the repetitive workAgents for the tasks nobody should still be doing manually.
- 04Working alongside the teamCowork for longer tasks, with human judgement kept in the loop.
- 05Copilot where work already happensInside the apps people use daily, not as another tab.
Four clusters, thirteen modules. Builds on either entry point, and where most of the depth sits.
- 01Past the basics, into real gainsThe features that save hours rather than minutes.
- 02Work that coordinates itselfPlanning and handovers that survive people being busy.
- 03Knowing where things liveFiles, permissions and data people can actually find.
- 04Making it hold at scaleGovernance and practice across the whole organisation.
An entry point. Start here where baseline confidence varies across the organisation.
- 01Documents that hold their shapeFormatting that survives editing, and templates worth reusing.
- 02Numbers you can trustStructure and formulas that reduce silent, expensive errors.
- 03Slides built in half the timeLess fiddling with alignment, more attention on the message.
- 04An inbox that stops running youSearch, rules and calendar habits that give the day back.
- 05Notes you can find againOne reliable place for the things people currently lose.
An entry point. The right one when collaboration is the immediate pain.
- 01Confident in the first weekOriented quickly, so early frustration does not set the tone.
- 02Channels, not another inboxThe structural decisions that prevent chaos six months in.
- 03Meetings worth attendingShorter, better prepared, with decisions that actually get recorded.
- 04One version of the fileCo-authoring instead of emailing attachments back and forth.
- 05Agreed ways of workingTeam norms that outlast the rollout and the enthusiasm.
Or, build your own
Not every organisation fits four fixed tracks cleanly. Modules combine freely, and delivery reshapes around what is actually happening on the ground.
- 01PaceCompressed into a single intensive week, or spread across a term.
- 02CombinationAny module from any track, drawn into one bespoke programme.
- 03AudienceWhole-organisation rollout, a single department, or a handful of champions.
- 04FormatLive workshops, embedded pairing, or asynchronous material.
Pick a starting point, not a package
Copilot is usually the reason people get in touch, it's the hot topic, and where most organisations are prioritising investment right now. What the engagement actually needs first, though, is often Teams Core or Foundations, depending on what's hurting, so that investment pays off instead of amplifying problems that are already there.
Pricing is scoped per engagement rather than fixed per module, since a five-person team and a two-hundred-person rollout need genuinely different amounts of time. Book a call and I'll give you a straight answer on scope and cost before anything is agreed.
Not sure which track fits?
Send over what's not working and I'll tell you honestly where to start, including if that's with someone other than me.