Claude Code and Cowork Certificate for Product Managers and Leaders

A documented PM OS, not notes. A PRD writer Skill, a research synthesis Skill that cites its evidence, a clickable prototype of a real backlog item, and eval rubrics that define good enough. In week 4 you assemble the library into one system and present it to the cohort.

No. Claude Code runs in the terminal, but you type plain English into it. Week 1 starts from terminal basics with no prior experience assumed, and a Skill is an instruction file written in English, not a script. Nothing you build requires you to read or write code.

Yes, and it is the point. Bring a real backlog item, interview notes, or a product idea, because every build lands on your own context rather than a demo. If the material is confidential, bring an anonymised version and point the finished Skills at the real thing afterwards.

Most hand you a prompt pack. Prompts live in a chat window and die there. This builds Skills: reusable instruction files installed in Claude Code that carry your product context and hold the same standard every time you run them. You leave with a system, not a transcript.

Around four to five hours. The live session plus that week's build, which is your PRD Skill in week 1, research synthesis in week 2, a prototype in week 3, and the capstone in week 4. The builds are the course, so students who skip them leave with a recording and nothing installed.

No. The terminal is the only unfamiliar surface and week 1 covers it from zero. If you can write a spec and argue about scope, you can do this. The hard part is deciding what belongs in a Skill, and that is product judgement, not engineering.

Because the last mile of AI product work is deciding whether output is good enough to ship, and most teams decide that on vibes. Week 4 covers rubrics, test sets, and pass or fail criteria, so you hold a bar you can defend to engineering.

Yes, Pro or Max. Claude Code and Cowork are not on the free tier, and the subscription is separate from the course fee. It is also the tool you run your PM OS on afterwards, so treat it as part of the cost rather than an extra.

Week 1 is slower, because you are building the thing that makes you fast. From week 2 the PRD Skill turns a brief into a decision-ready draft in minutes instead of days. Nobody can promise you a specific number, and you should distrust anyone who does.

Everything is recorded and yours for life, along with every Skill, template, and prompt you build. If a bad month knocks you out entirely, you can defer to a future cohort at no extra cost rather than losing your place.

Yes. Maven gives you a receipt at checkout to send to your manager or finance team. Most companies are comfortable expensing it, especially once they see you can ship a clickable prototype on your own and on schedule.

Your purchase is backed by the Maven Guarantee. If something comes up and you cannot fully participate in your cohort, you can defer to a future cohort at no extra cost instead of losing your spot.