The Claude product marketing decision framework [Series 6 of 6]

In part 1, I drew the map.

Chat, Cowork, Code, Design, Skills, Connectors – multiple distinct layers, each doing something different, all sharing the same foundation. Then we spent six editions going deep on each one.

You have the depth already. What I want to leave you with now is the decision framework – a way to look at any PMM task and know which surface to open.

💡

Want to go deeper on AI for PMMs?

Our AI for Product Marketing Certified course covers how to embed AI into positioning, messaging, and GTM. Worth a look if this series is landing for you.

The series in 60 seconds

One standout from each edition. The thing I’d want you to keep if you forgot everything else.

Part one: The Ecosystem

Claude is a system of surfaces, not a single tool. Chat, Cowork, Code, and Design each do fundamentally different things – but your Skills, your context, and your Connectors carry across all of them. Understanding the map before touching the tools changes what you end up building.

Part two: Cowork

This is where Claude starts producing deliverables. A working folder, a set of context files, and the desktop app – and suddenly Claude is writing your battle cards, your positioning docs, your launch briefs. The 20 minutes you spend on setup pays back on every task after that.

Part three: Skills

Your best conversation is your best starting point. After any session where the output is strong, ask Claude to create a Skill from it. And the biggest unlock I found: telling Claude what bad looks like. A set of negative constraints – phrases to avoid, structural patterns to block – changed the output quality more than anything else.

Part four: The Marketplace

Connectors bring your data in. Plugins give Claude capabilities. Skills give Claude your methodology. Stack all three and Claude stops working from a blank prompt and starts working from your actual Slack channels, your CRM data, and your positioning framework.

Part five: Code

The terminal sounds intimidating, but the interaction model is identical to Cowork – you describe what you want in plain English. The difference is what you get back: interactive dashboards, automated competitive monitoring, searchable objection libraries. Your Skills and context files carry straight over. The jump is genuinely smaller than it looks.

Part six: Design

A visual canvas where you build pages, decks, and videos by describing them. Landing page prototypes in 10 minutes. Sales decks in 15. Animated explainers from a text prompt. And the handoff to Code means your prototype can become a production page without rebuilding anything.

The PMM decision tree

I wanted to build a single reference you could come back to whenever you’re about to start a task and aren’t sure where to open it. Here’s how to read it.

What each surface actually does

Chat is where you think. You’re exploring a positioning angle, pressure-testing an argument, working through a strategic question with Claude as a sparring partner. Nothing gets produced. The value is the conversation – and often the best outcome is knowing what to go build somewhere else.

Cowork is where you produce. You need a file that exists when you’re done: a battle card, a positioning doc, a launch brief, a research summary. Cowork writes it, formats it, saves it to your folder, and applies your Skills automatically.

Code is where you build. You need something people interact with – a dashboard with filters, a monitoring system that runs weekly, an analysis that cross-references 20 files at once. If the output has a search bar, a filter, or runs on a schedule, it belongs here.

Design is where you make things look right. A landing page prototype where layout and hierarchy matter. A pitch deck that needs to look designed. An explainer video. If you’d normally wait for a designer, try this first.

How to route your PMM work

Research and analysis. Strategic questions and hypothesis testing go to Chat. A research summary or win/loss report goes to Cowork. Cross-referencing 20 customer transcripts against your messaging framework and pipeline data – that’s Code. The decision comes down to how many source files you’re working across and whether you need an interactive output.

Positioning and messaging**.** Exploring angles goes to Chat. Writing the positioning document goes to Cowork. Building a messaging testing tool where five stakeholders compare and vote on three options goes to Code. Prototyping the landing page so stakeholders can see the messaging in context goes to Design.

Content and creative. Blog posts, email sequences, and competitive briefs go to Cowork. Comparison pages, one-pagers, and explainer videos go to Design. Interactive content hubs and feature pages go to Code.

Sales enablement**.** Battle cards and talk track documents go to Cowork. Competitive decks and visual one-pagers go to Design. A searchable objection library built from Gong transcripts – where reps can find the right talk track mid-call – goes to Code.

Launch and GTM**.** Planning the launch strategy and sequencing the GTM timeline goes to Chat. Writing the launch brief, the campaign brief, and the GTM playbook goes to Cowork. The landing page prototype, the explainer video, and the sales deck go to Design. The launch readiness tracker that updates daily, and the competitive monitoring that catches reactions post-launch – those go to Code.

Where Skills and Connectors fit

They don’t need their own routing decision. You set them up once and they’re available across every surface.

Your positioning Skill applies in Cowork when you’re writing the doc and in Code when you’re building a messaging testing tool.

Your Slack connector works in Cowork when you’re pulling sales objections for a battle card and in Code when you’re building a competitive dashboard. Connect once, use everywhere.

The methodology and data follow you – you don’t re-configure anything when you switch surfaces.

The quick test

Two questions when you’re not sure where to go:

What’s the output?

Clarity --> Chat.

A document --> Cowork.

An interactive tool or automation --> Code.

A visual asset --> Design.

What does the audience do with it?

Read it --> Cowork.

Use it --> Code.

Look at it --> Design.

You’re the only audience --> Chat.

A launch, start to finish

Here’s what it looks like when all six layers work together on a single project.

You’re launching a new feature next quarter. You start in Chat, working through the positioning angle with Claude – exploring which competitor you’re positioning against, which use case to lead with, which persona cares most. Once you’ve got the direction, you move to Cowork.

In Cowork, you produce the positioning doc, the launch brief, and the competitive battle card. Your positioning Skill enforces your framework. Your Slack connector pulls the latest sales objections. Your HubSpot connector grabs the pipeline data so the battle card reflects what’s actually happening in deals this quarter.

Then you move to Design. You build a landing page prototype, a sales deck, and a 45-second explainer video. Your brand system keeps everything consistent. You walk into the positioning review with an interactive prototype instead of a slide deck – stakeholders react differently when they can see the messaging on a real page.

When the launch page is approved, you hand it to Code. The prototype becomes a production page. You build a launch readiness tracker that you update daily by telling Claude what’s changed. You set up competitive monitoring to flag any reactions from competitors in the weeks after launch.

One launch. Four surfaces. The same Skills, the same Connectors, the same context – following you through every step.

You won’t always use every surface. Some weeks, you live in Cowork producing briefs. Some weeks, you’re in Design building assets. The point is knowing which surface to reach for when, and knowing that whatever you’ve set up – your Skills, your context, your data connections – works everywhere.

The bottom line

Product marketing was never about producing assets efficiently. It was about deciding what deserved to exist in the first place – the positioning, the narrative, the competitive angle.

Claude handles the production. Your judgment decides what gets produced.

The full series: Mastering Claude as a product marketer

Part 1: Mastering Claude for product marketing**–** What everything actually is. The map.

Part 2: Claude Cowork for product marketing**–** How to set it up, the PMM workflows that benefit most, and how to go from “chat responses” to “finished deliverables in your folder.”

Part 3: The complete product marketing Claude skills pack**–** Everything you need to master Claude skills for product marketing

Part 4: The Claude marketplace for product marketing – Skills, plugins, and connectors. How to find them, install them, and build your own PMM toolkit.

Part 5: Claude Code for product marketing – When and why you’d go here. And why the jump from Cowork is smaller than you think.