Readiness
Review identity, sharing, permissions, data-governance dependencies, licensing, admin controls, and pilot prerequisites.
Product · Adopt
Part of Microsoft 365 Copilot
Put Microsoft 365 Copilot into real work in four weeks.
Copilot Kickstart is a focused deployment and adoption program for organizations that are ready to evaluate Microsoft 365 Copilot with real users and real workflows. We prepare the tenant, define role-based scenarios, configure governance, run a controlled pilot, train users, measure adoption, and leave leadership with a clear decision about what should scale next.
- 4-week program
- Focused pilot cohort
- $15,000 fixed fee
- Microsoft licensing separate
Activation is not adoption
A license does not create a new way of working.
The failure mode is simple: licenses are assigned, users attend a generic training session, a handful of enthusiasts experiment, and leadership cannot tell whether Copilot changed anything that matters.
Kickstart works backward from the jobs people actually do.
What is included
Seven workstreams across four weeks.
Scenario design
Choose a small set of high-value role-based scenarios for the pilot group—not a catalog of generic prompts.
Governance
Configure the policies and administrative controls available in your licensed Microsoft environment, document exceptions, and establish the operating rules for the pilot.
Pilot
Enable a controlled user group, establish baseline measures, and run the scenarios in real work.
Adoption
Train around the selected roles and workflows, provide practical usage guidance, and create a support path for pilot users.
Measurement
Review activation, usage, scenario adoption, user feedback, and the business measure chosen for each priority scenario.
Expansion decision
Deliver a written recommendation: scale, tune, pause, fix a dependency first, or move selected workflows into agent development.
What you leave with
Artifacts your team keeps.
- Readiness and dependency findings
- Approved pilot scope
- Role-based scenario library
- Governance and admin configuration record
- Training and adoption assets
- Pilot measurement baseline and results
- Expansion recommendation
- Prioritized next use cases
Microsoft 365 Copilot licensing and any consumption are separate from the Centered Networks fee and are sized during scope. Microsoft programs may help fund or accelerate eligible engagements. Availability, customer eligibility, workload eligibility, and investment amount depend on Microsoft’s current program rules and are confirmed before scope. Microsoft funding is not guaranteed.
Who it is for.
Start here when
- Leadership has already decided to evaluate Microsoft 365 Copilot
- The organization wants a governed pilot before broad rollout
- There are identifiable teams or roles with repeatable knowledge-work scenarios
- Microsoft 365 is already the core work platform
Start somewhere else when
- Leadership has not decided whether Copilot is the right next move, significant security, data, or governance questions remain unresolved, or the organization is comparing Copilot with agents, automation, and data modernization. Start with the 90-Day AI Roadmap.
- The target workflow needs a persistent agent, business process, orchestration, or system action beyond the personal Copilot experience. Move to Agent Launchpad.
After Kickstart
Adoption should become an operating discipline.
Scale Copilot
CompleteCare Intelligence
Expand role-based scenarios and adoption through ongoing Copilot and AI program operations.
See CompleteCare Intelligence →Build an agent
Agent Launchpad
Move a qualified workflow into a governed production agent with ownership, telemetry, and a runbook.
See Agent Launchpad →Fix the foundation
M365 InstantOn or CompleteCare Govern
Use these when the pilot exposes Microsoft 365 or data-governance dependencies that should be resolved before scale.
See M365 InstantOn →Transform more broadly
Frontier Transformation
Use this when multiple Copilot and agent workloads need to be scaled together with governance and measurement.
See Frontier Transformation →Questions
Frequently asked questions about Copilot Kickstart.
Do we need Microsoft 365 Copilot licenses before kickoff?
We need an agreed licensing path before the pilot is enabled. We can scope the program while licensing is being finalized.
Is this just training?
No. Training is one workstream. The engagement also covers readiness, governance, scenario design, pilot execution, measurement, and the expansion decision.
Do you guarantee adoption?
No. Adoption depends on role fit, leadership, workflow design, user behavior, change management, and the product itself. We establish the measures, run the program, and make the expansion decision based on evidence.
Can this include Copilot Cowork?
Where Cowork is licensed and appropriate, we can include it as a scoped scenario. Cowork uses usage-based Copilot Credits and requires additional cost controls; it should not be enabled casually.
What if permissions or data governance are not ready?
We identify the dependency and recommend remediation before broad deployment. That may mean M365 InstantOn, CompleteCare Govern, or focused project work.
Give Copilot a job before you give it more licenses.
Tell us about your tenant, your Copilot licensing status, and the pilot group you have in mind. We confirm scope on a short call and get the engagement on the calendar.
Not ready to deploy yet? Get Your 90-Day AI Roadmap →
Thanks, we’ve got it.
A senior member of our team will reach out within one business day to confirm scope and get the engagement scheduled.