This website uses cookies
Read our Privacy policy and Terms of use for more information.
The same six skills and the same curriculum, built on the work your team really does and the tools you already run. Everyone builds their own thing, so you finish with several running instead of one demo the room watched. Take the four weeks if the calendar allows it, and one sitting if it does not.
Split by how big your team is, not by how much you want to spend. Take the four weeks unless the calendar genuinely stops you.
For the owner plus whoever actually runs the process.
For a company that wants the team still doing this in month three.
For a company that wants the team started this month, not next.
For a team that needs all of it in one day.
Merlin, by Praxis, the free workspace your workflows live in. Download it and you are running in five minutes. Plus the complete guidebook for putting Claude to work in your company, and the guides built around your team's own workflows.
Ninety minutes taught, then a sixty minute open lab. Same day and time each week, so it holds a slot instead of competing for one. Every exercise is rebuilt on your workflows, so the practice week happens inside your own business.
Telling AI shaped work from work that only looks like it. Then map how the job actually runs in your company, not how the process document says it does, and pick the first thing worth building.
Writing instructions that hold up twice, and choosing the right model for this particular job. It runs by the end of the session. Some of it breaks, and the breaking is the part you came for.
Your real tools and your real data, the messy parts nobody demos. Where the model goes confidently wrong, and how to put a check in the path instead of hoping.
Hand it to whoever runs it, learn what drift looks like before it breaks, and leave with the next three things worth building plus the judgment to rank them.
Half of any private training fee credits against an install booked within 90 days. The amount and its expiry date are written on your invoice, not tracked in an email thread.
From me, not a sales team, usually the same day. It says which format actually fits what you described.
You take one of the dates in the reply, or you name the week that works and we hold it.
Payment in full on booking, paid online rather than chased by invoice. The dates are confirmed on payment and the calendar invites go out at once.
Not a sales call. A day built on the wrong workflows is a wasted day for ten people at once, so this call is what stops that.
The exercises get rebuilt around your workflows. That is what makes it private rather than a public class with fewer people.
Take the four weeks unless the calendar genuinely stops you. A team too large to hold the same weekly slot, a seasonal window, or a group travelling in anyway are all real reasons. Wanting to be done sooner is not.
Same spine, different examples. The private one is built on your workflows, so the exercises are your actual work instead of a made-up case.
No. Nobody writes code. If they can describe how they do their job, they can do this.
Say so in the request. Past 15 the room stops being a workshop and starts being a talk, so the answer is usually two sessions rather than one bigger one.
That is the default. Builders, insurance, legal, professional services. The material adapts to the vertical you are in.
Yes, and it is a separate thing rather than a replacement. Training handles the next forty workflows nobody will pay us to build. A build handles the one that is too load bearing to learn on.
Six short fields, about a minute. Say what your team does and how many people, and I will come back with which format fits.
One real system a week, written out. One AI term translated into what it actually costs you. Send it to whoever on your team would have to run the thing.