Independent · Cross-provider MEASURED FROM REAL WORK

The instrument the AI industry can't build for itself.

SkillBench measures whether your people are getting more capable, using signals from the AI-assisted work they already do.

The method
Skill formation · weekly +11.6%
W1W12
Measured Projected
Confidence
Fig. 1. Weekly skill formation, one enterprise cohort. Solid columns are measured; hatched are modeled.
63,0001
developers assessed in a single enterprise engagement
3.5×2
capability variance, identical AI tools
70–100
validated subtasks per role
03
screenshots or keystrokes collected
PROBLEM

Every enterprise bought a gas pedal. Nobody has the gauges. Existing tools measure activity: commits, velocity, tokens. None of them can tell you whether your AI spend is building capability or eroding it.

The model providers cannot grade their own work. SkillBench measures from outside, with no model of its own to defend.

In the field with Fortune 100 Tech Global Bank Asset Manager Talent Network Consulting Partner
DISTINCTION

Usage analytics asks a different question.

Plenty of tools now report how much AI your team uses and what it costs. None report whether the people using it are getting better at their jobs.

What usage dashboards ask, compared with what SkillBench asks
Usage dashboards ask SkillBench asks

How much AI-assisted output did we ship?

Are people getting better, or just busier?

What did the tokens cost, and what did they return?

Could your org still do the work without the AI?

Are we moving faster than last quarter?

Which AI habits build skill, and which erode it?

METHOD

First, decompose the role.

Every role breaks into 4–8 expert-validated tasks, and every task into 70–100 certified subtasks, linked into a dependency graph. Capability is then measured against that map, from the real back-and-forth of AI-supported work rather than self-report.

Allocation tools tell you where the effort went. The decomposition tells you what should be delegated to AI next, and what the skilling consequences will be.

Software engineer · role decomposition SME-CERTIFIED
Design & architecture 86 subtasks
Implementation 94 subtasks
Operations & incident response 71 subtasks
Measured today Partially delegated Candidate for AI
Fig. 2. Three of one role’s certified tasks. Each strip divides that task’s subtasks into twenty equal parts: solid is measured today, mid-tone is partially delegated, hatched is a candidate for AI.
INSTRUMENT

You don't need telemetry to start.

Assessment projects what AI will do to a role from job descriptions alone. Gauge measures what it did, once workers opt in. Tint means modeled and solid means measured, here and in the product.

PROJECTED · EPISODIC Available today

Assessment

Start from what you already have: job descriptions and org structure. SkillBench decomposes every role into its working parts and shows executives where AI can reshape work, skills, and structure, before touching a single internal system.

  • Executive view of AI impact and recommended actions
  • Workforce skill map and role development paths
  • Every assumption stated, every number ranged
OBSERVED · ONGOING For every worker

Gauge

A personal dashboard each worker owns. Consent-gated signals from real AI-supported work show individuals how their skills are growing through coaching. Their data stays theirs.

  • AI usage and human skill growth, from work artifacts
  • Own data only, nothing individual flows upward
  • No screenshots, no keystroke logging, opt-in always3
TRUST

The organization never sees an individual.

Workers use AI freely only when they aren't being watched. So the boundary between individual and organization is built into the architecture.

5.1

Individual data stops with the individual

Organizational surfaces see aggregates only, never any individual's data.

5.2

Nothing collected without activation

Collection requires activation. Each worker activates their own telemetry and sees exactly what is captured and who can see what.

5.3

Sanitized at the source

Signals come from work artifacts, sanitized in the collector before anything leaves the machine.

What each side can see
Data Worker Organization
Raw work artifacts stays on machine Never sees
Own skill signals Can see Never sees
Coaching & growth paths Can see Never sees
Cohort aggregates, k‑anonymous Can see Can see
can see never sees
Fig. 3. What each side can see. The dashes are enforced in the collector, before anything leaves the worker's machine.
  • ISO-27001 · CERTIFIED
  • MICROSOFT SSPA · COMPLIANT
  • SOC 2 · IN PROGRESS
  • SSO · SAML & OIDC
  • OPT-IN · ALWAYS
EVIDENCE

In one 11-week pilot, blind acceptance of AI output was the strongest predictor of poor outcomes,2 and it is a habit teams can be coached out of.

The kind of signal usage dashboards can't see.

25%2
of top performers flagged at risk from unsustainable AI use
4.4×2
more context switching among the lowest performers
BEGIN

See what your AI spend is actually building.

Start with an assessment of your organization: no telemetry, no installation, no risk. A walkthrough takes 30 minutes.