[ 01 ]
Licences for everyone at once
Rolling out to all staff at once buys many licences that nobody has a use for. Start with the people who have the tasks.
[ COPILOT ROLLOUT ]
The licences are the easy part. Habit is the work.
You bought Copilot licences and a few months later hardly anyone uses them. We check readiness, run a pilot group and give each team three daily tasks that work, then measure use at day 30.
Pilot group firstUsage measured after 30 daysTenant stays with worxspace
[ 01 — WHERE IT GOES WRONG ]
Why Copilot rollouts fade.
The licence is bought in a day. The habit takes weeks, and most rollouts stop at the launch email.
- [ 02 ]
Oversharing surfaces
Copilot shows users everything they can already open. Files that were technically accessible but never noticed suddenly appear in answers. - [ 03 ]
No task, no habit
People try it twice, get a mediocre result and go back to old routines. Without three concrete tasks per team, use fades. - [ 04 ]
Nobody measures
Without usage data at day 30, licences sit unused and nobody notices until renewal.
[ 02 — WHAT YOU GET ]
Adoption, not a launch email.
niivo covers adoption and agents. Tenant configuration, permissions and security remain with worxspace or your IT team.
- [ 01 ]
Readiness check
Are your files, permissions and sensitivity labels in shape? Copilot shows users everything they can already open, so we check before it does. - [ 02 ]
Pilot group
A small mixed group of 15 to 30 people, chosen for their tasks rather than their enthusiasm. - [ 03 ]
Three tasks per team
We pick three daily tasks per team, show them once in the team's own documents and give a one-page guide. - [ 04 ]
Usage measurement
Usage data and a short survey at day 30 show who uses what and where time is saved. Licences without use are flagged. - [ 05 ]
Path to agents
Where a task repeats often enough, we scope an agent in Copilot Studio or a custom build instead.
[ 03 — HOW WE DE-RISK IT ]
How niivo takes the risk out.
We prove the value on a small group, then extend.
- [ 01 ]
Permissions checked first
Findings on oversharing go to tenant operations with a written handover, before Copilot can surface anything. - [ 02 ]
A small group, not a big bang
15 to 30 people, chosen for their tasks. You buy licences for the people who will use them, wave by wave. - [ 03 ]
A number at day 30
Usage, survey and time samples show whether it works. You decide who gets a licence next, and unused licences are moved. - [ 04 ]
Honest about fit
Not every role gains from Copilot, and we say so. Where a task repeats often enough, an agent is the better answer.
[ 04 — PROCESS ]
Small group, then everyone.
Rollout in waves, each with a number to check.
- 01
Readiness
Review of permissions, labels and content hygiene in the areas Copilot will read. Findings go to tenant operations.1 to 2 weeks - 02
Pilot
Training and weekly check-ins with the pilot group on their three tasks each.4 weeks - 03
Measure
Usage, survey and time samples against the baseline. You decide who gets a licence next.Day 30 - 04
Roll out
Team-by-team training in waves, with champions in each team and a monthly usage report.Per wave
[ 05 — USE CASES ]
Tasks that work early.
Typical tasks per role. None of these describe a specific client.
Meetings
- Today
- Notes are written after the call, if at all.
- With the workflow
- Copilot in Teams drafts a summary and action list. The organiser corrects it and sends it.
Mail and documents
- Today
- Long threads and proposals take an hour to read and answer.
- With the workflow
- Copilot summarises the thread and drafts a reply from the attached files. The sender edits it.
Excel and reporting
- Today
- Recurring analysis is rebuilt each month from scratch.
- With the workflow
- Copilot proposes formulas and charts on the existing table. The analyst checks the logic.
[ 06 — SCOPE & PRICE ]
A pilot group, then a decision.
Compare the pilot with the licence cost of a rollout that stalls: every seat that nobody opens is paid for, month after month. The day-30 report shows which seats earn their price before you buy more.
Copilot rollout pilot · 6 weeks
from CHF 12,000fixed scope · excl. VAT
Copilot licences are not included. Extensions: CHF 2,200 per day.
- Readiness check with findings for tenant operations
- Pilot group and three tasks per team
- Training and weekly check-ins
- Usage report at day 30
[ 07 — QUESTIONS ]
What people ask about Copilot.
Is Copilot safe with our data?
Copilot works within the Microsoft 365 permissions users already have, in your tenant. That is why we check permissions first: oversharing becomes visible fast.
We tried Copilot and it did not stick.
That is the usual pattern when there is no task behind the licence. We give each team three daily tasks, show them once in their own documents and measure at day 30.
Do we need to buy licences before the audit?
No. Start with the audit or a small pilot group, and buy for the people who will use it.
Who fixes tenant issues we find?
Tenant operations stay with worxspace or your IT team. We deliver the findings with a written handover.
What if only a few people use it after 30 days?
Then we look at why, adjust the use cases or move licences. Not every role gains from Copilot, and we say so.
Do you sell licences?
No. Licensing is handled with your Microsoft partner or worxspace. niivo does adoption and agents.
Turn licences into a habit.
Start with readiness and a pilot group. Decide on the rest from the numbers.