Service 03 / 04 · AI training for teams · all services
Workshops for business teams built from 75-minute modules, up to four a day, on site or remote. Bring any device with a browser: the sandbox, the tools and the API tokens come from me.
Every engagement ends with a system your team can operate without me, so teaching is part of the job. The workshop is built the same way: no slides for the sake of slides, the material is the repository the team fills during the modules. The entry module needs nothing installed: each participant opens a browser, lands on their own sandbox desktop over RDP, and ships something in the first 75 minutes.
Business teams: operations, sales, marketing, finance, support, and the developers who serve them. Mixed groups work best. Nothing to install: the entry module runs in a browser.
Entry
Everyone opens a browser and lands on their own sandbox desktop. opencode with my tokens, the team repo, one real task each. By the end every participant has an agent that did something for them, committed.
A day
Modules follow the tree: a day is a path, not a list. On site in one room or remote, 9:00 to 15:00 with breaks. Most teams do one or two days to start.
Continuation
The deeper branches run on the team's real work: they bring what they built and where it broke, we harden and extend. The sandbox stays up for 30 days after the last module.
Eight modules of 75 minutes. Each one ends with something the participant built and committed. Arrows show what a module needs before it; a day is a path through the tree, up to four modules long.
Entry
Browser, sandbox, opencode. What an agent is and is not, writing a task it can finish, where it must stop and ask.
You build One recurring task of yours done end to end by an agent, committed to the team repo.
Nothing to install, nothing before it
Foundations
Agents with tools: reading files, running commands, browsing. Checklists of what they may not do. Working with Claude and opencode side by side.
You build An agent with a written scope and a checklist, running on a task from your week.
Needs 00
A repository as the team's shared memory. Commit, branch, pull request, review, revert, in plain words and in practice.
You build A pull request from every participant, reviewed by a peer, merged.
Needs 00
Branches
Word, Excel and PowerPoint from data and templates: reports, offers, monthly decks. The document is built from the source, not typed into a chat.
You build A generator that reads a spreadsheet or a CRM export and writes the file your team sends by hand today.
Needs 01
Automating what only has a web interface: portals, back-offices, suppliers' sites. Playwright driven by the agent, screenshots as proof, a stop when the page changes.
You build One automation of a portal your team logs into every week, with proof of each run.
Needs 01
Model Context Protocol: your systems as tools. A minimal server, a read tool, a write tool behind a confirmation, an audit log, connected for the whole team.
You build An MCP server over one company system the team can use from Claude or opencode the next day.
Depth
How to know it still works: small eval sets, a rule for when the agent must ask, secrets and data handling, cost per run.
You build An eval for one of the team's agents, running in the repo.
Needs 05
What to automate next and what not to. The playbook, the owners, the sandbox-to-laptop move for those who want it.
You build A one-page automation roadmap for the quarter and the playbook the team keeps in the repo.
Up to four modules a day, 9:00 to 15:00 with breaks. Any path through the tree works; these are the usual ones.
1 day · 4 modules
Entry, agents, git, and the first document generator. The team leaves with a repo and four working things.
2 days · 8 modules
The whole tree. Day two can be on site or split into remote modules over two weeks.
1 day · 4 modules
Entry, git, MCP servers, evals. For the people who will own the tools the rest of the team uses.
Requirements
The sandbox, the tools and the API tokens come from me. Nothing is installed on company laptops unless the team wants to keep going afterwards.
Your team pays for AI subscriptions and uses them like a search box.
Two people in the company can automate things; the other twenty send them tickets.
You want the team to build its own small tools and agents, safely, and keep them in git.
What you get
The systems behind this service, with the numbers their owners cleared for publication.
Open source, maintained on GitHub.
The material for the modules on agents, git and browser automation was built on this repository.
Runs on
Claude
Anthropic
MCP
Git
Github
Node.js
Python
TypescriptTap a question. The answer comes back like a text.
Scoping calls · most weeks
Any device with a browser and internet. Each participant gets a sandbox over RDP with everything installed, plus opencode with API tokens I provide for the workshop. Nothing is installed on company laptops unless the team wants to keep going afterwards.
A Linux desktop per participant reachable from the browser: opencode with tokens, git, Node, Python, VS Code, Playwright with a browser, and the team repo cloned. It lives for the workshop plus 30 days; the repo is yours forever.
No. The tree shows what each module needs before it. Most teams start with the entry module and one day, then pick the branches that match their work. The order inside a day is fixed by the tree, the set is yours.
Two to twelve people. Two is a pair that wants to move fast; above twelve the hands-on part stops working and I split it into two groups.
Either. A day is up to four 75-minute modules with breaks. The first day works best in one room; the continuation modules run remote, one or two per week, on the team's real work.
No. The entry module needs a browser and nothing else. Mixed groups work best: non-developers ship documents, browser automations and small tools; developers take the MCP and evals branch of the tree.
Per module per group, not per seat. A day is up to four modules. Sandbox, tokens and the team repo are included; you get a quote after a short call about who is in the room and which branch of the tree they need.
Yes, before you send the brief if you need it. Send yours or use mine.
Something else? Ask it on the call
A 30-minute call, free
Leave an email. I reply within one working day with three questions and a proposed plan, not a deck.