Zum Inhalt springen

Four paths, one starting point.

Every coaching format at a glance, plus the process every coaching session follows. Start with whatever's holding you up right now — the detail for your situation lives on that page, not this one.

Quick sort

Two questions, then you'll know where you belong

Drei Wege, je nachdem, worum es geht:

  • Einzelcoaching — Wir nehmen eine Aufgabe aus deiner Woche und bauen im Coaching, was sie kürzer macht.
  • IT und Admins — Wir bauen die Governance, bevor der Go-Live läuft, nicht als Nachbesserung danach.
  • Teams und Gruppen — Gemeinsamer Checkpoint, ein Agent, den alle nutzen, und eine Champion mit echtem Werkzeug.

What you need

Handwritten notes and sketches in an open notebook next to a laptop
Bild KI-generiert
Between sessions, what's written down is what remains.

Not sure?

The intro call sorts out 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 do.

Which format fits?

Formats at a glance

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

The formats differ in length, group size, and intent — not in quality. What they cost is below, and in full detail on Pricing and packages.

All formats with their scope and the intent behind each one. 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 packageZehn-Stunden-PaketYou want to genuinely change how you work, and be able to keep building on it yourself afterward.
Team workshop1 Tag, 5–15 PersonenYou want to kick things off together in a single day instead of spreading it across weeks.
Team package6–10 Stunden über 4–6 WochenYou want room to experiment and adjust between sessions.
Governance workshop1 Tag, IT-TeamSeveral people in IT need the same basis for their decisions.
Custom projectnach UmfangMultiple departments, a rollout, or a fixed timeline depend on it.

Single session or ten-session package

The difference is in the intent, not the price. If you want to push one specific topic, agent, or automation forward right now, take the single session. If you want to properly overhaul how you or your team work — with onboarding, with several rounds building on each other — take the ten-session package.

Compared by intent, not by price or scope.
Single sessionTen-session package
IntentOne specific topic, one agent, one automation — pushed forward nowDoing it properly from the start: a bigger shift, working toward the Copilot Mindset
CycleOne pass, tightly focused on a single thingSeveral rounds, each building on the last
OnboardingIncluded
OutcomeA usable result that's 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 work the same pattern. After Doing, the next checkpoint begins — for a single session that's one pass through; for the package, several rounds build on each other.

To make the cycle easy to follow, it carries the same example throughout: a project manager who spends every Monday manually pulling the status together from five project channels.

  1. Checkpoint

    We look at your actual task, not a demo example. I keep asking questions until the real obstacle becomes visible.

    “I need two hours every Monday just to pull the status together from five project channels before I can even get 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 against the email flood. The status report saves the most time, and the data's already there.

  3. Doing

    We build it in the session. Not a sketch — built far enough 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 — you build it yourself in Agent Builder, because you already know the pattern from the rounds before.

Where you start

Three stages, plus Control layered on top

The cycle is the same for everyone. Where you start isn't: Foundation, Agents, and Automations are stages of increasing complexity, but not a sequence everyone has to pass through. Control runs across all three stages — its own track for IT and admins, not a fourth rung on the same ladder.

Stufe 1

Foundation

For anyone who barely uses Copilot yet, or uses it without much 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 example

Stufe 2

Agents

For anyone who knows a single chat isn't enough

  • Agent Builder: one agent for a recurring task, built in a coaching session
  • Copilot Studio for multi-step processes with several stages
  • The first governance questions: who's allowed to act on whose behalf?

Stufe 3

Automations

For anyone making processes run end-to-end across system boundaries

  • Data foundations and process understanding before anything runs automatically
  • Error handling: what happens when a source is missing or changes
  • A process that runs across multiple systems with no manual handoff

Quer dazu

Control

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

  • SharePoint oversharing and permissions, before agents get rolled out
  • Sensitivity labels: classifying and protecting what an agent is allowed to 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 there for anyone who's never worked with Copilot in a systematic way — not the front door everyone has to walk through. If your next problem needs an agent, we build an agent in the first session. Where you start follows the task at hand, not a fixed curriculum.

One session

What happens in 45 minutes

0–10 Checkpoint: breaking 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, tightly focused on one thing. A ten-session package strings several of these passes together, with onboarding at the start and the Copilot Mindset as the direction it's heading.

Request an intro call

Which line fits you?

Write two sentences about what it's about. We'll reply within two business days with a read on which format fits — and we'll say so if none of them do.

Auch auf Deutsch verfügbar