Corporate training for product teams
Aakash Gupta teaches your team live, hands-on, in Claude Code. Every PM loads their own context and runs real skills on real tasks. Then the team joins its setups into one Team OS.
Starts with one team of up to 10 PMs and two live sessions. Programs and Company OS are scoped to your org.
Aakash built product at
Aakash Gupta
Former VP Product at Apollo.io · 15+ years in product
240K+
Product Growth subscribers
46K+
Growth Podcast YouTube subscribers
100+
iterations of the PM OS master file
15 sec
for a new engineer to get the reasoning behind a three-month-old decision from a Team OS
How an engagement runs
15 minutes. What your team already runs, what it repeats, and the logistics.
What gets installed, who attends, the pre-work, the dates, and what each PM leaves with.
Six short items, due 48 hours before Session 1.
Install and teach, then fix and build the Team OS, with real work in between.
What got installed, which issues were fixed, and the number each PM will track.
What the team ends up with
PM OS is the operating system Aakash runs his own product work on. Team OS is how a team shares one. Company OS is the same idea for the whole org.
Each PM
One folder holding the master instructions file, skills for the tasks they repeat, their context library, sub-agent reviewers and templates. Each PM loads their own product, users and metrics, then runs a skill on a real task before the first session ends.
Aakash’s own numbers: PRD drafts from 4-8 hours to 30 minutes, user interview processing from 2-3 hours to 15 minutes.
The team
The ten setups join into one shared layer, so answers stop living in people’s heads. /upgrade-to-team-os converts a personal setup and keeps personal context private. You pick the model that fits: everyone in the repo, one power user, or agents that handle the queries.
10 pings a day at 10 minutes each, 5 days a week, is 8+ hours a week going through one person.
The company
One repo of how the company works: people, owners, metrics, meetings, decisions and repeat tasks as skills, reachable in Slack. Added after the team layer runs, and only when each person’s skills and context are real.
Scoped on the call. It sits on top of PM OS and Team OS.
The workshop
Session 1 installs PM OS and teaches the skills. The PMs use it on their own work and log where it breaks. Session 2 fixes what broke and builds the Team OS.
What PM OS is
The master file, the skills, the context library, the sub-agents and the templates, on one screen.
Install together
Install what is missing on every PM’s machine and skip what they already have. Install and permission issues get fixed live.
Load their context
Company and product, users and competitors, key metrics, current priorities and the team’s templates. PMs dictate it and Claude fills the files.
Teach the skills on real work
Discovery: synthesize a PM’s own customer feedback or interview notes. Metrics: connect the analytics tool and ask it questions, if IT allows. Sub-agent reviewers check the output.
Each PM runs one skill
On a real task, in pairs, with Q&A. Each PM starts an issue log: the task, what broke, what fell short.
Issue logs, read out
One minute each, sorted into install, access, context and output quality.
Fix the issues live
Starting with the ones that hit several PMs.
Setup reviews
Aakash reviews three or four PMs’ setups on screen: context gaps, weak output, and work still done by hand that a skill could take.
Build the Team OS
Join the setups into one shared layer: shared context, shared queries, shared discipline. /upgrade-to-team-os runs live on one PM’s setup. The team picks its model.
Name the repeated work
Each PM names the work the OS now takes, what it frees, and the one number they will track.
What the workshop includes
Two live 90-minute sessions with Aakash
On video, hands-on, on your PMs’ own laptops, with Q&A throughout.
The work between them
Each PM uses PM OS on real tasks and logs where it breaks. Session 2 starts from those logs.
Setup reviews
Aakash reviews three or four PMs’ setups on screen and names the context gaps and the work a skill could take.
A working system
PM OS on each PM’s own context, and a Team OS the team already uses by the end of Session 2.
A one-page readout for you
What got installed, which issues were fixed, and the one number each PM will track.
Formats
One product team
Two 90-minute live sessions · up to 10 PMs
The shape we quote most. Session 1 installs PM OS on every PM’s own context. They use it between sessions and log where it breaks. Session 2 fixes those issues live and builds the Team OS.
Spec a workshopSeveral squads or a whole product org
Sessions per squad, office hours, one shared repo
The workshop run across squads, with a shared Team OS repo built together and follow-up office hours so the setups improve after the sessions end. Scoped to your teams.
Scope a programThe company, with an AI Ops owner
Intake sheet, permissions, rollout in the order that works
We stand up the Company OS for your org: intake, owners, connected tools, Slack as the door. The rollout waits until each person has real context and skills to start from.
Scope a rolloutWhy teams start here
A workshop is a fixed scope for one team. No annual seat bundle and no quarter-long commitment to start.
PMs bring their own tasks and inputs. The sessions run on those, and what they build keeps running after.
The person who built PM OS and Team OS teaches the Team Workshop and reviews the setups himself.
The 15-minute call ends with a written spec: what gets installed, who attends, the pre-work, the dates and what each PM leaves with.
Built to your spec
Aakash builds each workshop to the exact spec you want. On the call we ask four things, then send back what gets installed, who attends, the pre-work, the dates, and what each PM leaves with.
Pre-work for each PM
FAQ
Practising product managers who already know discovery and metrics and want to do both faster with Claude Code. A team of ten is the shape we quote most. Larger groups and mixed teams of PMs, designers and engineers are scoped on the call.
We ask first, on the 15-minute call. If it is blocked, the plan changes, so we agree the fallback on the call or decide not to proceed. We do not find this out in the first session.
Your PMs decide what goes into Claude Code and your security rules govern it. Pre-work asks for anonymized inputs where anything is sensitive. We agree data handling on the call.
Both live sessions with Aakash, the work your PMs do between them, Aakash’s review of three or four PM setups on screen, a working PM OS for each PM, a Team OS for the team, and a one-page readout for you after Session 2. The agenda for both sessions is on this page.
A working PM OS on their own context, tuned with Aakash, and an improvement list from the setup review. The team leaves with a Team OS it already uses on its own work.
When you want a library or a course for many people on their own schedules. Those teach the material to individuals. This runs privately for one team, on its real work, with a scope you agree on a call. If you want both, start with the workshop and scope the rest after it.
The sessions run on your PMs’ real work, on their own laptops, and the output is a system that keeps running after the call. Public talks and writing explain the ideas. These sessions put them to work on your team’s decisions.
Email us with your company, the number of PMs and your target dates. We set up a 15-minute spec call, then send the spec in writing with the price. Pricing depends on team size and format, so it is sent after the call, not published.
Email productgrowthppp@gmail.com with your company, the number of PMs and your target dates. We reply with times for the spec call.
As of Oct 2026. PM OS and Team OS figures are Aakash’s own, from www.news.aakashg.com/p/pm-os and www.news.aakashg.com/p/team-os-cc.