Anthropic’s latest labor-market analysis surfaced the core planning problem for every ops lead: AI capability is already wide, but real deployment is still narrow. In other words, most teams are under-automated relative to what is technically possible right now. If you run operations at a 20–50 employee firm, the immediate question is not “Will AI replace jobs?” It is “Which budget line gets better ROI this quarter: one more hire, or one focused automation sprint?”
The 61-point gap your budget can exploit
Anthropic compares theoretical task capability with observed, work-related AI usage. In Computer & Math, theoretical exposure is 94%, but observed coverage is 33%. That 61-point spread is the opportunity window for operators who move early and carefully. Across occupations, Anthropic also finds a mild but real relationship between higher observed exposure and lower projected growth (about a 0.6 percentage-point lower BLS growth projection for each 10-point increase in coverage).
This is not a layoff chart. It is a sequencing chart. Teams that close easy automation gaps first should get faster cycle times before labor markets fully reprice those gains.
Option A: Hire another coordinator
Hiring still wins when the work is:
- High-variance and relationship-heavy (vendor negotiations, escalations, client-sensitive communication)
- Full of judgment calls that depend on unstated context
- Bottlenecked by cross-team trust rather than throughput
In those cases, an additional coordinator can unblock revenue quickly, especially if your workflow breaks at handoffs rather than repetitive processing.
Option B: Automate the repeatable 30%
Automation wins when the work is:
- Repeatable (same structure, different inputs)
- Rules-based (clear pass/fail conditions)
- Delay-sensitive (queue time hurts delivery quality)
For a typical ops function at a services firm, this usually includes intake triage, status summarization, first-draft client updates, and recurring QA checks. A practical stack today looks like:
- OpenAI GPT-5.4 or Claude Opus 4.6 for drafting and classification
- Zapier for trigger-routing between forms, CRM, and project tools
- Airtable for state tracking and review queues
- Slack workflows for human approvals and exception routing
A conservative impact estimate for a 25-person agency ops team: automating the repeatable 30% of intake and status work can return 6–8 operator hours per week, equivalent to roughly 0.15–0.2 FTE without adding payroll.
A 6-week pilot stack for an ops lead
Week 1: identify one high-volume workflow with a stable input format.
Week 2: document decision rules and exception criteria.
Weeks 3–4: deploy a narrow automation path (draft + route + human approve).
Week 5: measure rework rate, turnaround time, and hours recovered.
Week 6: choose one of three outcomes: scale, revise, or stop.
This keeps risk bounded while turning “AI strategy” into an operating metric discussion: throughput, quality, and cost per completed workflow.
Sources
- Anthropic, Labor market impacts of AI: A new measure and early evidence (2026): https://www.anthropic.com/research/labor-market-impacts
- SignalFire, State of Tech Talent Report 2025 (entry-level hiring and staffing shifts): https://www.signalfire.com/blog/signalfire-state-of-talent-report-2025
The right default for most ops leads in 2026 is automate first, hire second—unless your bottleneck is trust-heavy judgment work rather than repeatable process volume.