The most expensive agent is the one you didn’t need to build.
A pattern I keep seeing across the industry — and I’ve been guilty of it myself: someone spends days building an agent for a task a good low-code UI would have handled in an afternoon.
A structured intake form. A route. A record created. No judgment, no ambiguity, no reasoning required. And still the instinct is to reach for the most powerful tool in the kit instead of the right one.
You can build almost anything as an agent. That’s the trap. The question was never “can this be an agent.” It’s “should it be.”
That distinction is the whole job. A deterministic UI flow runs essentially for free and fails in ways you can predict and debug. An agent makes multiple LLM calls every time it runs, so it carries a real cost on every execution and a probabilistic failure surface to match. None of that is a knock on agents — it’s the reason you spend them where they earn it.
So before I architect anything as an agent, I ask one thing: is a real decision being made here, or are steps just being executed? If the input is structured and the steps are fixed, you don’t need an agent. You need a form.
Done right, that discipline is what makes agentic investment pay off. Every agent you build is one that needed to exist. Reserve the capability for the problems that earn it, and the ROI takes care of itself.
Agentic is a capability. It is not a default. The hard part isn’t knowing how to build agents — everyone’s learning that part. It’s knowing when not to.