The Workshop · one day with your team · fixed price €3.950

We all use AI. What else is there?

Everyone on your team has an AI assistant open, perhaps an agent is already running, and still you sense that other teams are further along. What are they doing that we are not? The Workshop is one day on which your team shows each other how they work, I show what the next step looks like, and together we build something that is still running the next morning.

Everyone uses it differently, and nobody knows what works best.

We have one agent running, but the rest of the work is still done by hand.

I read about teams that really do it differently. I want to see that, not read about it.

We do not need another course on what AI is. We want to get to work.

01 · Watch, tools, build

What is The Workshop?

A workshop is where craftsmen stand side by side at their own benches, look over each other's shoulders, and have made something by the end of the day. That is what this day looks like. Not a session on what AI is, because your team already knows. Instead: showing each other how you work, watching an agent work, understanding which tool fits which job, and building something together that keeps running in your own environment.

This works if your team already works with AI.

A good fit

Your team uses Claude, ChatGPT or Copilot daily, and the question is not whether but how to go further.
One team, up to a dozen people or so. A development team, but just as well support, sales, finance or a leadership team.
There is recurring work you could explain to a colleague: that is the afternoon's build block.
Two teams that want to learn from each other. They may come from two companies.

Not a fit

You are looking for an introduction to AI for people who do not use it yet.
You want a strategy session on what AI means for the organisation. That is a conversation, not a workshop.
Access to your own environment cannot be arranged. Then the build afternoon falls away, and that is half the day.

02 · Five blocks, from watching to building

What does the day look like?

The morning is watching and understanding, the afternoon is building. The order is fixed; what happens in each block we decide in the intake, with your own work as the starting point.

Two figures at a workbench under a red workshop lamp; one works, the other looks on.

Morning · At the bench

Colleagues show how they do it

Three or four people each show their best way of working in ten minutes. No slides, just the screen. After each demo we pull out the pattern together and put it on the board.

What you have afterwards · The first lines of the pattern list: what already works, and why.

A bench drill press with a small block of wood on the table and red handles on the head.

Morning · An agent at work

From assistant to agent

I let an agent pick up a task live from start to finish: read, plan, execute, check, hand over for review. And above all how you steer it: fixed agreements, a checkpoint, and a human who has the last word.

What you have afterwards · A picture of the next step, and where the human stays in the loop.

A tool wall with hammer, saw, wrenches, screwdriver and chisel; one open-end wrench is red.

Morning · The tools

Which model for which work

What makes an AI session expensive or unreliable and how to prevent it. Which model to use for routine work and which for design. Why instructions written for a previous model now work against you.

What you have afterwards · A checklist for your own settings and instructions, per person.

Two wooden sawhorses with a plank across them and one red F-clamp on the edge.

Afternoon · Build

Something that is still running tomorrow morning

We build something in your own environment that keeps running after today. For a development team, an agent that clears open errors overnight and has a pull request ready in the morning. For support, an agent that prepares incoming questions. For finance, a check that lines up the exceptions every week. You choose in advance what pays off most.

What you have afterwards · Something that runs, with a human where the judgement counts.

A chalkboard on an easel with four short dashes as a list and a red piece of chalk on the ledge.

Closing · What works

The pattern list and three commitments

We walk through the pattern list of the day and each team picks three things it will do differently tomorrow. Small, concrete, with a name attached.

What you have afterwards · The list on paper, and three commitments I will ask about at the follow-up.

03 · Intake, preparation, the day, follow-up

How does it work?

Your time: a one-hour intake, the day itself, and an hour of follow-up. I do the preparation, so the build afternoon is not spent arranging access.

A tape measure with the tape pulled out a little and a red lock button.

Intake · one hour

What is going on and where it sticks

With the person who knows the team: how AI is used now, which work keeps coming back, who shows something in the morning, and what the afternoon's build block will be.

What you have afterwards · A programme for the day with names attached, and a chosen build block.

A half-unrolled tool roll with three chisels in it and a red tie ribbon.

Preparation · by me

The bench is ready

Access to your environment, the fixed agreements for the agent, the first checkpoint. Everything that would otherwise cost the first two hours of the afternoon.

What you have afterwards · Nothing to do. Just one person who can arrange access.

A group around a workbench; one of them holds up a small red workpiece and shows it to the others.

The day · at your office

Watch, tools, build

The five blocks above, from nine to half past four. I moderate the morning and build along in the afternoon.

What you have afterwards · Something that runs, the pattern list and three commitments per team.

A spirit level lying flat, with a red bubble in the vial.

Follow-up · within two weeks

Is it still running, and what is next

One hour, remote. Is what we built still running, were the three commitments kept, and what would the next Workshop or Build be.

What you have afterwards · A short note with what it delivered and what could come next.

If you do not yet know what to build, The Scan comes first.

Want to know if this fits your team?

A half-hour conversation costs nothing. You will hear whether a Workshop is the right instrument, or whether your team needs something else first.

Book a Workshop

04 · Price and next steps

What does it cost, and then what?

One fixed amount per team. No price per person. If the group grows or two companies take part, we look at the format together: more often two days than one full room.

One fixed amount, something that runs.

The Workshop · one day with your team

€3.950

fixed price, excl. VAT, one team of up to twelve people

One team of up to twelve people: intake, preparation, the day on site and the follow-up. Travel included within the Netherlands.
A larger group, or two companies that want to do it together? Then we settle the format in the conversation: usually a second day, sometimes a different setup. The price follows from that format.
What gets built is yours and runs in your environment. Even if you never buy anything from me again.

Also have a look at

Binoculars on a wooden tripod, with a red band around the eyepiece.

Not sure yet what to build? Then The Scan comes first: two working days with the people who know the work, one first trial, and a chosen build block for the Workshop. Half of it is credited when the Workshop follows.

See The Scan

A drawing table with a rolled-up drawing and a red ruler.

Want someone to stay involved? Then I stay involved two to four days a month: guarding the patterns, designing the next agent, coaching your team.

See Fractional AI Architect

05 · What people want to know

Questions?

The questions that always come up, with short answers. If yours is not here, a half-hour conversation is the fastest route.

Does everyone have to be a developer?

No. The structure of the day is the same for every team; only the build block differs. With a development team we build in the code. With a broader team we build with the assistant you already have, with an approval step instead of a test suite.

Does this work with ChatGPT, or does it have to be Claude?

It works with what you already use. I work mostly with Claude myself, and that is what I show in the demo, but the tools block is about choices that apply to every assistant.

What if the build block does not get finished?

That is why I set up access, the agreements and the first checkpoint beforehand. If it still does not get finished, I complete it in the week after and walk through it with you at the follow-up.

Can we do this with two companies?

Yes, and I recommend it. Two teams that see each other's way of working learn more than one team looking at itself. We do the build block per team, and the other team watches. How we divide that into days and costs, we agree beforehand.

What do we need?

A room with a screen, everyone's own laptop, and one person who can arrange access to the environment in advance. I bring the rest.

Am I tied to anything?

No. One day, one fixed amount. What gets built is yours and keeps running without me.

Who leads the day

I work this way myself, every day.

I am Daniel Plomp. Agents pick up tasks from my own backlog and deliver pull requests; I specify, review and merge. What I show in the Workshop is not a demo setup but how my own production line runs. That is why I can set it up at your place in one afternoon: I know the pitfalls from my own work.

Daniel Plomp · AI Architect & Builder

One day, and something runs.

Tell me briefly how your team works with AI today and what you hope will be standing at the end of the day. You will hear within one working day whether a Workshop is the right instrument.

Name

Work email

What is going on?

This check keeps spam out and usually passes on its own.

This form needs JavaScript for the spam check. If it is switched off, email mail@artisanatwork.dev directly.

Usually a reply within one working day