Tenxora · In development and validation

AI employees need a role. And a responsible human.

An AI employee is our term for a software participant assigned a business role, permitted work and an accountable human manager. It is not a person or an independent source of company authority. Tenxora is developing the shared controls that would let these roles work alongside a team.

What an AI role should make explicit

Illustrative role card: Payables AI employee

Reports to the Finance Manager

Permitted work: collect invoice context, compare an invoice with a purchase order and receipt, draft a match summary and prepare a proposed payment batch.

Access: only the supplier and purchasing records needed for its assigned work.

Approval boundary: every payment requires an authorized person. Preparing a payment batch grants no authority to send money or approve its own work.

Stop and escalate: missing receipts, inconsistent quantities, changed bank details or a task outside the role’s limits must be brought to a responsible person.

This card illustrates the intended design. It does not claim a production service or a finalized permission configuration.

How a person stays in control

A reviewer needs more than an “approve” button. The proposal should show the records used, the suggested action, unresolved questions and the expected effect. Where a separate decision is required—such as approving a supplier payment—the workflow should preserve it rather than treating an earlier request as blanket authorization.

If work fails, the team should be able to see whether any action completed before deciding to retry. Repeating a payment or posting because a response was unclear would create a new problem.

AI employees and AI agents

“AI employee” describes the intended business role. “AI agent” describes a technical pattern in which a model can select steps and use tools. A role could combine models, predefined workflows and ordinary automation. Read what AI agents are and how they work for business for the educational explanation.

Start with a bounded process

Useful validation starts with a real task, named owner, clear evidence and explicit completion criteria. Tenxora is in development and validation; the interactive homepage uses fictional data and scripted responses. It does not perform live business actions.

See the broader vision or follow an invoice across the connected workspace.

Which workflow would you improve first?

Tell us about your team and the work you want help with. Joining the waitlist does not commit you to a purchase or guarantee pilot access.

Join the waitlist ↗