The bottom line
Roughly 80% of the work in Tutors 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 overwhelmingly digital, with 29 of 30 tools falling in IT/software (Segment 43, prior 0.85) such as Zoom and educational platforms. Work activities are entirely cognitive and communicative, led by 'Training and Teaching Others' (4.71) and 'Interpreting the Meaning of Information' (4.10). The work context is highly sedentary ('Spend Time Sitting' at 4.86) and indoors, placing this firmly in the digital band, though high scores in 'Face-to-Face Discussions' and 'Physical Proximity' keep it from the absolute maximum due to its human-centric knowledge transfer.
grounded in the economy graph · digital scalar 0.80 · digital
Business-as-Code
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Tutors engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Tutors involves 41 work activities — the generalized motions beneath the role, each scored against the AI-deliverability frontier.
+29 more via involvesActivity
Autonomous Agents as digital employees
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Tutors performs 19 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+7 more via performs
Tutors is typically employed by 100 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+88 more via typicallyEmploys
Tutors is employed across 56 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+44 more via employs
Headless SaaS for Agents
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Tutors uses 6 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.
Tutors relies on 26 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.
+14 more via uses
The software Tutors 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.
The problems this exposes
Node-intrinsic problems read straight off the graph (exposesProblem) — the evergreen wedges a builder could take into this space.
Where Tutors sits
Related articles
No articles yet for this entity.
Recent capability events
No capability events for this entity yet.
Problems
- Student Lead Acquisitiondemand-gen
- Learning Outcome Validationretention
- Subject Expert Recruitingtalent
- Session Scheduling Frictionops
- Child Safety Clearancecompliance
- Session Payment Disputescapital
- Curriculum Alignment Trackingops
Opportunities
- Student Sourcing AgentAgent
- Automated Progress ReportingService-as-Software
- SMS Scheduling AgentAgent
- Headless Session BillingHeadless SaaS
- Curriculum Alignment AutomationHeadless SaaS