Requirements
How To Start
STEP 1: Persona Activation and Context Synthesis
- Activate the Strategic Brand Architect persona. Load all previous recipe outputs for pitch synthesis including audience profile from Recipe 2, value proposition summary from Recipe 4, and competitive advantages from Recipe 5. Review the selected pitch contexts, lengths, and styles requested by the user. Confirm all required inputs are present before proceeding.
STEP 2: Core Narrative Component Extraction
- Extract the seven core narrative components from previous recipe outputs: - Hook: Attention-grabbing opener (5 seconds) - Problem: Pain point framing with emotional impact - Solution: Your offering as the natural answer - Differentiation: Why you versus alternatives - Transformation: The after picture for users - Proof: Traction, validation, or social proof - Call to Action: Context-appropriate next step Create 2-3 variations of each component. Keep each element to 1-2 sentences maximum for flexibility.
STEP 3: Pitch Style Framework Selection
- Apply the appropriate pitch style framework based on context: - Problem-Solution: Establish problem, introduce solution, explain approach, show proof. Best for technical audiences and investors. - Transformation: Paint before/after picture, bridge gap with your solution. Best for aspirational buyers and lifestyle products. - Value-First: Lead with biggest benefit, explain how you deliver it, differentiate. Best for time-constrained contexts. - Story-Based: Relatable character journey from struggle to discovery to transformation. Best for press and emotional buyers.
STEP 4: Pitch Construction by Context and Length
- Build pitch variations for each requested combination of context, length, and style. Apply length constraints: - 15-second (30-40 words): Hook, Solution, Value, Call to Action only - 30-second (70-85 words): Add Problem and Differentiation - 60-second (140-160 words): Full narrative with Proof - 2-minute (280-320 words): Comprehensive with market context Provide complete pitch script, structural breakdown, strategic choices explanation, and confidence rating for each variation.
STEP 5: Delivery Guidance Creation
- If delivery tips are requested, provide for each pitch: - Pacing and Tone: Speaking pace, tone, emphasis points, pause moments - Body Language: Opening stance, key gestures, eye contact pattern, closing position - Adaptation Notes: How to handle interruptions, shorter time, engagement, confusion - Practice Recommendations: Recording review points, mirror checks, feedback focus, iteration count
STEP 6: Pitch Quality Assessment
- Assess each pitch against six quality criteria: - Clarity: Immediately clear what you do and for whom - Relevance: Addresses a problem listener cares about - Differentiation: Clear why you are different from alternatives - Credibility: Builds trust that this is real and achievable - Memorability: They will remember you 30 minutes later - Action: Clear and appropriate next step Rate each as Strong, Acceptable, or Needs Work. Provide overall rating and priority improvements.
STEP 7: Context-Specific Adaptation Guidance
- For each requested context, provide adaptation guidance including: - What to emphasize in this context - What to de-emphasize or omit - Priority proof points for this audience - Danger zones to avoid - Appropriate follow-up actions - 2-3 specific scenario adaptations - Common objections and response strategies
STEP 8: Common Mistakes Prevention
- Review pitches against eight common mistakes: - Feature Dumping: Listing capabilities instead of outcomes - Jargon Overload: Using technical terms without context - Weak Hook: Starting with product description instead of engagement - Vague Differentiation: Generic claims without specifics - No Proof: Grand claims without validation - Forgettable: Accurate but not sticky or memorable - Wrong Length: Mismatching pitch length to opportunity - Weak Call to Action: Vague or passive next step Flag any issues found and provide specific fixes.
STEP 9: Portfolio Summary and Next Steps
- Generate the Elevator Pitch Portfolio Summary Block containing: - Primary pitches (30-second and 60-second all-purpose) - Context-specific variations with emphasis notes - Pitch components library (reusable elements) - Adaptation guidance for quick, standard, and detailed formats - Top recommendations from strategic analysis - Quality assessment summary with improvement priorities Provide practice and refinement roadmap with weekly and monthly milestones. Confirm readiness for Recipe 7 or direct use.
When to Use This Recipe
Use this recipe when you need persuasive pitch contentfor any stakeholder communication: - Investor meetings: Fundraising, pitch competitions - Customer acquisition: Sales calls, demos, marketing - Networking: Conferences, introductions, social - Press: Media interviews, PR outreach, podcasts - Partnerships: Business development, collaborations - Hiring: Recruiting, talent attractionThis recipe is the sixth in the Brand Identity Cookbookfoundation sequence. Execute it after completing: - Recipe 2: Target Audience Analyzer - Recipe 4: Value Prop Crafter - Recipe 5: Competitive Edge DefinerAlso use this recipe when updating pitches aftersignificant business changes, new traction data, marketshifts, or competitive landscape changes.
Recipe FAQ
Q: Do I need to complete all previous recipes first?
A: Yes. This recipe requires outputs from Recipe 2
(Target Audience), Recipe 4 (Value Prop), and Recipe 5
(Competitive Edge). Recipe 3 (Pain Points) is optional
but enhances problem framing. The previous recipes
provide the raw material that gets synthesized into
compelling pitch narratives. Q: How many pitch variations will I get? A: It depends on your selections. Each combination of
context, length, and style produces one pitch. If you
select 2 contexts, 2 lengths, and 2 styles, you get up
to 8 pitch variations. Start with 1-3 contexts and 2
lengths for manageable output. You can always run the
recipe again for additional variations. Q: What if I do not have any traction data yet? A: The recipe works without traction data. Pre-launch and
early-stage pitches can emphasize vision, methodology,
team credentials, or early validation instead of
metrics. The persona will suggest appropriate proof
points for your stage. Update pitches as traction grows. Q: Can I use these pitches immediately? A: Yes. Each pitch is complete and ready to use. However,
practice is essential. The delivery guidance helps you
refine how you present the content. Plan to iterate
based on real-world feedback. The best pitches evolve
through actual use. Example 1: Fine Dining Restaurant Launch (Terra & Olive) Parameters:
- pitch_contexts: [customer, press]
- pitch_lengths: [30-second, 60-second]
- pitch_style: all
- audience_profile: [From Recipe 2: Local food
enthusiasts, couples seeking special occasions,
corporate entertainment buyers]
- value_prop_summary: [From Recipe 4: Farm-to-table
Mediterranean cuisine with seasonal tasting
menus]
- competitive_advantages: [From Recipe 5: Only
local restaurant with sommelier-curated pairings
and chef's table experience]
- include_delivery_tips: True
- traction_data: "Opening month, 500 reservations
already booked" Output: 8 pitch variations (2 contexts x 2 lengths x 2
styles). Customer pitches emphasize transformation and
experience. Press pitches use story-based structure
highlighting chef background and local sourcing
partnerships. Delivery tips tailored for in-person
networking and phone inquiries. Strategic Analysis: New restaurant needs memorable
pitch that conveys experience, not just food. Lead
with emotional hook about special occasions.
Confidence 90% for customer, 85% for press. Example 2: B2B Environmental Consulting (GreenPath) Parameters:
- pitch_contexts: [investor, customer]
- pitch_lengths: [30-second, 60-second, 2-minute]
- pitch_style: problem-solution
- audience_profile: [From Recipe 2: Mid-size
manufacturers facing sustainability compliance]
- value_prop_summary: [From Recipe 4: Sustainability
roadmaps that reduce costs while meeting
compliance]
- competitive_advantages: [From Recipe 5: Only
consultancy combining regulatory expertise with
operational cost reduction]
- include_delivery_tips: True
- traction_data: "15 clients, average 23% cost
reduction" Output: 6 pitch variations optimized for B2B context.
Investor pitches lead with market size and traction.
Customer pitches lead with compliance pain and cost
reduction proof. 2-minute version includes case study
structure. Strategic Analysis: B2B consulting requires credibility
focus. Lead with problem acknowledgment and proof
points. Avoid jargon. Confidence 92% for customer
(clear value), 85% for investor (traction solid but
early). Example 3: SaaS Productivity Tool Quick Pitch Parameters:
- pitch_contexts: [networking]
- pitch_lengths: [15-second, 30-second]
- pitch_style: value-first
- audience_profile: [From Recipe 2]
- value_prop_summary: [From Recipe 4]
- competitive_advantages: [From Recipe 5]
- include_delivery_tips: False
- traction_data: None Output: 2 concise networking pitches optimized for
memorability. Value-first style leads with outcome.
No delivery tips per request. Streamlined summary
block for quick reference. Strategic Analysis: Pre-traction startup needs
memorable hook over proof. Focus on unique
methodology as differentiator. Confidence 80% given
no validation data yet.
(Target Audience), Recipe 4 (Value Prop), and Recipe 5
(Competitive Edge). Recipe 3 (Pain Points) is optional
but enhances problem framing. The previous recipes
provide the raw material that gets synthesized into
compelling pitch narratives. Q: How many pitch variations will I get? A: It depends on your selections. Each combination of
context, length, and style produces one pitch. If you
select 2 contexts, 2 lengths, and 2 styles, you get up
to 8 pitch variations. Start with 1-3 contexts and 2
lengths for manageable output. You can always run the
recipe again for additional variations. Q: What if I do not have any traction data yet? A: The recipe works without traction data. Pre-launch and
early-stage pitches can emphasize vision, methodology,
team credentials, or early validation instead of
metrics. The persona will suggest appropriate proof
points for your stage. Update pitches as traction grows. Q: Can I use these pitches immediately? A: Yes. Each pitch is complete and ready to use. However,
practice is essential. The delivery guidance helps you
refine how you present the content. Plan to iterate
based on real-world feedback. The best pitches evolve
through actual use. Example 1: Fine Dining Restaurant Launch (Terra & Olive) Parameters:
- pitch_contexts: [customer, press]
- pitch_lengths: [30-second, 60-second]
- pitch_style: all
- audience_profile: [From Recipe 2: Local food
enthusiasts, couples seeking special occasions,
corporate entertainment buyers]
- value_prop_summary: [From Recipe 4: Farm-to-table
Mediterranean cuisine with seasonal tasting
menus]
- competitive_advantages: [From Recipe 5: Only
local restaurant with sommelier-curated pairings
and chef's table experience]
- include_delivery_tips: True
- traction_data: "Opening month, 500 reservations
already booked" Output: 8 pitch variations (2 contexts x 2 lengths x 2
styles). Customer pitches emphasize transformation and
experience. Press pitches use story-based structure
highlighting chef background and local sourcing
partnerships. Delivery tips tailored for in-person
networking and phone inquiries. Strategic Analysis: New restaurant needs memorable
pitch that conveys experience, not just food. Lead
with emotional hook about special occasions.
Confidence 90% for customer, 85% for press. Example 2: B2B Environmental Consulting (GreenPath) Parameters:
- pitch_contexts: [investor, customer]
- pitch_lengths: [30-second, 60-second, 2-minute]
- pitch_style: problem-solution
- audience_profile: [From Recipe 2: Mid-size
manufacturers facing sustainability compliance]
- value_prop_summary: [From Recipe 4: Sustainability
roadmaps that reduce costs while meeting
compliance]
- competitive_advantages: [From Recipe 5: Only
consultancy combining regulatory expertise with
operational cost reduction]
- include_delivery_tips: True
- traction_data: "15 clients, average 23% cost
reduction" Output: 6 pitch variations optimized for B2B context.
Investor pitches lead with market size and traction.
Customer pitches lead with compliance pain and cost
reduction proof. 2-minute version includes case study
structure. Strategic Analysis: B2B consulting requires credibility
focus. Lead with problem acknowledgment and proof
points. Avoid jargon. Confidence 92% for customer
(clear value), 85% for investor (traction solid but
early). Example 3: SaaS Productivity Tool Quick Pitch Parameters:
- pitch_contexts: [networking]
- pitch_lengths: [15-second, 30-second]
- pitch_style: value-first
- audience_profile: [From Recipe 2]
- value_prop_summary: [From Recipe 4]
- competitive_advantages: [From Recipe 5]
- include_delivery_tips: False
- traction_data: None Output: 2 concise networking pitches optimized for
memorability. Value-first style leads with outcome.
No delivery tips per request. Streamlined summary
block for quick reference. Strategic Analysis: Pre-traction startup needs
memorable hook over proof. Focus on unique
methodology as differentiator. Confidence 80% given
no validation data yet.
Actual Recipe Code
(Copy This Plaintext Code To Use)
# =========================================================# START RECIPE-ID: RCP-004-001-006-ELEVATOR-PITCH-v2.00a# =========================================================# =========================================================# PERSONA REFERENCE (Required for all Brand ID recipes)# =========================================================IF BRAND_PERSONA is defined: PERSONA_NAME = BRAND_PERSONA.name PERSONA_TITLE = BRAND_PERSONA.title PERSONA_TIER = BRAND_PERSONA.tierELSE: # Default to Morgan (Strategic Brand Architect) PERSONA_NAME = "Morgan" PERSONA_TITLE = "Strategic Brand Architect" PERSONA_TIER = "Beginner"# =========================================================ELEVATOR_PITCH_BUILDER = Recipe( recipe_id="RCP-004-001-006-ELEVATOR-PITCH-v2.00a", title="Elevator Pitch Builder - Multi-Context Pitch Creation", description=""" Creates compelling elevator pitches across multiple lengths, styles, and contexts. Synthesizes competitive advantages, value propositions, and audience insights into persuasive narratives. Includes pitch variations for investors, customers, networking, and press with delivery guidance and quality assessment framework. """, category="CAT-004-BRAND-IDENTITY", subcategory="SUBCAT-001-FOUNDATION", difficulty="medium", estimated_time="45-60 minutes", version="2.00a", parameters={ "pitch_contexts": { "type": "list", "required": True, "options": [ "investor", "customer", "networking", "press", "partnership", "hiring" ], "description": "Contexts for pitch creation" }, "pitch_lengths": { "type": "list", "required": True, "options": [ "15-second", "30-second", "60-second", "2-minute" ], "description": "Pitch durations to create", "default": ["30-second", "60-second"] }, "pitch_style": { "type": "string", "required": False, "options": [ "problem-solution", "transformation", "value-first", "story-based", "all" ], "description": "Pitch narrative structure", "default": "all" }, "audience_profile": { "type": "text_block", "required": True, "description": "Output from Recipe 2" }, "value_prop_summary": { "type": "text_block", "required": True, "description": "Output from Recipe 4" }, "competitive_advantages": { "type": "text_block", "required": True, "description": "Output from Recipe 5" }, "include_delivery_tips": { "type": "boolean", "required": False, "default": True, "description": "Include delivery guidance" }, "traction_data": { "type": "text", "required": False, "description": "Metrics or validation data" } }, prompt_template="""#H->AI::Directive: (Execute ELEVATOR-PITCH-BUILDER)#H->AI::Parameters: ( pitch_contexts: {pitch_contexts} pitch_lengths: {pitch_lengths} pitch_style: {pitch_style} audience_profile: [provided] value_prop_summary: [provided] competitive_advantages: [provided] include_delivery_tips: {include_delivery_tips} traction_data: {traction_data})# =========================================================# STEP 0: PERSONA ACTIVATION AND CONTEXT SYNTHESIS# =========================================================#AI->H::PersonaSwitch: (Activating {PERSONA_NAME} - {PERSONA_TITLE})#AI->H::Context: ({PERSONA_NAME} brings decades of pitch refinement experience from boardrooms to trade shows)#AI->H::Status: (Loading all previous recipe outputs for pitch synthesis)CONTEXT_INTEGRATION = { "from_recipe_2": audience_profile, "from_recipe_4": value_prop_summary, "from_recipe_5": competitive_advantages, "traction": traction_data, "contexts": pitch_contexts, "lengths": pitch_lengths, "styles": pitch_style}#AI->H::Note: ({PERSONA_NAME} says: "Alright, let us craft your pitches. Remember: a pitch is not about cramming in every feature. It is about creating curiosity, demonstrating value, and earning the right to continue the conversation. Different contexts need different emphasis.")#AI->H::Note: ({PERSONA_NAME} philosophy: "The best pitches follow a simple rule: make them care before you make them understand. Hook emotion first, justify with logic second. We will structure every pitch accordingly.")# =========================================================# STEP 1: CORE NARRATIVE COMPONENTS# =========================================================#AI->H::Status: (Extracting core narrative components)#AI->H::Note: ({PERSONA_NAME} says: "Every great pitch has the same building blocks. Let us identify yours, then we will assemble them differently for each context and style.")NARRATIVE_COMPONENTS = { "hook": { "purpose": "Grab attention in first 5 seconds", "approaches": [ "Provocative question related to pain point", "Surprising statistic about the problem", "Bold statement about the future or change", "Relatable scenario that resonates" ], "sources": "Pain points from Recipe 3, audience insights from Recipe 2" }, "problem": { "purpose": "Establish pain point with emotion", "elements": [ "Who experiences this problem", "What the problem is specifically", "Why it matters (business or emotional)", "Why existing solutions fail" ], "sources": "Recipe 3, Recipe 5 competitive gaps" }, "solution": { "purpose": "Introduce offering as natural answer", "elements": [ "What you built (category)", "How it works (methodology)", "What it enables (outcomes)", "Why now (market timing)" ], "sources": "Recipe 4, Recipe 5 positioning" }, "differentiation": { "purpose": "Why you vs alternatives", "elements": [ "Primary competitive advantage", "Unique approach or methodology", "Defensible positioning (moat)", "Proof point or validation" ], "sources": "Recipe 5 competitive advantages" }, "transformation": { "purpose": "Paint the after picture", "elements": [ "What changes for the user", "Quantifiable outcome if possible", "Emotional payoff (how they feel)", "Vision of better future" ], "sources": "Recipe 4 benefit translations" }, "proof": { "purpose": "Build credibility and reduce risk", "elements": [ "Traction metrics (users, revenue, growth)", "Social proof (testimonials, logos)", "Credentials (team, advisors, backers)", "Validation (awards, press, partnerships)" ], "sources": "traction_data parameter" }, "call_to_action": { "purpose": "Clear next step for context", "variations": { "investor": "Let us discuss the opportunity", "customer": "Try it or see a demo", "networking": "Can we connect", "press": "Available for interview", "partnership": "Let us explore collaboration", "hiring": "Join us" } }}FOR EACH COMPONENT: 1. Pull relevant content from Recipe 2, 3, 4, 5 2. Craft 2-3 variations of each component 3. Keep each element to 1-2 sentences max 4. Test for emotional resonance and clarityCREATE COMPONENT_LIBRARY: PITCH NARRATIVE COMPONENTS ========================== HOOKS (Choose based on context): 1. [Question-based hook] 2. [Statistic-based hook] 3. [Statement-based hook] PROBLEM STATEMENTS: 1. [Problem emphasizing pain] 2. [Problem emphasizing opportunity cost] SOLUTION INTRODUCTIONS: 1. [Solution as methodology] 2. [Solution as transformation] DIFFERENTIATION POINTS: 1. [Primary competitive advantage] 2. [Secondary unique approach] 3. [Defensible positioning] TRANSFORMATION OUTCOMES: 1. [Quantifiable outcome] 2. [Emotional outcome] PROOF POINTS: 1. [Traction metric if available] 2. [Social proof if available] 3. [Team or validation if available]#AI->H::Note: ({PERSONA_NAME} says: "These components are your pitch toolkit. We will mix and match them based on context, length, and style. Not every pitch uses every component - shorter pitches are ruthlessly selective.")# =========================================================# STEP 2: PITCH STYLE FRAMEWORKS# =========================================================#AI->H::Status: (Defining pitch narrative structures)#AI->H::Note: ({PERSONA_NAME} says: "There are four proven pitch structures. Each works better for different audiences and contexts. Let me show you the frameworks, then we will build your variations.")PITCH_STYLE_FRAMEWORKS = { "problem_solution": { "structure": [ "Hook: Establish problem dramatically", "Problem: Quantify impact and frustration", "Solution: Introduce your offering", "How: Explain approach at high level", "Proof: Validate it works", "CTA: Invite next step" ], "best_for": "Technical audiences, B2B, investors who want logic", "example_flow": "Problem is real, existing solutions fail, our approach works, proof", "emotional_arc": "Frustration, Relief, Hope, Confidence" }, "transformation": { "structure": [ "Hook: Paint before scenario vividly", "Current State: This is painful or limiting", "Vision: Imagine this better future", "Bridge: We make transformation possible", "How: High-level methodology", "Proof: Others have transformed", "CTA: You can too" ], "best_for": "Aspirational buyers, lifestyle or productivity tools, change agents", "example_flow": "Struggle now, dream future, we bridge gap, proof others did it", "emotional_arc": "Dissatisfaction, Aspiration, Possibility, Inspiration" }, "value_first": { "structure": [ "Hook: Lead with biggest benefit", "Value: What you will achieve or avoid", "How: Our unique approach delivers this", "Different: Why alternatives cannot match", "Proof: Validation or traction", "CTA: Get this value" ], "best_for": "Time-constrained contexts, networking, customers who know their pain", "example_flow": "Here is the value, here is how we deliver it, here is why we are different", "emotional_arc": "Interest, Desire, Conviction, Action" }, "story_based": { "structure": [ "Hook: Relatable character or situation", "Journey: Struggle they faced", "Discovery: They found our solution", "Transformation: How things changed", "Insight: Why this matters broadly", "Invitation: Your turn for transformation", "CTA: Next step" ], "best_for": "Emotional buyers, consumer products, storytelling contexts (press, social)", "example_flow": "Meet someone like you, they struggled, found us, life improved, you can too", "emotional_arc": "Connection, Empathy, Curiosity, Inspiration, Desire" }}#AI->H::Note: ({PERSONA_NAME} strategy: "Most founders default to problem-solution because it feels logical. But transformation and value-first often work better for customer pitches. Story-based is powerful for press and social, weaker for investors who want data.")CONTEXT_TO_STYLE_MAPPING = { "investor": "problem-solution or value-first (if traction exists)", "customer": "transformation (aspirational) or value-first (time-constrained)", "networking": "value-first (memorable) or story-based (builds connection)", "press": "story-based (narrative) or problem-solution (newsworthy angle)", "partnership": "value-first (mutual benefit) or problem-solution (market opportunity)", "hiring": "transformation (vision-driven) or story-based (cultural appeal)"}IF pitch_style == "all": FOR EACH CONTEXT in pitch_contexts: SELECT 2 MOST APPROPRIATE STYLES from mapping CREATE 2 STYLE VARIATIONS per contextELSE: USE SPECIFIED pitch_style for all contexts# =========================================================# STEP 3: PITCH CONSTRUCTION# =========================================================#AI->H::Status: (Building pitch variations)#AI->H::Note: ({PERSONA_NAME} says: "Now for the main event. I will create complete pitches for each combination you requested. Each pitch is standalone - you can use any of them depending on situation.")LENGTH_CONSTRAINTS = { "15_second": { "word_count": "30-40 words", "components": ["Hook", "Solution", "Value", "CTA"], "purpose": "Spark interest only", "use_case": "Quick intro, trade show, social bio" }, "30_second": { "word_count": "70-85 words", "components": ["Hook", "Problem", "Solution", "Differentiation", "CTA"], "purpose": "Create curiosity and establish value", "use_case": "Networking, cold call opener, speed round" }, "60_second": { "word_count": "140-160 words", "components": ["Hook", "Problem", "Solution", "How", "Differentiation", "Proof", "CTA"], "purpose": "Comprehensive value story with proof", "use_case": "Standard elevator pitch, pitch competitions, meetings" }, "2_minute": { "word_count": "280-320 words", "components": "All components with deeper problem, solution, and proof", "purpose": "Full narrative with market context", "use_case": "Investor meetings, podcast interviews, presentations" }}FOR EACH CONTEXT in pitch_contexts: FOR EACH LENGTH in pitch_lengths: FOR EACH STYLE selected for this context: CREATE PITCH: =============================================== {LENGTH} {STYLE} PITCH - {CONTEXT} CONTEXT =============================================== [COMPLETE PITCH SCRIPT] (Actual word count: XX words) ----------------------------------------------- PITCH BREAKDOWN ----------------------------------------------- Structure: - Hook: [Explain what hook does and why] - Problem: [Explain problem framing] - Solution: [Explain solution positioning] - Differentiation: [Explain competitive angle] - Proof: [Explain validation used] - CTA: [Explain call-to-action choice] Strategic Choices: [2-3 key decisions in this pitch version] Emphasis: Primary: [What this pitch emphasizes most] Secondary: [Supporting emphasis] Omitted: [What was left out and why] ----------------------------------------------- ASSESSMENT ----------------------------------------------- Strengths: [What works well in this pitch] Considerations: [What to watch for] Best Used When: [Specific situations] Confidence Rating: [5-star scale] Rationale: [Why this rating] ===============================================# =========================================================# STEP 4: DELIVERY GUIDANCE# =========================================================IF include_delivery_tips == True: FOR EACH PITCH CREATED: PROVIDE DELIVERY_TIPS: +-------------------------------------------------+ | DELIVERY TIPS FOR THIS PITCH | +-------------------------------------------------+ Pacing and Tone: - Speaking pace: [Recommended words per min] - Tone: [Conversational, Professional, etc.] - Emphasis points: [Which words to stress] - Pause moments: [Where to pause for effect] Body Language: - Opening stance: [How to begin physically] - Key gestures: [Where natural gestures fit] - Eye contact: [Pattern for this context] - Closing position: [How to finish strong] Adaptation Notes: - If interrupted: [How to pause and resume] - If time is shorter: [Which component to cut] - If they engage: [Natural dialogue points] - If they seem confused: [What to clarify] Practice Recommendations: - Record yourself: [What to listen for] - Mirror check: [What to watch for visually] - Feedback focus: [What to ask others] - Iterations needed: [Practice run count] +-------------------------------------------------+ | END DELIVERY TIPS | +-------------------------------------------------+# =========================================================# STEP 5: PITCH QUALITY ASSESSMENT# =========================================================#AI->H::Status: (Evaluating pitch quality)#AI->H::Note: ({PERSONA_NAME} says: "Let me assess your pitches against six proven quality criteria. This helps you identify which pitches are strongest and where you might want to refine.")QUALITY_CRITERIA = { "clarity": { "question": "Is it immediately clear what you do and for whom?", "green_flags": [ "Non-technical person understands immediately", "Audience and offering are explicit within 15 seconds", "No jargon or acronyms without context" ], "red_flags": [ "Requires explanation or follow-up questions", "Uses industry jargon as shortcuts", "Vague positioning" ] }, "relevance": { "question": "Does it address a problem the listener cares about?", "green_flags": [ "Hooks into existing frustration or aspiration", "Problem is specific and relatable", "Listener can see themselves in scenario" ], "red_flags": [ "Problem feels abstract or distant", "No emotional connection to pain point", "Solution looking for a problem" ] }, "differentiation": { "question": "Is it clear why you are different?", "green_flags": [ "Unique approach is explicit", "Competitive advantage is stated not implied", "Listener could not confuse you with others" ], "red_flags": [ "Could be any company in your space", "Differentiation is vague (better, easier)", "No mention of what makes you unique" ] }, "credibility": { "question": "Do you build trust that this is real and achievable?", "green_flags": [ "Proof points included", "Realistic claims that do not oversell", "Specific outcomes not generic benefits" ], "red_flags": [ "Grandiose claims without support", "No validation or social proof", "Sounds too good to be true" ] }, "memorability": { "question": "Will they remember you 30 minutes later?", "green_flags": [ "One clear sticky concept or analogy", "Surprising statistic or insight", "Vivid problem or solution contrast" ], "red_flags": [ "Generic phrasing that sounds like others", "Information-dense but not distinctive", "No emotional or intellectual hook" ] }, "action": { "question": "Is there a clear appropriate next step?", "green_flags": [ "Specific low-friction call to action", "Appropriate to context and stage", "Easy for listener to say yes" ], "red_flags": [ "Vague or no next step", "CTA is too aggressive for context", "Unclear how to follow up" ] }}FOR EACH PITCH CREATED: ASSESS AGAINST 6 CRITERIA: Rate each: Strong / Acceptable / Needs Work CREATE QUALITY_SCORECARD: PITCH QUALITY ASSESSMENT ======================== Pitch: {Length} {Style} for {Context} Clarity: [rating] [Brief explanation] Relevance: [rating] [Brief explanation] Differentiation: [rating] [Brief explanation] Credibility: [rating] [Brief explanation] Memorability: [rating] [Brief explanation] Action: [rating] [Brief explanation] Overall Rating: [Strong/Good/Needs Refinement] Priority Improvements: 1. [Most important thing to strengthen] 2. [Second priority if applicable]# =========================================================# STEP 6: COMPARATIVE ANALYSIS# =========================================================IF multiple pitches created: #AI->H::Note: ({PERSONA_NAME} says: "Let me compare your pitches side by side so you can see which works best for different situations.") CREATE PITCH_COMPARISON: PITCH COMPARISON MATRIX ======================= Context: [e.g., Customer] Aspect | Pitch A | Pitch B | Pick ------------+-------------+-------------+------ Clarity | [rating] | [rating] | [rec] Impact | [rating] | [rating] | [rec] Completeness| [rating] | [rating] | [rec] Memorability| [rating] | [rating] | [rec] Best For | [situation] | [situation] | [rec] ------------+-------------+-------------+------ Recommendation: [Which to lead with and when to switch to the other]# =========================================================# STEP 7: CONTEXT ADAPTATION GUIDANCE# =========================================================#AI->H::Status: (Providing adaptation guidance)#AI->H::Note: ({PERSONA_NAME} says: "Pitches are not one-size-fits-all. Let me show you how to adapt your core pitch for specific situations within each context.")CONTEXT_SPECIFIC_GUIDANCE = { "investor": { "emphasize": "Market size, growth trajectory, team credibility, competitive moats", "de_emphasize": "Product features, how it works technically, customer stories", "proof_priorities": "Traction metrics, user growth, revenue, LOIs", "danger_zones": "Vague TAM claims, dismissing competitors, unrealistic projections", "follow_up": "Clear ask: round size, timeline, what you need beyond capital" }, "customer": { "emphasize": "Their pain, transformation, ease of getting started", "de_emphasize": "Technical complexity, competitive positioning, fundraising story", "proof_priorities": "Customer testimonials, before and after examples, free trial", "danger_zones": "Overselling, forcing urgency, feature dumping", "follow_up": "Low-friction: demo, trial, case study, conversation" }, "networking": { "emphasize": "Memorable hook, who you help, what makes you distinctive", "de_emphasize": "Detailed explanation, competitive landscape, everything else", "proof_priorities": "One impressive metric or validation point", "danger_zones": "Going too long, being too salesy, not being conversational", "follow_up": "Exchange information, find connection points, stay memorable" }, "press": { "emphasize": "What is newsworthy, human interest angle, trends you represent", "de_emphasize": "Sales pitch, feature lists, investment ask", "proof_priorities": "Unique data, surprising insights, visual story possibilities", "danger_zones": "Jargon, hype without substance, no clear story angle", "follow_up": "Offer exclusive access, data, interviews, story angles" }, "partnership": { "emphasize": "Mutual value, complementary strengths, joint opportunity", "de_emphasize": "Your company full story, competitive threats, fundraising", "proof_priorities": "Examples of successful partnerships, integration ease", "danger_zones": "One-sided value prop, unclear benefit to them, vague collaboration", "follow_up": "Specific partnership proposal, pilot ideas, mutual customer benefits" }, "hiring": { "emphasize": "Mission, vision, team culture, growth opportunity, impact", "de_emphasize": "Business metrics, fundraising, competitive positioning", "proof_priorities": "Team credentials, company trajectory, exciting challenges", "danger_zones": "Only talking about company not role, overselling, being vague", "follow_up": "Role specifics, culture fit conversation, team intro opportunity" }}FOR EACH CONTEXT in pitch_contexts: PROVIDE ADAPTATION_SCENARIOS: {CONTEXT} PITCH ADAPTATIONS =========================== Base Pitch: [Reference pitch] SCENARIO 1: [Specific situation] Adaptation: [What to change] Example: [Specific phrasing change] Reason: [Why this works] SCENARIO 2: [Another situation] [Same format] SCENARIO 3: [Third situation if relevant] [Same format] Common Objections in {CONTEXT} Context: Objection: [Typical pushback] Response: [How to address using components] Follow-up: [What to say next] [Repeat for 2-3 common objections]# =========================================================# STEP 8: COMMON MISTAKES AND FIXES# =========================================================#AI->H::Note: ({PERSONA_NAME} reality check: "Let me save you from the mistakes I see repeatedly. These are the pitch killers that even experienced founders make.")COMMON_MISTAKES = [ { "mistake": "Feature Dumping", "looks_like": "Listing capabilities", "why_fails": "Features do not create emotional connection or communicate value", "fix": "Lead with outcomes, say helps you achieve X not has feature Y", "check": "If you are listing things, you are probably feature dumping" }, { "mistake": "Jargon Overload", "looks_like": "Using industry acronyms and technical terms without context", "why_fails": "Confuses listeners, makes you seem less credible not more", "fix": "Use 8th-grade language. If your aunt would not understand it, simplify", "check": "Record pitch, count acronyms and technical terms - should be under 2 total" }, { "mistake": "Weak Hook", "looks_like": "Starting with So we are building a platform that...", "why_fails": "Lost attention in first 5 seconds, no compelling reason to listen", "fix": "Start with provocative question, surprising stat, or relatable pain", "check": "Would someone put down their phone to hear your first sentence?" }, { "mistake": "Vague Differentiation", "looks_like": "We are better faster easier than alternatives", "why_fails": "Everyone claims this, meaningless without specifics", "fix": "Name your unique approach: Unlike X which does Y, we do Z because...", "check": "Could a competitor claim your differentiation? If yes, too vague" }, { "mistake": "No Proof", "looks_like": "Grand claims about outcomes with zero validation", "why_fails": "Credibility destroyed, sounds like vaporware or wishful thinking", "fix": "Include one concrete proof point: users, revenue, testimonial, data", "check": "If someone asks prove it, can you immediately?" }, { "mistake": "Forgettable", "looks_like": "Accurate description but nothing sticky or memorable", "why_fails": "30 minutes later, they cannot remember who you are or what you do", "fix": "Include one distinctive element: analogy, stat, visual, or unique framing", "check": "What is the one thing someone would tell a friend about you?" }, { "mistake": "Wrong Length", "looks_like": "Using 2-minute pitch in 30-second opportunity or vice versa", "why_fails": "Either rushed and incomplete or overstays welcome", "fix": "Have 15, 30, 60, 120-second versions ready, match to context", "check": "Practice with timer, know your length options cold" }, { "mistake": "Weak CTA", "looks_like": "So yeah, let me know if you want to learn more", "why_fails": "Unclear next step, too passive, easy to ignore", "fix": "Specific appropriate ask: Can we schedule 15 minutes next week?", "check": "Is your CTA a specific action or a vague hope?" }]FOR EACH MISTAKE: #AI->H::Note: ({PERSONA_NAME} warning: Watch for [mistake]) [Provide mistake details and fix]# =========================================================# STEP 9: PITCH PORTFOLIO SUMMARY BLOCK# =========================================================#AI->H::Status: (Creating pitch portfolio summary for Recipe 7 integration)#AI->H::Note: ({PERSONA_NAME} says: "Let me package everything for you. This summary block feeds into Recipe 7 for your complete brand profile, but it is also your standalone pitch reference guide.")CREATE RECIPE_OUTPUT_BLOCK: +-------------------------------------------------+ | ELEVATOR PITCH PORTFOLIO SUMMARY | | Output from Recipe 6: Elevator Pitch Builder | | To be used in: Recipe 7 (Brand Profile Synth) | | Standalone Reference: Complete pitch toolkit | +-------------------------------------------------+ PRIMARY PITCHES (Lead with these): === 30-SECOND PITCH (All-Purpose) === [Your best 30-second pitch - default for most] === 60-SECOND PITCH (Standard) === [Your best 60-second pitch - comprehensive value] CONTEXT-SPECIFIC VARIATIONS: Investor Context: - Lead with: [Which pitch and style] - Key emphasis: [What to stress] - Proof points: [Metrics to highlight] Customer Context: - Lead with: [Which pitch and style] - Key emphasis: [What to stress] - Transformation focus: [Outcome to paint] [Additional contexts as requested] PITCH COMPONENTS LIBRARY: - Primary hook: [Your best attention-grabber] - Problem statement: [Core pain point framing] - Solution positioning: [How you introduce] - Differentiation: [Primary competitive edge] - Transformation: [Key outcome promise] - Proof point: [Best validation or traction] - Call to action: [Default next step] ADAPTATION GUIDANCE: Quick (15-sec): [When to use, what to include] Standard (30-60 sec): [Default approach] Detailed (2-min): [When appropriate, structure] TOP RECOMMENDATIONS: 1. [Most important pitch strategy point] 2. [Second key recommendation] 3. [Third strategic consideration] QUALITY ASSESSMENT SUMMARY: Strongest aspects: [What works best across] Watch areas: [What needs monitoring] Improvement priorities: [Top 1-2 to refine] +-------------------------------------------------+ | END ELEVATOR PITCH PORTFOLIO SUMMARY | +-------------------------------------------------+# =========================================================# STEP 10: PRACTICE AND REFINEMENT ROADMAP# =========================================================REFINEMENT_PROCESS = { "week_1": { "focus": "Memorization and comfort", "activities": [ "Practice each pitch 10+ times out loud", "Record yourself, watch for filler words", "Get feedback from 3-5 people in target", "Note which parts feel awkward or unclear" ], "success_metric": "Can deliver without notes" }, "week_2_4": { "focus": "Real-world testing and adaptation", "activities": [ "Use pitches in 10+ real situations", "Track which hooks get best responses", "Note where people interrupt (good and bad)", "Identify which proof points resonate most" ], "success_metric": "Conversion to next step improves, fewer confused looks" }, "month_2_3": { "focus": "Data-driven optimization", "activities": [ "A/B test pitch variations", "Track outcomes by context and length", "Gather specific feedback", "Update proof points as traction grows" ], "success_metric": "Clear winner emerges for each context, confidence builds" }, "ongoing": { "focus": "Continuous evolution", "activities": [ "Update traction metrics quarterly", "Refresh hooks when market changes", "Add new proof points as they emerge", "Keep pitch current with product evolution" ], "success_metric": "Pitch stays fresh and relevant" }}# =========================================================# COMPLETION CONFIRMATION# =========================================================NEXT_STEPS = { "immediate_use": [ "Print or save your primary 30 and 60-second pitches", "Practice each variation 5+ times out loud", "Identify your next 3 pitch opportunities", "Share with team or advisors for feedback" ], "recipe_7_preparation": [ "Pitch Portfolio Summary Block feeds into brand voice definition", "Narrative components inform messaging pillars", "Quality assessments highlight brand strengths", "Context adaptations reveal personality dimensions" ], "integration_points": [ "Website homepage: Use 30-second pitch as hero", "Email signature: 15-second pitch as tagline", "LinkedIn: 60-second pitch adapted for About", "Pitch decks: 2-minute pitch forms narrative arc", "Sales calls: 30-second opener into conversation", "Social media bio: 15-second hook" ]}#AI->H::Note: ({PERSONA_NAME} final thought: "Remember: your pitch is a conversation starter, not a comprehensive company overview. Success is not measured by how much you say, but by whether they want to hear more. Keep iterating based on real responses, and do not be afraid to evolve as you learn what resonates.")#AI->H::Status: (Recipe 6: ELEVATOR-PITCH-BUILDER execution complete)#AI->H::Summary: (Created {total_pitch_count} pitch variations across {len(pitch_contexts)} contexts, {len(pitch_lengths)} lengths, and {style_count} styles)#AI->H::Output::ReadyFor: (Recipe 7: Brand Profile Generator)#AI->H::Output::ReadyFor: (Immediate use in pitching situations)#AI->H::Reminder: (Copy the Elevator Pitch Portfolio Summary Block - you will need it for Recipe 7 and as your ongoing pitch reference)#AI->H::COM::Status: (ELEVATOR-PITCH-BUILDER completed successfully) """, outputs={ "ELEVATOR_PITCH_PORTFOLIO": { "format": "Structured summary block", "purpose": "Complete pitch toolkit", "usage": "Copy for Recipe 7 and reference" }, "PITCH_VARIATIONS": { "format": "Complete pitch scripts", "purpose": "Ready-to-use pitches", "usage": "Use in actual pitching situations" }, "COMPONENT_LIBRARY": { "format": "Reusable pitch elements", "purpose": "Mix and match for custom pitches", "usage": "Build new variations quickly" }, "QUALITY_ASSESSMENTS": { "format": "Scorecard per pitch", "purpose": "Identify strengths and gaps", "usage": "Prioritize refinement efforts" }, "DELIVERY_TIPS": { "format": "Presentation guidance", "purpose": "Improve pitch delivery", "usage": "Practice and performance", "available_when": "include_delivery_tips True" } }, integration_notes=""" RECIPE DEPENDENCIES: - Required: Recipe 2 (Target Audience Analyzer) - Required: Recipe 4 (Value Prop Crafter) - Required: Recipe 5 (Competitive Edge Definer) - Optional: Recipe 3 (Pain Point Identifier) - Optional: Traction data (strengthens proof) FEEDS INTO: - Recipe 7 (Brand Profile Synthesizer) - Immediate use in real pitching situations - Website homepage and marketing copy - Sales materials and pitch decks PERSONA CONTINUITY: - Uses BRAND_PERSONA object if defined - Defaults to Strategic Brand Architect - Maintains consistent voice from Recipes 1-5 - Brings pitch coaching expertise to content COMMON MODIFICATIONS: - Add industry-specific pitch angles - Extend for stage-specific variations - Include cultural adaptation guidance - Add multilingual pitch versions """)# =========================================================# END RECIPE-ID: RCP-004-001-006-ELEVATOR-PITCH-v2.00a# =========================================================