Product Marketing for New Products

Session Scope: The presentation outlines a framework for product marketing new products, focusing on narrative, pricing, and sales enablement.

Core Premise: A superior product fails if potential customers do not understand the need to buy it or how to purchase it.

Organizational Alignment: Product marketing sits at the intersection of marketing, sales, customer success, and product/engineering to aggregate customer feedback and iterate on offerings.

Customer Segmentation Strategy: Success requires defining the buyer beyond their job title, including their motivations, pain points, internal allies, and enemies.

Audience Selection Logic: Founders must consciously select initial target audiences to avoid building product priorities for the wrong market segment (e.g., choosing an SMB focus vs. a team within an enterprise for future upsell).

Early Adopter Approach: Companies should pitch solutions before product readiness to validate assumptions, requiring face-to-face iterations to read signals and adjust.

Executive Briefing Centers: Partnerships between portfolio companies and corporates allow for early exposure to new products, helping corporations align needs and companies validate product-market fit.

The Narrative (Story):

• Founders own the origin story, but it must be translated into scalable messaging that sales reps can deliver effectively.
• The customer-facing deck is the primary tool available before a product is fully built.
• Three Primary Market Obstacles:
  • Technical Understanding: Customers may not understand the new architecture, requiring explanation of the "why" and "how" (e.g., Opsware emphasized redundancy and scalability to win large enterprises).
  • Budget Availability: New categories often lack dedicated budget lines; sales must align with existing funded initiatives (e.g., data center consolidation, patching) rather than requesting new budgets.
  • Problem Recognition: Customers may not realize they have a problem; messaging must articulate the issue in the customer's specific terms rather than the vendor's preferred language.
• Deck Framework:
  • As-Is State: Define the current context at an appropriate depth (avoiding history lessons or excessive technical weeds) to frame the problem.
  • Why Current Solutions Fail: Explicitly articulate why existing tools or methodologies will not work in the new future world.
  • Requirements for the New World: Flip the failure points into specific requirements needed for a solution.
  • The Solution: Present the product as the direct answer to the outlined requirements.
  • Use Cases & Demos: Tailor demos to the specific audience level (executives need dashboards/reports; users need functional workflows) and ensure the demo environment matches the deck narrative.
  • Social Proof: Provide third-party recognition, customer stories, or blog posts to demonstrate market traction.
  • Next Steps: Propose concrete actions like proofs of concept (POC) or trials rather than ending with open-ended questions.
• Audience Customization: Create distinct deck versions for different personas (e.g., managers vs. users) using language and examples that resonate specifically with each group.

Pricing Strategy:

• Pricing Difficulty: Raising prices from a free or low-cost entry point is significantly harder than establishing a value-based price initially.
• Value Guidance: In new markets, vendors must actively guide customers on value since no historical benchmarks exist.
• Discounting Levers: Product marketing must provide sales with multiple pricing levers to optimize deal sizes and reduce friction.
• Packaging Structure:
  • Feature Fencing: Group features by user type (e.g., developer, team, enterprise) to create logical bundles.
  • Freemium & Tiering: Use free tiers for acquisition, but keep enterprise features (compliance, regulation) behind custom sales discussions to avoid handicapping deal expansion.
  • Web Transparency: Avoid publishing all pricing online; only reveal pricing for starter tiers to maintain negotiation flexibility for larger deals.
• Incentive Alignment: Pricing models should incentivize desired behaviors (e.g., charging for flow creation but not flow execution).
• Engineering Integration: Pricing requirements must be fed back into engineering, with mechanisms for "true-up" reporting to ensure customers pay for exceeded usage or specific feature sets.

Sales Enablement:

• Material Ownership: Product marketing, not sales, must own the creation of sales collateral to ensure consistency in messaging and criteria setting.
• Required Collateral Suite:
  • Customer-facing deck.
  • Customized demo workflows.
  • Pilot or Proof of Concept (POC) test plans that highlight competitive advantages.
  • Technical wrap-up documentation.
  • Formal proposals.
• Channel-Specific Tools: Provide developers with code access, technical details, and influencer reviews; avoid broad marketing campaigns until product maturity.
• Competitive Strategy:
  • Pattern Matching: Analyze how buyers attempt to categorize the new product against known competitors.
  • Differentiation Levels: Define if the product is a breakthrough, a comparative improvement, or a holistic solution.
  • Data Collection: Gather competitive insights from all organizational teams to rationalize and build winning strategies.
  • Unified Playbooks: Internal competitive strategies and external sales materials must be identical to bake in the correct evaluation criteria for buyers.
  • Battle Cards: Create documents listing required features, differentiators, and specific questions to ask competitors during the sales cycle.