Skip to content

Copilot coaching: four paths, one starting point.

Every coaching format at a glance, plus the process every session follows. Start with whatever is holding you up right now — the details for your situation are on the page for it, not here.

Quick sort

Two questions, and you'll know where you fit

The three standard formats, depending on what it's about:

  • 1:1 Coaching – We take one task from your week and build, in the session, what makes it shorter.
  • IT and Admins – We build the governance before the rollout goes live, not as a fix afterward.
  • Teams and Groups – A shared checkpoint, one agent everyone uses, and a champion with a real tool.

What you need

Handwritten notes and sketches in an open notebook next to a laptop
AI-generated image
Between sessions, what's written down is what sticks.

Not sure?

The intro call tells you what fits

Twenty minutes, no strings attached. We look at your situation together and tell you which format fits — even if, right now, none of them does.

Which format fits?

Copilot coaching and training: formats at a glance

Daniel Rohregger and Sabrina Göttlinger presenting together to an audience, with a software screen behind them
A joint talk in front of a live audience.

The formats differ in length, group size, and goal — not in quality. What each one costs is on Pricing and packages.

Coaching, consulting, and workshops on Microsoft 365 Copilot run online by default and, by arrangement, on site in Germany, Austria, and Switzerland.

All formats with their scope and what each one is for. Prices are on the pricing page.
FormatScopeFits if
Intro call20 minYou're not sure yet whether a single session, a package, or a workshop is the right call.
Single session45 minYou have a specific task and want it handled this week.
Ten-session package10 sessions, booked as neededYou want to genuinely change how you work, and be able to keep building on it yourself afterward.
Team workshop1 day, 5–15 peopleYou want to kick things off together in a single day instead of spreading it across weeks.
Team package6–10 hours over 4–6 weeksYou want room to experiment and adjust between sessions.
Governance workshop1 day, IT teamSeveral people in IT need the same basis for their decisions.
Custom projectvaries by projectMultiple departments, a rollout, or a fixed timeline depend on it.

Single session or ten-session package

What sets them apart is the goal, not the price. If you want to move one specific topic, agent, or workflow forward right now, go with the single session. If you want to really change how you or your team work — with onboarding and several rounds that build on each other — go with the ten-session package.

Compared by goal, not by price or scope.
Single sessionTen-session package
GoalOne specific topic, one agent, one workflow — moved forward nowA bigger shift, done right from the start, toward the Copilot Mindset
CycleOne pass, tightly focused on a single thingSeveral rounds, each building on the last
Onboarding—Included
OutcomeA usable result that's up and running the next dayFourth phase: your Copilot Mindset

The cycle

Four phases, one cycle

Whether it's a single session or a ten-session package, we always follow the same pattern. After Doing, the next checkpoint begins — a single session is one pass through; in the package, several rounds build on each other.

To make the cycle easy to follow, one example runs through all of it: a project manager who spends every Monday pulling the status together by hand from five project channels.

  1. Checkpoint

    We look at your actual task, not a demo. I keep asking questions until the real sticking point is clear.

    “Every Monday I spend two hours pulling the status together from five project channels before I can even walk into the status meeting.”

  2. Route

    The checkpoint usually surfaces several possible paths. Together, we decide which one comes first.

    Three options are on the table: meeting summaries, an agent for the status report, custom instructions to tame the email flood. The status report saves the most time, and the data is already there.

  3. Doing

    We build it in the session. Not a sketch — far enough along that you can actually use it.

    By the end of the session, there's an agent that reads the five channels and hands you a draft status report every Monday.

  4. Copilot Mindset

    optional — only across several rounds

    After a few rounds, you stop asking whether Copilot could handle a new task — you just start with it.

    Next up is an agent for the sales reports — and you build it yourself in Agent Builder, because you know the pattern from the earlier rounds.

Where you start

Three stages, with Control running alongside

The cycle is the same for everyone. Where you start isn't: Foundation, Agents, and Workflows get progressively more complex, but they're not a sequence everyone has to go through. Control runs across all three — a separate track for IT and admins, not a fourth rung on the same ladder.

Stage 1

Foundation

For anyone who barely uses Copilot yet, or uses it without a system

  • Copilot in daily work: where it lives in the apps you already use
  • Custom instructions and memory, so Copilot knows your context
  • Prompting on a real task, not a canned exercise

Stage 2

Agents

For anyone who knows a single chat isn't enough

  • Agent Builder: an agent for a recurring task, built during a session
  • Copilot Studio for processes with several steps
  • The first governance questions: who can act on whose behalf?

Stage 3

Workflows

For anyone who wants processes to run end to end across systems

  • Data foundations and process understanding before anything runs automatically
  • Error handling: what happens when a source goes missing or changes
  • A process that runs across several systems without manual handoffs

Runs alongside

Control

For IT and admins — runs alongside every level, not a fourth stage

  • SharePoint oversharing and permissions, sorted out before agents roll out
  • Sensitivity labels: classifying and protecting what an agent can read
  • Blast radius: what a misconfigured agent or MCP server could reach

The most common question

No, you don't have to start at Foundation

Foundation is for anyone who has never worked with Copilot in a systematic way — not a front door everyone has to walk through. If your next problem calls for an agent, we build an agent in the first session. Where you start depends on the task at hand, not on a fixed curriculum.

One session

What happens in 45 minutes

0–10 Checkpoint: taking the task apart
10–15 Route: deciding what comes first
15–40 Doing: building it together
40–45 Handover: it's yours, not mine

A single session is one pass through the cycle, focused on one thing. A ten-session package strings several passes together, with onboarding at the start and the Copilot Mindset as the goal.

Request an intro call

Which path fits you?

Tell us in two sentences what you have in mind. We'll get back to you within two business days with our take on which format fits — and we'll tell you if none of them does.