Notes / Workers
The work that should never have been manual
Email triage, CRM updates, follow-ups, scheduling. Some repeat work becomes safer when a managed worker handles the first pass.
By Rich Hill III. Published May 30, 2026. 5 min read.
A surprising amount of business work survives because nobody has named how repetitive it is. The task is not hard enough to justify a project, but it is frequent enough to drain the week. Email sorting. CRM updates. Meeting prep. Follow-ups. Status summaries. The work sits in the gaps until everyone accepts it as normal.
AI workers are most useful in that category. Not because the work is unimportant, but because it is structured enough to be described, observed, and improved.
Manual does not mean human
A task being manual does not prove it requires human judgment. It may only mean the business never had a clean system for handling it. The question is whether the task depends on taste, context, relationship, or risk. If it does not, a worker may be able to handle the first pass.
That first pass matters. A worker does not need to replace the owner to create value. It can gather context, draft the response, update the record, prepare the agenda, or flag the exception so the human starts from a better place.
Good first candidates
The best early workflows are frequent, bounded, and easy to review. They have a clear input, a clear output, and a human who already knows what good looks like. If the task is rare, emotional, high-risk, or full of hidden context, it should not be first.
Inbox triage with categories, urgency, and suggested next actions. CRM cleanup after calls, forms, or email threads. Follow-up drafts that wait for human approval before sending. Weekly summaries that pull from known sources and flag missing data.
Key takeaways
- Good worker candidates are frequent, bounded, reviewable, and already understood.
- A worker can create value by handling the first pass, not the final decision.
- Defining the workflow is part of the value.
- Avoid starting with sensitive, ambiguous, or high-risk work.
Frequently asked questions
What is a good first AI worker workflow?
A recurring task with clear inputs, clear outputs, low risk, and a human who can quickly review the result.
Should a worker send messages automatically?
Usually not at first. Drafting and routing are safer initial steps. Sending can come later if the workflow proves reliable.
What if our process is messy?
Then the first step is mapping the process. A worker can only be reliable when the business has named the rules and exceptions.
Explore Workers