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, in the language they work in. You keep a playbook, a library of ready-made instructions, and a data policy you can adopt as it stands.
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 little, and client information is being pasted into consumer tools because nobody has drawn the line.
Nobody has agreed what the tools are for. That is fixable in an afternoon and a follow up.
What happens in the half day
We ask for your real work in advance and build the session on it. No fictional-company demos: your team works on its own tasks, with us, until each person has something that holds up.
By the end there is an agreed standard: what AI is used for here, what it is not, what a human checks 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 tasks we worked on together.
- A library of ready-made instructions and templates for the tasks your team repeats most.
- A data policy short enough that people read it, adoptable as it stands.
- A follow up session at thirty days, included, not sold after.
Why the follow up is part of it
Thirty days is when new habits die: the ones that survived are visible, and the questions people were too polite to ask in the room have surfaced at their desks. The follow up corrects the playbook against what happened.
Who it suits
Teams of roughly five to forty, where AI use is inconsistent or has not started. Delivered in Spanish or in English; if your team runs in both, the playbook comes in both.
The workshop stands on its own and commits you to nothing after it.
Quote only
SCOPED BEFORE PRICED FIXED FEE PER WORKSHOP
A fixed fee per session, banded by team size, agreed before a date is held.
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 another company could reuse the day unchanged, we built it wrong.
"Staff are already pasting client data into consumer tools." You leave with a policy your team will read.
"Nothing will have changed by Wednesday." Checking that is what the thirty day follow up is for.
READ
The next step
Tell us what your team does all week. We will show you what half a day changes.