What the organisation is actually doing with the AI it pays for, read across every seat and every vendor that reports. Findings are things you could act on this week; the tables underneath are the evidence for them, and the bottom of the page names what we still cannot see.
nicole@theecommerceaccelerator.com accounts for 73% of tokens across the estate. Either the rest of the team has not adopted it yet, or this person is doing work the others could be.
Bash (5 runs across 2 seats). Repeated practice across people is where a shared skill or template pays for itself.
| Seat | Model | Calls | Tokens | Share |
|---|---|---|---|---|
| tyler@theecommerceaccelerator.com | claude-sonnet-5 | 28 | 2.6M | 27% |
| nicole@theecommerceaccelerator.com | claude-sonnet-5 | 84 | 7.1M | 73% |
| claude-haiku-4-5 | 2 | 11.4k | 0% |
| Tool | Runs | Seats | Avg | Rejected |
|---|---|---|---|---|
| mcp_tool | 23 | 1 | 1.9s | – |
| TaskUpdate | 14 | 1 | 8ms | – |
| TaskCreate | 10 | 1 | 7ms | – |
| Bash | 5 | 2 | 3.1s | – |
| Grep | 5 | 1 | 4.0s | – |
| ToolSearch | 4 | 2 | 4ms | – |
| Read | 2 | 1 | 302ms | – |
| Skill | 1 | 1 | 13ms | – |
| WebFetch | 1 | 1 | 9.3s | – |
Rejected counts the times a person declined an edit the agent proposed. They are not failures – they are the only place a harness tells us a human pushed back, which is the control plane working.
No harness on this estate has reported a human decision yet. That is the honest reading: the gate exists, and nothing has been put through it.
Discovery
Needs a connector into a system of record
Finding AI nobody registered means reading SSO logs, browser telemetry or a SaaS admin API. Telemetry only ever shows what already reports to us, which is the opposite problem.
Entitlements
Needs a scopes read per harness
Whether an agent can reach more than it needs is a comparison between what it was granted and what it has used. We hold the second half; the first has to be pulled from each vendor.
Benefit
Needs telling us what the work was worth
Hours saved and deals closed are not observable from a token counter. The cost side above is measured; the return has to come from you, per use case.