One system goes in. After that, every job is one more agent on it.

You start with one job, the one costing you the most people. Every job after it runs on what gets built underneath.

What we build

Four things go into every install. Not one of them comes out of a box.

A product you buy has the same features for everyone and no idea what your systems hold. These are built out of what yours actually hold, and they go in before any agent does.

Reading your systems

One layer, four sources

ERP · nobody has the password

Shared drive · 2,410 files

WhatsApp · the price agreed

Rate card.xlsx · merged cells

One layer, current every night

Reading

0%

0%

Reading your systems

One layer, four sources

ERP · nobody has the password

Shared drive · 2,410 files

WhatsApp · the price agreed

Rate card.xlsx · merged cells

One layer, current every night

Reading

0%

0%

The data layer

All of it read into one layer, which is most of the engineering and the reason this cannot be bought.

ONE WEEK OF THIS JOB, OBSERVED

Request arrives in the shared inbox

4 min

Priced against the exceptions one person knows

1h 40m

Waits for one approval

3 days

Quoted, then chased on no schedule

25 min

Won or lost, logged or not at all

10 min

The waiting is the largest step and nobody had timed it. Four customers are priced as exceptions, and none of them are in the SOP.

ONE WEEK OF THIS JOB, OBSERVED

Request arrives in the shared inbox

4 min

Priced against the exceptions one person knows

1h 40m

Waits for one approval

3 days

Quoted, then chased on no schedule

25 min

Won or lost, logged or not at all

10 min

The waiting is the largest step and nobody had timed it. Four customers are priced as exceptions, and none of them are in the SOP.

The runbook

The judgement your best person carries, written down. Not the SOP: the SOP describes the clean case. The person who does the job corrects it before anything is built.

Run log

The last three runs

The investor report

Done

The counterparty file

Waiting on a person

The payment run

Running

Run log

The last three runs

The investor report

Done

The counterparty file

Waiting on a person

The payment run

Running

The workflow

The whole job, starting on its own. Every run is logged: what it did and on what basis. The first you hear is when the work is done, or when an exception needs you.

Card Image
Card Image

The delivery

The result lands where your team already works, not in another tab nobody opens. We build against whatever you run, including the system nobody has got round to replacing.

Your agents run on eight layers you never have to build, buy or keep alive.

When your work needs one of them to behave differently, we change the layer. Below is each one, and what it saves you building yourself.

1
ExperienceOne screen holds everything waiting on you.
Web / adminCitations / artifactsStreamingApproval queue

Finished work sits in one place with the sources beside it. You approve it or send it back, and the run carries on from where it stopped.

Otherwise you buildthat screen, and the record of who approved what and when.

The eight layers
1Experience
2Orchestration
3Governance
4Retrieval
5Model
6Data integration
7Platform services
8Infrastructure