Five people, five different ways of using Copilot — and nobody knows what's working for anyone else. One shared checkpoint, one agent everyone uses, and a champion with a real toolkit instead of a vague extra duty. For teams and entire departments.
Daniel Rohregger: Dual Microsoft MVP (Copilot & Copilot Studio), Most Active Speaker 2024 and 2025.
The usual mistake with teams isn't that nobody starts using Copilot — it's that everyone starts on their own. You end up with five ways of writing a prompt, several agents doing the same job, and nobody knows what anyone else has built.
Here's what it looks like in practice: three people on a team each build an agent for the same report. None of them finds the others' agents, because everyone saves theirs to their own profile. And when the one person who really knows Copilot goes on vacation for two weeks, the whole team is stuck — nobody else can answer their questions.
There's often a trust gap, too: some people don't trust Copilot at all, others lean on it too much. Without shared ground rules, automation quickly leads to frustration instead of progress.
For whom
Where you start
Starting as a group is different from starting alone. You build Foundation — Copilot in the apps, custom instructions, a shared way of prompting — together as a team, so everyone works from the same base. Then you move on to agents, together.
What we do
The answer fits in one sentence, but it's hard to pull off on your own: one shared agent instead of five separate fixes, and one shared way of prompting instead of five different styles. That takes a structured path for the whole group — not a series of back-to-back 1:1 sessions.
You meet as a group and everyone brings their own question — the result is a clear overview and a shared way of prompting.
Where is it already working, and where is the potential?
The one task that everyone on the team actually does regularly becomes a shared agent that everyone uses.
Instead of three people each building the same thing.
One person becomes the go-to for Copilot — with a prompt library, documented agents, and a clear escalation path.
Not just a title — an actual set of tools.
Monthly or quarterly: what's working, what needs adjusting, which task to take on next.
The champion's escalation path leads to me, not into the void.
The champion role is at the heart of it. Without one, the same questions keep coming up and never stay answered — everyone finds their own answer, often the wrong one. That's why the role isn't just a title but an actual set of tools: a library of the prompts that really work for the team, a description of every agent the team uses, and a clear escalation path for when the champion doesn't know the answer either. That path leads to me, not into the void.
An example
An example that fits almost any team: status updates written to a shared template and rolled up into one team status — instead of one person sorting through everything by hand at the end of the week.
Here are this week's status updates from the team, each in the same format: done, in progress, blocked. Combine them into one team status — grouped by project, starting with what's done, then what's coming up this week, and finally a separate section for anyone who needs support. Name the person who reported each item.
For: teams, as a shared template
You agree on that template — done, in progress, blocked — together in the coaching. After that, everyone just fills in their three lines, and the agent does the rest.
Formats
What sets them apart is the goal, not the price. A single session answers a question for one person. The team package and the team workshop answer it for the whole group — just by different routes.
Coaching, consulting, and workshops on Microsoft 365 Copilot run online by default and, by arrangement, on site in Germany, Austria, and Switzerland.
| Format | Ideal for | How it runs | Outcome |
|---|---|---|---|
| 1:1 coaching | One person with a specific question. | 45 minutes on that one task. | A solution for one person — invisible to the team until someone stumbles on it. |
| Team package | 3 to 15 people who want to build a shared strategy. | Several sessions over a few weeks; the team keeps working on its own in between. | One team agent, a trained champion, shared prompting standards. |
| Team workshop | 5 to 15 people who want to get started together in a single day. | One day, working on your own tasks, not on sample exercises. | Agent built, champion chosen, standards set, next step planned. |
free 20 min
Twenty minutes to figure out which format fits your task — and whether any of them do at all.
You're not sure yet whether a single session, a package, or a workshop is the right call.
€225 net 45 min
One coaching session on your actual task. By the end, something works.
You have a specific task and want it handled this week.
on request 1 day, 5–15 people
Scope and team size determine the price
A full day with the whole team. You leave with an agent everyone actually uses, and one person who can keep helping internally.
You want to kick things off together in a single day instead of spreading it across weeks.
on request 6–10 hours over 4–6 weeks
Scope and team size determine the price
Several short sessions spread across a few weeks, so the team can keep working on its own in between.
You want room to experiment and adjust between sessions.
All formats side by side, plus the questions people usually ask: Pricing and packages. After a workshop or package, the champion can keep getting support — a monthly check-in you can add if you need it. For larger teams, just get in touch and we'll tailor the format to your size.
From the field
Daniel is one of our top trainers for Microsoft 365 Copilot. He knows what he's talking about, his expertise runs deep, and participants consistently give him positive feedback.
KAYENTA arranges Copilot training for companies — which is exactly what a team workshop aims for: knowledge that sticks with every participant, not just the ones who already knew their way around.
Frequently asked
The team workshop (1 day, 5–15 people) gets a team going in a single day, and the team package (6–10 hours over 4–6 weeks) spreads shorter sessions across several weeks. Which one fits depends on whether you want to kick off in one day or practice between sessions.
The team workshop starts the team together in one day, while the team package supports it over several weeks with shorter sessions, so the team can practice in between. Both answer the same question for the whole group, by different routes.
One agent built for a recurring team task, a named champion as the internal go-to contact, and shared prompting standards. A plan for the next step comes on top.
With a shared checkpoint, one team agent for the task everyone does regularly, and a champion with a real toolkit instead of a vague extra duty. After that, a regular check-in, monthly or quarterly, keeps track of where things stand.
Tell us in two sentences how big your team is and which task you want to automate together. We'll get back to you within two business days with our take on whether a workshop or a package fits, and an honest answer if neither does.