How chief executives are reshaped as AGI capability advances.

Roughly 85% of the work in Chief Executives is information-shaped — already within reach of AI delivery. The question here is not whether it shifts, but which tasks go first and who staffs the residual.
Why: The occupation's toolset is completely digital, with all 30 tools falling into UNSPSC segment 43 (software/IT, prior 0.85), including Tableau and MS Teams. Work context heavily features desk-knowledge surfaces like E-Mail (4.97) and Telephone Conversations (4.92) in an Indoors, Environmentally Controlled setting (4.82). Combined with top activities focused on Making Decisions (4.85) and Communicating (4.75) rather than physical tasks, the value-producing work is heavily informational, placing it firmly in the digital band.
grounded in the economy graph · digital scalar 0.85 · digital
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Chief Executives engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Chief Executives involves 41 work activities — the generalized motions beneath the role, each scored against the AI-deliverability frontier.
+29 more via involvesActivity
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Chief Executives performs 49 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+37 more via performs
Chief Executives is typically employed by 557 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+545 more via typicallyEmploys
Chief Executives is employed across 320 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+308 more via employs
Chief Executives is linked from 1 entity via `performedBy` — a real edge on the economy graph, surfaced here so the claim stays grounded in data rather than assertion.
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Chief Executives uses 12 tools today. As each gains an agent-consumable surface (API / MCP / SDK), the human UI stops being the only way in — and the work routes straight to an agent.
Chief Executives relies on 61 products. The headless dimension of each — whether an agent can call it without a screen — is what decides how much of this work goes hands-free.
+49 more via uses
The software Chief Executives reaches for already exposes 12 agent-callable actions (via uses → exposedBy) — typed surfaces an agent invokes directly, no human screen in the loop. The work routes to the API, not the UI.
Node-intrinsic problems read straight off the graph (exposesProblem) — the evergreen wedges a builder could take into this space.
+3 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.