EmAGI
English
Docs · index

One digital employee or several

Any single piece of work can be done well only with the whole context: the company, its clients, its decisions and goals. That is why we recommend giving a digital employee a whole area of work, not a job title.

Why one employee for a whole area?

A digital employee who runs an area of work as a whole keeps all of that context, so everything it needs is already at hand. Split the work among narrow agents, and they would have to keep retelling the context to each other, and the work would turn into correspondence instead of results.

Such an employee does not get overloaded: its memory brings up only what each task needs.

Why do people split work differently?

People split work by job title: designer, developer, marketer, manager. They have to, because one person cannot physically do everything or know everything.

A digital employee has no such limit. It runs dozens of tasks at once, and all of them share one memory and one understanding of the work. There are no separate agents to train and keep up to date.

When do you need a second employee?

In two cases. The first is another area of your work. An area can be a company, a single business, a project, your family, your personal finances or something else. One employee should not be spread across dozens of unrelated areas.

The second is security. An employee who talks to outsiders does not need access to everything, and the one who holds valuable information should not talk to third parties.

What does this look like in practice?

An owner runs a web studio and a grocery delivery service, and also has family matters and a personal investment portfolio. Four employees fit:

Four employees for four areas, not a designer, a developer, a marketer and an accountant.

How does EmAGI do it?

We work this way ourselves. One project, three digital employees, and security is what separates them. Aurora runs the project as a whole: the platform, the product, marketing. Leo talks to third parties and finds new customers, so he does not have access to everything. Nova helps clients create their employees, and clients trust her with personal information, so she works separately too.

How do you decide how many you need?

List your areas: businesses, projects, personal matters. Then think about where separate protection is needed: who will talk to outsiders, and which data must never leave. One employee per area, plus a separate one wherever security calls for it. Nova, our agent who creates employees, will help you work this out in a conversation.

Should all tasks go in one conversation?

We advise against it. Even when one employee runs a whole area, it is better to split the tasks into topics or separate chats, for example one topic per project. In a single shared conversation, tasks from different projects get mixed up and get in each other's way. In separate topics every task has its own thread, nothing gets lost, and the employee works on them at the same time. Its memory is shared across all topics, so it keeps the context of the whole area. How to set up topics is explained in Topics: one thread per project.

Is this a strict rule?

No. It is a recommendation and our professional view. Businesses and situations differ, and you always arrange your employees the way that suits you.