ClaudeLab

Perspective

Why an assistant does not yet automate the process

Most businesses already pay for an AI assistant - through Microsoft 365, through a team subscription, through individual seats. The question of why a project is still needed is a fair one. The answer lies not in the quality of the model but in who starts the routine.

Last updated: July 2026

01

Two different things

Assistant
Automated process
A person sets it off
An event sets it off - an email, a document, a date
Sees what is in the window
Sees ERP, mailbox, file store and portal
Answers
Writes back into systems
The result lands in the clipboard
The result lands in the case file
Everyone uses it differently
Runs the same for everyone, logged and traceable

Both are useful, and one does not replace the other. An assistant lifts the productivity of individuals. An automated process takes a routine off the business. The difference becomes visible through a simple test: does anything happen when nobody is in the office?

02

Why the assistant stops at the connection

An assistant inside a word processor knows the document it is sitting in. It does not know the last thirty comparable jobs in the ERP, nor the supplier's current tier price, nor the fact that this customer has had a special rate for two years.

That is exactly where the value arises - and exactly where the work sits. The connection to your systems is the most demanding part of a project and the reason a subscription does not include it: your system landscape exists only once.

The assistant can do everything that is on the screen. The process needs what is not on the screen.

03

What that means for your order of play

Exhaust the assistant first
If the licences are paid for anyway, that is the cheapest first step. A serious introduction gets more out of it than most businesses expect.
Watch where it stops
The points at which your people still switch between windows, copy and look things up are the candidate list for the first project. It writes itself.
Then build the routine, not the tool
From here on it is about connection, scope of action, releases and acceptance - the questions a subscription cannot answer.

Frequently asked

We already have Microsoft Copilot. Do we still need anything?

For work on the document itself, rarely. As soon as a routine is meant to run without a person setting it off, or needs data from several systems, the assistant's territory ends - it sees only what is in the window.

Does an automated process replace our assistant?

No, the two run alongside each other. The assistant stays the tool at the desk; the process takes over the recurring routine behind it.

Do you work with a particular vendor?

We are neither a partner nor a reseller of any model vendor. Which model is used is decided by the use case - and by the question of where the data may be processed.

Tell us where your time goes.

In the audit we record the process, work out what is worth automating, and you get a plan with fixed prices - credited against the build if you go ahead.