Copilot & AI Agent Readiness Gauge

• Copilot licenses bought, adoption stalled, and nobody sure whether the blocker is content, training, or trust
• A board or executive team asking for an AI plan by a date
• The first shadow agents appearing — built in Copilot Studio or elsewhere, outside any review
• An oversharing incident — or the well-founded fear of one — because Copilot finds every file your permissions let it find
• An Agent 365 or agent-platform evaluation starting without governance to plug it into
• Pilots that impressed a demo audience and then went nowhere

The uncomfortable truth in most tenants: the AI isn't the risk — the permissions underneath it are. The Gauge measures that directly instead of asking anyone to take it on faith.

If you've already run one of the free automated readiness scans — Microsoft's included — bring the report: it's useful input, not a verdict. A scan lists what's open; the Gauge tells you what it means, which of it actually matters for your rollout, and what to fix first.

• Content and permission oversharing scan — what's actually exposed in the tenant, and to whom, before an AI starts surfacing it in answers
• Sensitivity-label and sharing-policy review — whether the controls that are supposed to contain Copilot exist, and whether they're doing anything
• Use-case discovery and prioritization — where AI actually fits your work, prioritized with a number attached to each so the sequence is an argument, not a guess
• Agent inventory — if agents already exist in the tenant, a census of what they are, who built them, and what they can touch
• Grounded Agent Ladder placement — each current and proposed use case placed on the ladder (Spark → Ground → Wire → Orchestrate), with governance recommendations proportional to each rung; a chat helper and an agent that acts in your systems should not carry the same controls
• Rollout and governance roadmap — the sequenced plan: what to fix, what to pilot, what to govern, in what order

Extended tier adds: design for a first pilot, an adoption plan for the rollout, and a draft of agent lifecycle standards — how agents in your tenant get proposed, approved, grounded, and retired.

• Tenant read access for the content, permission, and policy scans. We bring the tooling; nothing is changed in the tenant.
• Two workshops — typically one with IT and security, one with business stakeholders for use-case discovery.
• Whatever AI plans, pilot notes, or agent experiments already exist. Absence of these is normal and is itself a finding.

Two weeks for the focused tier; three for extended. The engagement closes with a readout workshop with your team, including, where wanted, a version of the findings shaped for the board or executive audience asking for the AI plan.

• Readiness findings deck — the oversharing scan results, label and policy review, and what they mean in plain language, written to be shown upward as well as inward
• Prioritized use-case portfolio — each candidate described, valued, and ranked, with the reasoning visible
• Agent inventory and Ladder placement — the census of existing agents and where each current and proposed use case sits on the Grounded Agent Ladder, with proportional governance recommendations per rung
• Rollout and governance roadmap — the sequence: remediation, pilots, policy, and platform decisions in order
• Extended tier: pilot design, adoption plan, and draft agent lifecycle standards
• Readout workshop — a working session, not a handoff

Fee credit: 100% of the focused-tier fee is credited toward any implementation engagement of $25,000 or more signed within 90 days of your readout.

The Gauge is not a Copilot deployment, an agent build, or a permissions remediation project. It tells you what's true and what to do; follow-on engagements do the fixing and building. That separation is deliberate — an AI readiness verdict you can trust can't have an agent-building contract riding on its conclusions.

Two more commitments. First, findings are never scoped to the entry topic: most readiness problems turn out to be SharePoint permission and content problems, and if that's your situation the findings will say so rather than dress it up as an AI project. Second, if the honest answer is "you're not ready for agents yet, start lower on the Ladder," that's what the roadmap will say.

The most common follow-on is readiness remediation: usually SharePoint permission and content work, which is why this Gauge and the SharePoint Modernization Blueprint cross-reference each other's findings. Clients with a strong use case move to a Flagship Agent QuickStart, building one well-grounded agent as the pattern for everything after it. Extended-tier clients typically carry the lifecycle standards draft into a standing agent governance program. In every case the fee credit applies to qualifying implementation, and the roadmap stands on its own if you execute elsewhere.