Your engineers already use AI. This is the day they fix what's actually holding them back.
For engineers who already use AI daily and have hit the ceiling of one-shot prompting. We rebuild the foundations — mental models, agentic systems, a shared team setup — then spend the rest of the time applying them.
Pick the format that fits your team
One day
~9:30 AM – 4:30 PM
A full day, in the room. Followed by a half-hour of open conversation — where you can debate the best ideas further.
Logistics
- Best for teams who can clear a day and want the highest-density version.
- Travel & lodging not included. Waived for San Francisco Bay Area engagements.
See an indicative agenda
We calibrate order and depth with each team during scoping. The shape below is where we start, not a fixed program.
- 09:30Understanding the context window
- 10:30Prompting and conversation craft
- 11:30Trust, risk, and evaluation
- 12:30Lunch + open conversation
- 13:30Agentic system design
- 14:30MCP — the protocol
- 15:30Hooks, skills, and team setup
- 16:00Live use case — proof of concept on a group-picked problem
- 16:30Open Q&A
What you walk out with
Equal weight on what individuals leave with and what the team leaves with — both matter, and they reinforce each other.
For each engineer
- The missing pieces in techniques you're already using — why your approach isn't producing the results it should.
- A real mental model for agentic system design: feedback loops, reducing human-in-the-loop, knowing when an agent is the answer and when it isn't.
- Hands-on time with at least one tool or pattern you've been meaning to explore — enough to leave with a clear idea of how to apply it.
- The build itself is instructional: the architecture decisions, the tradeoffs, when to trust the model and when to push back.
For the team
- A shared setup guide for knowledge, agents, and skills — one person's discovery becomes the team's automatically.
- A live proof of concept built around a real use case the team picks together — ideally the one causing the most friction.
- A follow-up call after the workshop — to answer the questions that only come up once you're actually applying it.
From people I've worked through these ideas with
Past collaborators sharing what they learned working with me — the same concepts this workshop is built around.
“Even as someone who already uses AI tools daily, I walked away from Olivier's training with entirely new approaches I hadn't considered. He has a real talent for meeting people where they are and tailoring his expertise to his audience's specific needs — I'd recommend him to any team looking to get more out of AI.”
“Olivier's skills and intuition not only made me more productive but also changed the way I work. He is a true AI pioneer and an exceptional force multiplier for everyone around him — building tooling for Cline, GitHub Copilot, and Claude Code, as well as MCP servers that supercharge product discovery and Jira integration, among many others.”
“Olivier worked with the team and closely with each developer to identify opportunities and deliver actionable optimizations — boosting individual productivity and raising overall team output. He also helped us build customized AI skills at both the team and individual level. My advice to other teams: don't wait. The gap between teams using AI effectively and those still figuring it out is growing fast. Olivier will help you close that gap.”
The line between technical and non-technical roles is blurring. Coding is increasingly expected outside engineering — for self-reliance and for impact. A tailored variant of this workshop is available for teams navigating that shift.
Book a call to scope your workshop
A short call to look at your team, your friction points, and whether this is the right fit.
Some teams use this workshop as a starting point for a deeper engagement. If that's where you're headed, the Embedded AI Program is built for that. Embedded AI Program →