Are AI agents worth it? Five Reddit threads, one verdict

For most jobs, no, and that is a recommendation rather than a dismissal. Build the rules-based automation first. Promote it to an agent only when the task genuinely needs judgment or language that a fixed sequence cannot encode. That is the call we make when a client asks us to build an agent, and it is the same call the builders on r/AI_Agents keep arriving at independently.

Here is the reasoning, because a verdict without one is just an opinion:

• The default should be an automation, and it is not close. Predictable steps, a rule or filter instead of a decision, a loud and obvious failure when something breaks. Cheaper to run, easier to debug, and you find out the same day when it goes wrong. Most of what gets briefed to us as "an AI agent" is this.
• An agent earns its cost on judgment, not on volume. Classifying a vague email, drafting a reply a human would send, deciding which of several paths to take on messy input. If you cannot name the specific judgment call the model is making, you are paying model prices for something an if-statement does better.
• The failure mode is what actually decides it. An automation crashes loudly. An agent can retry a bad call all night and bill you for it, which is the single most repeated warning in the threads below. That asymmetry is why the burden of proof sits on the agent, not on the automation.

The honest counter case: this rule can talk you out of something worth building. When a job is genuinely judgment-heavy and high-volume, the narrow well-scoped agent is a real edge, and the operators quietly winning with agents are doing exactly that rather than waiting for certainty. Our own five-day scorecard in the Manus AI review is the concrete version of that: research and report deliverables paid back immediately, and the two writing tasks did not. If the judgment is the whole job, build the agent and put the guardrails on from day one.

One thing the build choice will not fix: the gap between teams that get value out of this and teams that do not is almost never the tooling. It is whether anyone scoped the job before the spend started.

If you only read the headlines, you would expect r/AI_Agents to be a wall of hype. It is not. The dominant mood across its highest-engagement threads is best described as pro-precision skepticism: not "agents are fake," but "most of what people call an agent should have been a simple automation, and a lot of the spend is going to waste."

One of the clearest examples is a thread titled "Am I antiquated, or do a lot of the ways people use AI agents make no sense?" (74 upvotes). The fact that a question that doubts the whole category climbs to the top of an agent-building subreddit tells you where the room actually sits. The builders are not anti-agent. They are anti-waste.

This matters for anyone about to write a cheque. The people who have shipped agents in production are converging on a few hard-won rules. Below are the five threads that capture the mood best, and what each one teaches you before you spend.

If a fixed sequence can do the job, a rules-based automation in n8n, Make, or Zapier is cheaper, more reliable, and far easier to debug. The moment the task needs to read intent, weigh options, or write something a human would, that is when an agent earns its keep. Get this one call right and most of the "AI agents waste money" complaints disappear. For the full plain-English version of where agents pay off, see what is an AI agent: a guide for business owners.