Skip to content
Headless Agent Builder

Someprocessesareonlywaitingforsomeone.

We sit with the person who does the work and write the rules down. That specification becomes an agent that runs on an event.

Runs on an eventWithin limits you setA person when it must
Agent runs — AcmeMOCKUP · SAMPLE DATA

runs today

47

cost against limit

waiting for a person

3

CH.01·The problem

The rules are in someone's head

Every day someone repeats a process they already know by heart. It is constant rather than hard, and it occupies a whole person.

The knowledge of the process sits in the head of whoever does it. When that person leaves, it leaves with them.

While they are there, the process spends their hours instead of their judgement.

The same job, by hand, every day.

CH.02·Follow one event

From fired to posted, accounted for.

One event crosses the three filters and the gate. Watch every exit.

CH.03·The asset

The agent is disposable. The specification stays.

specification

  1. 01Read the invoice and match it to a purchase order
  2. 02Under the agreed limit and matched, post it
  3. 03Over the limit or unmatched, send it to a person
  4. 04Never pay. Posting is the last thing it does
  5. 05Record every run with what it cost

agent

reassembled from the same specification

The agent is disposable. The specification stays.

The agent is an assembled part. The specification is what stays written, versioned and auditable.

It outlives the tool that executes it and the person who wrote it.

A drawn Agent Builder screen. No product interface exists yet.

CH.04·The exchange

What you get, what we need.

  • Capacity without hiring

    On processes with stable rules, and only those.

  • The rules, written down

    The specification is yours, documented and auditable.

  • A cost per run you can know

    Every run has a cost, a record and a limit.

What we need from you

  1. One process, and the person who does it

    An hour with the person who handles it today is where the rules come from.

  2. The limits you want

    What it may spend, what it may touch, and the point at which it must stop and ask.

  3. Someone to work the queue

    What the agent cannot decide waits for a person. Someone needs hours for that queue.

  4. What runs alone, and what joins a queue for a person.

CH.05·Honestly

What the Headless Agent Builder is not

  • 01

    A robot that replaces people

    It takes the work with stable rules. Judgement stays with the person who had it.

  • 02

    An unsupervised flow

    Every run is recorded, and anything needing a decision joins a queue for a person.

  • 03

    A software licence

    What we sell is the assembly from a specification of yours, and the specification stays yours.

Pick one process and we will see whether it closes as rules

Book an hour. We bring the questions that turn a process into a specification, and we say no when it does not hold.

We connect nothing to your systems for a first conversation.

We use what you send only to reply about this. No lists.