Five people, five different ways of using Copilot — and nobody knows what works for anyone else. One shared checkpoint, one agent everyone uses, and a champion with a real toolkit instead of a vague add-on task. For teams and whole departments.
The typical mistake with teams isn't that nobody starts with Copilot — it's that everyone starts on their own. You end up with five ways of writing a prompt, several agents for the same task, and nobody knows about anyone else's solution.
In practice it looks like this: three people on a team independently build an agent for the same report. None of them finds the others' agent — everyone just saves it to their own profile. And when the one person who really knows Copilot is on vacation for two weeks, the whole team is stuck, because there's nobody else who can answer the question.
On top of that, there's often a trust gap: some don't trust Copilot at all, others overuse it — without a shared boundary, automation quickly turns into frustration instead of progress.
For whom
Where you start
Getting started as a group is different from getting started alone: Foundation — Copilot in the apps, custom instructions, a shared language for prompting — you build together as a whole team, so everyone starts from the same base. Only after that do you move on together to agents.
What we do
The answer fits in one sentence, and it's still hard to pull off alone: one shared agent instead of five island solutions, and one shared language for prompting instead of five different styles. That takes a structured path for the whole group — not a row of 1:1 coachings lined up back to back.
You come together as a group and everyone brings their own question — out of that comes a sorted overview and a shared language for prompting.
Where's it already working today, and where's the potential?
The one task that genuinely everyone on the team does regularly becomes a shared agent that everyone uses.
Instead of three people independently building the same thing.
One person becomes the Copilot go-to contact — with a prompt collection, documented agents, and a named escalation path.
Not an extra title — an actual set of tools.
Monthly or quarterly: what's working, where you need to adjust, which new task fits next.
The champion's escalation path leads to me, not into a void.
The champion role is the heart of it. Without one, the same question keeps coming up in the team without ever staying answered — everyone finds their own answer, often the wrong one. That's why the role isn't an extra title, but an actual set of tools: a collection of the prompts that genuinely work for the team, a description of every agent the team uses, and a named escalation path for when the champion doesn't know the answer either. That path leads to me, not into a void.
An example
One example that fits almost any team: status updates collected using a shared template and condensed into a team status — instead of one person sorting everything by hand at the end of the week.
Here are the team's status updates for this week, each following the same pattern: done, in progress, blocked. Combine them into one shared team status — grouped by project, starting with what's done, then what's coming up this week, and finally a separate section for where someone needs support. Name the person who reported each item.
Rolle: Team, shared template
You settle on that template — done, in progress, blocked — together in coaching. After that, everyone just fills in their own three lines, and the agent takes care of the rest.
Formats
The difference is in the intent, not the price. The single session solves a question for one person. Team package and team workshop solve the same question for the whole group — by different routes.
| 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 happens to find 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 kick off together in a single day. | One day, working directly on your own tasks, not on an example. | Agent built, champion named, standards set, a plan for the next step. |
kostenlos 20 Min
Zwanzig Minuten, in denen wir klären, welches Format zu deiner Aufgabe passt — und ob eines davon überhaupt passt.
Du weißt noch nicht, ob Einzelstunde, Paket oder Workshop das Richtige ist.
225 € netto 45 Min
Eine Coaching-Stunde an deiner echten Aufgabe. Danach läuft etwas.
Du hast eine konkrete Aufgabe und willst sie diese Woche vom Tisch haben.
auf Anfrage 1 Tag, 5–15 Personen
Umfang und Teamgröße bestimmen den Preis
Ein Tag mit dem ganzen Team. Am Ende steht ein Agent, den alle nutzen, und eine Person, die intern weiterhilft.
Ihr wollt an einem Tag gemeinsam starten statt über Wochen verteilt.
auf Anfrage 6–10 Stunden über 4–6 Wochen
Umfang und Teamgröße bestimmen den Preis
Mehrere kurze Termine über einige Wochen, damit das Team zwischen den Terminen selbst weiterarbeiten kann.
Ihr wollt zwischen den Terminen ausprobieren und nachjustieren.
All formats compared, with the questions that come up regularly: Pricing and packages. After a workshop or package, the champion's support can continue on an ongoing basis — a monthly check-in you can add if you need it. Bigger teams should just write to us — we'll tailor the format to your size.
From the field
Daniel is one of our top trainers for Microsoft 365 Copilot training. He knows what he's talking about, has deep expertise, and consistently gets positive feedback from every participant.
KAYENTA places Copilot training with companies — exactly the experience a team workshop aims for: knowledge that lands with every participant, not just the ones who already knew their way around beforehand.
Write two sentences on how big your team is and which task you want to automate together. We'll get back to you within two business days — with an assessment of whether a workshop or package fits, and an honest answer if neither does.