Skip to content
Aristo's read Grounded in page evidence

Adoption is shown as aggregate cohorts and movement, never as a leaderboard of people.

Why it matters
It reveals where enablement can move the estate while holding the privacy floor.
Recommended action
If a cold cohort is counted, start with the largest one and open the evidence behind it.

Adoption overview

How Contoso's paid Copilot estate moves from bought to assigned to genuinely active, which teams are carrying it, and which way it is moving — with counted evidence behind every figure.

Adoption, run by run

The counted share at every run Aristo has recorded, not a sampled month.

Seat use at each counted run
5 counted runs share of seats, per cent Counted
60%65%70%75%80%2026-05-012026-05-312026-06-302026-07-302026-08-29
Activation — share of assigned seats active
Evidence & data — Seat use at each counted run

Comparison

Activation counts assigned seats with recent qualifying activity. Bought-but-unassigned seats are outside this denominator. A run that did not store the figure breaks the line rather than being drawn through it.

Source & method

Microsoft Graph — licence records + Copilot usage signals, counted at each run.

Basis: Counted

Accessible data

Seat use at each counted run
RunActivation — share of assigned seats active
2026-05-0168%
2026-05-3168%
2026-06-3068%
2026-07-3068%
2026-08-2968%

The gaps between the points are the gaps between counts, not months. The axis is banded 60–80; the figures here are the readings themselves. A run reading “not recorded” did not store that share.

Adoption by team

Which teams are carrying adoption, at 5 people or more.

Adoption by team
this counted run share of each team's assigned seats Counted (24) · Labelled estimate (13)
Team
Assigned seats active
counted
Assigned seats cold
counted
Consumption fit
estimate
Engineering
680 counted seats · 1,550 people
76%
24%
high
Sales
600 counted seats · 1,370 people
65%
35%
high
Operations
420 counted seats · 1,020 people
64%
36%
high
Customer Success
390 counted seats · 885 people
67%
33%
high
Finance
340 counted seats · 650 people
79%
21%
high
Marketing
260 counted seats · 540 people
65%
35%
medium
IT
250 counted seats · 495 people
82%
18%
medium
Product
260 counted seats · 455 people
77%
23%
high
Human Resources
180 counted seats · 370 people
67%
33%
medium
Manufacturing
210 counted seats · 537 people
60%
40%
medium
Supply Chain
210 counted seats · 445 people
57%
43%
medium
Data & Analytics
240 counted seats · 425 people
46%
54%
high
Other team (1 small team, aggregated)
no counted seat row yet
low
Solid — counted from your Microsoft signalsHatched — a labelled assessment, not a measurementDashed — genuinely not known, and not estimated
Evidence & data — Adoption by team

Comparison

The shade runs on a fixed scale — never re-normalised to this organisation's own spread — so the same share is the same shade in every month and every copy of this page. 1 row carries an em dash in the two counted columns rather than a guess.

Source & method

Microsoft Graph — directory joined with Copilot usage signals; consumption fit from the Aristo readiness allocator.

Basis: Counted (24) · Labelled estimate (13)

Accessible data

Adoption by team
TeamAssigned seats activeAssigned seats coldConsumption fit
Engineering76%24%high
Sales65%35%high
Operations64%36%high
Customer Success67%33%high
Finance79%21%high
Marketing65%35%medium
IT82%18%medium
Product77%23%high
Human Resources67%33%medium
Manufacturing60%40%medium
Supply Chain57%43%medium
Data & Analytics46%54%high
Other team (1 small team, aggregated)low

Active and cold are the counted split of assigned seats from your Microsoft signals; bought-but-unassigned seats are outside this team activity grid. Consumption fit is a labelled assessment. An em dash is a figure this product does not have, never a zero. 1 row carries an em dash in the two counted columns rather than a guess.

Privacy floor, stated rather than assumed. No page of this product can name a person. Every row here is a team of 5 people or more, and every cohort is a count of a group. 1 team is withheld from the counted-utilisation column for the same reason. There is no per-person view, screen or export of anyone else in this system for any leader to pull.

What moved

Every line here is a comparison against the previous counted run — never against a window this page chose.

counted

2,760 of 4,040 assigned seats are genuinely active — up 3 seats from 2,757 active at the counted run on 2026-07-30.

1,280 assigned seats did no work this period — down from 1,283 cold at the counted run on 2026-07-30.

4,200 paid = 4,040 assigned + 160 bought but unassigned. Activation is measured only across the assigned seats.

On the Frontier Scale the estate stands at 78 of 100 — Advancing (55–84 of 100) — up 4 points from 74 at the counted run on 2026-07-30.

Source: Aristo counted composition, compared against the previous persisted run As of: 2026-08-29 Active seats are counted from usage signals; the comparison is against the previous persisted run, not a window this page chose.
Open the surface that proves this → History & status →
Scope Whole organisation Period This counted run Compared with 2026-07-30 Adoption is composed for the current run, so there is nothing here to narrow. Slice it by team, role, country or location on Users & teams.

Cohorts

3

Each of these is a count of a group, never a list of people. They are counted out of different populations — the line under each figure says which — so they are not added together anywhere in this product, and there is no total here to quote.

1,120
people, assessed from counted activation and engagement

Credit-ready

estimate

These people are getting value from the included Copilot seat already — active, engaged, and saying the help lands. They are the cohort that earns its keep on metered credits rather than burning them learning.

Fund the enterprise-ready cohort behind a governed monthly cap.

Source: Aristo readiness assessment over counted adoption signals As of: 2026-08-29
See the evidence →
Not tracked as an object Set the funding cap
1,280
people Aristo has met — 12,543 of them so far

Cooling off

counted

They activated and are drifting — the seat is warm and going cold. The easiest seat to keep is the one that has not been given up on yet.

A cooling seat costs the same as a working one and is a fraction of the effort to recover, because the habit was already there once.

Source: Aristo engagement lifecycle (aggregate) As of: 2026-08-29
See the evidence →
Not tracked as an object See the ranked moves
1,280
assigned Copilot seats, of 4,040

Never started

counted

Seats that are assigned and paid for and show no qualifying activity this period. The spend is already committed; none of the work has arrived.

Aristo activates before it reclaims — the first move on a cold seat is to switch it on, turning spend you have already made into work, rather than to take it away.

Source: Microsoft licence records + Copilot usage signals As of: 2026-08-29
See the evidence →
New Owner: Unassigned Open chargeback History & status →
How every number on this page was arrived at, and what is not measured yet

Counted means read directly from your Microsoft licence records or usage signals — a seat is active when it shows recent, qualifying activity, not when a licence has been assigned to it. Estimate means an assessment Aristo made and labelled as one. Every figure above carries the weaker of the words that apply to it.

The three cohorts do not share a denominator and are never added together. Credit-ready and Never started are counted out of your Copilot seats; Cooling off is counted out of the people Aristo has actually met in Teams, which is a different and usually smaller population. Each figure prints what it is counted out of, directly underneath it.

The seat movement on this page is the same subtraction the Home command centre and the Executive Summary print, read from one shared reading rather than computed here — so no two surfaces of this product can state a different movement for the same run.

  • Movement is measured for the organisation, not per team. A persisted run stores the estate's active and cold seat counts, not a figure per department, so no team row on this page carries an arrow — a per-team trend would have to be invented, and an invented trend is the one thing a team leader would act on hardest.
  • 1 team row could not be shaded for seats in use: the counted utilisation join has not reached it, or it is the privacy-merged aggregate. It is shown with an em dash rather than a guess.