Skip to content
All instruments

2 min · no login · nothing stored

Should this job be an agent, a chatbot, or left alone?

Not every AI job needs an agent. Answer five questions about frequency, finished output, tools, risk, and review. Get a plain recommendation before you buy another tool.

Built for

Founders and ops leads who were pitched a chatbot, a copilot, or an 'autonomous agent' and need a filter.

You leave with

One of four calls: build an agent, hybrid with a tight leash, grounded chatbot, or do not automate yet.

Setup

2 min · No account · Nothing stored

How to run itOpen
  1. 01

    Name the job in your head (example: new-lead follow-up, invoice routing, kickoff asset chase).

  2. 02

    Answer all five questions honestly — 'it depends' is usually the middle option.

  3. 03

    Read the recommendation and the reason. Screenshot it for your team.

  4. 04

    If it says agent, run the workflow audit next with real volume.

Do this well. If you cannot describe a finished job in one sentence, do not buy an agent yet.

tool · agent-fit

0/5
01How often does this job happen?
02Can you describe a finished job in one sentence?
03Does the work require updating systems, not just answering a question?
04What happens if the system is wrong?
05Will a person review exceptions?

Answer every line. The call appears here.

Want this on a live workflow?

This stays in your browser. A production agent writes to your CRM and waits for your click.

If you came from Google

What is the difference between a chatbot and an AI agent?
A chatbot answers. An agent takes approved actions across tools — draft, update a CRM, file a record — and should stop for a person when the case is unusual or high value.
Can I use this for support, not sales?
Yes. The questions are about the job shape, not the department.
Is my data stored?
No. Answers stay in your browser. Nothing is sent unless you later use a form on this site.

Other tools