LiveVulnWatch and ContentDesk are in production

Agents that do the work.
Officials who approve it.

An AI workforce for South African public institutions. Agents handle the repetitive work: leave, correspondence, patching, publishing. A named official signs off on every binding action.

Request a demo Browse the agents

Built for PFMA and MFMA institutions · Every approval logged against a named person

Describe the work, and see which agent comes closest.

Process a leave request

Persal · Outlook · Teams

Threads

Process the leave request from employee 4471, 5 days annual leave, 22 to 26 September.

You · 9:02 AM

Built for the institutions the PFMA and the MFMA already name

National department
Provincial department
National public entity
Metropolitan municipality
Local municipality
Higher education institution
SETA

The catalogue

An agent for every desk that does the same thing every week.

Each one connects to the systems the institution already runs and stops at the same place: the moment something becomes binding.

See every agent

See agents at work

Four desks, one Monday morning.

Every thread below starts with somebody asking for something in plain English. Watch where each one stops. That pause is a named official, and it is the whole product.

People Desk
Persal · Outlook · Teams
01
Check the balance, apply the leave policy, and hand the supervisor one decision to make.
Process a leave request
It works the system, not a spreadsheet about the system
The agent signed in to Persal, read the real balance and wrote the real record. Nothing was re-keyed into a side file and nothing was exported to be imported later, which is where most automation in an institution quietly goes wrong.
Executive Assistant
Outlook · Teams · Calendar
02
Your calendar, your unread mail and your open tasks, in one brief, before seven.
The morning brief
Three systems, one answer
A calendar, a mailbox and a task list are three places to look before seven in the morning. This is one place, and the second request turned it into something nobody has to ask for again.

Governance

What an official is actually agreeing to

The part that has to survive an audit, not a demo.

It signs in as itself
Its own account, its own permissions, in the systems you already run. You can see what it touched and take the account away in an afternoon.
It stops before it binds
Capturing leave, sending a letter, publishing a page. The agent prepares; a named official decides. That order is not configurable.
The record names a person
Every approval is logged against the official who gave it, not the agent. When someone asks who authorised this, there is an answer.

Correspondence
Outlook
03
A reply written in your voice, waiting in your drafts. Nothing sends without you.
Draft a reply for sign-off
Your voice, your outbox, your name
The agent writes; you send. An institution's correspondence is a record that can be produced in an enquiry years later, so the last click stays with the person whose name is at the bottom of it.
Project Desk
ClickUp · Teams · SharePoint
04
What is overdue, what is blocked, and the chase-ups already drafted for approval.
Where the project stands
Once is a favour. Every Monday is a colleague.
Every thread here ends with the same move: say it again, and the one-off becomes standing work at a fixed hour. That is the difference between a tool you remember to use and work that simply gets done.

Five more, one per agent in the catalogue: patching a portal, publishing a statement, filing registry mail, assembling a monthly pack, watching the public sites.

From the blog

Notes from the work

All posts

15 September 2026Governance
Why every agent stops for a person
The approval gate is not a safety feature bolted onto the product. It is the product, and here is how we think about where it sits.
Agent1000 · 4 min read

Give an agent its first task.

Tell us the work that eats a morning every week. We will show you which agent takes it, and exactly where it stops for you.

Request a demo Become a reseller