Free tool · 90 seconds · Updated 2026-08-17
Do you actually need an AI agent?
Seven questions and an honest verdict: fix the process first, a $20/month automation, a deterministic workflow with one LLM call, a real AI agent, or a company second brain. It is the same triage we run on inbound requests before quoting, and most of the time the answer is not an agent. No email, no signup, nothing leaves your browser.
By Ashutosh Upadhyay, founder of Cognio Labs — the rules below come from triaging requests across 100+ agent deployments, including the ones we talked people out of.
Optional, but it is the single best predictor of whether a build will succeed. We only echo it back to you; it is never sent anywhere.
7 questions · instant verdict · no email required
How this tool decides
There is no score and no black box. Six rules run in order, and the first one that matches wins. Process problems are checked before technical ones, because no architecture survives a workflow nobody can describe. The reversibility rule is a modifier rather than a verdict — it can attach to any of the others.
| Signal | Verdict | Why |
|---|---|---|
| Nobody describes the process the same way twice, no named owner, or no clear trigger | Fix the process first | Every rule below assumes a describable process. This one is checked first and overrides the rest. |
| Same steps every time + structured inputs (fields, rows) + a real trigger | Simple automation | No model needed. Volume doesn't change this — a script is a script at 5/week and 5,000/week. |
| A few branches, or documents and email as input, but a stable path | Deterministic workflow + one LLM call | Code the path, use the model only for the language step. The answer for most requests we get. |
| Judgment on messy inputs + 3 or more tools per run + 10+ runs a week | AI agent | Orchestration across systems in an order nobody can enumerate up front is the actual job of an agent. |
| Any action involving money out, outbound customer comms, or deletions | Add human approval gates (draft state) | A modifier on any verdict above, not a verdict itself. Irreversible actions ship as drafts. |
| The answer lives in heads or chat history, and the inputs are documents and conversations | Company second brain | A retrieval and capture problem wearing an automation costume. |
The one-sentence-with-a-number test
The best public answer to “how do I know if my business needs this?” is a comment sitting at one upvote in a r/smallbusiness thread: the clearest signal is not your tech maturity, it is whether you can already describe the problem in one sentence with a number attached. “We lose track of leads” is vague. “We miss about a third of after-hours calls and never call back” is a project.
The number does three things at once. It sets the acceptance test, so you can tell afterwards whether the thing worked. It bounds the budget, because a number implies a value and a value implies a ceiling. And it exposes vagueness early, while vagueness is still free — the failure mode we see most often is a vague problem turned into an expensive project. If you cannot attach a number today, the first piece of work is measuring for two weeks, not building.
Why most requests don't need an agent
The highest-voted honest post in this space is a practitioner on r/AI_Agents writing that 90% of the AI agent projects I get hired for don't need agents at all, describing a founder who spent a month researching agent frameworks for lead qualification when what he needed was a script checking three fields in an email against his ideal-customer criteria. It took four days. The runaway thread in the category is titled “Stop building AI agents.” Neither is anti-AI. Both are anti-architecture-shopping.
The reason is structural. A workflow has a path you wrote; an agent chooses its own path at runtime. That freedom is what you pay for, in build cost, in tokens, and above all in debugging — a workflow fails at a step you can name, an agent fails somewhere in a chain of decisions you have to reconstruct. Buying that freedom for a process that never varies is buying a liability. The verdict worth remembering: if you can draw the decision tree on one page, you do not need something that invents the tree at runtime.
One more standard from the same communities, and we hold our own work to it: if a human has to check everything your AI automation does, you did not automate the process — you moved the work. Approval gates on irreversible actions are deliberate design. Blanket review of everything is a failed build wearing a safety label.
When an agent is the right call
Three conditions have to hold together. The work needs genuine judgment on inputs that arrive messy. One run touches three or more systems, in an order that varies. And it happens at least ten times a week, so the build and the maintenance pay back inside a quarter or two. Remove any one of those and a cheaper shape wins.
The best real business deployment we have seen described publicly fits this exactly: a smart-home electronics company whose agent manages inventory and purchasing decisions, places orders with vendors and tracks purchase orders across systems — but creates every purchase order in draft state, with a separate scheduled job executing drafts only when criteria are met. Judgment across tools, with the irreversible step gated. That is the shape that survives contact with a real business.
What to do next
Whatever verdict you got, the sequence is the same and each step should cost less than the one it justifies. Write the problem down with a number in it. Run the free readiness check to see whether the foundations — documentation, data access, ownership — are in place; roughly four in ten companies that come to us are not ready, and finding that out early is worth more than a proposal. Then build the smallest thing that closes the number, and only scale what it proved.
If you want the background: our guide to AI agents for business covers what they do and do not do, the cost guide has the real 2026 price bands, and the second brain guide is for the knowledge-problem verdict. On the service side, agent transformation is the pilot-to-production programme and Company Second Brain is the knowledge build.
Frequently asked questions
How do I know if I need an AI agent or just an automation?
Ask whether the path varies. If the same steps run every time on structured data, you need an automation — a script, a Zapier zap or an n8n workflow, typically $20–$50/month. If the work requires judgment on messy inputs, touches three or more systems per run, and happens at least ten times a week, an agent is defensible. Everything in between is a deterministic workflow with a single language-model call, which is where most requests land.
What is the difference between an AI agent and a workflow?
A workflow has a path you wrote; an agent chooses its own path at runtime. That single difference explains the cost gap: a workflow fails at a step you can point to, while an agent fails somewhere in a decision chain you have to reconstruct from logs. Choose the agent only when the path genuinely cannot be enumerated in advance.
What does 'describe the problem in one sentence with a number' mean?
It means replacing a category with a measurement. 'We lose track of leads' is a category and cannot be scoped. 'We lose about 12 quote requests a week because nobody follows up within an hour' is a project: it has a subject, a frequency, a cause and an implied acceptance test. If you cannot attach a number, the first piece of work is measuring, not building.
Is this tool just going to tell me to hire you?
Three of the five possible verdicts end with advice to build it yourself or fix something internally first, and one of those explicitly says we would decline the work. We published the triage we actually run because telling people they do not need an agent is a faster way to earn a call than pretending everyone does.
What should I do if I get 'fix the process first'?
Get the two or three people who do the work in one room and answer three questions in writing: what event starts this, what the steps are, and whose name is on it when it breaks. That document is worth more than any tool selection. Once it exists, run this check again — the verdict usually changes.
Does the tool store my answers?
No. Everything runs in your browser, there is no email gate, and the sentence you type is never sent anywhere. We record only which of the five verdicts was shown, so we can see whether the tool is telling people what we expect it to.
Want a second opinion on the verdict?
30 minutes, no pitch. Bring the sentence with the number in it and we will tell you what we would build — including when the answer is “nothing, do this instead.”