Notes on working with AI
How Much Does an AI Workshop for a Company Actually Cost?
You searched for a price and found a form instead. We won't publish a number either, and here's why, plus what actually drives the cost of a corporate AI workshop: group size, format, how much it's built around your own documents, and what happens after.
You searched "how much does an AI workshop cost" and found exactly what everyone finds: a nice page, a few lines about transformation, and a form asking for your details instead of a number. We're not going to publish a price here either, and we owe you the actual reason instead of the same dodge. A workshop for a team of eight, built around their own documents and their own workflow, and a company-wide rollout spanning several departments are not the same product. One number trying to describe both of those doesn't save you time, it misleads you. What we can do, and should, is walk through exactly what moves the price, so you know what to ask before you talk to any provider, us included.
What actually drives the cost
Group size. A workshop for eight people around one table is different work from a workshop for thirty, and different again from a series of parallel groups across departments. A small group means the instructor can open every person's real file in the room. A large group means more independent practice and less one-on-one time per person, and that changes the shape of the whole day, not only the number at the bottom of it.
On-site or online. A workshop at your offices means travel, setup, and often a full day instead of two split half-days. Online removes that, but loses some of the energy a group gets from actually sitting in one room together. Both formats work. They're just not the same experience, and not the same cost.
How much the exercises are rebuilt around your own documents. There's a real gap between a workshop that teaches on generic examples and one where every exercise runs on your actual spreadsheet, your actual email thread, your actual process. The second version needs a discovery call with someone who knows the process, and sometimes early access to examples that have already been scrubbed of sensitive data. That's real work that happens before anyone from your team ever sits down, and it's usually the difference between a workshop that sticks past week one and one that doesn't.
Whether follow-up is included. A good day followed by total silence is the most common pattern, and it's also the main reason workshops don't stick. A follow-up session, two weeks of an open question channel, a check-in a month later, each one changes what happens after the workshop itself, and changes the price to match.
Hebrew or English delivery. Preparing materials in both languages, or running a workshop in a language that isn't the instructor's native one, takes more than a literal translation. Professional terms need to carry over correctly, not word for word, and that's extra prep work that shows up in the cost.
What makes a workshop cost more than it should
There's also a way to spend more and get less, and it's worth knowing before you book anything.
Training a whole team on Claude, then finding out only a quarter of them actually have a license to use it. This happens more than you'd think. A quarter of the room gets a demo, not a tool, and pays for the day exactly like everyone else did. Check this before the workshop, not after.
A workshop with nothing built in after it. A good day, forgotten within two weeks, because nobody came back to practice, nobody asked a follow-up question, and nobody checked whether it actually stuck. That's a wasted training budget, and worse, a full working day lost for everyone who sat in the room.
One giant all-hands session instead of role-specific groups. A finance manager and a graphic designer don't need the same exercise, and a session built to fit everyone usually fits nobody particularly well. Small, role-specific groups cost more to schedule, but they produce something people can actually use that same week.
What you get in a conversation instead of a price list
On a first call with us, we don't reach for a price sheet. We ask what your team does today that takes too long, which tools you already have licenses for, how many people, how many sessions, and what you want to be true a few weeks after. That produces a scope, not a generic quote pulled off a rate card, and you leave the call knowing exactly what will set the cost for your team, before you've committed to anything.
So why talk to us anyway
If you landed on this page after searching for a price, you've probably already been through a few sites without a straight answer. We're not giving you a number in this post, but we are giving you a conversation that ends with you knowing exactly what will decide the cost for your team. No pitch, and no long form asking you to guess your own budget before anyone's even talked to you.
Frequently asked questions
Why doesn't any training provider publish prices?
Because nearly every serious AI workshop changes with group size, format, and how much it's adapted to the organization's real documents. A number that ignores all of that isn't really describing what you'd get, it just looks like an answer.
How long does it take to schedule a workshop, from the first call to the actual day?
It mostly depends on how much preparation the workshop needs, meaning how much work goes into adapting the exercises to your documents. The first scoping call gives you a realistic estimate for a date, not a generic promise.
We're a small team. Is this even worth it?
Yes. A large share of our workshops run for teams under ten people, and a smaller group usually gets more one-on-one time per exercise, not less.
What happens if only part of the team has a license for the tool being taught?
Better to know that before the workshop than during it. It's exactly the kind of question we ask on the scoping call, so everyone sitting in the room actually leaves with a tool they can use the next day instead of a memory of a demo.