What is an AI employee?

An AI employee is an AI system with its own role in the business. It prepares recurring office work in your systems and sends, books or changes nothing until the right person has said yes.

It is also called an AI coworker or a digital employee. ALEX is the AI employee Kapaciti builds in Skellefteå, Sweden.

Book a 30-minute callSee what ALEX can do today

An example with invented details. A draft reply with its source in view.
  1. 1 ReadsWhat comes in.
  2. 2 PreparesA finished draft with the right person.
  3. 3 Your yesNothing leaves without it.
  4. 4 DoneALEX finishes and saves the receipt.

You keep your systems. The draft waits for you, you read it, say yes and move on.

The difference between a chatbot, RPA, an AI agent and an AI employee

An AI agent carries out multi-step tasks. Whether it waits for your approval depends on how it is built. That is why the table compares three of the four questions: who acts, who approves and what is logged. The fourth, who is accountable, has the same answer for all five: the business.

KindWho actsWho approvesWhat is logged
ChatbotYouNo oneThe conversation
RPAThe robot, following a recorded pathNo oneThe run
Assistant in a tool, such as CopilotYou, in one tool at a timeYouDepends on the tool
AI agentThe agentDepends on how it is builtDepends on how it is built
AI employeeThe AI employee, preparing across several systemsThe right person says yesEvery step, in a signed log

Four tasks an AI employee takes on in an office

Four tasks and how far each has come today.

  • DemoFinance. Produce the monthly report from the books and check every figure against the source, with the source visible to the controller.
  • BuiltAdministration. Read incoming email, draft replies in your tone with sources and leave them for approval in the right thread.
  • DemoCase registry. Suggest how incoming documents are registered, find duplicates and watch deadlines, while the registrar decides.
  • DemoCustomer service. Handle first-line email, answer what is routine and hand over to a person when it is not.

An invented example: two letters arrive in the morning, the monthly report is done and a contract expires the same week. Everything is prepared by eight o'clock, with the material beside each draft.

An example with invented details. The morning's drafts gathered in one place.

Not sure it fits your team?

A thirty-minute call about your week. Then a shadow week where ALEX reads and suggests without touching anything, so you see the result before you decide.

Alexander replies by the next working day.

Book a 30-minute call

Common questions about AI employees

What is the difference between an AI employee, an AI agent and a chatbot?

A chatbot answers questions. An AI agent carries out multi-step tasks, and the word says nothing about who approves. An AI employee holds a role, prepares the work across several systems and waits for a yes from the right person before anything happens. The difference comes down to four questions: who acts, who approves, who is accountable and what is logged. ALEX is built from agents, but nothing they do leaves the building without your yes.

How does it differ from RPA and Copilot?

RPA follows a recorded path through the screens and stops when something looks different. An assistant such as Copilot helps inside the tool where it lives and cannot see the case in your other systems. An AI employee gathers the material from several systems and puts the draft forward with the source beside it, so whoever reads it can see what it rests on.

How do you hire an AI employee, step by step?

It happens in four steps.

  1. A thirty-minute call about your week and about what must never be touched.
  2. A shadow week where ALEX reads and suggests without being able to act.
  3. You see the result and decide.
  4. ALEX works for real inside the limits you set, and everything that leaves the building passes a person who says yes.

Do we need to replace our systems?

No. ALEX works in the systems you already have, and the connection is set up when ALEX is introduced. Microsoft 365, Teams and Slack can be connected today, and the books are read through SIE, the Swedish accounting file format. A direct connection to your ERP system is planned.

Who is accountable when an AI employee gets it wrong?

Accountability stays with the business, exactly as when an employee gets something wrong. That is why approval is built in. Nothing is sent, booked or changed until the right person has read it and said yes. Everything ALEX does is written to a signed log with an external timestamp that your auditor can verify independently. There, every yes can be traced to one text and one person afterwards.

Is an AI employee compatible with GDPR and the EU AI Act?

That depends on which personal data is processed, the data processing agreement and how the use is classified under the EU AI Act. Three things are built for it: a dedicated server per customer in the EU, a signed log with an external timestamp that your auditor can verify, and your choice of where the model runs.

Where is our data held?

Each customer gets a dedicated server in the EU, and your data is never shared with another customer. If you require it, ALEX runs in your own environment with your own model key. Every sub-processor, including the AI provider and where it operates, is listed openly in the privacy policy. The privacy policy is in Swedish for now.

What does an AI employee cost?

It depends on which tasks ALEX takes on, at what scale and in which systems. You get the price in writing after the discovery phase, before anything is booked.

Is ALEX live with any customer today?

No. Kapaciti runs ALEX in shadow mode on its own inbox. How far each task has come is shown in the list above.

Newsletter

The EU AI Act and what we learn building ALEX.

We email when something changes that affects Swedish organisations. Reply STOP to any email and you are removed.

The details are used for the newsletter only. No other mailings without separate consent.