What these tools do
- What building software with AI means when you have never written any
- The tools worth your time, and what each one is good at
- Where they fall over, covered before you build anything
- What you can realistically expect to finish
We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Build and ship a working tool without writing code, and without waiting for a developer to have time.
Rebuilt on your team's work
Run privately for your team, on dates and at a length that suit you.
Every module ends with something participants can repeat on Monday morning in their own work and tools, so the team gets more done without adding people.
Take a real task from your own work and turn it into a tool a colleague can open.
Say what a thing should do precisely enough that the first attempt comes back close instead of wild.
Read what went wrong, change one thing at a time, and get out of a loop of broken attempts.
Get your own spreadsheet, form or list into the thing so it stops being a demo.
Recognise the point where a tool needs an engineer, and hand it over before it becomes a problem.
Publish it, collect what colleagues say about it, and decide whether it earns a second version.
Most of the time goes on hands-on exercises. Module order and depth are set for your group before the first day.
Your version builds the tools your team has wanted and never got a developer for: a tracker, a form, an internal calculator. The tools follow your IT rules, and each person leaves with something a colleague has already tried.
How a booking worksIn your office, with the team in the room. Best for a first rollout.
Live over video, in shorter blocks across several days.
A day on site to start, then shorter remote sessions on real work.
Every course runs privately for one team, on dates we agree together.
Every module can be rebuilt on your team's own work and tools. Tell me what the team works on and I will tell you what I would change.
AI agent trainer and software engineer
I build production software with AI agents every day, so I know where a vibe-coded tool holds up and where it needs an engineer. I also studied psychology, which helps in a room of people who have never written code.
What teams ask before they book.
Yes, the course is designed around you. There is no code to read and none to write. If your group does write code, the Claude Code course is the better booking.
Tools that turn a description into a running app, such as Lovable, Bolt or v0, or a coding agent like Claude Code. I pick what fits your group and your IT constraints, and the way of working carries over when the tools change.
Usable for a small internal job with a handful of users. Not for anything holding customer data or money, and the course shows where that line runs.
Every booking covers what these tools store, what should never be pasted into them, and how to check with your own IT before publishing anything. Bring your policy and we work against it.
It stays yours and it keeps running. The last module covers what to write down so an engineer can pick it up if a tool proves useful enough to grow.
This course ends with a tool people open: a form, a tracker, a small app with screens. The no-code agents course ends with something that runs without anyone opening it, such as a workflow that sorts incoming requests every morning. If your team's wish list is mostly apps, start here; if it is mostly chores that repeat, start there.
Have a question about your team's setup?
Tell me what your team works on and how it uses AI today. A few lines are enough. I reply myself, usually within a day, and if this course is the wrong one I will point you to the one that fits.
In English or German, on site, remote or hybrid.
Vibe Coding Training
A few lines are enough