
In one day you use AI to build custom software that connects your systems or replaces them. No coding skills needed.
Build sessions we ran at


| Question | A software agency | An AI knowledge workshop | An AI build day |
|---|---|---|---|
| Up front | A quote and a schedule | An afternoon about prompts | An intake and a fixed price |
| A week later | You wait for the first version | The team asks the chatbot loose questions again | Software runs that connects your systems |
| When your work changes | You ask for a new quote | You start over with the chatbot | Your team changes it themselves |
| What your team learns | Nothing, the knowledge stays at the agency | Asking better questions | Building and changing software themselves |
SammyFrietboutique Sammy & Pebbles“You walk in with a list of things that have been lying around for years, and you go home with something that actually works. You don't have to be technical: we run a fries and ice cream shop, we're not programmers.”
Bart LacroixFounder of GoodUp“Learned more here than from all those podcasts.”
Quotes translated from Dutch.
Retyping purchase invoices from the inbox into the accounts. Pulling the numbers from six ad channels together every week. Retyping data because your systems don't connect. On the build day your team builds software that connects those systems.
That software talks directly to the systems you already use, through their API. Nothing leaves the building until someone presses Yes.
By hand
/purchases
38 invoices read from the inbox
38 draft entries ready, PDF attached
Approve? 1. Yes2. No
Approved
/ads
6 channels fetched via API
1 paused ad group found
Approve? 1. Yes2. No
Approved
Everyone builds for a task from their own work. You build with Claude Code, on your own files. At the end everyone shows what their tool does and you have a list of the next tasks.

Your team keeps building without getting stuck. After six weeks we come back for half a day. After that there is a check-in every month and you email us when you get stuck. If nobody is using a tool they built after six weeks, we come back at no cost until they do.
Is AI causing unrest in your team? That's what the team day is for.
Wouter van den AckerPKW was the first training we gave. We gave Wouter van den Acker's team a safe foundation and they did the building themselves. A report went from eight hours to half an hour per complex. Across 140 complexes that saves well over a thousand hours. They have their code reviewed independently and want to sell the tools next.
It works if
It does not work if
No. The team at energy label consultancy PKW had no software background and built 17 tools in five months.
That's how it starts for most teams. On the build day the whole team builds at the same time, on your own work, and everyone goes home with a tool that works.
On the team day. You sit down with your whole team and decide per person what they need to work with AI.
They can ask questions and hand over single tasks themselves, even with AI connected to email and calendar. Custom work for your own processes, like reports that appear in your fixed format by themselves, has to be built. That's where we help.
After the build day you have a list of what you build next, with what pays off most at the top.
If you keep building with us, there is a check-in every month. We look at what is going well and where it could go wrong, and pick the next step together.
How far do you get on your own, and where do we help? See the four levels →
Our people don't hallucinate. They just call the client.

Free and online. You bring one task that takes a lot of time, and we look at whether a build day fits. You are not tied to anything afterwards.
Or plan a build day straight away: €1.500 for your team of up to 4 people, money back if the day was not worth it. Plan a build day →
Then I will get back to you within 24 hours.