Skip to content
Multiple departments Rollout with a date Role-specific training

Custom Copilot projects in a format that fits.

For initiatives that outgrow every standard format — in scope, duration, or number of people. Put together from workshops, coaching, and ongoing support, and tailored to your rollout.

Daniel Rohregger: Dual Microsoft MVP (Copilot & Copilot Studio), Most Active Speaker 2024 and 2025.

Who it's for

Signs this is the right fit

Four people standing side by side in a modern event space with large windows
Four people involved in the Copilot rollout at GBG Gruppe Mannheim.
Multiple departments at once
Not one team but several, each with different work to do — a single format can't cover that.
A rollout with a fixed date
Something has to be live by a set date, with several waves of people to bring along before then.
Role-specific training
Sales, engineering, HR — every role uses Copilot differently, and one generic training doesn't really work for any of them.
Longer-term support
Not a single session or a package, but one dedicated point of contact for several weeks while the rollout is underway.
A mix of formats
Workshops, 1:1 coaching, and ongoing support belong together in one project, not in separate bookings.

If even one of these applies, that's reason enough to talk — you don't need all five.

One example: supporting GBG Gruppe Mannheim as it prepared and rolled out Microsoft Copilot.

The process

A Copilot rollout in four phases, each with a clear outcome

Custom projects follow the same checkpoint pattern as any coaching, just over a longer stretch and with more people involved. More on the underlying pattern: Copilot coaching overview.

  1. Clarify

    A kickoff with your team on scope and boundaries — what's in, what's out. The timeline and the price are built on that.

    The kickoff settles on: three departments, one date for wave 1, one open governance question.

  2. Plan

    A project plan with roles, responsibilities, and milestones. The price is locked in by the end of this phase, not at some point later.

    Milestone 1 is the governance workshop with IT, milestone 2 is the first pilot group.

  3. Deliver

    Workshops, coaching, and support follow the plan. Regular status calls keep track of what's next.

    The pilot group works with support for four weeks while the material for wave 2 comes together.

  4. Handover

    A final training for your team, documentation for the entire project, and a checklist for running things on your own from here.

    Your champion team takes over support for waves 2 and 3, working from the documentation they received.

Pricing

What determines the price

There's no standard price, because no two projects are alike. What drives it: the scope of the work, the number of people involved, and how long the support runs. A six-week rollout across three departments is priced differently from role-specific training for a single department.

Intro call

No obligation

free 20 min

Twenty minutes to figure out which format fits your task — and whether any of them do at all.

  • Talk through your situation and what you're planning next
  • An honest read on which format fits
  • A straight answer if none of them do

You're not sure yet whether a single session, a package, or a workshop is the right call.

Custom project

By scope

on request varies by project

Scope, duration, and number of people involved determine the price

For when scope, duration, or the number of people involved rule out a standard format — assembled from the other formats.

  • Scope and boundaries clarified together before any proposal
  • A mix of workshop, coaching, and ongoing support
  • One fixed point of contact for the whole duration
  • A documented handover to your team

Multiple departments, a rollout, or a fixed timeline depend on it.

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

All formats side by side, plus the questions people usually ask: Pricing and packages.

Frequently asked

Questions about custom Copilot projects

How do we roll out Copilot across the company?

In four phases, each with a clear outcome: clarify scope and boundaries, plan with roles and milestones, deliver through workshops, coaching, and support, and hand over with training, documentation, and a checklist. The price is locked in at the end of the planning phase, before delivery starts.

When does a custom project make more sense than a standard format?

When scope, duration, or the number of people involved rule out every standard format, for example with several departments, a rollout with a fixed date, or role-specific training. If even one of these applies, that's reason enough to talk.

Who supports a Copilot project for its whole duration?

One fixed point of contact stays with the project for its whole duration, with regular status calls along the plan. At the end, the project is handed over to your team with documentation and a checklist for running things on your own.

Which formats does a custom project consist of?

A mix of workshops, coaching, and ongoing support, put together from the other formats and tailored to your rollout. Before any proposal, we clarify scope and boundaries together.

Tell us about your project

Tell us what it's about: how many departments, whether there's a fixed date, which roles are involved. We'll get back to you within two business days with a first assessment — and we'll tell you if a simpler format would do the job.