Skip to content
Nulladmin
← Back to the blog

What turns an AI into a colleague?

· Author: Gábriel Pielka · 6 min read

  • SMB
  • AI agents
  • AI adoption
  • automation

At most companies, artificial intelligence today still amounts to a simple chat window. We type in the question, we get the answer, and the process closes there. That is a useful tool, but nothing more.

There is another level, though, and the gap between the two is far deeper than you would think at first. A tool is passive: it waits to be asked. An AI colleague, by contrast, carries the task it was given through to the end on its own, and comes back to you only when it is done, or when it runs into something you need to know about.

In an earlier post I described how I built four such digital assistants: a developer, a correspondent, a coordinator and a content writer. This time I want to cover what that piece left out: what is the real secret of making it work? I have three key conditions, and two of them have almost nothing to do with technology.

Its own account, with dedicated access

The first condition is perhaps the least spectacular, and yet everything stands or falls on it. A digital colleague needs an account of its own. It must not work under your identity.

There are two strong reasons for this. The first is traceability: if the AI assistant signs in under your name, it becomes complicated afterwards to separate what the system did from what you did. The second is security and scope: with an account of its own, you can meter out permissions with engineering precision. It reaches only what its work genuinely requires, and if something goes wrong, its access can be switched off with a single click.

Here is what this looks like in practice at my end: the agent that runs my correspondence writes under its own name and sends me a copy. Whoever receives the message can see who it came from. There is no deception in it, and I can see the correspondence too.

Many people never think of this step, and yet in the long run this is what keeps the whole arrangement sustainable.

A machine that never sleeps

The second condition rests on a simple truth: a browser tab left open is not infrastructure. Close it, and your digital colleague stops with it.

Whatever reviews the incoming mail at seven in the morning has to run at seven in the morning, including on the days when you are travelling or on holiday. That takes a machine that stays switched on. In my case a dedicated machine does this, but cloud solutions work just as well.

It is worth saying that this is not a question of computing power. We are not talking about a high-performance machine, and certainly not about a server room. What matters is continuous, reliable availability: a scheduled task is only worth something if, at the appointed time, there really is something there to start it.

The conductor who designs the process and draws the boundaries

The third condition is the expertise I provide, and this is precisely the link in the chain that cannot be automated.

A digital assistant will not work out its own job, and that decision must not be left to it either. The real intellectual work here is to think the process through step by step, to describe the tasks precisely, and to draw the boundaries: how far may the AI go on its own?

That last part is the most critical point. At my end, every outgoing message and every public piece of content is subject to mandatory approval. The assistant prepares the material and shows it to me, and I am the one who gives the final confirmation. This is not needless caution, it is what makes a well-working system dependable. Because I built a checkpoint into the risky points, I can hand the lion’s share of the work to the AI with a clear conscience. The industry calls this the human-in-the-loop approach. In my experience, this is what makes artificial intelligence genuinely reliable, rather than slower.

This is not where you should start

Now comes the part you rarely read from people who sell services built on artificial intelligence.

Everything I have described so far is the top of the range. At Nulladmin, too, this is the most premium service, and let me be completely honest with you: most companies should not start at this level. Creating those three conditions calls for a serious investment. That investment only pays off if the organisation already runs a stable, recurring process whose volume and frequency justify this level.

If you are only beginning to explore the possibilities, the first step is far simpler and far more cost-effective. For most businesses, a well-structured project on an artificial intelligence workspace is more than enough. In practice this means that the company’s documents, templates and internal policies all end up in one shared space. The team can then work with an assistant that knows the company’s context inside out. This needs no machine of your own running around the clock, and no continuous IT operations.

One thing, though, cannot be missing even at this entry level: the third condition. Here too, someone has to build the framework the assistant works within. You have to define what counts as an official template, what it may communicate towards clients, and when it has to stop and ask instead of guessing. This is exactly the same intellectual work as with digital colleagues, only on a smaller scale. AI on its own does not know a company’s internal rules, and it will not work them out by itself.

This approach costs a fraction of developing a standalone digital colleague, and yet it brings measurable time savings in everyday work almost immediately. On top of that, practice will show you which recurring processes are genuinely worth building a dedicated agent for later on. Starting from the other end is much harder and considerably more expensive.

In summary

Building a digital colleague does not come down to a software subscription. It takes an account of its own, a machine that never sleeps, and a leader who designs the processes and then draws the boundaries. Two of those three conditions are management and organisational decisions, not technology questions.

This is the upper tier, though, and it is very rarely where you should begin. A well-structured internal company project will already take you far enough to see in black and white where the greatest return lies in your organisation.

If you would like to know which level makes sense at your company right now, and exactly which process is worth starting with, request our free assessment and let us plan the next step together.