For problems bigger than a workshop.
Consulting is for when the fix isn't one session. A rollout that stalled. A team that was handed tools and no plan. A function that's supposed to lead the company on AI and hasn't been taught it yet. An engineering org whose AI-assisted development is still one developer at a time.
Every engagement is built from scratch, because every organization needs something different.
I've spent a decade on both the engineering side and the people side of technology, so engagements range widely: building an L&D team's AI curriculum, redesigning how an engineering team works with AI tools, helping leadership decide where AI belongs and which teams move first. If you're not sure which you need, let's have a conversation.
AI training your team will actually use.
Hands-on sessions shaped to your team's real work, so the skills stick after the session ends. Pick one below, or ask about a custom session.
Most people trust AI too much or too little. This fixes both.
Your team will
- Understand what AI, GenAI, and LLMs actually are, without the jargon
- Write prompts that get noticeably better results
- Know when to use AI, and when not to
- Solve a real business problem with AI
Most teams ask AI for answers. Yours will use it to build.
Your team will
- Build a real, working solution: a dashboard, an app, an automation, etc.
- Use AI to learn new skills as they go
- Leave with a repeatable process to do it again
Your team can teach anything. They just haven't been taught AI yet.
Your L&D team will
- Get hands-on with AI and Claude in their own design and delivery work
- Know which AI training actually changes how people work
- Decide what to make first, and what to skip
- Partner with the business on AI training instead of taking orders
Two days, built around your business.
Your L&D team will
- Work through your own learners, your own tools, your own constraints
- Build real training assets they can use the week after
- Get a shared point of view on AI across the whole team
- Test what actually works with your own people before it goes company-wide
The competitive edge isn't better tools. It's developers who know how to use them.
Your developers will
- See what today's AI tools can really do, not what they did a year ago
- Move past autocomplete to directing AI through real, complex work
- Manage context and token costs so AI delivers more, for less
- Put advanced features to work: skills, config files, custom workflows, etc.
AI doesn't stop at one developer. It accelerates the whole team.
Your team will
- Set up repo-level configuration and shared context files
- Agree on conventions so the whole team works the same way
- Build workflows that make AI a multiplier across the codebase
- Turn individual outputs into assets the whole team can use
Standardizing on Claude Code? See the Claude Code path →
Most managers use AI to save time. The best use it to lead better.
Your managers will
- Get AI to challenge, not flatter, and surface other perspectives
- Move faster on the hard parts: feedback, prioritization, team problems
- Hand the busywork to AI and free up time to lead
AI strategy is easy to set. Harder to lead.
Your executives will
- Get hands-on with the tools shaping the industry
- Direct AI investment toward real returns.
- Lead the shift with credibility, not just talking points
The 2-day intensive
Pick a track and go all in: two days to dig into your hardest problems and cover far more ground.
Available for any track.
Every workshop is adapted to the work your team actually does, and flexes to fit your size, format, and schedule. Don't see yours? Ask me about custom workshops →