AI Foundations: half a day on your team's real work, not generic demos
ENTRY OFFER HALF DAY, PLUS A FOLLOW UP AT THIRTY DAYS SPANISH OR ENGLISH
A workshop built on the tasks your team does every week, delivered in the language they work in. You keep a written playbook for your business, a prompt library for the jobs that come round every week, a data handling policy you can adopt as it stands, and a follow up session thirty days later.
Start the conversation.
The tools got bought and nothing changed
Someone signed up for the licences. Two people use them well, most use them for nothing much, and nobody has agreed what good looks like or who decides. Meanwhile client information is being pasted into consumer tools by capable staff who were never told where the line is, because nobody has drawn one.
That is a standards gap, and it closes in an afternoon and a follow up.
What happens in the half day
We ask for your real work in advance. The emails, the documents, the enquiries, whatever your team spends its week on. The session is built on those.
A demo about a fictional company does not change how anyone works on Monday, so we do not run one. Your team works on its own tasks, in the room, with us, until each person has something that holds up and can show it to the person sitting next to them.
By the end of the half day there is an agreed standard: what AI is used for here, what it is not used for here, what has to be checked by a human before it leaves the building, and where client information may and may not go.
READ
What you keep afterwards
- A written playbook for your business, built on the workflows we worked on together rather than on a generic handbook.
- A prompt and template library for the tasks your team repeats most.
- A data handling policy, short enough that people read it, that you can adopt as it stands.
- A follow up session thirty days later, included in the workshop rather than sold after it.
Why the follow up is part of it
Thirty days is when adoption dies. By then the habits that survived the first fortnight are visible, the ones that did not are obvious, and the questions people were too polite to ask in the room have surfaced at their desks.
The follow up is where the playbook gets corrected against what happened. That is why it is in the workshop rather than sold as a refresher later.
Who it suits
Teams of roughly five to forty, where AI use is inconsistent or has not started, and nobody has agreed a standard. Delivered in Spanish or in English. If your team runs in both, that is the normal case here rather than an edge case, and the playbook comes in both.
It is the smallest thing we sell and the most common way people start with us. It also stands on its own. Plenty of teams do the workshop and build nothing.
The people who run the studio are the same people who run the workshop. You can read how the studio works first.
Quote only
SCOPED BEFORE PRICED FIXED FEE PER WORKSHOP
The workshop is a fixed fee per session, banded by team size and agreed before a date is held. We do not publish it, because the shape of the day changes with the team and the number should describe the day you get.
Every engagement here is scoped before it is priced. It is the same discipline that runs through the AI visibility audit and everything after it.
Three things included because of what usually goes wrong
"We have sat through a session like this before." The playbook is written on your workflows. If the same day could be delivered to another company unchanged, we have built it wrong.
"Staff are already pasting client data into consumer tools." You leave with a data handling policy you can adopt as it stands, in language your team will read.
"Nothing will have changed by Wednesday." The follow up thirty days later is included, and checking that is what it is for.
Where teams go next, if they go anywhere
The workshop feeds both halves of the studio and commits you to neither.
- Growth systems, when the session shows the constraint is that the right customers are not arriving.
- Operations systems, when it shows the constraint is that people are doing by hand what should not need a person.
- Our published method, if what you want next is to see how a project runs before you start one.
READ
The next step
Tell us what your team does all week. We will show you what half a day changes.