Product Marketer

---
name: product-marketer
description: Do product marketing — positioning, messaging, launches, sales enablement, and competitive intelligence.
category: business-marketing
---

## Overview

Product marketing sits between product and the market: translating what was built into why anyone should care. This skill covers positioning and messaging frameworks, go-to-market planning, launch execution, sales enablement, and competitive intelligence — the connective tissue that turns features into revenue.

## When to use

- Positioning a new product or feature
- Planning and running a product launch
- Writing messaging (homepage, one-pagers, decks)
- Enabling sales with battlecards and talk tracks
- Analyzing competitors and building battlecards
- Fixing "great product, weak adoption" problems

- Naming and packaging new products or features
- Creating competitive displacement campaigns
- Developing customer evidence (case studies, ROI calculators)
- Developing tiered pricing and packaging
- Creating sales battlecards
- Planning end-of-life communications
## Core concepts

**Positioning.** The mental slot your product occupies: for [target audience] who [need], [product] is a [category] that [key benefit], unlike [alternatives] which [weakness]. If prospects can't repeat your positioning after one conversation, it's not working.

**Messaging hierarchy.** Value proposition (one sentence) → 3 supporting pillars → proof points under each pillar → elevator pitch versions (10s, 30s, 2min). Everyone in the company should tell the same story at different depths.

**Buyer personas.** Go beyond demographics: goals, pains, buying triggers, objections, decision criteria, and where they get information. Interview real buyers; personas built from imagination mislead.

**Launch tiers.** Tier 1 (major: new product, big bet — full campaign), Tier 2 (meaningful feature — targeted push), Tier 3 (incremental — changelog + in-app). Match effort to impact; not every release deserves a launch.

**Sales enablement.** Battlecards (competitor strengths/weaknesses, trap questions, landmines), one-pagers, demo scripts, objection-handling guides, talk tracks. Enablement is measured by sales usage and win rates, not by decks produced.

**Competitive intelligence.** Track competitors' positioning, pricing, features, and messaging changes. Win/loss interviews are the richest source — ask lost deals why they chose the competitor.


**Jobs-to-be-done messaging.** Customers hire products to make progress in their lives. Messaging built on jobs (when [situation], I want [motivation], so I can [outcome]) resonates more than feature lists because it mirrors how buyers actually think and talk.

**Proof hierarchy.** Strongest to weakest: customer ROI data → named customer stories → analyst validation → awards → vendor claims. Build messaging upward from the strongest proof available, and invest in generating better proof (beta programs with measurement) where it is thin.

**Buyer personas for messaging.** Economic buyer (ROI, risk) → champion (career win, ease) → end user (daily pain relief) → technical evaluator (specs, security).
One message does not fit all — tailor proof points per persona while keeping the core narrative consistent.
Interview each persona type; internal assumptions about buyers are usually wrong.
**Category creation.** When no category fits: name the problem (not your solution), evangelize the problem's cost, position as the definitive answer.
Category creation is expensive and slow — only attempt with genuine differentiation and funding.
Most companies are better served winning an existing category than creating one.
**Sales enablement.** Battlecards (competitor handling), talk tracks, demo flows, objection handling, and ROI calculators.
Great enablement is used — track asset usage and retire what sales ignores.
Ride along on sales calls quarterly; enablement designed without field input misses.
## Practical workflow

1. **Research.** Interview 5–10 customers and 3–5 lost prospects. Review support tickets, reviews, and win/loss data. Map the competitive landscape.
2. **Draft positioning and messaging.** Write the positioning statement, value prop, and pillar messages. Test with friendly customers: "does this sound like us? Is anything missing or wrong?"
3. **Build the messaging house.** Document the hierarchy in one shareable page. Create channel-specific adaptations (homepage hero, ad copy, sales deck opening, email).
4. **Plan the launch.** For the tier: define goals, audience, key messages, timeline, channel plan (PR, email, social, in-app, sales), and success metrics. Work backward from launch day with clear owners.
5. **Enable sales.** Deliver battlecards, talk tracks, and demo flows two weeks before launch. Train the team; quiz them. Unused enablement is wasted work — follow up on adoption.
6. **Launch and measure.** Ship the campaign, monitor leading indicators (site traffic, demo requests, sales conversations), then lagging ones (pipeline, win rate, adoption). Run a retro: what landed, what didn't.

**Battlecard structure:** competitor overview → where they win → where we win → trap-setting questions → objection responses → proof points → pricing notes.


**Message testing protocol:** test value props with 5–8 target buyers using comprehension checks (in your own words, what does this do?), resonance ranking (which pillar matters most?), and differentiation probes (who else claims this?). Iterate until 80%+ describe it accurately.

**Launch tiering:** Tier 1 (major: new product, new market) → full campaign: PR, events, content, sales plays. Tier 2 (significant feature) → targeted: email, in-app, sales alert. Tier 3 (minor) → changelog only.
Tier honestly — everything cannot be Tier 1, and Tier 1 everything means Tier 1 nothing.
**Win/loss program:** interview 10–15 recent decisions quarterly (wins and losses) → code themes → share with product and sales → track action items.
Win/loss is the highest-signal marketing research — buyers tell you exactly why you won or lost.
## Common pitfalls

- **Feature-led messaging.** Leading with what it does instead of why it matters. Translate every feature into an outcome.
- **Positioning by committee.** Watered-down statements that offend no one and excite no one. Positioning requires choices — and choices exclude.
- **Launching without sales readiness.** Marketing launches while sales learns about it the same day. Enable sales first.
- **Stale battlecards.** Competitors move; battlecards updated annually mislead. Review quarterly.
- **No differentiation.** "Easy to use, great support, affordable" describes everyone. Find the genuinely different thing and prove it.
- **Measuring launches by activity.** Press mentions and pageviews are nice; pipeline and adoption are the point.
- **Internal jargon in external messaging.** Category names and acronyms the market does not use. Mirror customer language, verified in interviews.
- **Launching without a story.** Feature lists without narrative. Every launch needs: why now, why us, why it matters — in that order.
- **Feature-factory marketing.** Announcing features without customer outcomes. Every launch answers: what can customers now achieve that they could not before?
- **Ignoring post-launch.** Launch day is the starting line. Adoption campaigns, customer stories, and sales follow-through determine launch ROI.