The author shares insights on building AI agents for small businesses, emphasizing that the hardest part is selecting the right task to automate, not the agent itself. Key considerations include volume, input structure, cost of errors, and existence of manual processes.
I build inbox and lead automations for small businesses, and the pattern I keep hitting is that the agent is almost never what kills the project. Task selection is. The failure I see most: someone builds a genuinely impressive agent for a task that happens twice a month, while the thing eating six hours a week never gets touched. It demos beautifully and changes nothing. Four questions I now run before writing a single node: 1) Volume x minutes, not "how annoying is it." Rank every repetitive task by (times per week) x (minutes each). People rank by irritation instead, and irritation correlates badly with actual hours lost. The top row of that list is rarely the thing they asked me to build first. 2) Is the input structured enough to classify reliably? Inbound email works because intent falls into a handful of buckets: pricing question, booking request, complaint, spam. "Handle my Slack" doesn't, because the buckets are unbounded. If I can't write the categories down on paper, the model will invent them at runtime. 3) What does being wrong once actually cost? This is the question that decides architecture, not model choice. If a bad output means a slightly awkward internal note, auto-execute is fine. If it means a customer gets a wrong price in writing, the agent drafts and a human approves. For anything customer-facing I've settled on draft-only, and I build it so the workflow never calls the send endpoint at all rather than gating it behind a flag, because a flag is something you can flip at 11pm and regret. 4) Does a manual version already exist? If nobody is doing the task by hand today, automating it usually means automating a process nobody has validated. Those are the builds that quietly get switched off a month later. The uncomfortable part is that 1 and 3 tend to disqualify the exciting build. The highest-ROI thing is usually a boring classifier plus a draft step, not an autonomous agent. Curious where people land on 3 specifically. Has anyone shipped full auto-send for customer-facing replies and had it hold up over months? I've stayed draft-only and I honestly can't tell anymore whether that's justified caution or just me being conservative because one bad send is more memorable than a hundred good ones.
An opinion piece arguing that the real challenge for AI agents in small businesses is governance and accountability, not just capability. It emphasizes the need for bounded action, role-aware authority, and clear human oversight.
The article argues that the main constraint on AI agent adoption is not capability but verification, including how companies define quality, evaluate ongoing performance, and compound feedback. It explores challenges like tacit standards, company-specific evals, feedback ownership, and self-improving loops.
The article discusses the operational challenges companies encounter when scaling from a few AI agents to dozens, proposing a solution that separates business logic from technical control to manage agentic workflows effectively.
The article discusses which AI agent workflows businesses should automate first, seeking recommendations from real-world experiences and identifying potentially overrated automations.
The article explores practical use cases and challenges for AI voice agents in small businesses, emphasizing that workflow and integration are often more critical than the voice model itself.