Tailored agents for specific problems, or one general tool?

Start with the general tool in everyone's hands, because it costs little and shows you where the hours are going. Build a tailored agent only for a job that's repeated, measured and worth owning.

By Matthew Steele3 min read28 October 2026

A workshop office with one person at a laptop and a wall of printed job cards behind them, seen through a doorway
Illustrative scene, not a customer's premises.

What the general tool is for

A general assistant, the kind anyone on the staff can open in a browser, is good at the work that's different every time: a first draft of a difficult email, a summary of a long document, a plan for a meeting, a plain-English explanation of a contract clause, a second opinion. It's personal productivity. Some people will save 5 hours a week with it and some will never open it, and that unevenness is normal.

What it teaches you is worth more than what it saves. Within a month you'll know which people lean on it and for what, and that tells you where a tailored agent would pay for itself. That's the knowledge the strategy answer uses to pick the first three jobs.

What the general tool is bad at

It doesn't do the same job the same way twice, because a person has to ask each time and asks differently. It doesn't connect to your systems on its own, so the answer gets copied somewhere by hand. It doesn't enforce a rule, and you can't measure it, because nobody knows how often it was used or what came of it. For a job that happens 40 times a week, those are the things that matter.

What a tailored agent actually is

Strip the word "agent" back and what you've got is a small piece of software with six parts:

Part What it means
A defined job One thing, written down. "Read each new enquiry, draft a reply from the price list, put it in the rep's drafts folder."
An input Where the work arrives from: a mailbox, a form, a CRM record.
A connection The systems it may read and write, and nothing else.
Rules What it must never do, and when it must stop and ask a person.
An owner A named person who checks it, changes it, and can switch it off.
A log A record of what it did, so someone can check.

If you can't fill in all six rows, you're not ready to build it. That's the test. Most jobs people want an agent for fail at the first row, because the job hasn't been defined, or at the fifth, because nobody will own it.

From the personal assistant to the embedded agentA line from left to right. On the left, a personal assistant answering a question a day. Then a saved brief for a job that comes up weekly. Then a shared agent that runs daily on live data with a number. On the far right, an embedded agent that writes to systems. The shaded zone on the right marks where a tailored agent is worth building: jobs that repeat, have a number and an owner.Build a tailored agent hereA questiona dayA saved brieffor a weekly jobA daily jobwith a numberEmbeddedwrites to systemsGeneral assistantEveryone, from week one.Shows you where the hours are.Tailored agentOne job, six parts, an owner.Only once the job is known.
From the personal assistant to the embedded agent. Move right only for jobs that repeat and have a number on them.

The order for a smaller business

In the businesses we work with, this is the order that works:

  1. General assistant for everyone, with a one-page rule about what not to paste into it. Two weeks.
  2. Watch for a month. Ask people what they use it for.
  3. Pick the first job that repeats every week, has a number, and has a willing owner. Build one tailored agent for it. 6 to 8 weeks.
  4. Only when that one is used, measured and owned, start the second.

A smaller business that starts with three tailored agents before anyone has used the general tool usually ends up with three half-built things and a team that hasn't learned what the technology is like to work with.