
Only about 10% of Roofers is information work today — the rest is physical, and moves slowly. The exposure is concentrated in the back office: the books, the paperwork, the scheduling, the marketing.
Why: While the tool distribution shows use of segment 43 software for estimating and record keeping, the core of the role is overwhelmingly physical. Top Work Activities like 'Performing General Physical Activities' (4.30) and 'Handling and Moving Objects' (4.22), combined with severe Work Contexts like 'Outdoors, Exposed to All Weather' (4.98) and 'Exposed to High Places' (4.90), firmly place this work in the physical band.
grounded in the economy graph · digital scalar 0.10 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Roofers engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Roofers 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.
Roofers performs 27 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+15 more via performs
Roofers is typically employed by 59 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+47 more via typicallyEmploys
Roofers is employed across 37 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+25 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Roofers uses 131 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.
+119 more via usesTool
Roofers relies on 28 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.
+16 more via uses
The software Roofers 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.
+4 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.