Claude Code & CoWork in 30 Minutes: For PMs and Leaders
Stop spending 25 minutes on tasks that only need your judgment for 5. This guide shows how PMs and leaders use Claude Code and CoWork together to automate status updates, meeting prep, research synthesis, and inbox triage - without writing code.
Key Takeaways
- Comprehensive strategies proven to work at top companies
- Actionable tips you can implement immediately
- Expert insights from industry professionals
What Claude Code and CoWork actually are
They are two different entry points into the same AI - each optimised for a different kind of work.
Claude Code is a terminal-native agentic coding system. You install it, open your project folder, describe what you want, and it reads your files, runs commands, and delivers a finished result. For PMs it means: prototype a feature, build an internal tool, synthesise a folder of research - all by describing it in plain English.
CoWork lives in the Claude desktop app. No terminal. No setup beyond the app you already have. You give it a task involving your files and desktop apps - draft this from my inbox, compile meeting notes, triage my action items - and it returns a finished deliverable. This is the entry point for most PMs and leaders.
Used together, they cover the full PM workflow: CoWork handles the information layer - gather, synthesise, organise - and Claude Code handles the build layer - prototype, automate, ship. You do not need both for every task. Knowing which one to reach for is what makes the combination powerful.
| - | Claude Code | CoWork |
|---|---|---|
| Interface | Terminal or VS Code extension | Claude desktop app |
| Who it's for | Developers and technical PMs | PMs, operators, leaders |
| Superpower | Build and ship software by describing it | Cross-app automation: Gmail + Calendar + Notion in one instruction |
| For PMs | Prototype features, build internal tools, synthesise research | Status updates, meeting prep, inbox triage, tracker updates |
5 things PMs and leaders are automating right now
1. Weekly status update, written automatically
Every week you pull updates from Notion, email, and your calendar. CoWork does that pull for you. Give it access to your tools, describe the format you want, and it returns a draft. You edit the two sentences that need judgment. Everything else is already there.
CoWork instruction
"Pull this week's completed tasks from my Notion project board, the key decisions from last week's meeting notes, and the top 3 priorities from my calendar for this week. Draft a status update in the format: what shipped, what's next, what I need."
2. Meeting prep in 3 minutes instead of 30
Before a stakeholder call you need the context from the last meeting, any open action items, and the agenda. CoWork compiles that from your calendar, notes, and email and has it waiting before you join.
CoWork instruction
"I have a call with [name] at 2pm. Pull the notes from our last meeting in Notion, any open action items assigned to them, and the last 3 emails between us. Summarise in a brief: context, open items, what I should cover today."
3. Research synthesis across documents
PMs and leaders doing market research or investment analysis spend hours reading and synthesising across tabs and docs. Claude Code pointed at a folder of research files - PDFs, CSVs, markdown notes - synthesises across all of them, extracts the key signals, and flags contradictions. No switching between sources.
Claude Code instruction
"Read all the files in /research/q2-competitive-analysis and give me: the 3 strongest signals, the 2 biggest unknowns, and a one-paragraph recommendation for the roadmap decision we are making on Thursday."
From the session
John from Nike raised exactly this - synthesising investment research across multiple documents, including Bloomberg data. Aki walked through how Claude Code handles multi-file synthesis natively, and how a custom MCP connector can pipe Bloomberg data directly into the workflow. A 3-hour research prep becomes a 10-minute structured brief.
4. Internal tools built before standup
The request that usually goes into an engineering sprint - "can someone build a simple dashboard that shows X" - can now be scoped and prototyped by a PM directly using Claude Code. You describe the tool in plain English, Claude Code builds a working version, and you arrive at the engineering conversation with something running, not just a spec.
Claude Code instruction
"Build a simple internal page that reads from our signups CSV and shows: total signups this week, breakdown by plan, and the top 5 referral sources. Plain HTML so the team can open it without any setup."
5. Automated routines that run without you
The most powerful use is routines that run on a schedule. Connect Claude Code to Gmail, Google Calendar, and Notion once via MCP. Then describe what you want to happen: every Friday at 4pm, pull this week's action items from my inbox, check which ones are overdue, and draft a follow-up for each. Claude runs it. You review the output.
From the session
Dean connected CoWork to his Gmail and had it pull every thread tagged "action required" and summarise the asks in a single list. What previously took 25 minutes of inbox scanning took 40 seconds. He now runs it every morning before his first meeting.
How to get set up: the 15-minute install
Install Claude Code
You install Claude Code once. After that it is available in any project folder on your machine.
# Install via terminal (requires Node.js)
npm install -g @anthropic-ai/claude-code
# Or install the VS Code extension:
# Extensions panel → search "Claude Code" → Install
Once installed, navigate to any folder and type claude to start. Claude reads everything in that folder and waits for your instruction.
Set up CoWork
CoWork lives inside the Claude desktop app. Download it from claude.ai, open it, and look for the CoWork tab. No terminal required.
Connect your tools with MCP
MCP (Model Context Protocol) is what lets Claude reach into Gmail, Google Calendar, Notion, Slack, and other tools. You connect a service once - Claude can use it in every future instruction.
- Open Claude Code settings by typing
/configin the terminal - Add an MCP connector for the service you want: Gmail, Calendar, Notion, Linear, or a custom data source
- Authenticate once with your account credentials
- From that point, Claude can read from and write to that service in any instruction
Custom MCP connectors
If your tool does not have a public MCP connector - like Bloomberg or a proprietary internal system - a custom one can be built. It exposes the data source as a tool Claude can call, using the same pattern as any other MCP integration. Reach out if you have a specific data source you want to connect.
The prompt pattern that makes the difference
The most common mistake is treating Claude like a search engine - asking a vague question and hoping for a useful answer. Claude Code and CoWork are instruction-following agents. The more precisely you describe the output you want, the better the result.
✗ "Summarise my emails"
- summarise what? For what purpose? What format?
✓ "Read my Gmail inbox for the last 7 days. Find every thread where someone
is waiting on a response from me. List them as: sender name, subject, what
they need, how many days since their last message. Sort by oldest first."
The structure that works every time: what to read → what to extract or do → what format to return it in. Add a time range and a sort order whenever relevant.
The before and after for PMs
| Task | Before | With Claude Code + CoWork |
|---|---|---|
| Weekly status update | 25 min pulling from 4 tools | 40 sec + 5 min review |
| Meeting prep brief | 30 min reading notes and email | 3 min instruction + review |
| Research synthesis | 3 hours across tabs and docs | 10 min brief from Claude Code |
| Internal tool prototype | Sprint ticket, 2-week wait | 30 min in Claude Code, running today |
| Inbox action item triage | 25 min every morning | Automated, waiting when you wake up |
What to prepare before the session
- Install Claude Code before you join. Run
npm install -g @anthropic-ai/claude-codein your terminal. Message us if you hit any issues and we will help you get set up before the session starts. - Download the Claude desktop app from claude.ai if you do not already have it.
- Pick one recurring task you want to automate. It does not have to be complex. Anything you do on a schedule using information from email, calendar, or docs is a candidate.
- Have your Anthropic API key ready. You will need it to authenticate Claude Code. Get one at console.anthropic.com.
Not a developer? You are the target audience.
This session is designed for PMs, operators, and leaders - not engineers. Aki will walk through every step in plain English. If you can describe what you want, you can build it.
Want to go further after this session?
The AI Native Product Management cohort covers exactly this stack - Claude Code, CoWork, MCP connectors, and AI features - live with Aki in a small group. You leave each session with something running, not a folder of notes. Browse upcoming sessions →
Aki Wijesundara
Expert team of AI professionals and career advisors with experience at top tech companies. We've helped 500+ students land internships at Google, Meta, OpenAI, and other leading AI companies.
Ready to Launch Your AI Career?
Join our comprehensive program and get personalized guidance from industry experts who've been where you want to go.
Table of Contents
Share Article
Get Weekly AI Career Tips
Join 5,000+ professionals getting actionable career advice in their inbox.
No spam. Unsubscribe anytime.