All insights

INSIGHTS · 5 MIN READ

When not to build an AI agent, and what to build instead

AI agents are exciting, and they are often the wrong first step. An agent that decides what to do on its own is harder to test, harder to explain and more expensive to run than a well-designed workflow. The goal is a dependable result, not the most autonomous system.

By Itzhak Shaul · October 11, 2026

Start with the question: is the path known?

If you can write down the steps a competent employee follows, you probably want a workflow with AI used at specific steps, such as reading a document or classifying a message. Use an agent, where the model chooses its own steps and tools, only when the path genuinely varies from case to case.

Ask what a mistake costs

A wrong answer in a casual search assistant is an annoyance. A wrong amount in an invoice, a wrong customer record or a message sent to the wrong person is a business problem. The higher the cost of error, the more you need validation rules, limits on what the system may do, and a human approving sensitive actions.

A safer pattern for most business automation

For documents and data entry, a reliable pattern is: extract the data into a strict structure, validate it against rules, attach a confidence score to each field, and route anything missing, conflicting or low-confidence to a human review queue. Everything the model does is logged, so you can see why a decision was made.

This usually delivers most of the time savings with far less risk, and it produces data you can measure.

Add guardrails before autonomy

Before giving a system more freedom, add provider fallback so an outage does not stop work, read-only database access for any question-answering over data, idempotent actions so a retry never repeats a payment or message, and defenses against prompt injection from content the system reads.

When an agent is justified

Agents make sense when tasks vary a lot, when the system must combine several tools, and when you can bound what it is allowed to do. Even then, start narrow, measure results on real cases, keep a human hand-off, and expand only when the numbers justify it.

A simple way to decide

Choose one workflow. Define what success looks like in numbers: time saved, error rate, cases handled without review. Build the smallest version with validation and review. If it works, extend it. If not, you learned that cheaply.

If you are considering AI for documents, customer conversations or CRM work, a short discovery step to pick the right first workflow is usually the best investment.

Discuss your project

More articles

How to build a multi-tenant SaaS without leaking customer data · Modernizing a legacy .NET system without a risky rewrite