AI engineering · automation

AI automation that survives production

I build production-grade AI automation and LLM features — and ship them fast with small, AI-augmented teams. Fifteen years of engineering behind every system, not a demo.

Remote · Europe & AsiaTaipei time · EU hoursDutch & EnglishAvailable for new work
Selected proof

Most "AI" is a demo. I ship the version that holds up.

Everyone is adding AI right now, and the demo was never the hard part. The hard part is the 20% that decides whether anyone still uses it once the novelty wears off: retrieval that stays current, evaluations that catch regressions before your users do, and automation that fails safe instead of silently doing the wrong thing. I've spent fifteen years shipping production systems, and I hold AI to the same standard.

I help teams in two ways.

AI-accelerated delivery

A small team that leans hard on AI throughout the development loop can move like a much bigger one. I'm doing precisely this today — building a full creator platform from scratch (subscriptions, courses, live streaming, billing) with a handful of people and an AI-first workflow, shipping in a fraction of the usual time. If you want to move faster without ballooning headcount, this is the model.

Production AI & automation

I build the AI features and automations that actually run in production: LLM-powered workflows, retrieval over your own data (RAG), evaluation harnesses so changes are measured rather than guessed at, and agentic automation that takes real work off people's plates. I've shipped AI features inside a live consumer product on AWS Bedrock, and wired LLMs into systems where both correctness and cost matter.

I build the tooling, not just call the API

Here's what separates me from the wave of "AI consultants": I build the developer tooling that AI agents run on. Under Arjia Labs I maintain open-source tools like clu, a local-first tracker for coordinating AI coding agents, and yori, a library for managing AI prompts, agents, and skills. I work at the layer beneath the chatbot — which is exactly the layer that breaks when you try to put agents into production.

How I work

Proof over promises. I'll tell you where AI genuinely helps and where it's the wrong tool, scope a concrete first deliverable, and ship something measurable instead of a slide deck. Boring, reliable foundations; AI where it earns its place. If you want to ship faster with AI — or get a real AI automation into production without the hype — let's talk.

Frequently asked

What do you actually mean by "AI automation"?+

Using LLMs and agents to take real, repetitive work off people — document and data processing, support and ops workflows, retrieval over your own knowledge, and decisions that used to need a human in the loop. The goal is leverage, not a chatbot bolted onto the side.

Can a small team with AI really replace a big one?+

It can't replace deep domain experts, but a handful of people who lean hard on AI in the development loop can deliver what used to take a much larger team. I'm doing exactly that right now.

Do you build with LLMs and agents in production, or just prototypes?+

In production. Retrieval (RAG), evaluation harnesses, agent orchestration, and LLM features that have to be correct and cost-aware — including shipped AI features in a live consumer product on AWS Bedrock. I also build the open-source tooling that AI agents run on.

Isn't this all hype?+

A lot of it is. My filter is simple: AI where it genuinely earns its place, boring and reliable everywhere else. I'll tell you where it's the wrong tool.

What does it cost?+

Every engagement is different, so I scope and quote per project rather than publishing a fixed rate. Tell me what you're trying to automate and I'll come back with a clear proposal.

Have a project in mind?

Tell me a little about what you’re working on — I reply quickly.

Let's talk