AI agents that work like employees,
with humans who make the decisions.
An AI workforce for South African small and medium businesses and public institutions. Agents handle the repetitive work: leave, correspondence, patching, publishing. A human signs off on every binding action.
How an agent works
Process a leave request
ThreadsProcess 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.
- LeaveDesk
Checks each leave application against the leave determination and the balance on Persal, and routes it to the line manager and HR.
- ClaimsDesk
Builds travel and kilometre claims from the approved trip, checks every receipt against the rates in force, and pre-reviews each claim for Finance.
- VulnWatch
Checks the software behind an institution's custom applications every day and reports what needs patching, most urgent first.
- ContentDesk
Turns an emailed request into a web page, and holds it until the officer who asked for it approves the preview.
- RecordsDesk
Files incoming correspondence against the right case record and tells the registry clerk what it filed.
- ReportPack
Assembles the same monthly reporting pack from the same sources each month and sends it to the responsible manager to sign off.
- SiteWatch
Watches an institution's public websites for downtime, expiring certificates and changed pages, and says which one broke.
- Azure Ops
Reads an institution's Azure cost and usage every morning, finds where money is being wasted, and puts each fix to a human as an approval card.
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 human, and it is the whole product.
Check the balance, apply the leave policy, and hand the line manager and HR one decision each.
It works the system, not a spreadsheet about the system
Executive Assistant
Your calendar, your unread mail and your open tasks, in one brief, before seven.
Three systems, one answer
Governance
What you are 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 human decides. That order is not configurable.
The record names a person
Every approval is logged against the person who gave it, not the agent. When someone asks who authorised this, there is an answer.
Correspondence
A reply written in your voice, waiting in your drafts. Nothing sends without you.
Your voice, your outbox, your name
Project Desk
What is overdue, what is blocked, and the chase-ups already drafted for approval.
Once is a favour. Every Monday is a colleague.
Seven more from the catalogue: booking sick leave, claiming for a trip, patching a portal, publishing a statement, filing registry mail, assembling a monthly pack, watching the public sites.
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.