Every output from this skill follows these standards without exception.

This skill helps you build and maintain a product marketing context document. This document is the foundation every other piece of marketing output should draw from. It defines who your customer is, what your product does for them specifically, how you are different from alternatives, and how you talk about all of this.

Without a shared product marketing foundation, every marketing surface becomes inconsistent. Your ads say something different from your website. Your sales deck uses different language than your onboarding emails. Your team writes copy from memory rather than from strategy.

This skill produces a living document, not a one-time deliverable. Products change. Markets shift. Customer language evolves. The product marketing context document needs to be reviewed quarterly and updated whenever a significant product change, customer shift, or competitive development occurs.

The central question this document must answer: why should a specific person, in a specific situation, choose your product over every alternative available to them right now?

To build a product marketing context document from scratch, provide:

To update an existing document, provide:

A complete product marketing context document has eight components. Each one builds on the previous.

A plain-language summary of what your product does, who it is for, and what it helps people accomplish. Two to four sentences.

This is not your tagline. It is not your elevator pitch. It is an internal document designed for clarity, not beauty. It should be specific enough that someone reading it could explain your product to a stranger accurately.

Bad product summary: "We help teams work better together."

Good product summary: "We build project management software for software development teams who ship weekly. The product replaces status meetings by making work visible in real time. Teams using it report shipping 30% faster and spending 40% less time in meetings."

The specificity in the good example is what makes it useful as a foundation. Every claim is grounded in a specific customer type, a specific outcome, and specific numbers.

Your ICP defines the specific type of customer that gets the most value from your product, is most likely to buy, and is most likely to retain.

The ICP is not every company that could theoretically use your product. It is the company profile where your product fits best, the value is clearest, and the sales cycle is most efficient.

A complete ICP includes:

Company characteristics:

Buyer characteristics:

Situational triggers:

Anti-ICP:

The ICP is calibrated from data, not intuition. Look at your top 20 customers by retention, NPS, and expansion revenue. What do they have in common? What does the profile of customers who churn early look like? The difference between those two groups is your ICP.

A positioning statement is an internal sentence or paragraph that defines where your product sits in the market. It is written for your team, not for customers. It answers the question: what is your product, for whom, and how is it different from alternatives?

The classic format (Geoffrey Moore, "Crossing the Chasm"):

For [target customer] who [has this problem], [Product Name] is a [category] that [key benefit]. Unlike [alternative], we [key differentiator].

Example: "For marketing teams at B2B SaaS companies who need to ship more content without adding headcount, ContentCo is a content operations platform that makes it possible for one writer to manage the output of three. Unlike project management tools, ContentCo is built specifically around content workflows, with editorial calendars, brief templates, and performance tracking that marketing leaders can use without involving their ops team."

A well-written positioning statement does three things: it names the customer specifically, it names the problem specifically, and it names the differentiator against a specific alternative. Vague positioning statements name none of these specifically.

Your value proposition describes the concrete value your product delivers. It is not a tagline. It is not a mission statement. It is the answer to "what will I get if I use this?"

A value proposition has three levels:

Functional value: what the product does. "Automates the manual work of building monthly reports."

Outcome value: what the customer achieves. "Your team closes the month in 2 days instead of 5."

Strategic value: why this matters at a business level. "You can scale revenue operations without scaling headcount."

Most marketing focuses only on functional value. The strongest value propositions articulate all three levels and lead with outcome or strategic value, not features.

Write your value proposition for each primary use case and customer role. A CFO and a marketing analyst will respond to different framings of the same product's value. The CFO cares about strategic value (cost reduction, scalability). The analyst cares about functional value (the specific time it saves them on specific tasks).

The messaging hierarchy organizes your key messages in order of priority. It defines:

Your primary message: the single most important thing you want a customer to understand about your product. This is your headline message. It should be compelling enough to earn the next five seconds of attention.

Your secondary messages (three to five): the supporting points that explain and validate your primary message. These map to the main objections and questions a buyer has after hearing your primary message.

Your tertiary messages (by audience segment): messages tailored to specific buyer roles, use cases, or stages of the funnel.

How to build the hierarchy:

Start with your primary message. This is often your most important differentiator, stated as a customer outcome. "Ship reports in hours, not days" is a primary message. "We have an intuitive interface" is not.

Build secondary messages around the five most common objections or questions your sales team hears after explaining the product. If prospects consistently ask "but can it handle our data volume?", that is a secondary message slot.

Build tertiary messages by interviewing customers in different roles and asking what they care about most. A CTO and a marketing analyst in the same company need different messages even though they are buying the same product.

The messaging hierarchy should be short enough to memorize and specific enough to act on. A 40-page messaging document that no one uses is not a messaging hierarchy. A single page with your primary and secondary messages is.

Competitive differentiation maps how your product compares to the alternatives your customers consider. "Alternatives" include direct competitors, adjacent tools, and doing nothing.

How to structure competitive differentiation:

Name each alternative explicitly. Not "other project management tools" but "Asana," "Monday.com," and "spreadsheets." Specific names are more useful for training sales teams and writing copy.

For each alternative, document:

Your differentiation should be true, defensible, and meaningful to customers. "We have a better UI" is not a defensible differentiator. "We are the only tool that integrates with both Salesforce and HubSpot without a middleware layer" is a specific, verifiable claim.

Avoid the "we're better at everything" trap. No product is genuinely better than every competitor on every dimension. Acknowledging where a competitor might be a better fit (and being clear about the customer profiles where you win) builds credibility and helps your sales team have more honest conversations.

Keep competitive differentiation updated. Competitors ship features. They change prices. They enter new segments. Competitive intelligence should be a quarterly review, not a one-time project.

The product narrative is the story of why your product exists and why it matters. It is the "long form" version of your positioning, designed to be told in sales calls, investor pitches, conference talks, and long-form content.

A strong product narrative has four elements:

The world before: what is the current state that creates the problem? Describe the environment that makes the problem exist and feel inevitable.

The problem: what specifically does your customer experience because of that environment? Use concrete, observable details. Not "teams struggle to collaborate" but "the weekly status meeting exists because no one can see what anyone else is doing."

The solution: how does your product change the situation? Describe the new state, not the features. Not "we have real-time updates" but "your team can see the status of every project without asking, which means your Monday meeting becomes optional."

The proof: evidence that the solution works. Customer outcomes, retention rates, case studies. Specific, named examples wherever possible.

The product narrative is not the same as your elevator pitch. It is a longer, richer story that earns the emotional investment of the listener by making the problem feel real before introducing the solution.

Use case mapping documents the specific jobs-to-be-done that your customers use your product for. Most products have two to five primary use cases. Each use case may have a different ICP, a different primary message, and a different conversion path.

For each use case, document:

The job to be done: what is the user trying to accomplish? Not a feature description but a task-level description of the work they are doing.

The customer profile: who is the primary user for this use case? Their role, their context, their goal.

The before state: what are they using now to do this job? What is painful or limiting about the current approach?

The after state: what does their work look like after they start using your product for this job? Specific, concrete changes in their workflow.

The key message: the one sentence that speaks directly to this use case customer.

The proof: a customer example or outcome that demonstrates this use case.

Use case mapping drives your content strategy, your ad targeting, your onboarding personalization, and your sales playbooks. Each use case is a different landing page, a different ad campaign, a different email sequence. Without mapping, you default to generic messaging that speaks to no one specifically.

A product marketing context document decays. The product changes. Customers change. Competitors change. Here is how to keep it current.

Quarterly review: schedule a 90-minute review every quarter with the people who are closest to customers. Your product manager, head of sales, a customer success lead, and your best salesperson. Ask: what has changed about who buys us, why they buy us, and what they say about us?

Trigger updates: outside of the quarterly review, certain events should trigger immediate document updates.

A significant product launch that changes your differentiation or expands your ICP.

A major competitor move: a new feature that erodes one of your differentiators, a price change, or a new player entering the market.

A shift in your ICP: if your last 20 customers are a different profile than your first 20, your ICP needs updating.

A message that stops working: if your primary message is generating fewer responses from ads, if your sales team is struggling with a specific objection that does not appear in the document, the document is behind reality.

Version control: date every version. When you update the document, archive the previous version with a date stamp. Being able to look back at how your positioning evolved is valuable context for future decisions.

Distribution: the document only helps if people use it. Share it with everyone who writes any customer-facing content: marketing, sales, product, customer success. Put it in a shared location everyone can access. Reference it in onboarding for new hires.

Writing for everyone: a positioning statement that says "we help businesses of all sizes" is not positioning. It is an absence of positioning. The more specifically you define your ICP, the more effective every piece of marketing becomes.

Leading with features instead of outcomes: customers do not care about your features. They care about what your features allow them to do, accomplish, or avoid. The features are the mechanism. The outcome is what they are buying.

Copying competitor language: if your positioning uses the same words as your top competitor, you are not differentiated. You are confirming the competitor's framing and asking customers to choose based on minor distinctions. Create your own language.

Neglecting the anti-ICP: failing to define who is not a good fit leads to winning deals you should not win. Those customers churn, write negative reviews, and drain customer success resources. Being clear about your anti-ICP is a sign of confidence, not limitation.

One-time positioning: the biggest mistake is treating product marketing as a one-time project. Markets move. The document must move with them.

Separating product marketing from product: product marketing should be involved in product decisions, not handed a finished product to market. The positioning implications of a product decision are part of the decision. Teams that separate these functions ship products that are hard to market because no one thought about market fit at the product level.