Back to AI Focus

An independent review of your running AI workflows

I examine how AI workflows run day to day in small and medium-sized businesses, where controls fall short and what owners and managers should address first.

What I review

  1. Who can act, and who is responsible?

    I review which actions AI may take independently and which need a person’s approval. I check who owns each open case, whether approval requests actually reach that person, and whether the notification load makes important requests easy to miss.

  2. What can the workflows access and send?

    I check what the AI is allowed to read, change and send. I look at which accounts and access keys it uses and which data each tool receives. I also check whether restrictions on emails and payments actually work.

  3. How do you know the work is done?

    I check how failures and uncertain outcomes are handled, and whether ‘done’ is confirmed against the business system. I review monitoring of scheduled jobs, checks on the monitors themselves, and how fixed mistakes are prevented from recurring.

  4. Does the AI have the right business context?

    I check which recorded information about the company, customers and earlier decisions the AI relies on. I look at where the agreed reference is kept, who updates it and how corrections affect later work. These operating questions also matter when planning AI.

Two failures from my own operations

I run AI workflows myself, including at my own company KRUT GmbH. I have gradually improved my platform’s security safeguards through repeated checks and continue to check them.

The approval request did not arrive

In autumn 2026, I was meant to review and approve proposed payments on my phone each week. After a change to how messages were sent, the request did not reach my phone on at least four consecutive Mondays.

No incorrect payments were made, but critical processes need a check that approval requests actually reach the person meant to approve the payments.

The check that was green while broken.

A daily backup job reported success every morning for weeks, while a large part of company files was left out of the backup. I found and fixed this in August 2026.

Test whether your checks can detect a failure.

Define the scope

Discuss the scope of your review in the free introductory call.