TL;DR: A one-day AI workshop is not a lecture with slides. It's your team, laptops open from the first minute, working on your real quotes, your real customer messages and your real weekly post until three flows actually run before anyone leaves the room. A single day can't finish the harder part: turning that into a habit, and moving from using AI to building your own tools with it. That's why the day ends with 30 days of follow-up and, for teams that want to keep going, a four-session program.
What you actually bring to the room
The workshop only works if the material inside it is yours. Before the day starts, the team brings the documents that describe the business: the price list, the service menu, a few real customer messages that were hard to answer, and whatever a new hire gets handed on day one. None of it gets swapped out for a generic example halfway through. The whole point of Sinsajo's team AI training is that the AI ends up sounding like your business, not like a demo built for someone else's.
This format is built for six to twenty people who will actually use what gets built: owners, office staff, sales, operations. It is not the right room for one manager who wants a personal overview; that shorter conversation exists too, as a 90-minute kickoff for the whole team, including the people who are sure this isn't for them.
The day, block by block
The published workshop material from the sessions Sinsajo already ran in Ankeny, Iowa breaks the same ground into four Saturdays: meeting the assistant, putting it to work on real files, building brand and website pieces, and moving from chatting to building tools. A one-day version compresses the parts a team can put to work immediately into a single sitting, instead of spreading everything across four weeks. Here's roughly how the hours split:
| Block | What happens |
|---|---|
| Setup | Everyone opens a laptop and sets up their own AI workspace. No slideshow, no watching someone else click through a demo. |
| Loading the business | Services, prices, tone and the rules that never get broken go in, so answers stop sounding generic. |
| Building flow one: quoting | A real quote gets built end to end, using the price list the team brought in. |
| Building flow two: answering | The hard customer message from the inbox becomes a draft the AI can produce on its own, with a person still approving it before it goes out. |
| Building flow three: the weekly post | The team writes and publishes something for its own business, not the example business from the slides. |
| Writing the policy and the plan | The one-page AI policy gets agreed on in the room, and each person leaves with what to do on Monday. |
Three flows is a deliberate limit, not a shortcut. A day is long enough to get quoting, answering and the weekly post genuinely working against real data. It is not long enough to also cover everything a business might eventually want to automate, and nobody in the room needs a fourth half-built flow to take home and forget about.
What you leave with
By the end of the day, the business is loaded into an AI workspace that already knows what it sells, what it charges and how it talks. Three flows are running against the real documents the team brought in, not sample ones from a slide deck. The team has agreed on a one-page rule for what the AI is allowed to draft and what a person always has to read and approve before anything goes out to a customer. And each person leaves with a short, individual plan for what changes on Monday morning, rather than a folder of slides to review whenever there's time, which in practice is never.
How to prepare
- Bring the price list or service menu, even a rough one. The quoting flow needs something real to build from, not a placeholder.
- Pull two or three real customer messages that were annoying or slow to answer. A generic example produces a generic result.
- Decide who's actually in the room. Six to twenty people works well, and it should include the people who touch quotes, messages and the weekly post directly, not only managers who approve things later.
- Bring one laptop per person, not one shared between three. The day is hands-on-keyboard from the first minute, and sharing a screen slows everyone down.
- Agree beforehand on what never goes out unread. That conversation moves faster if it starts before the workshop instead of in the middle of it.
- Pick the one flow you most want working, in case time only allows for finishing one really well: quoting, answering or the weekly post. That way the day has a clear priority if it runs short.
What a single day can't do
A day is enough to get three flows running and to take the fear out of a team's first real conversation with an AI assistant. It is not enough, on its own, to turn that into a habit that survives a busy Friday, and it is not enough to teach a team to build its own tools instead of just using the ones set up during the workshop. Both of those gaps are why the format doesn't simply end at 5pm.
The workshop includes 30 days of follow-up afterward specifically because what gets built in a single day tends to quietly die once the calendar fills back up with the usual work. That follow-up is where the habit either sticks or doesn't, and it's a built-in part of the format rather than something sold as an extra later.
For teams that want to go further, not just use AI day to day but build their own tools with it, write their own brand and website with it, and work out what to charge once they start doing this for someone else, that calls for a different, longer commitment: a four-session program, the same one already run as four Saturdays in Ankeny. It exists precisely because a single day, however well spent, cannot also cover four weeks of material. If it isn't clear which one a team needs, the honest answer is usually to start with the day and decide from there once it's over.
Virtual vs onsite, English vs Spanish
Onsite is where the one-day format works best. Sinsajo runs it in person across Iowa and neighboring states, including teams reachable through AI training in Iowa. Online is possible for teams spread across several locations, though the hands-on parts travel better when everyone is in the same room. Either way, the day runs in English, in Spanish, or in both, depending on who's in the room, so nobody has to pick one language and hope the rest of the team keeps up.
Not sure whether a one-day workshop is the right starting point for your team? Run the free AI readiness assessment first. It takes a few minutes and gives you a clearer sense of where your business actually stands today. Or skip straight to booking a call, and we'll figure out together whether a day, a kickoff, or the longer program fits what you're trying to do.
