53 AI agents? Why the number says nothing about your AI maturity

Ralf Metz & Andreas MesserliRalf Metz & Andreas Messerli·25 July 2026·5 min read
Beitrag 1 53 KI Agenten v2

Perhaps you don’t have too few agents. Perhaps you have too little clarity.

The number that helps nobody

In conversations with management teams, one number comes up a lot at the moment. How many agents are running in your organisation? Twelve. Thirty. Fifty-three. The number is mentioned the way the number of servers used to be, with a mix of pride and quiet uncertainty about whether that is a lot or a little.

The question is understandable. It is just not the question that will get you anywhere.

Because the number does not answer what you actually want to know: is our use of AI responsible? Do we know what is running? And will we notice if something goes wrong?

A name is not a unit of analysis

The most common error in thinking lies in how things are cut. Systems, product names or personas get counted. What actually happens are individual workflows.

An example. “Emma” is the AI in sales at your company. Emma is a name. Behind it there may be three different workflows:

  • She turns keywords into the text of a quote. The result stays internal and is checked before it is sent.
  • She accesses the customer history and suggests price levels. In doing so, she influences a decision with financial consequences.
  • She answers enquiries outside office hours on her own. The result reaches the outside world without prior checking.

These are three different matters, with different risk, different data access and different need for responsibility. In your count, it is one agent.

Whoever takes the name as the unit gets a picture that is either too reassuring or too alarming. Both mislead. The unit you need to talk about is the individual workflow.

The relevant unit is not the agent, but what it does in a specific process.

The blind spot we already know

This pattern is not new. We know it from agile transformations.

Organisations introduce Scrum, Kanban or SAFe. The processes visibly change. Teams iterate, hold retrospectives, deliver faster. And yet one question often stays unanswered: who makes which decision, and on what basis? Agile methods improve processes. They do not automatically change the understanding of leadership, and without that there is no agile leadership.

With AI, something similar happens, only faster. Tools change workflows. They do not clarify who may decide, who checks and who has to intervene. Whoever counts the tools and concludes maturity from that is measuring activity and overlooking the leadership question.

Why changed processes alone do not yet create a clarified order of decision-making is described in more detail by Andreas Messerli in the article “Kollegiale Führung, ein dezentrales System für komplexe Zeiten” (Wirtschaftsinformatik & Management, 11 March 2026): doi.org/10.1365/s35764-026-00592-7

Five questions per workflow

Instead of counting agents, you go through your workflows. For each one individually, not for the product name:

  1. Task. What task does this workflow carry out, in which process?
  2. Data access. What data does it access, and who approved this access?
  3. Decision impact. Does its result influence a decision with consequences for customers, employees or finances?
  4. Checking. Which person checks or signs off before the result takes effect?
  5. Intervention. Who may change, limit, pause or switch off the workflow, and does that person know they are allowed to?

In our experience, the fifth question is the one where it goes quiet.

If you can answer these five questions for every workflow, it is secondary whether there are five or fifty-three. If you cannot answer them for a single one, that very workflow is your next topic.

Clarity instead of maturity level

We deliberately do not speak of a maturity level. A scale suggests that more is better and that there is a general target state. Both mislead. A company that has properly regulated three workflows is not more backward than one with thirty unregulated ones.

Clarity can be checked on three levels:

  • Technically. Can a person judge whether the result is usable? Whoever cannot assess an AI analysis on its merits cannot effectively approve it either.
  • Organisationally. Is it settled who decides, who escalates and which procedure applies? And is that documented in a way a new person can follow?
  • Personally. Does anyone dare to question a result that sounds plausible? Without that willingness, roles and approvals remain empty shells.

If one of these levels is missing, the next automation will not help.

Why this is not bureaucracy

The most common objection is: we are an SME, we have no capacity for governance exercises.

The objection is understandable, but it misses the point. This is not about a rulebook, but about a shared list. Whoever goes through the five questions for ten workflows gets far in one focused session. What comes out of it is not a document for the filing cabinet, but a shared view of what is clarified and what is not.

Something else often becomes visible too. Some of these questions were already unanswered before AI. Who may give which discount in sales may already have been unclear. AI did not create the gap. It only makes it harder to overlook.

That is not bad news. It is the most useful insight you can take away from a session like this.

For your next leadership meeting

Take a single AI workflow that is running in production at your organisation. Not the most harmless one and not the biggest. Go through the five questions.

If you arrive at a shared, concrete answer to all five, you have gained clarity. If not, you have found your next topic, and one you can work on.


Background reading: How are companies changing in the age of AI?
Next post: Who actually decides here? The question that comes before every AI project


Ralf Metz & Andreas Messerli
AuthorsRalf Metz & Andreas MesserliFounders of me&me · More about us
Next step

Ready for the next step?

In a free, no-obligation initial conversation, we look together at what fits your organisation. Concrete and to the point.

30 minutes. Free. No obligation.Further reading