What you need to set up an agent, and what you don't
It isn't a platform decision. An agent is a written job, a trigger, a connection, a set of rules, an owner and a log. The tool that holds those six things matters far less than whether all six exist.

The six parts
| Part | What it is | The test |
|---|---|---|
| The job | One thing, in a sentence. "Read each new enquiry and draft a reply from the price list into the rep's drafts folder." | Could a new starter do it from this sentence? |
| The trigger | When it runs: every morning at 7, when an email arrives, when a record changes. | Is it written down, and can the owner change it? |
| The connection | The systems it reads and writes, granted by the systems owner, with the smallest permissions that do the job. | Can you see the permission on the system's own screen? |
| The rules | What it must never do, and when it stops and asks a person. | Are they written as tests, not hopes? See validating what AI produces. |
| The owner | A named person who checks the sample, changes the rules and can switch it off. | Would they get the phone call on a Thursday afternoon? The owner's card says what that involves. |
| The log | A line per action: what it read, what it wrote, when. | Could the owner piece together last Tuesday from it? |
Three places to build
| Where | What it's good for | Where it runs out |
|---|---|---|
| A general assistant's project or agent feature | Personal and small-team agents: a meeting-notes writer, a research brief, a drafting assistant. Minutes to set up. | Running on a schedule without a person, writing reliably into systems, logging, and anything that has to behave the same way every time. |
| A low-code automation tool | Agents that run on a trigger and move data between systems, with a model step in the middle. Most first agents in a small business belong here. | Complex branching, heavy volume, fine control over what the model gets asked, and keeping the logic portable when you change tools. |
| Code | Anything at volume, anything with lots of small steps, anything you want to own completely. | Needs a builder, and then a builder to maintain it. |
Start at the top and move down only when the row above can't do the job. Most businesses start in the middle for their first real agent and stay there for a year or so.
What you don't need
A platform strategy before the first agent. A data warehouse. A vendor bake-off that takes a quarter. A new hire with "AI" in the title. An agent framework because a conference speaker used one. What you do need is one job, one owner and the six parts – and for the second agent to look like the first, so that someone other than the builder can understand both.
Why we don't answer this with product names
We get asked this a lot, and we don't name the tools we use. Partly because they change, and a list from last quarter would already be wrong. Mostly because the names aren't the answer. Every agent we run has the six parts above and a person on it, and that's what makes it reliable, not the tools. If you've got the 6, you're most of the way there with whatever you chose. If you're missing one, the best tool in the world won't supply it.