Product/AI employees

AI employees with real roles,
real limits, and someone accountable for them.

Not an assistant with a personality. A named remit, a defined scope of work, system access that is granted rather than assumed, and a person who answers for it.

Get a Demo→

What a role is

Three things, written down before anything runs: what the employee is responsible for, what work falls inside that, and which systems it may reach. Everything it later does is judged against those three.

You write it in ordinary words. Xalios turns that into the role, and you approve it before it exists.

remitOne named responsibility, in a sentence a manager would recognise

scope of workThe kinds of work inside the remit, each carrying its own trust level

system accessNamed systems, named scope, read or write stated separately

reporting lineOne named person, and an escalation path above them

Job description

awaiting your approval

“Match supplier invoices against purchase orders in the accounts mailbox. Query anything that doesn't add up with the supplier. Report to the accounts lead.”

scope

Invoice matching, supplier queries

system access

Accounts mailbox (read), ledger (read), order records (read)

trust level

level 1, in training

reporting line

Accounts lead

escalation path

Accounts lead, then head of finance

Approve the hireNothing runs until you do.

How it's briefed

A new employee is briefed the way a new starter is: shown where the work comes from, what good looks like, who to ask, and what to leave alone.

01

Where the work comes from

A mailbox, a folder on a drive, or a person handing something over. It watches the place, not a queue you have to feed.

02

What good looks like

Your own past work and conventions, and the corrections a person makes in the first weeks. Every correction is a piece of the brief.

03

What to leave alone

Stated as plainly as the remit. What sits outside the scope is not a gap to be filled by initiative.

One piece of work

What it does between
arriving and done.

Between arriving and done there is a sequence anyone who has done this work would recognise: read it, find what it belongs to, decide whether it holds, then finish it or stop and ask. This is an AI employee working through that on a matching job.

An invoice against an order. A claim against a policy. A renewal against the contract. A delivery note against what was shipped. Whatever the work, it stops rather than guesses, and it leaves the same kind of record behind.

It notices the work arrive

It watches the place work already lands: a shared mailbox, a folder, a handover. Nobody forwards it to a special inbox or logs it into a queue first.

It reads what arrived

Whatever shape it came in. Every sender lays theirs out differently, so it reads the document rather than filling a template.

It gathers what this relates to

The earlier records this one should agree with, the policy that governs it, and what was decided last time something like it came through.

It works out whether they agree

Most of the time they do, and this is quick. The work is in the times they do not.

Two records disagree. Is that a mistake, or did something legitimately change between them? It checks what was true on the day, not what is true now. If it cannot tell, that is a reason to stop rather than to guess.

It finishes it, or it stops and says why

If everything holds, the work is done and filed where you would look for it. If it does not, it stops with the disagreement named, the evidence attached, and the question a person actually has to answer.

What it can reach, and what it cannot

Access is granted, never assumed. Each system is named in the job description with the scope requested and read or write stated separately. Nothing inherits access from anything else, and revoking it takes effect on the next piece of work rather than at the next review.

Where a person cannot see a document, neither can the employee working on their behalf.

Who manages it

Every AI employee reports to a named person. That person approves the role, sees the queue, decides what it proposes, and is the one asked why. Promotion and demotion are theirs.

If nobody will put their name to it, it does not get hired. That is deliberate.

When work changes hands

Work moves the way it does between colleagues, and the moment it changes hands is part of the record rather than a gap in it.

To another AI employeePassed with what it found and what it could not settle. The receiving employee works within its own scope and level, never the sender's.

Back to a personWith the reason written at the moment it escalated, and the documents it was working from attached at the version it used.

From a personSomeone forwards a document or assigns an item. It arrives as work, with the sender recorded as the origin.

NextAutonomy is earned, one kind of work at a time.The five levels, what each one means for a piece of work, and the floors no configuration can weaken.Trust levels →

Write one job description, on one real queue, and watch a fortnight of proposals before anything acts.