# JCB Hit 83% Monthly Copilot Use — What They Did Differently

> How JBC reached 83% monthly Copilot adoption — and what founders can copy from their role-first, leader-modeled rollout without enterprise budgets.

- Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board)
- Published: 2026-11-22
- Updated: 2026-11-22
- Source: https://aiadvisoryboard.me/blog/jcb-83-percent-monthly-copilot-use-what-they-did-differently

When a founder told me his team had bought Copilot licenses for everyone but adoption stalled at 20%, I recognized the pattern. The licenses were there, the training deck was shared, and nobody was using it.

## TL;DR

JCB reached 83% monthly active Copilot use by treating adoption as a workflow change, not a software installation.

They started with role-specific scenarios instead of generic prompts.

Leadership used the tool publicly before asking anyone else to.

## Definition: Monthly active use

The share of licensed employees who open and use the tool at least once in a 30-day period. High license count does not equal high adoption.

## Definition: Copilot

Microsoft’s AI assistant embedded in 365 apps — Word, Outlook, Teams, Excel — that drafts, summarizes, and answers questions based on company data.

## Why Most Copilot Rollouts Stall

Buying licenses is the easy part. Getting people to open the app daily is where most companies fail.

The typical pattern looks like this:

- IT deploys Copilot across the tenant.
- HR sends a generic “learn AI” email with a link to documentation.
- Managers never change their own habits, so staff see no reason to change theirs.
- After 60 days, usage flatlines and leadership concludes “AI doesn’t work here.”

JCB avoided this by reversing the order.

## How JCB Approached It Differently

### 1. They Started With Roles, Not Features

Instead of showing employees what Copilot can do, JCB showed them what their specific job requires.

A sales rep got scenarios for pipeline summaries. A project manager got templates for status rollups. An operations lead got meeting-capture workflows. The training was not “here is Copilot”; it was “here is how you finish your Thursday faster.”

### 2. Leaders Modeled the Behavior First

Executives did not delegate AI adoption to a task force. They used Copilot in visible contexts — drafting board memos, summarizing long email threads, preparing for 1:1s — and shared the output in team channels.

When the person signing payroll checks uses the tool in public, the stigma of “cheating” or “cutting corners” disappears.

### 3. They Measured Monthly Active Use, Not License Assignment

JCB tracked who actually opened the tool, not who had a seat assigned. This forced them to confront the real bottleneck: not technical access, but behavioral change.

Low usage in a specific department triggered a conversation with that department’s lead, not another generic training invite.

## Tool tip (Course for Business)

If your team has licenses but nobody is opening the app, the problem is usually not the software — it is the first scenario. Our corporate intensive starts with three priority tasks your company actually faces, and participants build working automations around them across four live sessions. No coding required. See how we map the first week at https://course.aiadvisoryboard.me/corporate

## Copy/Paste: Role-Specific Copilot Scenarios

Use this template to build your own internal rollout list.

```markdown
| Role | Weekly Task | Copilot Scenario | Success Signal |
|------|-------------|------------------|----------------|
| Sales Rep | Pipeline review | Summarize last week’s email threads with open deals | Deal status updated in CRM before Monday meeting |
| Project Manager | Status report | Draft weekly update from Teams channel history | Report sent in under 15 minutes |
| Ops Lead | Meeting notes | Turn call transcript into action items with owners | Tasks assigned before the call ends |
```

## Manager Scan (2-Minute Digest Example)

If you want to see whether Copilot is actually landing in your company, scan for these signals:

- How many team channels contain AI-generated summaries vs. manual notes?
- Are managers forwarding long email threads to Copilot before asking staff to read them?
- Is “I asked Copilot to draft this” showing up in status updates without prompting?
- Which departments have zero active users after 30 days?
- Are employees asking for help with prompts, or have they gone silent?

## Micro-Case (What Changes After 7–14 Days)

A mid-size professional services firm copied JCB’s role-first approach. Instead of a company-wide webinar, the COO ran three 45-minute sessions — one for sales, one for delivery, one for finance. Each session ended with one live automation built in the room.

Within two weeks, the sales team stopped spending Friday afternoons on pipeline summaries. The delivery team cut status-report time by half. The partner running the sessions did not mandate usage; he simply stopped accepting manually written drafts for internal review.

The shift was visible because the baseline was measured before the first session, not after.

> **Note on this case:** This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

## FAQ

**Did JCB use only Copilot, or other AI tools too?**

Public case details focus on Copilot as the primary assistant within the Microsoft 365 environment. Most SMBs should pick one platform first and master it before adding others.

**Can a 50-person company replicate this without an IT department?**

Yes. The JCB pattern is behavioral, not technical. You need one person to own rollout, three role-specific scenarios, and a weekly check on who is actually using the tool.

**How long until we see 80%+ adoption?**

JCB’s result came from sustained leadership modeling and role-based training, not a one-time launch. Expect 30–60 days before monthly active use stabilizes.

**What if some teams refuse to try it?**

Start with the willing. Public wins from early adopters usually create more pull than a mandate from leadership.

## Conclusion

JCB’s 83% monthly active use was not caused by buying more licenses. It came from starting with real work, having leaders go first, and measuring behavior instead of seat assignment.

If your team has Copilot but adoption is flat, pick one role, build one scenario, and run a live session this week.

If you want your team to finish with working automations they built themselves — book a 30-min call and we’ll map your first three tasks.

https://course.aiadvisoryboard.me/corporate

---

When citing, link to https://aiadvisoryboard.me/blog/jcb-83-percent-monthly-copilot-use-what-they-did-differently. More articles: https://aiadvisoryboard.me/blog
