• ½

    day to working agents

  • 6

    production-ready agent

  • 10

    Claude surfaces

What does your team walk away with?

A Claude AI agent workshop should send your team back to work with things they keep, not notes. Here is what each person and team takes away.

  • Working agents, live before you leave

    Your team builds and tests real agents during the session, working in three pods of two, for six production-ready agents scoped to your actual week: meeting prep, request triage, candidate comparison, or whatever fits. Each one is running on your real tools before the session ends.

  • A reusable skills library

    Custom SKILL.md files that teach Claude your processes once and apply them to every future task. Contract review, report formatting, a house style for briefs: written as Skills your team owns and keeps extending long after the workshop. This is the asset that compounds.

  • Role-specific playbooks

    Each attendee leaves with a personal playbook tailored to their function, not a generic handout. It names the agents worth building next for their role, the connectors those agents need, and the prompts that already worked.

  • Shared Claude fluency

    Your whole team leaves able to tell a Chat prompt from a Project, a Skill from a Managed Agent, and to know which surface a task calls for. No one has to be talked through the basics again, and no prior AI experience is assumed going in.

  • A map of your automatable work

    The discovery sprint leaves you with a ranked list of the tasks worth automating first, clustered into agent opportunity zones. It is a backlog your team can keep working on long after the workshop.

  • A prioritized 90-day roadmap

    A clear plan for the next quarter, plus a graduation path. When an agent outgrows the Claude platform and needs enterprise reliability or governance, it moves to our AI agent development services. When the backlog is bigger than one team, it feeds an AI consulting engagement.

How does a Claude AI agent workshop work?

Working agents, a reusable skills library, role playbooks and a 90-day roadmap: that is what your team walks out with. Here is how the half-day itself runs, segment by segment.

  • Frame & foundations (45 minutes)

    We orient the team on all ten Claude surfaces, so everyone shares a mental model before building. No one writes a prompt until the whole room can name the tool for the job.

     

  • Brainstorm & cluster (30 minutes)

    A guided discovery sprint where your team surfaces the tasks it repeats most, the handoffs that break, and the context that gets lost. We cluster those into agent opportunity zones and pick the ones worth building today.

  • Build hour (2 hours)

    Your team splits into three pods and builds two agents each, six in all, on its own workflows, with a facilitator at every table. Not a demo, not a sandbox: agents connected to your actual tools, running before the hour is out.

  • Share-back & next steps (30 minutes)

    Each pod demos what it built, we pressure-test it together, and you leave with a ranked backlog and a 90-day roadmap for what to build next.

What's covered in Claude training?

Your team walks out fluent in all ten Claude surfaces, knowing when to reach for each one. That is the Claude AI training you cannot get from the product docs.

  • Chat: The starting point for any task.
  • Connectors: Gmail, Drive, Slack, Notion and 50+ more, via Claude AI integration.
  • Projects: Context that travels with the work.
  • Artifacts: Docs, slides, apps and dashboards.
  • Skills: Teach once, apply forever.
  • Cowork: Claude works on your files directly.
  • Claude Code: Terminal-native for engineering.
  • Managed Agents: Hosted, long-running workflows.
  • Claude Design: Visual work through conversation.
  • Claude in Chrome: Browser-native agent automation.

Who are Claude AI agent workshops for?

This is corporate AI training scoped to one team's actual week, not an all-hands literacy session. It works best for a focused group of 6 to 15 people who share workflows. Three functions get the most out of it.

  • Operations and finance teams

    Replace repetitive coordination, reporting, and triage with agents that know your workflows and connect to your stack, the same pattern behind our AI automation services and the scheduling portal we built for Apex Leaders. Inbox and request triage. Weekly briefings and status summaries. Contract review and compliance flagging. Meeting prep pulled from calendar and email.

  • HR and recruiting teams

    Hand the administrative load to agents, so your team can focus on the areas that need a person’s touch. In the session an HR team will decide on what to build. For example, they can build agents that compare candidates against a rubric, run onboarding workflows and checklists, answer policy questions from your handbook, and schedule interviews. The hiring judgment stays with your recruiters; the admin runs on agents.

  • Engineering and product teams

    Put Claude to work inside the build, not just around it. Claude Code for real changes. Managed Agents for long-running jobs. MCP connector development for the tools you use. Code review triage.

Frequently Asked Questions

Reach Out

Ready to build with your team?

Tell us which team, what they do, and when you want to run it. We'll scope the right format and get it on the calendar.