Kenmark T.
AI Systems & Automation Builder
AI Systems & Automation

I turn messy business processes into systems that just work.

You know those little tasks that keep your business running, the ones that live in someone's head and only happen when they remember? I build systems that handle that stuff reliably, so it stops depending on anyone's memory. And I'm careful about where a human should still make the call.

What I do

Three ways I can help

Most of my work starts the same way. A process that used to fit in someone's head has gotten too big for it, and now you're seeing the cracks: stuff slips, things get typed wrong, work waits on one busy person. Here's where I come in.

Figure out what's actually broken

Before building anything, I map how your work really flows and find where it leaks or breaks. Sometimes the fix isn't even automation. You'll know either way.

Build it (or fix what's already there)

I build the workflows that quietly handle the repetitive stuff, and I'm good at hunting down the weird failures that only show up once something's actually running.

Put AI to work without the risk

AI can do real work for you, but only with the right guardrails. I add the checks that keep it safe and keep a person in the loop wherever judgment actually matters.

Selected work

A case study

AI Content Operations · Regulated finance

Finding the hidden failure in an AI content pipeline

A content system was passing all its own checks and still letting bad facts slip through to a human. Turned out it was checking the wrong thing. Here's how I found it and fixed it.

Read the case study
Background

How I got here

Before any of this, I worked as a process controller at VidaXL, a big Dutch e-commerce company that runs its own warehouses. My job was watching order data as it moved from the website through their systems, into SAP, out to the warehouse, and onto the carriers. One bad handoff between any two of those and a whole order could just stall.

That job taught me to watch the seams. Not the systems themselves, but the gaps between them, where things quietly go wrong and nothing tells you until a customer complains. That's the same instinct I bring to automation now. The hard part was never connecting the tools. It's spotting the thing that'll break once it's actually running, knowing what you should not hand off to a machine, and keeping a person in the loop right where it counts. I build stuff to be run day after day, not just to look good in a demo.

Contact

Got something that's outgrown one person?

If your operations are starting to creak, things slipping through, work that only happens when someone remembers, that's exactly the kind of problem I like. Tell me what's driving you nuts and I'll tell you honestly if I can help.