Hands-on Workshop
Claude for Product Teams
Level up the whole product org. Use Claude Cowork to delegate the work you currently do by hand, use Claude Code to build personal agents and small internal tools, and turn the meetings, inboxes, and spreadsheets that eat your week into running automations.
Why this workshop exists
Product teams are sitting on top of a quiet productivity unlock that almost nobody is using fully. Most people in product roles stop at "Claude as a smarter chat box." They write a PRD, paraphrase research, get unstuck on a tricky email. That is fine, and it is also a tiny fraction of what is now possible.
The leap is two-sided. Claude Desktop now makes advanced agentic tools accessible in two new tabs: Claude Cowork and Claude Code. Claude Cowork turns Claude into a delegate that can sit on your shared documents, your inbox, your tickets, and your research drives, and do the back-and-forth work you would normally do yourself. Claude Code lets anyone in product, not just engineers, ship small but real software: a personal agent, a script that parses your email and posts a daily digest, a tiny internal tool for the team to use on Monday.
This workshop teaches both, end to end, using your own work as the material.
The Programme
Eight modules. Heavy on practice, light on slides. Bring a real product task and ship something with it.
Pick the right Claude plan for your role, configure Cowork and Claude Code on your machine, set up memory and projects so Claude actually knows your product, your stack, and your voice.
Delegate file-based product tasks: turning customer-call transcripts into themes, drafting PRDs from a problem statement and a Linear backlog, comparing competitors against a feature matrix, refreshing a roadmap deck from raw notes.
Wire Claude into Notion, Linear or Jira, Drive, Outlook or Gmail, Slack, and GitHub. Keep it in sync with your specs, tickets, transcripts, and design docs so it stops asking you to paste things in.
Use Claude Code to build a scoped, opinionated agent for your role. PMs build a shipping coach that audits PRDs and Linear tickets. Designers build a critique partner. Researchers build an interview synthesiser. You leave with a real one.
The single highest-leverage automation for most product roles. Parse incoming email, extract action items, route by priority, generate a morning digest, draft replies in your voice. Built live, end to end.
Build a small but real internal tool with Claude Code: a lightweight dashboard, a viewer for some messy data, a form that turns input into a structured Notion page. Hosted by the end of the day.
Turning a recurring task you currently do by hand into a repeatable agent or skill. Naming, scoping, version control basics, sharing patterns with the team, and knowing when to stop polishing.
What stays personal, what lives at team level, what needs IT involved. Security boundaries, secrets, data handling, and a 30-day roll-out plan you sign off on before you leave.
The Experience
Designed for how product people actually learn
Concept, Practice, Reflect
Every block is a short framing, then twenty to forty minutes of doing, then a structured share-back. No long lecture sections.
Built Around Your Stack
We adapt the demos to your toolchain (Linear vs Jira, Notion vs Confluence, Gmail vs Outlook, Figma, Amplitude) so what you build during the day works on Tuesday with no rewrite.
Everyone Ships
Designers, researchers, and ops people often arrive thinking this is the engineers workshop. They leave with a running automation. We have designed it that way on purpose.
What Shipping by Monday Actually Looks Like
A few examples from real product teams. These are the size of thing people typically leave with, not aspirational stretch projects.
For: PM
Inbox triage agent
Reads the PM inbox each morning, separates customer escalations from internal chatter, pulls feature requests as candidate Linear tickets, posts a daily digest in Slack. Half a day to build. Saves 45 minutes a morning.
For: Researcher
Customer-call synthesiser
Takes a Teams or Zoom transcript, extracts themes against the team research codebook, cross-references quotes, drafts a one-page summary for the team channel. Replaces a multi-hour weekly chore.
For: Group PM
PRD auditor
Sits on the team Notion. When a PM marks a draft ready for review, it checks against the team PRD checklist, flags missing sections, suggests questions an engineer would ask, and posts the result as a comment.
For: PM
Spec-to-tickets converter
Reads a finalised PRD, drafts a tree of Linear tickets with acceptance criteria, lets the PM review and edit before creating them. Cuts an hour of finger work down to ten minutes of judgement.
For: Product Ops
Ask-the-docs internal tool
A tiny web app the team can ask questions of, indexed against the company product wiki and runbook. Hosted and accessible by the end of the workshop.
None of these are research projects. They are small, sharp, and real, and they are exactly the kind of thing this workshop teaches everyone in the room to build.
What You Walk Away With
- A working personal agent, scoped to your role and your team's stack
- At least one running automation that does something useful by Monday
- A small internal tool you built yourself during the day, hosted somewhere your team can reach
- A shared playbook of prompts, skills, connectors, and patterns the whole team keeps extending
- A clear sense of where Cowork ends and Claude Code begins, and when to reach for each
- Concrete next steps for the next 30 days, agreed in the room
Who It's For
You do not need to write code. If you have ever edited a Notion doc, set up a Zap, or written a SQL query, you have more than enough to keep up.
- Product managers and senior PMs
- Group product managers and product leads
- Product designers and design ops
- User researchers and research ops
- Product analysts and data PMs
- Product ops, programme managers, chiefs of staff
- Engineering managers modelling the new workflow
Pick a Format
Same curriculum, different depth. We come to your office or run it virtual. Group size up to 20 for tight, hands-on work. Larger formats shift toward offsites with multiple facilitators.
Half Day
Cowork end-to-end
Enough to cover Cowork end-to-end and ship a small automation. Best for teams who already have some Claude muscle and want to push deeper into delegation.
- Modules 1 to 5
- A working automation by the end
- Shared prompt library for the team
- Up to 20 people
Full Day
Add the Claude Code build track
You finish the day with a personal agent, an automation, and a small internal tool, plus a shared playbook the team keeps using.
- All eight modules
- A personal agent + an automation + an internal tool
- Hosted, working, ready to demo on Monday
- Up to 20 people
Pre-work, about 30 minutes
- Each participant has a Claude plan that includes Cowork (Pro or Team).
- Claude Code installed on the laptop they will bring (we send a one-page setup guide).
- One real task they currently do by hand and would love to never do again. That task becomes their workshop project.
Ready to Level Up Your Whole Product Org?
Book a discovery call. We will talk through your team, your stack, and what useful by Monday looks like for you, then put together a tailored proposal.
Also From Our Education Hub
For Engineers
GenAI for Engineering Teams
Plan-driven development, agentic coding, and quality guardrails for engineering teams.
For Marketing
GenAI Marketing Resources
Public and private workshops, free resources, and the prompt guide for marketers.
For Executives
GenAI for Leaders
Strategic framing, governance, and executive briefings for senior leadership.
Frequently Asked Questions
Do non-engineers really build internal tools in this workshop? +
Yes. That is the point. Claude Code makes it possible for a PM or a designer to ship a small, useful tool by the end of a workshop day, with the right scaffolding and supervision. We have done it many times. The tools are small on purpose.
What if our team has a mix of AI experience? +
Good. Mixed teams work better in this format than uniform ones. We meet each participant where they are. The more advanced people often end up coaching the less advanced ones during the practice blocks, which is exactly what you want happening on Monday too.
Is this just a Claude Code workshop with a different name? +
No. About half of the day is Cowork, which most product roles get more value from than Claude Code. Claude Code unlocks a different class of work (agents, automations, tools) and it is a genuine step up, but the workshop is balanced across both.
How does this differ from your engineering workshop? +
The engineering workshop goes deep on plan-driven development, code review, and quality guardrails for teams already shipping AI-assisted code. This workshop is product-wide. We build smaller things, the bar is "useful by Monday" rather than "production-ready," and we put much more emphasis on Cowork, integrations, and workflow design.
How does this differ from your marketing workshop? +
Same backbone, different examples. Marketing teams care about content engines, brand voice, and campaign ops. Product teams care about specs, tickets, research synthesis, and internal tools. The exercises and the demo material are different.
Can we run this just for our PMs, just for designers, or just for researchers? +
Yes, and we will tune the examples accordingly. The mixed-role version tends to be the most fun, but role-specific cohorts also work well, especially in larger product orgs.