The SMB Reality Check: What Agents Can & Can't Do
Stop trying to automate everything. Here are three wins you can ship today, and three traps that will quietly burn your budget.
Omri Dan · Nomadan founder
Most small business owners are getting two flavors of bad advice right now.
The first is "agents will replace your whole team." They won't. The second is "agents are still science fiction." They aren't.
The truth lives in a narrow practical band, and that band is where Nomadan operates. Here's what's working, and what's quietly draining bank accounts.
Three wins you can ship this quarter
1. Inbound triage. Email, support tickets, missed-call follow-ups. An agent that reads, classifies, drafts a reply, and waits for you to hit send is a 10-hour-a-week win for almost any service business. It does not need to be magical. It needs to be consistent.
2. Internal knowledge retrieval. Your team is asking the same five questions in Slack every week. Point an agent at your docs, your wiki, your past invoices. Let it answer. The ROI is measured in interruptions you don't have anymore.
3. Quote and proposal drafting. Structured input, structured output, a human reviewer at the end. This is the boring agent that pays for itself in week one.
Three traps that will burn your budget
1. The no-touch pitch. If a vendor is selling you something that runs your business while you sleep, with no approval step anywhere, run. Ask them where it stops and waits for a person. A vendor who cannot answer that in one sentence is selling you risk, whatever they call the product.
That test applies to us. We build AI agents, and we answer it in writing before the build starts, not after. Reading, sorting, filing and drafting run on their own in almost every build. The steps that spend money, delete something or go out to a customer are the ones worth arguing over, and where that line sits is your call, not ours. Some builds hold every outbound message for your approval. Some send the routine ones and stop at the rest. Both are defensible. What is not defensible is a vendor who cannot tell you where the line sits before you pay.
2. The "let's connect 47 SaaS tools" dream. Every integration is a place where your agent will silently fail. Start with one workflow, one data source, one outcome. Earn the right to add the second.
3. Branded ChatGPT wrappers priced like real software. A lot of "AI tools for small business" are a system prompt and a logo. Before you buy, ask: what does this do that I can't get from a standard ChatGPT seat plus 30 minutes of setup? If the seller can't answer in one sentence, pass.
The honest middle
The honest middle is unglamorous: a three-week build, a clearly defined workflow, a human checkpoint, and a measurable hour-saved-per-week number on the other side. That's the whole game right now.
Do that three times and you have a different business.
Updated 2026-09-08. Two things changed in trap #1, and the second one is the one worth reading. The first is the name: the trap used to be titled "Full autonomous 'AI employee' pitches", and Nomadan now uses "AI employee" as its own product noun. The trap was never the word, it was the claim of full autonomy with no approval step, and it is written that way above. The second change is a retreat, so here it is in plain words: the old version also laid down a blanket rule for the whole category, that the good agentic systems propose and you confirm. That is a stronger standard than our own builds meet. Plenty of steps we ship send without asking, because that is what the client agreed to, and the demo on our own homepage shows jobs that end in "Send it". Keeping a standard we do not meet would have been the more flattering edit. The standard above is the one we will defend: the approval line is agreed per build, it is the buyer’s call where it sits, and a vendor should be able to tell you where it sits before you buy. Both original wordings are in the git history.
Updated 2026-09-20. The product noun moved again, back to "AI agent", and the whole build is now called the AI OS. That dates one sentence in the note above: Nomadan no longer uses "AI employee" as its own product noun. The note stays as written because it is the record of why the trap was retitled, and the retitling still holds for exactly the reason it gives. The trap was never the word. It was the claim of full autonomy with no approval step, and trap #1 above still tests for that.