Contact

AI agents

Projects, social media, code, competitors, reports Service 05 / 08 ← 0406 →

We hand repetitive work to an agent, a second agent checks the result, and a person always makes the decision. What each agent does, what it must not touch and when its work counts as done are all written down.

We start with one job; once we see it working, we add the second.

Project tracking
Reads the task board and sums up every morning what is late, what is pending and what finishes today.
Social media
Prepares a draft for each channel; the publishing decision stays with a person.
Code agents
Writes and tests on its own branch; a separate agent reviews.
Competitor tracking
Collects, with dates, the changes on competitors’ pages and in AI answers.
Reporting
Produces the monthly figures in the same template and checks them against the source.

05.1The work in three parts

Setting up an agent is half the job. The other half is seeing when it gets things wrong and fixing that.

aWhat we do

  • Choosing the jobWe find work that takes a few hours a week, can be written as rules, and has a result that can be checked.
  • Task definitionFor every agent I write the goal, inputs, outputs, limits and definition of done.
  • Checking layerWe set up a second agent that runs on different instructions from the one doing the work; it only writes findings.
  • ConnectionsWe connect to sources such as the task board, calendar, analytics tool and repository, with only the access needed.

bWhat we deliver

  • A working agentConnected to the tools where the work is done, with its first runs watched together.
  • Written rulesWhat it does, what it does not do, when it stops and asks.
  • LogFor every run: what the agent read, what it produced, who approved it.
  • Handover noteA short guide to turning the agent on and off and changing its rules.

cHow we measure

  • Send-back rateHow many jobs the checking agent sends back for fixes; this should fall over time.
  • Human correctionsShare of outputs a person changed before approving.
  • Time savedTime spent on the same work before and after the agent, from the team’s own records.
  • Error logThe wrong output, its cause and the line added to the rules.

05.2How an agent runs a job

Every type has the same four steps. Pick a type, then click the steps: its input, output and limits open up.

Workflow

Agent that does the work, agent that checks, human who decides

Diagram

05.3Related packages

Agents can be set up on their own or as part of another piece of work.

Setup

AI agents built for the project

One of the five types on this page, or an agent built for your work; with a checking layer and a log.

  • Task definition and limits
  • A second agent that checks
  • Close follow-up at the start

Visibility

Client dashboard

A dashboard showing on one screen what the agents are doing, what they sent back and what is waiting for approval.

  • Work waiting for approval
  • What was sent back and why

Security

Compliance and risk review

A review of which data the agents can reach, which access they run with and where secrets are kept.

  • Access list
  • Personal data and secrets check

Continuity

Regular reporting

Monthly reports from the reporting agent, with the figures checked against the source.

Write the job that takes up most of your week.

Who does it, how long it takes, where the result goes; write those three and I will tell you whether it suits an agent.