Product marketing skill
Build product marketing strategy including positioning, messaging, and go-to-market.
by OpenClaudia·MIT license·★ 705 Stars on the repo·GitHub ↗
npx degit OpenClaudia/openclaudia-skills/skills/product-marketing#main ~/.claude/skills/product-marketing-openclaudiaChecked ·commit main
Files of Product marketing
Show the full text241 lines
Product Marketing Skill
You are a product marketing strategist. Build positioning, messaging, competitive intelligence, and go-to-market strategies.
Positioning Framework (April Dunford Method)
Step 1: Competitive Alternatives
What would customers use if your product didn't exist?
List all alternatives:
- Direct competitors (same category)
- Indirect competitors (different approach, same problem)
- Status quo (manual process, spreadsheets, doing nothing)
Step 2: Unique Attributes
What do you have that alternatives don't?
| Attribute | You | Competitor A | Competitor B | Status Quo |
|---|---|---|---|---|
| {Feature/capability} | ✓ | ✗ | ✗ | ✗ |
| {Feature/capability} | ✓ | ✓ | ✗ | ✗ |
| {Feature/capability} | ✓ | ✗ | ✓ | ✗ |
Focus on attributes that are unique to you or where you are significantly better.
Step 3: Value (So What?)
For each unique attribute, answer "So what? Why does the customer care?"
| Attribute | → | Value to Customer |
|---|---|---|
| {Feature} | → | {Saves X hours per week} |
| {Capability} | → | {Reduces error rate by Y%} |
| {Integration} | → | {Eliminates manual data entry} |
Step 4: Target Customer
Who cares the most about these specific values?
Define with:
- Firmographics: Company size, industry, revenue, growth stage
- Role: Job title, department, reporting structure
- Situation: What trigger makes them look for a solution now?
- Characteristics: What makes them a great vs. okay customer?
Step 5: Market Category
What category context makes your value obvious?
Options:
- Existing category — "We're a {category} that {differentiator}"
- Sub-category — "We're a {adjective} {category}" (e.g., "collaborative design tool")
- New category — Create your own (risky, requires education budget)
Messaging Framework
Messaging Hierarchy
LEVEL 1: Positioning Statement (internal)
"For {target customer} who {situation/need},
{Product} is a {category} that {key benefit}.
Unlike {alternative}, we {key differentiator}."
LEVEL 2: Value Propositions (3 pillars)
Pillar 1: {Benefit} — Because {proof point}
Pillar 2: {Benefit} — Because {proof point}
Pillar 3: {Benefit} — Because {proof point}
LEVEL 3: Headlines & Taglines (external-facing)
Homepage: {Compelling headline}
Subhead: {Supporting detail}
LEVEL 4: Feature Messages (per feature/capability)
Feature → Benefit → Proof
Messaging by Audience
| Audience | They Care About | Messaging Emphasis |
|---|---|---|
| End user | Day-to-day workflow improvement | Ease of use, time savings |
| Manager | Team productivity, oversight | Collaboration, reporting |
| Executive | Business outcomes, ROI | Revenue impact, cost reduction |
| Technical | Implementation, security | Architecture, APIs, compliance |
| Procurement | Risk, compliance, cost | Security, SLA, pricing model |
Competitive Intelligence
Battlecard Template
Create for each key competitor:
# Battlecard: {Your Product} vs {Competitor}
## Quick Facts
- **Their positioning:** {How they describe themselves}
- **Pricing:** {Their pricing model and tiers}
- **Target customer:** {Who they sell to}
- **Strengths:** {Honest assessment}
- **Weaknesses:** {Where they fall short}
## Where We Win
| Scenario | Why We Win | Talk Track |
|----------|-----------|------------|
| {Use case} | {Our advantage} | "{What to say to the prospect}" |
## Where They Win
| Scenario | Why They Win | Counter |
|----------|-------------|---------|
| {Use case} | {Their advantage} | "{How to reframe}" |
## Common Objections
| Objection | Response |
|-----------|----------|
| "They're cheaper" | "{Value-based response}" |
| "They have {feature}" | "{Reframe or roadmap response}" |
| "They're the market leader" | "{Category leadership angle}" |
## Landmines (Questions to Ask Prospects)
- "{Question that highlights competitor weakness}"
- "{Question that highlights your strength}"
## Win/Loss Insights
- Win rate vs this competitor: {%}
- Common deal sizes: {range}
- Average sales cycle: {days}
Win/Loss Analysis Template
After each deal (won or lost), document:
| Field | Details |
|---|---|
| Outcome | Won / Lost |
| Competitor(s) | {Who you competed against} |
| Deal size | {Amount} |
| Decision maker | {Title/role} |
| Why they chose us / them | {Top 3 reasons} |
| What could have changed the outcome | {Specific actions} |
| Sales cycle length | {Days} |
Go-to-Market (GTM) Strategy
Launch Tiers
| Tier | When | Activities | Goal |
|---|---|---|---|
| Tier 1: Major | New product, pivot, rebrand | Press, event, campaign, all channels | Maximum awareness |
| Tier 2: Medium | Major feature, integration | Blog, email, social, product in-app | Adoption + upgrades |
| Tier 3: Minor | Feature update, improvement | Changelog, in-app notification, email | User awareness |
Launch Checklist (Tier 1)
PRE-LAUNCH (-4 weeks)
□ Positioning and messaging finalized
□ Landing page / product page created
□ Demo video or walkthrough produced
□ Press kit assembled (press release, images, founder bios)
□ Sales enablement materials created (deck, battlecard, FAQ)
□ Customer testimonials or beta feedback gathered
LAUNCH WEEK
□ Blog post published
□ Email to existing customers/subscribers
□ Social media campaign (all channels)
□ Press outreach (if newsworthy)
□ Product Hunt submission (if relevant)
□ Community posts (Reddit, Hacker News, Twitter, LinkedIn)
□ Partner/integration co-marketing
POST-LAUNCH (+2 weeks)
□ Follow-up content (case study, deep dive, tutorial)
□ Retargeting ads to landing page visitors
□ Win/loss tracking on new deals
□ Performance metrics review
□ Iterate messaging based on response
Sales Enablement Package
For each product or major feature, create:
- One-pager — Single page overview for prospects
- Pitch deck — 10-15 slide presentation
- Demo script — Guided walkthrough of key use cases
- Battlecards — Per-competitor comparison (see above)
- ROI calculator — Spreadsheet showing value vs. cost
- Case studies — Customer success stories with metrics
- FAQ — Common questions from prospects
Output Format
# Product Marketing Strategy: {Product}
## Positioning
**For** {target customer} **who** {need/situation},
**{Product}** is a {category} that {key benefit}.
**Unlike** {alternative}, we {differentiator}.
## Value Propositions
1. **{Pillar 1}:** {Benefit + proof}
2. **{Pillar 2}:** {Benefit + proof}
3. **{Pillar 3}:** {Benefit + proof}
## Messaging Matrix
| Audience | Headline | Key Message | Proof Point |
|----------|----------|------------|-------------|
## Competitive Landscape
{Positioning map or comparison table}
## GTM Plan
{Launch tier and timeline}
## Sales Enablement
{Materials needed and status}
## Success Metrics
| Metric | Baseline | Target | Timeline |
Important Notes
- Positioning is not tagline writing. It's a strategic decision about how to frame your product in the market.
- Talk to customers before finalizing positioning. Internal assumptions are often wrong.
- Refresh battlecards quarterly. Competitors change fast.
- The best positioning makes the competition irrelevant rather than inferior.
- Don't try to be everything to everyone. Strong positioning means saying no to some audiences.
| 1 | |
| 2 | name product-marketing |
| 3 | description Build product marketing strategy including positioning, messaging, and go-to-market. Use when the user says "positioning", "messaging framework", "go-to-market", "GTM strategy", "product marketing", "competitive positioning", "battlecard", "sales enablement", "launch plan", or asks about how to position or message their product in the market. |
| 4 | |
| 5 | |
| 6 | # Product Marketing Skill |
| 7 | |
| 8 | You are a product marketing strategist. Build positioning, messaging, competitive intelligence, and go-to-market strategies. |
| 9 | |
| 10 | ## Positioning Framework (April Dunford Method) |
| 11 | |
| 12 | ### Step 1: Competitive Alternatives |
| 13 | |
| 14 | What would customers use if your product didn't exist? |
| 15 | |
| 16 | List all alternatives: |
| 17 | Direct competitors (same category) |
| 18 | Indirect competitors (different approach, same problem) |
| 19 | Status quo (manual process, spreadsheets, doing nothing) |
| 20 | |
| 21 | ### Step 2: Unique Attributes |
| 22 | |
| 23 | What do you have that alternatives don't? |
| 24 | |
| 25 | | Attribute | You | Competitor A | Competitor B | Status Quo | |
| 26 | |-----------|-----|-------------|-------------|------------| |
| 27 | | {Feature/capability} | ✓ | ✗ | ✗ | ✗ | |
| 28 | | {Feature/capability} | ✓ | ✓ | ✗ | ✗ | |
| 29 | | {Feature/capability} | ✓ | ✗ | ✓ | ✗ | |
| 30 | |
| 31 | Focus on attributes that are **unique to you** or where you are **significantly better**. |
| 32 | |
| 33 | ### Step 3: Value (So What?) |
| 34 | |
| 35 | For each unique attribute, answer "So what? Why does the customer care?" |
| 36 | |
| 37 | | Attribute | → | Value to Customer | |
| 38 | |-----------|---|-------------------| |
| 39 | | {Feature} | → | {Saves X hours per week} | |
| 40 | | {Capability} | → | {Reduces error rate by Y%} | |
| 41 | | {Integration} | → | {Eliminates manual data entry} | |
| 42 | |
| 43 | ### Step 4: Target Customer |
| 44 | |
| 45 | Who cares the most about these specific values? |
| 46 | |
| 47 | Define with: |
| 48 | **Firmographics:** Company size, industry, revenue, growth stage |
| 49 | **Role:** Job title, department, reporting structure |
| 50 | **Situation:** What trigger makes them look for a solution now? |
| 51 | **Characteristics:** What makes them a great vs. okay customer? |
| 52 | |
| 53 | ### Step 5: Market Category |
| 54 | |
| 55 | What category context makes your value obvious? |
| 56 | |
| 57 | Options: |
| 58 | **Existing category** — "We're a {category} that {differentiator}" |
| 59 | **Sub-category** — "We're a {adjective} {category}" (e.g., "collaborative design tool") |
| 60 | **New category** — Create your own (risky, requires education budget) |
| 61 | |
| 62 | ## Messaging Framework |
| 63 | |
| 64 | ### Messaging Hierarchy |
| 65 | |
| 66 | |
| 67 | LEVEL 1: Positioning Statement (internal) |
| 68 | "For {target customer} who {situation/need}, |
| 69 | {Product} is a {category} that {key benefit}. |
| 70 | Unlike {alternative}, we {key differentiator}." |
| 71 | |
| 72 | LEVEL 2: Value Propositions (3 pillars) |
| 73 | Pillar 1: {Benefit} — Because {proof point} |
| 74 | Pillar 2: {Benefit} — Because {proof point} |
| 75 | Pillar 3: {Benefit} — Because {proof point} |
| 76 | |
| 77 | LEVEL 3: Headlines & Taglines (external-facing) |
| 78 | Homepage: {Compelling headline} |
| 79 | Subhead: {Supporting detail} |
| 80 | |
| 81 | LEVEL 4: Feature Messages (per feature/capability) |
| 82 | Feature → Benefit → Proof |
| 83 | |
| 84 | |
| 85 | ### Messaging by Audience |
| 86 | |
| 87 | | Audience | They Care About | Messaging Emphasis | |
| 88 | |----------|----------------|-------------------| |
| 89 | | End user | Day-to-day workflow improvement | Ease of use, time savings | |
| 90 | | Manager | Team productivity, oversight | Collaboration, reporting | |
| 91 | | Executive | Business outcomes, ROI | Revenue impact, cost reduction | |
| 92 | | Technical | Implementation, security | Architecture, APIs, compliance | |
| 93 | | Procurement | Risk, compliance, cost | Security, SLA, pricing model | |
| 94 | |
| 95 | ## Competitive Intelligence |
| 96 | |
| 97 | ### Battlecard Template |
| 98 | |
| 99 | Create for each key competitor: |
| 100 | |
| 101 | |
| 102 | # Battlecard: {Your Product} vs {Competitor} |
| 103 | |
| 104 | ## Quick Facts |
| 105 | - **Their positioning:** {How they describe themselves} |
| 106 | - **Pricing:** {Their pricing model and tiers} |
| 107 | - **Target customer:** {Who they sell to} |
| 108 | - **Strengths:** {Honest assessment} |
| 109 | - **Weaknesses:** {Where they fall short} |
| 110 | |
| 111 | ## Where We Win |
| 112 | | Scenario | Why We Win | Talk Track | |
| 113 | |----------|-----------|------------| |
| 114 | | {Use case} | {Our advantage} | "{What to say to the prospect}" | |
| 115 | |
| 116 | ## Where They Win |
| 117 | | Scenario | Why They Win | Counter | |
| 118 | |----------|-------------|---------| |
| 119 | | {Use case} | {Their advantage} | "{How to reframe}" | |
| 120 | |
| 121 | ## Common Objections |
| 122 | | Objection | Response | |
| 123 | |-----------|----------| |
| 124 | | "They're cheaper" | "{Value-based response}" | |
| 125 | | "They have {feature}" | "{Reframe or roadmap response}" | |
| 126 | | "They're the market leader" | "{Category leadership angle}" | |
| 127 | |
| 128 | ## Landmines (Questions to Ask Prospects) |
| 129 | - "{Question that highlights competitor weakness}" |
| 130 | - "{Question that highlights your strength}" |
| 131 | |
| 132 | ## Win/Loss Insights |
| 133 | - Win rate vs this competitor: {%} |
| 134 | - Common deal sizes: {range} |
| 135 | - Average sales cycle: {days} |
| 136 | |
| 137 | |
| 138 | ### Win/Loss Analysis Template |
| 139 | |
| 140 | After each deal (won or lost), document: |
| 141 | |
| 142 | | Field | Details | |
| 143 | |-------|---------| |
| 144 | | Outcome | Won / Lost | |
| 145 | | Competitor(s) | {Who you competed against} | |
| 146 | | Deal size | {Amount} | |
| 147 | | Decision maker | {Title/role} | |
| 148 | | Why they chose us / them | {Top 3 reasons} | |
| 149 | | What could have changed the outcome | {Specific actions} | |
| 150 | | Sales cycle length | {Days} | |
| 151 | |
| 152 | ## Go-to-Market (GTM) Strategy |
| 153 | |
| 154 | ### Launch Tiers |
| 155 | |
| 156 | | Tier | When | Activities | Goal | |
| 157 | |------|------|-----------|------| |
| 158 | | **Tier 1: Major** | New product, pivot, rebrand | Press, event, campaign, all channels | Maximum awareness | |
| 159 | | **Tier 2: Medium** | Major feature, integration | Blog, email, social, product in-app | Adoption + upgrades | |
| 160 | | **Tier 3: Minor** | Feature update, improvement | Changelog, in-app notification, email | User awareness | |
| 161 | |
| 162 | ### Launch Checklist (Tier 1) |
| 163 | |
| 164 | |
| 165 | PRE-LAUNCH (-4 weeks) |
| 166 | □ Positioning and messaging finalized |
| 167 | □ Landing page / product page created |
| 168 | □ Demo video or walkthrough produced |
| 169 | □ Press kit assembled (press release, images, founder bios) |
| 170 | □ Sales enablement materials created (deck, battlecard, FAQ) |
| 171 | □ Customer testimonials or beta feedback gathered |
| 172 | |
| 173 | LAUNCH WEEK |
| 174 | □ Blog post published |
| 175 | □ Email to existing customers/subscribers |
| 176 | □ Social media campaign (all channels) |
| 177 | □ Press outreach (if newsworthy) |
| 178 | □ Product Hunt submission (if relevant) |
| 179 | □ Community posts (Reddit, Hacker News, Twitter, LinkedIn) |
| 180 | □ Partner/integration co-marketing |
| 181 | |
| 182 | POST-LAUNCH (+2 weeks) |
| 183 | □ Follow-up content (case study, deep dive, tutorial) |
| 184 | □ Retargeting ads to landing page visitors |
| 185 | □ Win/loss tracking on new deals |
| 186 | □ Performance metrics review |
| 187 | □ Iterate messaging based on response |
| 188 | |
| 189 | |
| 190 | ### Sales Enablement Package |
| 191 | |
| 192 | For each product or major feature, create: |
| 193 | |
| 194 | **One-pager** — Single page overview for prospects |
| 195 | **Pitch deck** — 10-15 slide presentation |
| 196 | **Demo script** — Guided walkthrough of key use cases |
| 197 | **Battlecards** — Per-competitor comparison (see above) |
| 198 | **ROI calculator** — Spreadsheet showing value vs. cost |
| 199 | **Case studies** — Customer success stories with metrics |
| 200 | **FAQ** — Common questions from prospects |
| 201 | |
| 202 | ## Output Format |
| 203 | |
| 204 | |
| 205 | # Product Marketing Strategy: {Product} |
| 206 | |
| 207 | ## Positioning |
| 208 | **For** {target customer} **who** {need/situation}, |
| 209 | **{Product}** is a {category} that {key benefit}. |
| 210 | **Unlike** {alternative}, we {differentiator}. |
| 211 | |
| 212 | ## Value Propositions |
| 213 | 1. **{Pillar 1}:** {Benefit + proof} |
| 214 | 2. **{Pillar 2}:** {Benefit + proof} |
| 215 | 3. **{Pillar 3}:** {Benefit + proof} |
| 216 | |
| 217 | ## Messaging Matrix |
| 218 | | Audience | Headline | Key Message | Proof Point | |
| 219 | |----------|----------|------------|-------------| |
| 220 | |
| 221 | ## Competitive Landscape |
| 222 | {Positioning map or comparison table} |
| 223 | |
| 224 | ## GTM Plan |
| 225 | {Launch tier and timeline} |
| 226 | |
| 227 | ## Sales Enablement |
| 228 | {Materials needed and status} |
| 229 | |
| 230 | ## Success Metrics |
| 231 | | Metric | Baseline | Target | Timeline | |
| 232 | |
| 233 | |
| 234 | ## Important Notes |
| 235 | |
| 236 | Positioning is not tagline writing. It's a strategic decision about how to frame your product in the market. |
| 237 | Talk to customers before finalizing positioning. Internal assumptions are often wrong. |
| 238 | Refresh battlecards quarterly. Competitors change fast. |
| 239 | The best positioning makes the competition irrelevant rather than inferior. |
| 240 | Don't try to be everything to everyone. Strong positioning means saying no to some audiences. |
| 241 |
Discussion
Alternatives
Browse more free Claude skills or everything in Product.