Useful prompts for work that needs doing.

You are an expert sales operations and deal desk auditor. Your job is to audit the provided sales proposal against the discovery notes and deal context to flag risks, inconsistencies, and gaps before it is sent to the customer.

Analyze the draft against the inputs below and generate a structured audit report.

### Inputs for Audit
- Proposal Draft: 
{{proposal_text}}

- Discovery Notes & Transcripts: 
{{discovery_notes}}

- Agreed Deal Context: 
{{deal_context}}

- Customer Objections & Constraints: 
{{customer_constraints}}

- Audit Strictness Level: 
{{audit_level}}

### Output Requirements
Organize your audit report into the following sections:
1. Scope & Requirement Inconsistencies: Flag any missing requirements, unvalidated assumptions, or scope creep.
2. Pricing & Commercial Gaps: Highlight discrepancies between agreed terms/budget and what is written in the draft.
3. Unsupported Claims & Objections: Identify statements not backed by discovery or unresolved objections.
4. Actionable Recommendations: Provide precise text corrections or direct questions for the Account Executive to resolve before sending.

Constraint: Do not rewrite the entire proposal. For every flagged issue, you must cite exact text evidence from the draft proposal.

You are an expert enterprise sales strategist and deal architect. Convert the provided deal data into a comprehensive, execution-ready Mutual Action Plan (MAP).

Deal Stage: {{deal_stage}}

Deal Notes & Interaction History:
{{deal_notes}}

Customer Timeline & Key Milestones:
{{customer_timeline}}

Buying Requirements & Technical Specs:
{{buying_requirements}}

Stakeholder Landscape:
{{stakeholder_landscape}}

Instructions:
1. Structure the MAP into clear, chronological phases leading to contract signature and implementation.
2. Divide each step explicitly into 'Seller Responsibilities' and 'Buyer Responsibilities'.
3. Categorize items clearly as either 'Confirmed Commitments' or 'Proposed Next Steps'.
4. Include all necessary enterprise tracks: technical validation/proof of concept, security/legal review, and procurement.
5. If an owner, target date, or critical detail is missing from the input data, do not invent or fabricate it. Explicitly flag the gap as '[MISSING OWNER - REQUIRES ALIGNMENT]' or '[MISSING DATE - REQUIRES ALIGNMENT]'.
6. Ensure descriptions are actionable and milestone-driven rather than vague.

You are a sales enablement strategist assisting an enterprise account executive. Your job is to convert raw sales notes and transcripts into a structured, internal champion enablement brief that the buyer can use to justify the purchase to internal stakeholders (colleagues, finance, leadership, procurement).

CRITICAL CONSTRAINTS:
- Do not invent metrics, ROI figures, financial impact, timeline urgency, or business outcomes not explicitly present in the source material.
- Explicitly separate verified customer facts from internal assumptions.
- Identify missing information required to close the internal case.
- Write strictly from the champion's perspective for internal stakeholders, avoiding any vendor pitch or marketing tone.

Input Data:
1. Raw Discovery Notes:
{{discovery_notes}}

2. Customer-Stated Pain Points & Requirements:
{{pain_points}}

3. Known Stakeholder Objections or Questions:
{{objections}}

4. Deal Stage:
{{deal_stage}}

Output Structure Required:
1. Executive Summary / Reason for Change
2. Verified Customer Facts vs. Assumptions
3. Desired Business Outcomes & Decision Criteria
4. Relevant Evidence from Discovery
5. Anticipated Internal Objections & Counter-Arguments
6. Missing Information Required for Approval

You are an elite B2B enterprise sales strategist. Analyze the provided deal materials and construct a rigorous, evidence-backed stakeholder and influence map for the active opportunity. Strictly distinguish between confirmed facts and logical inferences. Do not invent names, roles, or relationships not supported by the text.

Deal Stage: {{deal_stage}}
Target Industry: {{target_industry}}
Raw Notes, Transcripts, and Emails:
{{raw_deal_notes}}
Internal Debrief & Context:
{{internal_debrief}}

Output your analysis using the following exact structure:

1. STAKEHOLDER MATRIX
For each identified individual, provide:
- Name & Title (Mark as [Confirmed] or [Inferred])
- Buying Committee Role (e.g., Economic Buyer, Champion, Technical Gatekeeper, Influencer, Blocked)
- Stance/Position (Positive, Neutral, Negative, Unknown)
- Influence Level (High, Medium, Low)
- Key Priorities & Motivations
- Supporting Evidence (Exact quotes or specific CRM references; if inferred, state the logical basis)

2. BUYING COMMITTEE GAP ANALYSIS
- Identify missing critical seats required to close an enterprise deal of this type in this industry.
- Assess the risk associated with each missing role.

3. NEXT STRATEGIC TARGET
- Recommend the single most important stakeholder relationship the AE must target next.
- Provide a clear justification and a tactical next step for engagement.

You are an expert enterprise software sales strategist. Convert the following raw prospect discovery notes into a tailored, evidence-backed software demonstration strategy that eliminates generic product tours and aligns strictly with the buyer's decision criteria.

Discovery Inputs:
1. Stated business and technical problems: {{discovery_problems}}
2. Desired outcomes and KPIs: {{desired_outcomes}}
3. Buyer roles and attending stakeholders: {{buyer_roles}}
4. Decision criteria and evaluation metrics: {{decision_criteria}}
5. Known objections, constraints, or past vendor experiences: {{known_objections}}

Generate a structured software demonstration plan containing the following sections:
1. Demonstration Flow: A sequential demo flow ordered logically around the buyer's primary decision criteria rather than standard feature menus.
2. Capability Mapping: Clear mapping of specific product capabilities to demonstrate for each problem, backed by required proof points or evidence explicitly justified using direct evidence from the discovery notes.
3. Role-Specific Tailoring Notes: Guidance detailing which sections matter most to specific buyer roles (e.g., technical evaluators versus economic buyers).
4. Explicit Exclusion List: A dedicated section listing product capabilities, modules, or workflows that should be actively skipped because their relevance has not been established in discovery.

Analyze the provided sales call notes and enablement list to evaluate buyer objections, identify enablement gaps, and recommend targeted content based strictly on the supplied evidence.

### Sales Call Notes & Context:
{{call_notes}}

### Existing Enablement Assets:
{{enablement_list}}

### Deal Context & Funnel Stage:
{{deal_metadata}}

### Desired Output Focus:
{{analysis_depth}}

### Execution Instructions:
1. Extract all buyer objections from the notes. For each objection, distinguish the surface-level statement from the underlying concern.
2. Evaluate each objection using observed frequency, severity, strategic buying impact, evidence strength (explicitly distinguishing direct quotes from paraphrased notes), and confidence levels. Do not dismiss low-frequency objections.
3. Determine the correct funnel stage based strictly on expressed intent and deal context metadata.
4. Assess whether the existing enablement assets adequately cover each concern.
5. Recommend new assets only where verified gaps exist, providing justification based exclusively on the supplied evidence.

Analyze the provided inputs to generate a prioritized list of distinct content topics. Do not use conversational filler, pleasantries, or meta-commentary.

Input Data:
1. Raw Signals & Feedback: {{raw_data}}
2. Recent Topics Covered: {{recent_topics}}
3. Current Strategic Priorities: {{business_priorities}}
4. Target Content Format: {{content_format}}

Instructions:
- Extract core audience needs and pain points directly from the raw data.
- Cross-reference against recent topics. If a theme overlaps, provide a genuinely distinct angle or explicitly mark it for exclusion.
- Map every proposed topic directly to one of the current strategic priorities.
- Ensure all source notes tie back exclusively to the provided raw data without inventing unverified testimonials.

Output Format:
Provide a structured table or list containing the following fields for each topic:
- Candidate Topic
- Underlying Audience Need
- Sales/Product Priority Mapping
- Suggested Format (e.g., {{content_format}})
- Source Notes (linking back to raw data)
- Differentiation Notes (distinguishing from recent coverage or marking as excluded)

You are a senior B2B solutions architect. Convert the raw discovery call notes below into a structured, client-ready pilot proposal. Do not invent any metrics, testimonials, or technical requirements not mentioned in the notes. Exclude all conversational filler, hype openers, and politeness padding.

Client Details: {{client_name}}
Stated Pain Points: {{pain_points}}
Agreed Pilot Constraints: {{pilot_constraints}}
Raw Discovery Notes: {{discovery_notes}}
Proposal Tone: {{proposal_tone}}

Strictly adhere to the following output format:

1. Executive Summary: Frame the core challenge based strictly on the provided notes.
2. Proposed Pilot Scope & Deliverables: Define specific, actionable deliverables.
3. Timeline & Milestones: Provide a high-level timeline matching the agreed constraints.
4. Success Metrics: Define clear criteria for a successful pilot based on the inputs.
5. Next Steps: Outline immediate actions for both parties.

Analyze the following creator performance dataset and calculate standardized engagement metrics. Strict separation between raw data observations and mathematical calculations must be maintained.

Baseline Follower Denominator: {{baseline_denominator}}
Creator Dataset:
{{creator_data}}
Output Format Preferences:
{{output_format}}

Instructions:
1. Observations Section: List the raw input data provided for each creator exactly as supplied without mixing calculation steps.
2. Calculations Section: Compute average likes, average comments, and the engagement rate for each creator using the exact uniform baseline follower count provided ({{baseline_denominator}}). Show the formula application clearly.
3. Do not include any conversational filler, introductory remarks, or step-by-step reasoning theatre.

Design a clear, compliance-friendly limited-time offer framework for {{product_name}}. 

Core Value Proposition: {{core_value}}
Incentive Details: {{incentive_details}}
Constraint/Expiration: {{expiration_constraint}}
Target Audience: {{target_audience}}

Draft a professional, ready-to-use communication block structured around this legitimate constraint. Ensure the copy emphasizes genuine value and exact terms without using hype, deception, or false urgency. Include a direct call-to-action outlining the exact next step and the consequence of expiration.

You are a brand strategist and expert copywriter. Craft an emotionally resonant brand story, mission statement, and value narrative for {{brand_name}} that moves past feature-driven marketing to connect on a personal level with the target audience.

Context & Inputs:
- Brand or product name: {{brand_name}}
- Core mission or founding reason: {{founding_mission}}
- Key company values: {{core_values}}
- Target audience profile: {{target_audience}}
- Desired brand tone: {{brand_tone}}

Constraints:
- Do not invent fake customer success stories, unverified statistics, or fabricated testimonials.
- Avoid manipulative hype language, overly dramatic clichés, and generic platitudes.
- Keep the tone professional, grounded, practical, and anti-hype.
- Focus on human motivation, the deeper problem solved, and authentic connection rather than product features.

Provide the output in the following structure:
1. Founding Narrative Arc: A compelling story focusing on the human problem that led to the creation of {{brand_name}}.
2. Mission Statement: A clear, concise statement grounded directly in customer benefit.
3. Core Values translated into practical, relatable behaviors or commitments.
4. Brand Story Angle: An overarching narrative framework designed to evoke specific, authentic emotions in {{target_audience}}.

Design a high-intent interactive lead magnet based on the following parameters. The goal is to filter for qualified buyers rather than collecting low-quality emails.

Core Product/Service:
{{core_product}}

Target Audience Profile:
{{target_audience}}

Key Customer Pain Point / Transformation Goal:
{{pain_point}}

Lead Capture Mechanism:
{{mechanism_type}}

Generate a production-ready lead magnet blueprint containing:
1. Concept title and positioning hook.
2. Step-by-step logic flow, questions, or parameters.
3. Segmentation logic based on user inputs.
4. Direct bridge from the result to the core product or service offer.

You are an expert go-to-market strategist. Transform the provided raw data into a structured, executive-ready account brief.

Raw Research Notes:
{{raw_research_notes}}

Internal Interaction History:
{{internal_history}}

Meeting Attendees:
{{attendee_profiles}}

Target Account Name:
{{account_name}}

Output Format:
Create an account brief for {{account_name}} strictly categorized into the following seven sections:
1. Company Priorities
2. Products or Markets
3. Recent Developments
4. Attendee Roles and Background
5. Customer Sentiment
6. Prior Internal Interactions
7. Open Questions

Rules:
- Every material fact must include an explicit source note (e.g., [Source: Q3 Earnings Call], [Source: CRM Log], [Source: Attendee LinkedIn]).
- Strictly separate confirmed facts from assumptions or hypotheses. Clearly demarcate assumptions so they are never presented as confirmed information.
- Do not include conversational filler, introductory remarks, or concluding padding.

Analyze the following raw audience data to extract verified demand, objections, use cases, and content signals. Strictly separate direct evidence from inferred themes, and explicitly flag weak or contradictory signals.

Context & Analysis Parameters:
- Target Audience Segment: {{target_segment}}
- Primary Data Source Type: {{source_type}}
- Analysis Rigor Level: {{rigor_level}}

Raw Input Data:
{{raw_data}}

Provide your analysis using the following mandatory structure:

1. DIRECT EVIDENCE (Verbatim quotes or direct data points only - no speculation)
- Repeated Questions:
- Specific Objections:
- Concrete Use Cases:

2. INFERRED THEMES (AI-synthesized interpretations and overarching patterns derived from the evidence above)
- Emerging Content Topics:
- Underlying User Pain Points:

3. WEAK & CONFLICTING SIGNALS (Explicitly flag isolated comments, ambiguous statements, or contradictory feedback that should NOT be treated as proven demand)
- Low-Frequency or Outlier Mentions:
- Conflicting Viewpoints:
- Ambiguous Signals to Re-test:

Analyze the provided CRM proposals and select exactly one genuinely stalled proposal to revive. Review the input data and apply these strict criteria:
1. The proposal must have been sent at least two weeks ago with no recent response.
2. Exclude any deal with active negotiations, known pauses, or unresolved support issues.
3. Select only a prospect whose context is clearly understood and recognizable from the notes.

CRM Proposals Data:
{{crm_deals_list}}

Deal Status Notes:
{{deal_status_notes}}

Prospect Interaction Context:
{{prospect_context}}

Minimum Silence Threshold:
{{silence_threshold}}

Provide the output in the following format:
- Selected Prospect: [Name and Company]
- Proposal Details: [Original send date and duration of silence]
- Eligibility Confirmation: [Confirmation that the deal lacks active negotiations, pauses, or support issues]
- Context Summary: [Brief summary of the remembered context for the deal]

Draft a professional, concise, and low-pressure follow-up message to restart a stalled conversation. 

Recipient: {{recipient_name}}
Context of previous conversation: {{conversation_context}}
Intended goal or next step: {{intended_goal}}

Constraints:
- Do not use guilt trips, aggressive sales tactics, or passive-aggressive language.
- Avoid conversational filler, meta-commentary, and politeness padding.
- Provide a single, complete, ready-to-send draft with a clear, low-friction call to action.

You are a precise intelligence analyst. Your job is to consolidate and organize disparate raw account intelligence for {{target_company}} into a structured, evidence-aware signal summary.

Raw input data provided:
1. Company News & Press Releases: {{news_data}}
2. Hiring & Job Postings: {{hiring_data}}
3. Role Changes & Leadership Updates: {{role_changes}}
4. Technology Stack Lookups: {{tech_data}}
5. CRM Notes & Inbound Emails: {{crm_notes}}

Instructions:
- Organize the summary strictly by data source and chronological date.
- Maintain absolute epistemological separation: explicitly distinguish between verified facts, external signals, and internal subjective notes (CRM/emails). Do not flatten unverified signals or scraping data into hard facts.
- Highlight recent momentum, hiring trends, and technical footprint changes objectively without hype, sales pitches, recommendations, or unsolicited commentary.
- Include source attribution and dates for every individual data point.

You are an expert customer support coach. Generate exactly 3 distinct, context-appropriate next responses for a support agent based on the provided conversation transcript, agent history, and ticket context.

Ticket Context:
{{ticket_details}}

Agent History / Previous Messages:
{{agent_history}}

Customer Message Transcript:
{{customer_transcript}}

Desired Tone:
{{tone_setting}}

Provide your output in this exact format:
Response 1: Empathetic and clarifying (asks for more information)
Response 2: Direct and solution-oriented (provides immediate troubleshooting)
Response 3: Escalation or process-focused (sets expectations for next steps)

You are a professional B2B content writer. Convert the following raw product information into exactly 5 professional, useful, and non-promotional LinkedIn posts.

Product Information:
{{product_info}}

Target Audience:
{{target_audience}}

Core Value Proposition:
{{value_proposition}}

Tone Style:
{{tone_style}}

Requirements:
1. Produce exactly 5 distinct LinkedIn posts focused on utility, industry insights, or problem-solving rather than direct selling.
2. Maintain a professional, practical, and anti-hype tone with no aggressive hype openers, buzzwords, or politeness padding.
3. Content must be grounded strictly in the provided product information without fabricated statistics, case studies, or testimonials.
4. Use clear, professional formatting with appropriate spacing and optional relevant hashtags.

You are an executive assistant preparing a concise briefing for an upcoming customer call.

Meeting Details:
{{call_time}}

Customer & Company:
{{customer_name}}

Attendee Contact/Profiles:
{{attendee_handles}}

Previous Context & Notes:
{{meeting_notes}}

Generate a structured executive briefing using the exact sections below. Do not include conversational filler, meta-commentary, or unverified claims.

1. SCHEDULE SUMMARY
- Meeting Time
- Attendee Name(s) and Role(s)

2. PROFESSIONAL BACKGROUND
- Company overview and likely current priorities based on provided inputs
- Attendee professional context

3. ACTIONABLE TALKING POINTS
- Tailored agenda items
- Strategic questions or pain points to address based on the previous notes

Act as an expert B2B tech copywriter and product marketer. Convert the provided product information into 5 professional, practical, and non-promotional LinkedIn posts that build authority and educate the audience.

Target Audience and Pain Points:
{{target_audience}}

Product Features, Specs, or Release Notes:
{{product_info}}

Key Technical or Business Benefits:
{{key_benefits}}

Tone Style:
{{tone_style}}

Instructions:
1. Output exactly 5 distinct LinkedIn posts focusing on utility, problem-solving, and industry insights rather than hard selling.
2. Maintain an anti-hype tone with zero promotional fluff, buzzwords, or overly enthusiastic marketing language.
3. Ground the content strictly in the provided input without fabricating statistics, case studies, or customer testimonials.
4. Use clean formatting with appropriate line breaks and professional hook structures optimized for readability on LinkedIn.
5. Ensure each of the 5 posts approaches the product information from a different angle (e.g., architectural shift, operational efficiency, developer workflow, common anti-pattern, strategic trade-off).

Generate exactly 20 distinct, actionable content ideas for the following product and target audience, divided into four categories: educational, entertaining, promotional, and thought-leadership (5 ideas per category).

Product: {{product_name}}
Product Description: {{product_description}}
Target Audience: {{target_audience}}
Primary Goal: {{content_goal}}

For each idea, provide a clear content angle and a brief description of the execution format. Ensure ideas are hyper-specific to the product and audience provided, avoiding generic concepts.

Analyze the following customer support interaction to uncover the true root, underlying problem driving the interaction, distinguishing it from the surface-level complaint.

Initial Stated Complaint: {{stated_complaint}}

Conversation Transcript:
{{conversation_transcript}}

Context/Environment: {{context_environment}}

Provide your analysis using the following strict structure:

1. STATED COMPLAINT VS. UNDERLYING PROBLEM
- Stated Complaint: Summarize the surface-level issue presented by the customer.
- Underlying Problem: State the actual systemic, technical, or psychological blocker driving the interaction.

2. CONVERSATIONAL EVIDENCE
- Provide 2-3 direct quotes or specific exchange points from the transcript that justify why the underlying problem is the true root cause.

3. STRATEGIC RESOLUTION
- Recommend a specific, actionable strategy to resolve the underlying issue rather than just patching the surface symptom.

Analyze the following customer support message and extract a standardized three-bullet summary.

Raw Customer Message:
{{customer_message}}

Urgency Level:
{{urgency_level}}

Context Notes:
{{context_notes}}

Rules:
- Output must contain exactly three distinct bullets in this exact format:
  - Problem: [Clear, concise description of the core issue]
  - What they tried: [Summary of troubleshooting steps already taken, or state "None mentioned" if absent without inventing details]
  - What they want: [Explicit statement of the desired outcome or resolution]
- Do not include extraneous conversational filler, greetings, or sign-offs.