Usage drops off
After the kick-off there are no regular impulses, and employees quickly fall back into their previous ways of working.
Copilot in 30 turns a non-committal trial into a structured evaluation. We guide your team from planning through the first productive use cases to the analysis – so that after 30 days you know whether and how you want to roll out Microsoft 365 Copilot further.
Download the offer as a PDFPDFCopilot in 30 is a guided 30-day evaluation of Microsoft 365 Copilot by Obungi: 25 test users use Copilot in their own day-to-day work, while Obungi structures the planning, KPIs, enablement and analysis. After 30 days you have a reliable basis for deciding whether and how to roll out Microsoft 365 Copilot more widely.
Trying out Microsoft 365 Copilot is easy. Finding out whether a rollout is worthwhile for your company is harder.
After the kick-off there are no regular impulses, and employees quickly fall back into their previous ways of working.
Without guidance, users test Copilot more or less at random instead of finding out where Copilot actually improves their daily work.
Without a baseline, KPIs and usage data, the perceived added value remains subjective.
Copilot in 30 turns the trial into a structured evaluation – with a clear result.
In 30 days your team goes through five clearly defined steps. Obungi supports the evaluation with planning, enablement and analysis.
Together we plan the trial, select the 25 test users and define KPIs against which success can be assessed.
Licences and the Teams channel are ready, communication starts and the users receive their first concrete scenarios.
Your employees use Copilot in their daily work and test concrete prompts and scenarios.
Usage, engagement and feedback are analysed. This shows you where Copilot actually creates added value.
Together we look at KPIs and feedback and derive the next steps from them – right through to a possible larger rollout.
The Core Package deliberately focuses on the decisive points of the evaluation. You book additional support where your team needs it.
Joint setup of licences, Copilot settings and Teams, plus a Data & Security Check covering permissions, sensitivity labels and, if required, Restricted Search.
60–90 minutes live with all 25 test users: first prompts, best practices and dos and don’ts.
1–2 hours to prepare the kick-off communication, Teams channel, templates and guides.
Regular Q&A sessions on use cases, prompts and concrete scenarios.
A joint look at progress and KPIs, with individually agreed measures.
Not just 30 days of Copilot experience, but a reliable basis for the next decision.
25 employees have tested Copilot in their own day-to-day work.
KPIs, usage and feedback show where Copilot can create added value.
You see which scenarios work for your employees.
Together we assess whether and how you then roll out Copilot more widely.
Obungi supports companies not only with the Copilot evaluation, but also with more advanced scenarios – from Microsoft Copilot Studio and Microsoft 365 integrations to building your own agents.
When initial Copilot experience gives rise to automation or agent scenarios, your journey builds on it seamlessly.
Copilot in 30 is a guided 30-day evaluation of Microsoft 365 Copilot by Obungi: 25 test users use Copilot in their own day-to-day work, while Obungi structures the planning, KPIs, enablement and analysis. After 30 days you have a reliable basis for deciding whether and how to roll out Microsoft 365 Copilot more widely.
Without structure, usage quickly drops off after the kick-off, users test Copilot more or less at random rather than in relevant use cases, and without a baseline, KPIs and usage data the added value remains subjective. Copilot in 30 turns this into a structured evaluation with a clear result.
In five steps: week 0 “Get ready” (plan the trial, select 25 test users, define KPIs), week 1 “Start strong” (licences and Teams channel ready, communication starts, first scenarios), weeks 1–3 “Prove value” (Copilot in day-to-day work with concrete prompts and scenarios), week 3 “Track progress” (analyse usage, engagement and feedback) and week 4 “Make it last” (assess KPIs and feedback, derive next steps through to a possible rollout).
25 test users. They are selected together with Obungi in week 0.
Planning & Onboarding Workshop, Joint definition of KPIs, Closing Call, KPI and feedback review, Recommendations for the next steps. The Core Package deliberately focuses on the decisive points of the evaluation.
Setup & Security: Joint setup of licences, Copilot settings and Teams, plus a Data & Security Check covering permissions, sensitivity labels and, if required, Restricted Search. Kick-off Session: 60–90 minutes live with all 25 test users: first prompts, best practices and dos and don’ts. Communication Workshop: 1–2 hours to prepare the kick-off communication, Teams channel, templates and guides. Weekly Office Hours: Regular Q&A sessions on use cases, prompts and concrete scenarios. Project Lead Check-in: A joint look at progress and KPIs, with individually agreed measures.
Real usage experience: 25 employees have tested Copilot in their own day-to-day work. Measurable insights: KPIs, usage and feedback show where Copilot can create added value. Relevant use cases: You see which scenarios work for your employees. Clarity for the next step: Together we assess whether and how you then roll out Copilot more widely.
Obungi also supports more advanced scenarios – from Microsoft Copilot Studio and Microsoft 365 integrations to building your own agents. When initial Copilot experience gives rise to automation or agent scenarios, your journey builds on it seamlessly.
Together we plan the trial, define the relevant KPIs and lay the foundation for making a well-founded decision after 30 days.
Would you first like to clarify whether Copilot in 30 is a good fit for your organisation?
Talk to our Microsoft expertsMicrosoft 365 Copilot is a trademark of Microsoft Corporation.
Last updated: