Sign in Start free
Back to the journal

Your first agent in a single afternoon

A plain starting point for teams who know they do too much by hand.

Nov 4, 20266 min read

Most teams do not need a big automation project. They need one agent that runs on its own and hands back a few hours every week. Here is how to choose it, build it and learn to trust it, all before the end of the day.

1. Write down the work that repeats

Spend twenty minutes listing what your team does the same way every time: moving data from one tool to another, sending the same follow-up, sorting requests as they arrive. Then ask three questions about each item:

  • Does it happen more than ten times a week?
  • Does it follow the same steps every time?
  • Would anyone miss doing it by hand?

2. Score what you found

Not every repeat task makes a good first agent. A short scorecard keeps the choice honest:

TaskHow oftenClear rulesRisk if wrongFirst agent?
Hand new leads to an ownerDailyYesLowYes
Tag and sort support ticketsDailyYesLowYes
Send the weekly status noteWeeklyMostlyLowYes
Approve refundsWeeklyPartlyHighLater, with review
Negotiate renewalsRarelyNoHighKeep it human

Start at the top: frequent, predictable and easy to undo.

3. Write the steps before you build

Describe the agent as a short list: what starts it, what it decides and what it leaves behind. If it takes more than five lines, it is too big for a first try.

Example: when someone fills in the demo form, look up the company, score it by size and region, give it to the right rep and post a two-line summary in the sales channel.

4. Let it run next to the old way

For the first week, the agent runs while a person still checks the result. Edge cases show up early and the team gets used to the idea.

  • Compare the agent's result with the manual one
  • Write down every case it handled differently
  • Adjust the brief and run it again

5. Measure, then pick the next one

Track how often it runs and how much time it saves. Once the numbers are clear, the next agent is an easy decision, and usually the team suggests it before you do.