Service · Copilot Kickstart
A productized four-week Copilot deployment for nonprofits, foundations, and rural hospitals. AI Readiness Assessment, governance setup, a first-wave pilot for 10–25 users, role-based adoption training, and a written handoff. Fixed scope, fixed price, predictable outcome.
Not sure if you are ready to deploy? Start with a Discovery Sprint → The roadmap will tell you.
Why most Copilot deployments fail
The problem is not the platform. It is that Copilot requires three pieces of work that almost nobody does in advance.
01 : Skipped
Sensitivity labels, restricted SharePoint settings, semantic-index management, identity controls. Without these, Copilot inherits every data-governance gap your tenant already has, and surfaces poorly-governed data to users who could not find it before.
02 : Skipped
A pilot group of 10–25 users, with a documented prompt library tied to mission workflows, role-based training, and an adoption measurement framework. Without this, Copilot sits inside Word and Outlook and people use it for nothing in particular.
03 : Skipped
A written document that tells leadership what to do next: continue alone, expand the pilot, or graduate to an ongoing managed AI program. Without this, the kickoff becomes a one-time event with no second move.
Copilot Kickstart does all three. Four weeks. $15,000. Pilot live by day 21. Handoff document in your hands by day 28.
What you get
A fixed-scope, fixed-price engagement that produces seven concrete deliverables across four weeks.
A documented scorecard of your tenant's Copilot prerequisites: Foundations completeness, data-governance posture, license inventory, shadow-AI exposure. The same assessment included in the Discovery Sprint, run inside the Kickstart for organizations that already know they want Copilot deployed.
Sensitivity-label integration, restricted SharePoint configuration, semantic-index management, identity governance for Copilot. The work that prevents Copilot from becoming a shadow-data risk.
10–25 users onboarded with role-based provisioning. A documented prompt library tailored to your mission workflows: fundraising, program intake, grant operations, clinical scheduling, board reporting. Not a generic Microsoft demo library.
Two role-based training sessions for the pilot group: one for power users, one for everyone. Recorded for replay. A short prompt-library reference card every pilot user keeps.
Baseline metrics captured at week 1, re-measured at week 4. Documented KPIs leadership can hold the program accountable to.
A 60-minute session at week 4 with the pilot group: what worked, what did not, what the next-wave expansion should change.
Written summary of what was deployed, what governance is now in place, what the pilot results show, and a clear recommendation for the next 90 days, including whether you are ready to continue alone or whether ongoing managed AI is the right next step.
Why governance first
Mission-driven organizations are accountable to donors, funders, patients, and the communities they serve. Ungoverned AI is a liability, not an asset. Every Copilot deployment we ship includes:
This is not overhead. It is the difference between an AI deployment your organization can trust and one you will have to redo.
How it works
Four weeks with a clear outcome at each stage. Pilot live by day 21. Handoff in your hands by day 28.
01
Week 1
AI Readiness Assessment completed: tenant audit, license inventory, governance gap analysis.
Sensitivity labels designed and deployed for the pilot scope. Restricted SharePoint and semantic-index settings configured. Pilot user list confirmed; pilot success criteria documented with leadership.
02
Week 2
Pilot user provisioning: Copilot license assignment, conditional access posture verified.
Prompt library v1 drafted with the pilot user owners across fundraising, program, clinical, and ops workflows. Power-user training session delivered (90 minutes, live, recorded). Pilot baseline metrics captured.
03
Week 3
General pilot training session delivered (60 minutes, live, recorded). Pilot users active on Copilot for one full work week with prompt library in hand.
Centered Networks engineer on standby for pilot questions (Teams channel, two-hour SLA). Mid-pilot check-in at day 17: usage data reviewed, prompt library refined, blockers cleared.
04
Week 4
Pilot retrospective session with the pilot group (60 minutes). Adoption metrics re-measured and documented.
Handoff Document written and delivered. 60-minute leadership presentation: what was deployed, what the pilot shows, what comes next.
Copilot Kickstart is the productized entry point. The Handoff Document tells you which path fits.
Kickstart deploys the pilot governed. CompleteCare Intelligence runs the program: ongoing AgentOps discipline, FinOps for AI, a monthly Intelligence Pod for new agent builds, quarterly board-ready ROI reporting, and the maturity path from Stage 1 through Stage 4.
The Kickstart Handoff Document is the bridge into the Intelligence kickoff. If the pilot proves out, the path forward is clear on day 28.
Path 2
Pilot proved out, governance is in place, the prompt library works. You run the next-wave expansion yourselves and re-engage Centered Networks at quarter-end for a review or the next agent build. This is a fine outcome. We will tell you on day 28 if it is the right one for you.
Path 3
The pilot surfaces a specific high-value workflow: donor research, intake routing, board reporting. The next move is a single named agent. The Agent Kits are each 4–6 week deployments on top of the Copilot foundation Kickstart establishes.
Path 4 · Healthcare
Copilot Kickstart can be delivered in a HIPAA-aligned configuration for healthcare organizations. The Healthcare AI Readiness assessment is the recommended pre-step for rural hospitals and health centers.
Pricing
No 12-month commitment. No hidden fees. No open-ended consulting engagement.
| Item | Investment |
|---|---|
| Copilot Kickstart (all-inclusive, up to 25 pilot users) | $15,000 |
| Additional pilot users (26–50) | $250 per user |
| Microsoft 365 Copilot licenses (client-procured) | Passthrough |
| HIPAA-aligned configuration add-on (healthcare) | +$3,000 |
Compare to running the same pilot internally with an FTE coordinator over 3–6 months, with no governance posture and no documented handoff. The Kickstart compresses that into four weeks with a defensible outcome.
Microsoft alignment
We deploy what Microsoft ships, configured for mission-driven accountability.
Questions
Long enough to set governance correctly and produce real pilot data; short enough to maintain momentum and avoid the open-ended pilot trap. The four-week container is a feature, not a constraint.
You need the baseline that Foundations provides: Conditional Access, sensitivity labels, MDM, MDO. If you are already there (or close enough that we can confirm during the Readiness Assessment in Week 1), you can run Kickstart standalone. If not, we either fold Foundations into the engagement or stage Kickstart 60 days later. The Readiness Assessment makes this call honestly.
Kickstart is the productized four-week pilot deployment. Intelligence is the ongoing managed AI program: AgentOps, FinOps, monthly Intelligence Pod, quarterly board reporting, the maturity path through Stages 1–4. Most clients run Kickstart first and graduate into Intelligence.
No. The prompt library is co-built with your pilot users during the engagement, because a generic library does not produce ROI. The Kickstart includes the library; the library does not ship standalone.
Honest answer: it depends on the workflows you are trying to apply it to and on your governance posture. The AI Readiness Assessment in Week 1 produces a candid answer. If the answer is "not yet" or "not this way," we tell you, and you stop the engagement with the assessment in hand. We have never had a client complete Week 1 and disagree with the readiness verdict.
A Microsoft-certified solutions architect leads the engagement, supported by a delivery engineer for the technical configuration and a change-management lead for the adoption training. Chris or another senior leader is the executive contact.
You can license everyone; we just do not recommend it. The pilot wave catches governance issues before they hit the whole org, and produces the prompt-library refinements that make the org-wide rollout actually work. Once Kickstart completes, you are set up to expand at the pace that fits.
That happens, and we tell you. The Handoff Document is candid about what worked and what did not, and the recommendation in those cases is usually: do not expand yet. Change these three workflows, or refocus on agents instead of Copilot itself. You leave the engagement smarter regardless.
Four weeks to a governed Copilot pilot. Fixed price. Predictable outcome.
Tell us about your tenant, your Copilot licensing status, and the pilot group you have in mind. We confirm scope on a 30-minute call and get the engagement on the calendar.
Not ready to deploy yet? Start with a Discovery Sprint → The roadmap will tell you where Copilot fits.
Considering an ongoing program? See CompleteCare Intelligence →
A senior member of our team will reach out within one business day to confirm scope and get the engagement scheduled.