That sentence is either a slogan or a system. Here is the system.
Like a Human runs on the system it sells: internal context, our own tools wired in over MCPs and APIs, behaviour in CLAUDE.md, skills, agents and a human in the loop. Sales, finance, content and operations, not a pilot in one team.
It is also how we stay current. We read the research and follow what Anthropic, OpenAI, Mistral and Google actually ship, and anything promising lands in our own workspace first. Nothing reaches a classroom before it has become routine here.
Around 95% of our work runs through AI. Our operational data lands in one internal database, and Claude reads it directly over our own MCP.
A workflow that works gets written down as something you can run again: a CLAUDE.md, a skill, an agent, and a checklist for the step where a person still decides. Not a slide about it.
Those files sit in the system we work in every day. When a capability changes we change the file, and everyone is on the new version the same week.
Every pattern we teach is a file in our own workspace, in daily use.
Only then does it become teaching material, and that is a craft of its own. Our Head of Education builds the pattern into modules and exercises where your team does the real work in the room, on your own codebase and your own workflows.
Your team leaves with material clear enough to keep going on its own. Every example comes from work we did ourselves, never from a vendor demo.
What your team hits in the room is what we fix in our own system next. That is why no module is older than three months.
Development and Business, one or two days per team, with a Day C that equips your champions to carry it further.
Like a Human started from a gap Stefan kept running into. He came out of marketing, and marketing teams had a knowledge gap nobody was closing. So he ran workshops to close it and used them as research: which tasks come back every single week, and which of those can be automated? The answers turned into real implementations.
Meeting Jasper added the second track. He had been building with Claude Code since the early days, so together they built the masterclass that became the development side of the academy. Tim came in to own education, and that is the shape we run today.
You get the person who builds it every day, not the person who read about it.
Lead engineer at McLaren Applied, VanMoof and DPG Media.
LinkedIn
Claude Code, out of legal tech and the Dutch government.
LinkedIn8 senior instructors · no junior trainers
Ask us whatever you still want to know.
We use cookies or similar technologies for technical purposes and, with your consent, for other purposes as specified in the cookie policy. Use the "Accept" button to consent.
Cookies are small files a website stores on your device. Similar technologies, such as local storage and pixels, do the same job. We use them for three purposes. Two of them are your choice.
These keep the site working. We store your cookie choice in your browser, so we do not ask again on every page. The ticket button and the ticket checkout come from Luma, our ticketing platform. Luma and its security provider Cloudflare set cookies that protect the checkout against bots. These need no consent and are always on.
Umami counts visits and clicks without cookies and without identifying you, so it always runs. Google Analytics and Google Tag Manager show us in more detail how people use the site, and Microsoft Clarity shows where people click and scroll, with heatmaps and recordings of visits in which what you type is masked. Google Analytics sets cookies such as _ga, kept for up to 2 years, and shares data with Google Ireland Limited; Clarity sets _clck and _clsk and shares data with Microsoft. They run only if you allow them.
On our event pages the Meta pixel tells Meta which pages you saw and when you start a checkout, so we can see which ads work. It sets the _fbp cookie, kept for 90 days, and _fbc when you arrive from a Meta ad. The data goes to Meta Platforms Ireland Limited. It runs from the moment you open an event page. Switch off Marketing below to stop it.
Separately from these switches, when you buy a ticket our server reports that purchase to Meta, with your email, name and location in hashed form. Our privacy policy explains this.
Switch off what you do not want and press Save choices. You can change or withdraw your choice at any time through Cookie settings at the bottom of every page. The cookie policy lists every tracker, who provides it and how long it is kept.
