CIO, CTO and CDO
Owns the AI platform, security and the data the Cockpit needs.
1Open with
“Your Copilot rollout is done. How many licensed users are active every week?”
Recommended package
Enterprise Activation, or Foundation plus the Cockpit
2They care about
- Adoption of the platform they have rolled out
- Security, approved content and data governance
- No new platforms to support
- Clear technical ownership after handover
3The story
- Think about
- Technical rollout does not create usage. Without role-specific learning and measurement, adoption stays flat and renewals get harder to justify.
- Position it
- Products built inside your Microsoft estate: the Engagement Hub on SharePoint, the Learning Agent in Copilot Studio, the Cockpit in Power BI, with documented ownership and runbooks.
- How we prove it
- Adoption telemetry you already have, combined with learning data, in an agreed metric dictionary.
4Proof to use
- Built and proven on Microsoft Copilot
- Hub and Agent in production at the life sciences reference
- At an energy utility, one front door and KPI framework now being extended to the client's other AI programs
5Ask them
- Which usage telemetry can we access, and who owns it?
- What are your security review and release processes?
- Which AI platforms are approved besides Copilot?
6Likely objections
- “We use Gemini or Claude, not Copilot.”
- The framework and content carry over. Integrations have to be adapted and tested for your platform, so we assess that with you before committing scope.
- “Who supports the products after you leave?”
- Ownership, runbooks and support are agreed upfront. Ongoing support is a separately scoped option.
Avoid:Claiming a ready Google or Anthropic agent. Promising real-time data in the agent.
The internal portal is hidden in client view. Switch to internal view in the top bar.