Get in touch
Portfolio

AI in day-to-day ERP, without giving up control.

This is what I work on: agents, automations and tools around support, documentation, costs and integration. Sorted by the problem they solve. Perhaps you’ll recognise yours.

One principle runs through everything

The agent does the work, a person signs it off. Nothing goes to customers, colleagues or into the system before someone has approved it. What the agent did can be traced.

How I show what I show

Much of this came out of my professional practice. From that work I describe the pattern: which problem, which flow, which guardrails. Names, figures, code and screenshots stay where they belong. My own projects I show openly, and some you can try right away.

From practiceOwn project

Our support is drowning in the same questions

Key users and IT answer the same question for the tenth time, and the documentation falls behind with every update.

From practice

Support that learns from every case

The situation: A problem comes back and someone starts searching from scratch again. Last time’s fix sits in a closed ticket nobody can find.

  1. Question in the team chat

    Someone reports a problem in the support channel, just as before.

  2. Search with a source

    The assistant searches the ticket system and wiki, then the vendor’s documentation.

  3. Answer and follow-up

    It answers with a source and asks whether that helped. It doesn’t guess.

  4. Escalation when needed

    If it didn’t help, it opens a ticket with a description and the screenshots from the chat.

  5. Knowledge stays

    From solved cases it writes troubleshooting pages into the wiki. Where a guide is missing, a draft is created.

  6. First steps for the next caseNext step

    When a similar case comes in, it attaches the matching page straight away as a first course of action.

Guardrails:
  • Answers only with a source
  • Escalate instead of guessing
  • Wiki pages as drafts for review

We want AI, but safely

The worry is justified: data leaks, an agent sends something out, nobody knows what it did. Guardrails help, bans don’t.

Own project

Guardrails I use every day

The situation: AI should help, but confidential names must never show up anywhere, and nothing may go out unchecked.

  1. Block list

    Confidential terms sit in a list outside the code. Every output is checked against it automatically, PDFs included.

  2. Check in the pipeline

    If the check finds a hit, nothing gets published. That applies to this website too.

  3. Approval before sending

    Emails, meeting replies and publications only go out after approval in the chat.

  4. Scheduled runs can’t change themselves

    Automated routines are not allowed to change their own rules.

  5. Goal check

    At the end of every task the agent checks whether the goal was really met, instead of just reporting “done”.

Guardrails:
  • Redact, don’t hope
  • Approval before anything goes out
  • Traceable logs

We don’t really know what it costs

Invoices arrive by email, timesheets as spreadsheets, and at month end management asks.

Our systems don’t talk to each other

ERP, shop, shipping and accounting: each fine on its own, together a patchwork.

We lose time on routine

Inbox, meetings, back-and-forth. None of it is hard, all of it together eats the morning.

A living page instead of a spreadsheet attachment

I like to deliver results as an artifact: a page an agent creates and keeps current, and that people read, comment on and approve.

Dashboard
Numbers at a glance, kept current by a routine
Cockpit
Monitor how agents are running
Report
The monthly report without manual work
Map
Understand data flows and connections
Presentation
A decision paper, exportable as PowerPoint or PDF
Script and handout
Talk and handout from one source
Calculator
Play through scenarios yourself
Workbench
A tool instead of a document, with tasks for the agent
Guide
User documentation you can share
Checklist
Make sure quality is right before handover

Agent, workflow or interface?

With Claude, ChatGPT and MCP, a lot can be done today without a classic workflow tool. For processes that run thousands of times the same way, scheduled and subject to audit, a fixed workflow or an interface is often cheaper and safer. Which solution fits is the real architecture question. I’ll answer it with you.

Lab

My own products, where I try out what AI makes possible in a short time today.

Do you recognise your problem?

Tell me where things are stuck. I’ll tell you which building block fits, and whether it needs AI at all.

Request a conversation