Marketing Product DescriptionsAdvanced68 minSaves 2+ hours

Multi-Persona Message House for B2B SaaS Products

Product Marketing Managers in B2B SaaS can define a core product message, adapting it for end-users, buyers, and executive sponsors, ensuring alignment across diverse buying committees.

This prompt guides B2B SaaS PMMs through creating a comprehensive message house. It covers a core promise, three pillars with proof points, and tailored messaging for end-users, buyers, and executive sponsors, ensuring strategic alignment for complex sales cycles.

ChatGPT Claude Gemini

READY-TO-USE PROMPT

Copy Prompt

prompt.txt

As a seasoned Product Marketing Manager, your objective is to develop a comprehensive message house for a B2B SaaS product. This message house must address the distinct perspectives of a multi-persona buying committee, typically comprising an end-user, a primary buyer, and an executive sponsor.

### Role
You are a strategic Product Marketing Manager with deep expertise in B2B SaaS positioning and messaging, skilled at translating complex product value into compelling narratives for varied audiences.

### Context
Your task is to craft a message house for `{{product_name}}`, a B2B SaaS solution. The product description is: `{{product_description}}`. The primary target ICP is `{{target_icp}}`.

The message house needs to articulate a single core promise, supported by three distinct message pillars. Each pillar must be substantiated by three specific proof points. Crucially, the entire structure—core promise, pillars, and proof points—requires translation for three specific personas:

1.  **End-User:** Focus on daily workflow improvements, efficiency gains, and direct impact on their tasks.
2.  **Buyer:** Emphasize ROI, cost savings, risk reduction, and departmental performance.
3.  **Executive Sponsor:** Highlight strategic value, business growth, competitive advantage, and alignment with company-wide objectives.

Maintain a sharp, buyer-centric, and differentiated tone throughout the entire message house.

### Task
Develop the message house following the structure outlined below. Ensure each section is tailored for the specified personas.

### Constraints
*   **One Core Promise:** A single, overarching benefit statement.
*   **Three Message Pillars:** Each pillar must clearly support the core promise.
*   **Three Proof Points per Pillar:** Specific, quantifiable, or qualitative evidence for each pillar.
*   **Persona-Specific Translation:** Every element (core promise, pillars, proof points) must be explicitly rephrased for the End-User, Buyer, and Executive Sponsor.
*   The output must be a positioning document.

### Output Format
Provide the message house as a structured positioning document, including the following sections:

**1. Product Overview**
*   **Product Category:** [e.g., "AI-powered CRM," "Cloud-based HRIS"]
*   **Target ICP:** [As provided]
*   **Key Differentiators:** [3-5 bullet points]
*   **Point of View (POV):** [1-2 sentences on your product's unique stance in the market]

**2. Core Message House**
*   **Core Promise:** [Main benefit statement]
    *   **End-User Translation:** [Core promise rephrased for end-user]
    *   **Buyer Translation:** [Core promise rephrased for buyer]
    *   **Executive Sponsor Translation:** [Core promise rephrased for executive sponsor]

*   **Message Pillar 1: [Pillar Name]**
    *   **End-User Translation:** [Pillar rephrased for end-user]
    *   **Buyer Translation:** [Pillar rephrased for buyer]
    *   **Executive Sponsor Translation:** [Pillar rephrased for executive sponsor]
    *   **Proof Points (for Pillar 1):**
        *   [Proof Point 1.1]
            *   **End-User Focus:** [Relevance for end-user]
            *   **Buyer Focus:** [Relevance for buyer]
            *   **Executive Sponsor Focus:** [Relevance for executive sponsor]
        *   [Proof Point 1.2]
            *   **End-User Focus:** [Relevance for end-user]
            *   **Buyer Focus:** [Relevance for buyer]
            *   **Executive Sponsor Focus:** [Relevance for executive sponsor]
        *   [Proof Point 1.3]
            *   **End-User Focus:** [Relevance for end-user]
            *   **Buyer Focus:** [Relevance for buyer]
            *   **Executive Sponsor Focus:** [Relevance for executive sponsor]

*   **Message Pillar 2: [Pillar Name]**
    *   **End-User Translation:** [Pillar rephrased for end-user]
    *   **Buyer Translation:** [Pillar rephrased for buyer]
    *   **Executive Sponsor Translation:** [Pillar rephrased for executive sponsor]
    *   **Proof Points (for Pillar 2):**
        *   [Proof Point 2.1]
            *   **End-User Focus:** [Relevance for end-user]
            *   **Buyer Focus:** [Relevance for buyer]
            *   **Executive Sponsor Focus:** [Relevance for executive sponsor]
        *   [Proof Point 2.2]
            *   **End-User Focus:** [Relevance for end-user]
            *   **Buyer Focus:** [Relevance for buyer]
            *   **Executive Sponsor Focus:** [Relevance for executive sponsor]
        *   [Proof Point 2.3]
            *   **End-User Focus:** [Relevance for end-user]
            *   **Buyer Focus:** [Relevance for buyer]
            *   **Executive Sponsor Focus:** [Relevance for executive sponsor]

*   **Message Pillar 3: [Pillar Name]**
    *   **End-User Translation:** [Pillar rephrased for end-user]
    *   **Buyer Translation:** [Pillar rephrased for buyer]
    *   **Executive Sponsor Translation:** [Pillar rephrased for executive sponsor]
    *   **Proof Points (for Pillar 3):**
        *   [Proof Point 3.1]
            *   **End-User Focus:** [Relevance for end-user]
            *   **Buyer Focus:** [Relevance for buyer]
            *   **Executive Sponsor Focus:** [Relevance for executive sponsor]
        *   [Proof Point 3.2]
            *   **End-User Focus:** [Relevance for end-user]
            *   **Buyer Focus:** [Relevance for buyer]
            *   **Executive Sponsor Focus:** [Relevance for executive sponsor]
        *   [Proof Point 3.3]
            *   **End-User Focus:** [Relevance for end-user]
            *   **Buyer Focus:** [Relevance for buyer]
            *   **Executive Sponsor Focus:** [Relevance for executive sponsor]

Estimated results

DifficultyAdvanced

Setup time68 min

Time saved2+ hours

Best modelsChatGPT, Claude, Gemini

Best audienceSaaS

Editor's note

Why this prompt matters

The complexity of B2B SaaS sales cycles often hinges on aligning diverse stakeholders. Product Marketing Managers face the challenge of crafting a single, cohesive product narrative that resonates with multiple personas—from the daily user to the budget holder and the executive sponsor. A generic message risks alienating critical decision-makers, leading to stalled deals or misaligned internal efforts.

This workflow provides a structured approach to developing a multi-persona message house. It's designed for PMMs at B2B SaaS companies who need to articulate their product's value proposition in a way that speaks directly to the unique concerns and motivations of each individual within a buying committee. By systematically translating core messages and proof points, teams can ensure their outreach, sales enablement, and content strategies are precise and impactful.

Reach for this framework when launching a new product, refining existing messaging, or preparing for a significant sales push. It helps solidify internal understanding of the product's value across different roles and equips sales teams with tailored narratives for every conversation.

Anatomy

Prompt engineering breakdown

Role

You are a strategic Product Marketing Manager with deep expertise in B2B SaaS positioning and messaging, skilled at translating complex product value into compelling narratives for varied audiences.

Context

The prompt provides a product name, description, and target ICP. It then defines the structure of a message house: one core promise, three pillars, and three proof points per pillar. Crucially, it specifies that all elements must be translated for three personas: End-User, Buyer, and Executive Sponsor, with clear guidance on what each persona cares about. The desired tone is sharp, buyer-centric, and differentiated.

Goal

To develop a comprehensive message house for a B2B SaaS product, explicitly tailored for a multi-persona buying committee (end-user, primary buyer, executive sponsor).

Constraints

One Core Promise, Three Message Pillars, Three Proof Points per Pillar, Persona-Specific Translation for every element, and the output must be a positioning document.

Output format

A structured positioning document including Product Overview (Category, ICP, Differentiators, POV) and a Core Message House (Core Promise, three Message Pillars, each with three Proof Points), where all elements are translated for End-User, Buyer, and Executive Sponsor.

Why this structure works

This prompt employs explicit constraints to ensure all required components of the message house are covered, including the crucial persona-specific translations. Role priming as a 'seasoned Product Marketing Manager' ensures the output aligns with industry best practices and a buyer-centric perspective. The detailed structured output format guides the model to deliver a complete, usable positioning document.

Pick your version

Prompt variations

BeginnerWorks with any model

For quick drafts or when starting with a new product, requiring less detailed input and a simpler messaging framework.

prompt.txt

As a marketing assistant, outline a message house for `{{product_name}}`. The product is `{{product_description}}`. Create one main promise, three message pillars, and one proof point for each pillar. For each of these, briefly explain how it matters to an End-User, a Buyer, and an Executive. Keep the language simple and direct. Output Structure: Core Promise: * End-User View: * Buyer View: * Executive View: Pillar 1: [Name] * End-User View: * Buyer View: * Executive View: * Proof Point 1.1: * End-User Focus: * Buyer Focus: * Executive Focus: Pillar 2: [Name] * End-User View: * Buyer View: * Executive View: * Proof Point 2.1: * End-User Focus: * Buyer Focus: * Executive Focus: Pillar 3: [Name] * End-User View: * Buyer View: * Executive View: * Proof Point 3.1: * End-User Focus: * Buyer Focus: * Executive Focus:

ProfessionalBest with chatgpt

When a detailed, persona-centric messaging framework is required for a B2B SaaS product, ensuring alignment across all key stakeholders in the buying process.

prompt.txt

Assume the role of a Product Marketing Lead specializing in B2B SaaS. Your task is to construct a comprehensive message house for `{{product_name}}` (`{{product_description}}`), targeting the `{{target_icp}}`. The message house must feature a singular core promise, three distinct message pillars, and three supporting proof points for each pillar. Each component—the core promise, all pillars, and all proof points—must be explicitly adapted for three key personas: 1. **End-User:** How does it improve their daily tasks and productivity? 2. **Buyer:** What is the ROI, cost efficiency, or departmental benefit? 3. **Executive Sponsor:** What strategic impact does it have on business growth or competitive standing? Maintain a direct, buyer-focused, and differentiated narrative. Deliverable Structure: 1. Product Snapshot * Product Category: * Target ICP: * Core Differentiators: (3-5 points) * Market POV: (1-2 sentences) 2. Message House Detail * Core Promise: * End-User Lens: * Buyer Lens: * Executive Lens: * Pillar 1: [Pillar Concept] * End-User Perspective: * Buyer Perspective: * Executive Perspective: * Proof Points (Pillar 1): * [Proof Point 1.1] (with End-User, Buyer, Executive Relevance) * [Proof Point 1.2] (with End-User, Buyer, Executive Relevance) * [Proof Point 1.3] (with End-User, Buyer, Executive Relevance) * [Repeat for Pillar 2 and Pillar 3, maintaining the same detailed structure for translations and proof points.]

Short VersionWorks with any model

For rapid ideation or when needing a high-level overview of messaging points without deep detail, suitable for early-stage discussions.

prompt.txt

As a PMM, generate a concise message house for `{{product_name}}` (`{{product_description}}`), aimed at `{{target_icp}}`. Outline one core promise, three message pillars, and one proof point per pillar. For each of these elements, provide a brief translation for an End-User (daily impact), a Buyer (ROI/efficiency), and an Executive Sponsor (strategic value). Focus on sharp, differentiated messaging. Present this as a bulleted summary with persona translations.

EnterpriseBest with claude

For large organizations where messaging must account for complex internal politics, compliance, and significant risk assessment, beyond typical sales enablement.

prompt.txt

Act as a Principal Product Marketing Strategist for an enterprise B2B SaaS organization. Your mandate is to construct an exhaustive message house for `{{product_name}}` (`{{product_description}}`), targeting `{{target_icp}}`. This message house must comprehensively address the perspectives of an intricate multi-persona buying committee, including the End-User, Primary Buyer, and Executive Sponsor, while also considering implications for compliance, IT security, and long-term organizational risk. Define a singular core promise, three strategic message pillars, and three robust, verifiable proof points for each pillar. Every element, from the core promise to each proof point, requires explicit translation for: 1. **End-User:** Daily operational efficiency, workflow integration, skill development. 2. **Buyer:** Total Cost of Ownership (TCO), vendor consolidation, departmental risk mitigation, procurement alignment. 3. **Executive Sponsor:** Enterprise-wide digital transformation, market differentiation, regulatory adherence, strategic growth, long-term competitive advantage. 4. **Compliance/Risk Officer:** Data governance, security posture, audit readiness, regulatory compliance (e.g., GDPR, HIPAA). The tone must be authoritative, risk-aware, and strategically differentiated. Structure the output as a formal positioning document, mirroring the detailed breakdown of the original prompt but incorporating the additional persona considerations where relevant, especially within proof point elaborations.

What you'll get

Expected output

Product Overview

Product Category: Cloud Integration Platform (iPaaS)
Target ICP: Mid-market companies facing manual data transfer, siloed applications, and inefficient cross-departmental workflows.
Key Differentiators:

* 200+ pre-built connectors. * Visual drag-and-drop interface. * Real-time data synchronization with error handling. * Scalable for mid-market growth.

Point of View (POV): SyncFlow Connect believes seamless data flow is fundamental to operational efficiency and informed decision-making, unblocking growth for mid-market businesses.

Core Message House

Core Promise: SyncFlow Connect streamlines operations and accelerates business processes by automating data flow across your applications.

* End-User Translation: Automate tedious tasks, get accurate, up-to-date information. * Buyer Translation: Reduce operational overhead, improve data reliability. * Executive Sponsor Translation: Drive organizational efficiency and agility.

Message Pillar 1: Eliminate Manual Data Entry & Errors

* End-User Translation: Data moves automatically and accurately. * Buyer Translation: Cut labor costs, minimize data mistakes. * Executive Sponsor Translation: Improve data integrity, reduce operational risk. * Proof Points (for Pillar 1): * Reduces manual data entry time by up to 80%. * End-User Focus: Frees time for high-value tasks. * Buyer Focus: Cost savings, increased productivity. * Executive Sponsor Focus: Optimizes resource allocation. * Automatic error detection and retry. * End-User Focus: Confident data accuracy. * Buyer Focus: Less time on reconciliation. * Executive Sponsor Focus: Reliable data for decisions. * Unified view of customer/operational data. * End-User Focus: Access complete, current info. * Buyer Focus: Better service, informed decisions. * Executive Sponsor Focus: Holistic insights for planning.

Message Pillar 2: Accelerate Cross-Departmental Workflows

* End-User Translation: Tasks flow smoothly, no bottlenecks. * Buyer Translation: Speed up critical business processes. * Executive Sponsor Translation: Enhance organizational responsiveness. * Proof Points (for Pillar 2): * Automates triggers between applications. * End-User Focus: Work moves forward automatically. * Buyer Focus: Reduces processing times. * Executive Sponsor Focus: Streamlines core functions. * Visual workflow builder. * End-User Focus: Create custom automations quickly. * Buyer Focus: Adapt workflows without developers. * Executive Sponsor Focus: Fosters innovation. * Supports complex conditional logic. * End-User Focus: Handle intricate business rules. * Buyer Focus: Automate unique processes. * Executive Sponsor Focus: Scalable automation for growth.

Message Pillar 3: Empower Business Users, Reduce IT Burden

* End-User Translation: Control integrations, customize yourself. * Buyer Translation: Reduce IT reliance, save costs. * Executive Sponsor Translation: Empower business units, free IT. * Proof Points (for Pillar 3): * No-code, drag-and-drop interface. * End-User Focus: Connect apps without IT. * Buyer Focus: Lower consulting costs. Executive Sponsor Focus: Accelerates digital transformation. * Centralized monitoring dashboard. * End-User Focus: See integration status. * Buyer Focus: Proactively manage health. * Executive Sponsor Focus: Ensures operational transparency. * Extensive library of connectors/templates. * End-User Focus: Connect to all apps easily. * Buyer Focus: Rapid deployment of integrations. * Executive Sponsor Focus: Maximizes ROI on software.

Under the hood

Why this prompt works

This prompt effectively uses several prompt engineering techniques to generate a comprehensive and nuanced message house. First, role priming establishes the model as a "seasoned Product Marketing Manager" with expertise in B2B SaaS, guiding its output towards industry-specific language and strategic considerations. This is crucial for obtaining a document that sounds like it came from an experienced PMM, rather than a generic content generator.

Second, the prompt employs explicit constraints and structured output. By dictating a single core promise, three pillars, three proof points per pillar, and specific persona translations for every element, the prompt prevents superficial or incomplete responses. The detailed output format, including sections like "Product Overview" and "Core Message House" with nested bullet points and persona-specific fields, forces the model to organize its thoughts methodically. This structure ensures all required components are present and presented in a usable, actionable format for a product marketing team.

Finally, the inclusion of persona-specific instructions for End-User, Buyer, and Executive Sponsor, detailing their respective focus areas (e.g., "daily workflow improvements" for end-users, "ROI, cost savings" for buyers), directly trains the model to tailor messaging appropriately. This granular guidance, applied to the core promise, pillars, and individual proof points, is what enables the nuanced, multi-faceted output that would be impossible with a simpler, less guided request. It moves beyond basic content generation to strategic messaging development.

Model fit

Best AI models for this prompt

ChatGPT

ChatGPT handles structured output well, making it suitable for organizing the message house components. It can generate distinct persona translations, but you may need to guide it with specific examples to achieve the desired sharp, buyer-centric tone consistently. See the full ChatGPT hub for deeper guidance.

Claude

Claude excels with complex, multi-faceted tasks and long contexts, which is beneficial for maintaining coherence across the entire message house and its persona-specific translations. Its ability to grasp nuances helps in differentiating messaging for end-users, buyers, and executive sponsors effectively. See the full Claude hub for deeper guidance.

Gemini

Gemini is proficient at generating varied and creative phrasing, which can be useful for exploring different ways to articulate the core promise, pillars, and proof points for each persona. It adapts well to tone requirements, allowing for a sharp and differentiated voice in the output. See the full Gemini hub for deeper guidance.

When to use

Launching a new B2B SaaS product or major feature requiring distinct value propositions for multiple stakeholders.
Revising existing product messaging when market feedback indicates inconsistent understanding across buying committee roles.
Aligning internal sales, marketing, and product teams on a unified yet persona-specific narrative.
Preparing for strategic marketing campaigns or sales enablement initiatives targeting complex B2B buying cycles.
Entering new enterprise markets where demonstrating specific ROI and strategic value to different decision-makers is critical.
When a product's value needs clear articulation from daily workflow impact to C-level business outcomes.

When not to use

For products with a single, clearly defined user persona and a straightforward purchase path.
During very early-stage product discovery where core value propositions are still highly fluid and unvalidated.
When quick, tactical messaging is needed for a single channel or short-term campaign.
For consumer-facing products where buying decisions are typically individual and less complex.
If your product's market is highly niche with minimal differentiation required across roles.

Get more from it

Pro tips

1
Before generating, explicitly define each persona's primary pain points and motivations. This ensures the output's translations are genuinely relevant, preventing generic messaging.
2
Gather specific, quantifiable proof points in advance. Vague or qualitative proofs weaken the overall message house and its credibility across personas.
3
Draft the core promise and message pillars manually first. This establishes a strong foundation, preventing disjointed or inconsistent messaging from the model.
4
Test the persona-specific translations with actual target audience members or sales representatives. This validates authenticity and addresses potential misinterpretations.
5
Ensure your differentiators are truly distinct from competitors. Weak differentiators lead to a diluted message house that fails to stand out.
6
Be concise. While comprehensive, each statement should be direct to avoid overwhelming busy executives or technical users with unnecessary detail.
7
Refine the 'Point of View' until it feels opinionated and unique. A strong POV anchors your product's identity and guides all subsequent messaging.

Don't ship this

Common mistakes

✗ Providing generic or unquantifiable proof points that lack impact.
Fix — Input specific metrics, customer success stories, or direct product features that clearly substantiate each pillar's claim.
✗ Persona translations sound too similar, failing to address distinct needs.
Fix — Ensure each translation directly speaks to the unique concerns, language, and priorities of that specific persona, highlighting different benefits.
✗ Message pillars do not clearly support or ladder up to the core promise.
Fix — Re-evaluate the logical flow. Each pillar must be a distinct, foundational reason why the core promise is true and valuable.
✗ Key differentiators are vague or easily replicated by competitors.
Fix — Refine differentiators to be specific, defensible, and clearly distinct, highlighting unique aspects of your product or approach.
✗ The 'Point of View' is bland or doesn't establish a unique market stance.
Fix — Craft a bolder POV that reflects a strong, opinionated position on the market problem and your product's solution.
✗ Using internal jargon or overly technical language in persona translations.
Fix — Simplify language, especially for buyer and executive sponsor translations, focusing on business outcomes and strategic value understandable to them.

Frequently asked questions

Q.How detailed should the `product_description` input be for best results?

Provide a concise but comprehensive description. Include core functionality, primary benefits, and any unique features. Avoid excessive marketing fluff; focus on factual product capabilities. A good description is 3-5 sentences, capturing the essence without overwhelming the model.

Q.Can I adapt this prompt for more than three personas?

The prompt is structured for three personas for clarity and depth. While you could technically add more, it might dilute the focus and increase output complexity, potentially leading to less distinct translations. For more, consider running it multiple times with different persona groups.

Q.What if I don't have three distinct proof points for every message pillar?

Aim for three if possible, as it strengthens credibility. If you only have two strong ones, provide those. The model will still generate the translations. However, identify areas where you need to develop more evidence to bolster your messaging in the future.

Q.Is this message house suitable for early-stage products still defining their market fit?

This prompt assumes a relatively stable product and target ICP. For early-stage products, it's better to first validate core problem/solution fit and primary value propositions before building out such a detailed multi-persona message house.

Q.How long should each persona's translation of a pillar or proof point be?

Keep translations concise—typically one to two sentences. The goal is clarity and impact, not extensive detail. Each translation should succinctly capture the essence of the message element from that persona's perspective.

Q.Can this framework be used for B2C products with complex family or household buying decisions?

While designed for B2B, the underlying principle of tailoring messages to distinct decision-makers can apply. However, the persona archetypes (End-User, Buyer, Exec Sponsor) are B2B-specific. You would need to rename and redefine those roles to fit a B2C context.

Version 1.0Last reviewed July 12, 2026

Reviewed by PromptInFlow Editorial Team