AI Project ConsultingFree AI Course1:1 AI SupportAI Team TrainingAI Coding Bootcamp Book a call
Idea to working app · two days · Amsterdam

2-Day AI Coding
Bootcamp.

You walk in with an idea and walk out with a working app. Web or mobile, your choice, built from an empty screen over two days with a coding agent doing the typing and you doing the deciding.

When
Dates coming soon
Where
Amsterdam, walk from Centraal
Waiting list price
€1,169 €1,299excl. VAT, 10% off for the list
You leave with
A working app, deployed
Join the waiting list See how the two days go

No payment and no commitment. We mail you once, when the dates are set.

The bootcamp room: long tables and chairs, plants, daylight, and the DenkWork logo lit up on the back wall.
Why two days

One day gets you a demo.
Two gets you a product.

Getting something on screen that looks like an app is fast now. Genuinely fast, in an afternoon. It is also where nearly everyone stops, which is why there are so many impressive AI demos and so few things anyone actually uses.

The second day is the one that matters. That is where it starts holding real data, where it survives somebody else clicking around in it, and where it ends up online at an address you can send to a colleague. Almost nobody gets to that day on their own, because that is where the interesting problems live.

It has to happen in a room because things go wrong, and when an agent goes wrong it looks exactly like it going right. Confident, plausible, finished. Learning to spot that takes someone sitting next to you saying "stop, look at what it just did" while it is still on the screen. You cannot get that from a video.

You go home with two things. The app, which is yours. And the setup that produced it: the instructions you wrote for the agent, the checks you made it pass, the habits you picked up by the second afternoon. That second part is what makes the next app take an evening instead of two days.

The programme

Today an idea.
Tomorrow a working app.

Web app or mobile app, whichever you want to build. Day one gets the foundation and the habits in place and the first real pieces working. Day two turns it into something you could actually put in front of someone.

Day one

Foundations, and the core of the thing

Getting set up, getting the mental model straight, and getting the first working pieces on screen.

  • Your agent running properly, and what it can actually see and do
  • What you actually control: the model is the same one everybody rents, the setup around it is not
  • Prompting that survives contact: planning before building, being specific, feeding it what it cannot guess
  • Project memory, so you stop repeating yourself every session
  • The first real pieces: where the data lives, the logic that runs on it, something you can drive it with
  • Teaching the agent your conventions so it stops making the same wrong choice
  • Staying in control: reading what changed, correcting course, knowing when to stop it
Day two

From working to shippable

Everything from day one put to work, until the thing is online and somebody other than you could use it.

  • A real interface, in a browser or on a phone, that somebody else could use
  • Tests, so you find out it broke before somebody else does
  • Getting it deployed and reachable, and the automation that keeps it that way
  • Splitting work across several agents, and when that helps rather than hurts
  • Sandboxing: letting it run without letting it loose
  • Audits and review loops that keep an agent honest
  • Less structure than day one, more building. We follow the work.
Who it is for

Professionals who are done
skimming the surface.

You do not need to be a developer. You do need to have used these tools enough to know that a chat window is not the whole story, and to want to find out what the rest of it looks like.

This is for you if

  • You use AI most days and suspect you are using a fraction of it
  • You are technical enough not to panic at a terminal window, without being a developer
  • You keep having ideas that stall because building them means asking somebody else
  • You want to watch someone build a real system live, mistakes included
  • You lead a team and want to know what is genuinely possible before you plan around it

Probably not if

  • You have never opened an AI tool. Start with the free course, then come back.
  • You want a strategy overview rather than two days of hands-on building.
  • Your team needs written material afterwards. You go home with a working app and your own notes, not a course pack.
  • Two full days away from your desk is not realistic right now. The 1:1 sessions exist for exactly that.
What to bring

You build.
We do not demo at you.

Everyone works on their own laptop for two days. There is no watching option, because watching is how people leave with notes instead of a skill.

Who runs it

The people who
actually build.

DenkWork ships production software with AI every day. Two days here is two days with the people doing that work, rather than with somebody who read about it and made slides.

Melvin

Melvin

Managing Partner

Originally from the Netherlands, Melvin has been the founding engineer of five VC-backed companies that have collectively raised over $400M. In Silicon Valley he led 100+ engineer teams at companies like Wag.

Önder

Önder

Managing Partner

Önder runs operations and client relationships from Rotterdam. He brings years of management experience and has founded and built businesses in the Rotterdam area.

The waiting list

Dates are coming.
Put your name down.

The room is small, so the first run fills from this list rather than from an announcement. It costs nothing and commits you to nothing.

One email when the dates are set. Nothing else, and no list you have to escape from later. Prefer to write to us instead? Send an email