Product Marketing

Product Marketing Brief Core Method

Use when: preparing the marketing strategy for a new product, major feature, or repositioning effort. This is the PMM's equivalent of a PRD — the strategic document that aligns everyone on how this product goes to market.

Target audience. Who is this for? Not the broad market — the specific buyer and user personas who will evaluate and adopt this product. Include their role, their pain, their current alternatives, and what triggers them to look for something new. Be precise: "VP of Engineering at Series B-D startups with 20-100 engineers" is actionable. "Technical leaders" is not.

Positioning statement. For [target customer] who [situation/need], [product] is a [category] that [key benefit]. Unlike [primary alternative], we [key differentiator]. This isn't copy — it's the strategic foundation that all copy derives from. Every team member should be able to recite the core positioning.

Value pillars. Three to five themes that organize your product's benefits. Each pillar gets a headline, a supporting claim, and proof points (data, customer quotes, demos). These pillars structure everything: the website, the sales deck, the launch messaging. More than five and you're saying too much. Fewer than three and you're likely underselling.

Competitive frame. Who do customers compare you to? Not who you think your competitors are — who customers actually evaluate alongside you. Define your differentiation against each, focusing on what matters to the buyer, not what you're proud of technically.

Key objections. What reasons do prospects give for not buying? Map each objection to a response. Sales teams need these before launch day, not after the first lost deal reveals a gap.

Message Testing Protocol Core Method

Use when: you have candidate messaging and need to validate that it resonates before committing it to the website, ads, and sales materials.

Concept testing. Show 3-5 message variants to target customers and ask: which best describes what this product does? Which is most compelling? Which would make you want to learn more? Use surveys (n=50+) for quantitative signal and interviews (n=5-8) for qualitative depth. Test positioning concepts, not polished copy — you're validating the strategic message, not the exact words.

A/B testing in market. Run the top 2-3 messages as ad variants or landing page headlines. Let real behavior (click-through rate, conversion rate) validate what surveys suggested. Surveys measure what people say they'd do. Market tests measure what they actually do. Both matter, but behavior wins when they conflict.

Win/loss validation. After deals close (or don't), interview buyers about what messaging resonated and what fell flat. This retroactive data is the highest-quality signal you'll get — it reflects actual purchase decisions, not hypothetical preferences.

Sales Enablement Kit Core Method

Use when: launching a new product or feature and need to arm the sales team with everything they need to position, demo, and close. A sales team that doesn't understand the product will describe it wrong. One that understands it but lacks tools will describe it differently every time.

Sales deck. Not a marketing deck with your logo on it — a deck designed for the sales conversation flow. Start with the customer's problem (not your company story), introduce the solution in terms of outcomes, show proof (customer results, demos), and end with a clear next step. 10-15 slides maximum. Every slide should earn its place in the conversation.

Competitive battle cards. One-page reference cards for each primary competitor. Include: what they claim, what's true, where we win, where they win, common objections when competing against them, and trap questions to ask prospects that highlight our advantages. Update quarterly — stale battle cards are worse than none because they give sales false confidence.

Objection handling guide. The top 10-15 objections with scripted responses. Not word-for-word scripts — frameworks that help reps respond naturally. Each objection gets: why the prospect says this, the truth behind it, how to respond, and a pivot to our strengths. Pull from real win/loss data, not assumptions.

Demo script and environment. A recommended demo flow that highlights differentiation, addresses common concerns, and tells a story. Include the "aha moment" — the specific thing in the demo that makes prospects lean forward. Maintain a demo environment that's always ready with realistic data.

One-pagers and leave-behinds. Collateral the sales rep can share after a meeting. Different versions for different personas — the CTO cares about architecture and security; the VP of Engineering cares about developer experience; the CFO cares about ROI. Same product, different emphasis.

Competitive Battle Card Template Core Method

Use when: a specific competitor comes up frequently in deals and the sales team needs a quick-reference guide to compete effectively.

Structure a battle card in four quadrants:

1. Overview — what the competitor does, their positioning, pricing model, target segment, recent news. Keep factual and current.
2. Where we win — specific capabilities, experiences, or outcomes where our product is genuinely better. Include proof points: benchmark data, customer quotes, feature comparisons.
3. Where they win — be honest about their strengths. Sales reps who discover these in a live conversation look unprepared. Acknowledge and pivot: "They're strong at X. What we've found is that customers who prioritize Y find that our approach to Z matters more.".
4. Trap questions — questions the sales rep can ask the prospect that naturally highlight competitive advantages. "How important is [thing we're great at] to your evaluation?" These steer the conversation toward your strengths without overt competitor bashing.

Feature Announcement Framework Core Method

Use when: deciding how to market a product update, from a minor improvement to a major release. Not every feature deserves a blog post — and some deserve more than a changelog entry.

Tier the launch. Assign each release a tier based on market impact, not engineering effort. Tier 1 (major): new product or category-defining release — full campaign, press, event, sales enablement refresh. Tier 2 (significant): important feature or expansion — blog post, email to customers, sales notification, landing page update. Tier 3 (incremental): improvement or enhancement — changelog entry, in-app notification, support documentation. Tier 4 (maintenance): bug fix, performance improvement — release notes only. The tiering prevents two failure modes: under-marketing a big release and over-marketing a small one.

Craft the narrative. Every launch announcement answers three questions: What changed? Why should I care? What do I do next? Lead with the customer benefit, not the feature name. "You can now close deals 40% faster with automated proposal generation" beats "Introducing ProposalBot AI." Technical details go in the documentation, not the announcement.

Coordinate timing. Work backward from the external announcement date. Sales needs battle cards and talking points before the public announcement — customers should never learn about your product from a blog post before their account rep tells them. Support needs documentation and FAQs before launch — the support queue spike on launch day shouldn't reveal documentation gaps. Marketing needs assets finalized and campaigns queued before the announcement — not scrambling to write the blog post the night before.

Win/Loss Interview (Marketing Lens) Core Method

Use when: gathering post-decision feedback to improve positioning, messaging, and competitive strategy. Product management runs win/loss to improve the product. Product marketing runs win/loss to improve how the product is sold and marketed.

Interview buyers 2-4 weeks after the decision (while memory is fresh). Ask: What alternatives did you evaluate? What criteria mattered most? At what point did you decide to go with us (or the competitor)? What messaging resonated? What claims did you doubt? What almost stopped you from buying? What would you tell a colleague considering our product?

The marketing-specific insights live in the messaging and perception answers. If buyers consistently say "I didn't understand what made you different from [Competitor]," your positioning needs work. If they say "Your pricing page was confusing," that's a conversion problem. If they say "The sales rep couldn't answer my question about [Topic]," that's an enablement gap. Pattern these across 15-20 interviews and you'll have a roadmap for marketing improvement that's grounded in actual buyer behavior.

Demo Design for Sales Core Method

Use when: creating or improving product demos that sales teams use to close deals.

Most product demos fail because they're feature tours, not stories. Effective demos are structured around the buyer's problem, not the product's capabilities. Demo scripting: Structure every demo as a narrative: start with the buyer's current pain (validated by discovery call), show the "before" state, then walk through the solution showing the "after." Each feature shown should connect to a specific pain point the buyer mentioned. Feature prioritization for demos: Show 3–5 features maximum. Pick the ones that address this specific buyer's top pain points, not the ones the product team is most proud of. Features not shown can be referenced as "we also do X" without a walkthrough. Interactive demo design: For self-serve sales motions, build interactive product demos (using tools like Navattic, Reprise, or Storylane) that let prospects explore on their own. These demos need careful path design: a guided happy path that shows value in under 3 minutes, with optional branches for deep dives. Track which paths prospects take to understand what matters to them.