Build the apps you need. In sixteen hours.
Four four-hour modules, in a room, with your laptop open and your own work on the table. You don't learn to program: you learn to direct artificial intelligence so that it writes the software for you. You leave with an app of your own, online, that your staff opens on their phones on Monday morning.
Wherever it's asked for. In Italian, German or French, depending on the room.
Not notes. Something that runs.
The app, in production
Not an exercise: the real thing, with your data, opened on your staff's phones. You choose it in the first module — attendance, housekeeping checklist, allergies, a small CRM, the daily dashboard.
Three templates already running
You don't start from a blank page: you take home the attendance register, the housekeeping checklist and the staff meals app — the versions running today in a 515-bed property, stripped of data and commented so you can change them. You use and modify them in your own property as much as you like; you don't resell them. They're a starting point, not a product with support.
The method, which holds for the next one
The part that stays once the app is done: spotting which process pays off, writing down how you do it today before automating anything, testing on copies. Whoever has done it once does it alone on the next process.
The accounts, in your name
Everything we open in the room is yours, and stays yours. No licence in my name, no buy-out, no subscription that starts later. If I disappear tomorrow, your app keeps running.
The two things holding you back.
"I'm not capable"
You don't need to be. The work isn't programming: it's explaining. If you can tell a new hire how your job is done, you can do this — with the difference that this one doesn't take offence when you correct it. The code is written by artificial intelligence; deciding what it should do is your job, and it's the only part nobody can learn for you, because it takes knowing your own business.
"I don't have time"
Sixteen hours, once. Put them next to the hours you lose in a year waiting on a vendor for a half-hour change, and you'll do the sum yourself. And if three days in a row is impossible in season, the course splits over two weekends: that's why the format exists, not out of politeness.
Four modules. By the end of the second, your app is already online.
Mindset and tools
Not a line is written. What changes is where you sit: you direct, artificial intelligence writes. We open the accounts in your name, set up the working environment, and everyone picks the app they'll build over the next three modules.
The first app that runs
Guided build, all together, each on their own laptop and their own shifts: the staff attendance register. By the end of the module it's online and opens on a phone. That's the moment it stops feeling like a course. At the end of the module I hand you mine too, the one that genuinely runs: you compare them, and you see the difference between something that works and something that holds.
Your app
Workshop, one to one. Everyone works on their own idea; I move between the desks, unblock and correct. This is the part that can't be recorded and resold online — and the reason the room is small.
Production and survival
Putting it online properly: domain, backups, minimum security, guest data and GDPR, what to do when it breaks. How to change it in six months without wrecking it, and how to switch AI provider without rebuilding the app. We close with your first ninety days.
What this course is not.
- ×You do not replace the PMS, and in the room I explain why that would be a bad idea.
- ×You don't come out a developer. You come out able to tell artificial intelligence what to do — and to spot when it has done it badly.
- ×It isn't a course to watch on the sofa in the evening: it's in person, with me walking the room.
- ×It isn't a generic AI course. Here we talk housekeeping shifts, allotments, allergies and wine delivery notes.
One weekend, and a small room on purpose.
In person
A long weekend, Friday to Sunday, or two split weekends when the season won't give up three days in a row.
Six to ten people. Never more
That isn't marketing: in the third module I spend an hour with each of you. Above ten, that module ceases to exist — and without it you don't leave with an app.
Three months of group support
When the course ends a dedicated group stays open, where you keep asking as the app goes into service. Those are the three months when something breaks.
The recordings are yours
The modules are recorded and you keep them, to go back over a step. I don't sell them separately: without the room they're worth nothing.
What your vendors charge you in three months.
Everything included: the sixteen hours, the materials, the three months of group support afterwards, the recordings. Nothing that appears on the invoice later. I'll give you the figure on the call, once I know which format you need.
- ›The tools you'll use stay yours, in your name: no licence under mine.
- ›The course pays for itself with the first program you stop renewing.
- ›The three working templates are included: attendance register, housekeeping checklist, staff meals.
- ›It can also be one to one, just you: same method, your pace, all sixteen hours on your own process.
- ›It is a one-off: what you build doesn't renew, and in year five it still costs nothing.
It depends on the format — a room, an edition at your place, or one to one — and editions outside Italy carry local costs. Thirty minutes on a call: I'll tell you the figure and whether it pays off.
One evening. Ninety minutes, free.
- +Online, ninety minutes: you are there wherever you work.
- +You watch a real app run, in production, with the data masked. Not slides.
- +Awkward questions are welcome: they're the ones I fix the course with.
A hotelier who codes, not a trainer who talks about hotels.
- ›Thirty years in the industry, today Cluster Manager of four properties and 515 beds.
- ›The Smart Suite apps are in production, not in a demo.
- ›Corporate trainer since 2019: hotels, restaurant chains, software houses, wineries.
- ›Italian and German native, French and English: I run the room in the room's language.
Three roads, and none of them forces you to call me back.
You carry it on alone
That's the outcome the course aims at, and it's what brings me the next participants. The group stays open three months, then you're on your own and you owe me nothing.
Support on a monthly fee
If you'd rather someone kept an eye on the apps while the property grows, there's monthly support. It starts after the course, if you want it, and you can end it whenever.
The things not worth rebuilding
PMS, revenue, concierge: where you need an integrated, maintained product there's the Smart Suite, already in production. In the room I tell you which pieces are worth buying and which aren't — including when the answer costs me a sale.
A trainer speaks one language. I speak three.
Italy
German-speaking countries
French-speaking countries
Anywhere, if there are five of you
Wherever you work: if there are five or more of you, the edition comes to you, and the introductory evening is online. It can be arranged.
The questions I always get.
What computer do I need?
Yours, as long as it's from the last few years, plus a connection. You don't need to buy anything to attend.
And what does it cost me to keep these apps running?
A few euros a month of tooling, and the accounts are in your name. The exact figure depends on how many apps you run and how hard you use them: I'll work it out on your case before you enrol.
What if AI pricing changes?
That's the real risk, and the course is built to absorb it: what you learn holds for one model as much as another, and part of the fourth module is precisely how to switch provider without rebuilding the app.
Where does my guest data end up?
On your infrastructure, under your accounts, in Europe. The fourth module is devoted to this: what you may keep, what you must delete, what must never pass through a model.
Why not run it online for €99?
Because the third module is the reason you leave with a working app, and the third module doesn't exist online. You watch fifteen per cent of a recorded course and build nothing: we both know it.
Isn't the course really there to sell me your Smart Suite?
If you build your own apps after the course and never call me again, it worked: you're the one who brings the next group. The Smart Suite is about what isn't worth rebuilding in-house, and in the room I tell you which pieces those are — including the ones you're better off not buying.
Do you issue a certificate? Can we use a training fund?
I'm not an accredited training body and I issue no certificates: what remains is an app of your own that runs. If the programme has to go through a fund, we check the formal side with your advisor before you enrol, not after.
The first editionis small.
The room holds ten people: in the third module I spend an hour with each one, and above ten that module doesn't exist. The dates are set with the first people who enrol, and before the course there's an open evening where you can watch me work without committing to anything. In thirty minutes we look at how you work and I tell you whether it's the right place to start — and if it isn't, I'll say so.