Help me plan my sales week. Current state: ● Open pipeline: [TOTAL VALUE] ● Deals closing this month: [NUMBER AND VALUE] ● Meetings booked this week: [NUMBER] ● Prospecting target: [CALLS/EMAILS] ● Admin tasks due: [WHAT'S NEEDED] Help me plan: 1. Priority deals to advance (top 3-5) 2. Prospecting blocks (when and how much) 3. Follow-up tasks (who needs what) 4. Meeting preparation time 5. Admin time (CRM, forecasting) Weekly cadence template: ● Monday: Week planning + top deals ● Tuesday-Thursday: Prospecting + meetings ● Friday: Follow-up + forecast Time blocking suggestions: ● Deep work windows ● Call blocks ● Email processing ● CRM updates

Based on these recurring deal themes [DEAL_THEMES], write 3 LinkedIn posts that position me as a thought leader to my buyer [PERSONA]. Each post should: open with a pattern interrupt, share an insight from the field, and end with a question. No pitching.

Help me navigate this security review process. Context: ● Prospect: [COMPANY] ● Their industry: [INDUSTRY - affects compliance needs] ● Security contact: [NAME, TITLE] ● Questionnaire type: [SIG / CAIQ / CUSTOM / VSAQ] ● Questions I'm stuck on: [LIST SPECIFIC QUESTIONS] ● Our certifications: [SOC2 / ISO27001 / GDPR / HIPAA / etc.] ● Our security page: [URL IF EXISTS] Help me with: 1. Understanding what they're really asking 2. Drafting responses that are accurate and reassuring 3. Identifying gaps we need to address honestly 4. Red flags that could slow us down 5. How to position security as a differentiator 6. Questions to ask their security team Format responses as copy-paste ready with appropriate caveats.

Generate SPIN questions for my sales conversations. Context: ● My product: [WHAT YOU SELL] ● Target persona: [WHO YOU SELL TO] ● Main problems we solve: [TOP 3 PAIN POINTS] ● Typical objections: [COMMON PUSHBACK] Generate 5 questions for each category: SITUATION (establish context): ● Questions about their current state ● Non-threatening, fact-finding PROBLEM (uncover difficulties): ● Questions that surface pain ● Focus on challenges and frustrations IMPLICATION (develop seriousness): ● Questions that expand the problem ● Connect to business impact NEED-PAYOFF (envision solution): ● Questions that make them articulate benefits ● Let them sell themselves Include transitions between each phase.

You are acting as an expert RFP response manager, solution writer, sales engineer, product marketer, and compliance-oriented researcher for my company. Your job is to help me complete an entire prospect RFP using only verified information you can find across our connected company systems, documents, knowledge bases, past RFPs, security documentation, product documentation, internal wikis, approved messaging, legal language, Slack, and any other relevant internal sources available to you. This is not a simple Q&A task. You must act like an internal proposal team member responsible for producing accurate, defensible, submission-ready RFP responses. PRIMARY OBJECTIVE Review the entire RFP I provide and generate the strongest possible complete response set, using grounded company information only. Do not guess. Do not invent capabilities, certifications, commitments, integrations, roadmap items, customer examples, legal terms, security claims, or implementation details. CORE RULES 1. Accuracy is more important than completeness. 2. Never fabricate information. If something cannot be verified, clearly label it as: - “Not verified from available sources” - “Needs SME review” - “Needs Legal review” - “Needs Security review” - “Needs Product confirmation” 3. Use the most recent and authoritative internal source available. 4. Prefer approved language from: - prior winning RFP responses - official product documentation - security/compliance documentation - legal-approved templates - internal knowledge base content - current solution briefs / datasheets 5. If sources conflict, call out the conflict and use the most recent authoritative source. 6. Never overstate. If the prospect asks whether we “do” something and the answer is nuanced, explain the nuance precisely. 7. Keep responses professional, clear, concise, and submission-ready. 8. Preserve any prospect-required formatting, answer scale, yes/no structure, tables, or character limits whenever provided. WORKFLOW Follow this process for the full RFP: PHASE 1, INGEST AND ORGANIZE - Read the full RFP document or pasted questions carefully. - Break the RFP into a structured list of questions/requirements. - Categorize each item by type, such as: - company overview - product capability - implementation / onboarding - integrations - architecture - security - compliance / certifications - privacy / data handling - support / SLA - training - pricing / commercial - legal / contractual - customer references / case studies - Identify any instructions from the prospect, such as: - word count limits - yes/no only - table completion - mandatory attachment requests - formatting requirements - deadlines - requested exhibits or evidence PHASE 2, SEARCH STRATEGY For each RFP section, create multiple small searches across relevant connected tools and sources. - Start broad to build context. - Then run narrower searches to verify exact claims, wording, dates, metrics, and supporting evidence. - Reuse wording from approved prior answers only when still accurate and supported by current sources. - Search for: - prior RFP answers to similar questions - security questionnaires - trust center or compliance documents - legal-approved language - product capability documentation - architecture diagrams / deployment docs - support and SLA details - implementation methodology - customer proof points and case studies - internal notes about limitations or exclusions - SME commentary if needed, but label it appropriately if not formal/approved PHASE 3, EVIDENCE GATHERING For every answer: - Identify the best supporting sources. - Pull the most relevant quotes/snippets. - Note the source name, date, and exact URL if available. - Judge source quality: - highest: official current company documentation, legal/security approved material - medium: recent internal RFPs or internal wiki pages - lower: Slack discussions or informal notes, use only to guide further searching unless explicitly needed - If only weak evidence is available, say so clearly. PHASE 4, DRAFT THE RESPONSE For each RFP item, provide: 1. Question ID / section 2. Prospect question text 3. Recommended final answer, submission-ready 4. Confidence level: - High - Medium - Low 5. Review flag: - None - SME Review - Legal Review - Security Review - Product Review 6. Supporting citations with numbered hyperlinks 7. Notes on any assumptions, limitations, or wording risks PHASE 5, GAP AND RISK REVIEW After drafting all responses, provide: - A list of unanswered or weakly supported questions - A list of questions that may require: - legal signoff - security signoff - product management confirmation - services/implementation review - executive approval - A list of risky prospect asks, such as: - custom commitments - unsupported functionality - non-standard SLA language - roadmap promises - data residency guarantees - bespoke integration promises - unlimited support or liability language - Suggested follow-up questions for internal SMEs, if needed SEARCH AND REASONING BEHAVIOR When investigating: 1. Break each question into smaller search tasks. 2. Search multiple relevant tools, but only ones that are actually useful. 3. Capture exact supporting language where possible. 4. Compare recent vs older material. 5. Stop when you have a reasonable, supported answer. 6. If support is incomplete, do not fill gaps with assumptions. 7. Offer the best grounded draft possible and explicitly flag anything that needs human review. OUTPUT FORMAT Use this exact structure. ## Executive Summary Provide a 3-6 sentence summary covering: - overall completeness of the draft - major gaps - highest-risk sections - what likely needs internal review before submission ## RFP Response Table For each question, use this format: ### [Question ID or Section Name] **Prospect Question:** [Paste the exact question] **Recommended Response:** [Provide the final submission-ready answer] **Confidence:** High / Medium / Low **Review Needed:** None / SME / Legal / Security / Product / Services / Executive **Supporting Evidence:** - [1] [Source title](exact-url) , brief note on relevance - [2] [Source title](exact-url) , brief note on relevance **Notes / Risks:** [Only include if relevant] ## Open Items and Gaps List every question where: - the answer is weakly supported - no verified answer was found - a response may create risk - clarification is needed ## Internal Follow-Up Questions Write the exact questions I should send to internal SMEs to close the gaps. ## References Include all citations used in numbered format: [1] [Source Name - Date](exact-url) [2] [Source Name - Date](exact-url) CITATION RULES - Every factual claim used in an answer must have a citation. - Always use the exact URLs from search results. - Use numbered hyperlinked citations like [1], [2]. - Include Slack citations if used, but prefer formal documents over Slack. - Include a full References section at the bottom. - If no URL exists, cite the source name and date if possible, and clearly note that no direct URL was available. STYLE RULES FOR FINAL RFP RESPONSES - Write in plain, professional business language. - Be clear and direct. - Avoid hype, fluff, or marketing adjectives unless the source itself uses approved language. - When possible, answer in a way that helps the prospect evaluate us positively without overstating anything. - Preserve prospect wording requirements, yes/no structure, and formatting rules. - Where appropriate, provide concise but complete responses that sound like they came from a professional proposal team. IMPORTANT - Do not just summarize what you find. - Produce actual proposed RFP answers. - Do not skip hard questions. - Do not hide uncertainty. - If the RFP contains a spreadsheet or matrix-style questionnaire, preserve the row-by-row answer structure as much as possible. - If prior answers appear outdated, do not reuse them without verification. - If a question appears to require a non-standard commitment, flag it clearly rather than answering aggressively. When I provide the RFP, start by: 1. identifying the major sections, 2. listing any formatting or submission constraints you detect, 3. then drafting the response table section by section.

Create trial check-in messages. Context: ● Product: [WHAT YOU SELL] ● Trial length: [DAYS] ● Key activation event: [WHAT SHOWS THEY'RE ENGAGED] ● Customer persona: [WHO'S USING IT] Create check-ins for: Day 1: Welcome + quick start Day 3: First milestone check Day 7: Engagement check (are they using it?) Day 10: Value conversation Day [X-2]: Trial ending soon Day [X]: Final ask For each check-in: ● Subject line ● Body (under 100 words) ● Goal of the touchpoint ● If low engagement, alternative message ● CTA Include both email and in-app message versions.

Create a value proposition for [PRODUCT/SERVICE]: What we do: [DESCRIPTION] Who we help: [TARGET] Problem we solve: [PAIN POINT] How we're different: [DIFFERENTIATOR] Create: 1. One-sentence value prop 2. Three-sentence version 3. Elevator pitch (30 seconds) 4. Why it matters (so what?) Value Prop by Persona Create persona-specific value propositions for [PRODUCT]: Persona 1: [TITLE - e.g., VP Sales] Persona 2: [TITLE - e.g., SDR Manager] Persona 3: [TITLE - e.g., CEO] For each: ● What they care about ● Value prop in their language ● Specific benefit that matters to them ● One-sentence version Value Prop for Specific Deal Create a custom value proposition for this prospect: Prospect: [COMPANY] Their situation: [WHAT YOU KNOW] Their pain: [SPECIFIC CHALLENGES] Our solution: [WHAT WE OFFER] Craft value prop that: ● Speaks to their specific situation ● Uses their language ● Addresses their exact pain ● Quantifies impact if possible Proposals Executive Summary Write an executive summary for a proposal to [COMPANY]: Context: ● What we discussed: [KEY POINTS FROM SALES PROCESS] ● Their challenges: [PAIN POINTS] ● Proposed solution: [WHAT YOU'RE RECOMMENDING] ● Investment: [PRICING] Format: 5. The situation (their challenge) 6. The impact (cost of status quo) 7. The solution (what we're proposing) 8. The outcome (what they'll achieve) 9. The ask (clear next step) Keep it to one page. Full Proposal Outline Create a proposal outline for [COMPANY]: Deal context: ● What we're proposing: [SOLUTION] ● Their needs: [REQUIREMENTS] ● Decision makers: [WHO'S INVOLVED] ● Timeline: [WHEN THEY NEED IT] Create section headers and bullet points for: 10. Executive Summary 11. Understanding Your Challenge 12. Proposed Solution 13. Implementation Approach 14. Investment and Timeline 15. Expected Outcomes 16. Why [Your Company] 17. Next Steps ROI Justification Build an ROI justification for [PRODUCT] for [PROSPECT]: Our price: [AMOUNT] Their current situation: [WHAT THEY DO TODAY] What we'll improve: [METRICS] Calculate and present: 18. Current costs (status quo) 19. Expected savings/gains 20. Time to value 21. Payback period 22. 1-year ROI 23. 3-year ROI Make assumptions clear and reasonable. Business Case One-Pager Create a one-page business case for [PRODUCT] for [COMPANY]: The ask: [WHAT YOU NEED APPROVED] For: [WHAT YOU'RE BUYING] Investment: [COST] Include: 24. Problem statement (why we need this) 25. Proposed solution (what we're buying) 26. Expected benefits (quantified) 27. Cost breakdown 28. Risk of not doing this 29. Recommended action Format for internal champion to share. Pitch Decks Pitch Deck Outline Create a pitch deck outline for [PRODUCT] presenting to [AUDIENCE]: Context: [SALES STAGE - first meeting / demo / final pitch] Goal: [WHAT YOU WANT TO ACHIEVE] Time: [HOW LONG] Create slide-by-slide outline: ● Slide title ● Key point ● Supporting content ● Visual suggestion Customer-Specific Deck Customize my standard pitch deck for [COMPANY]: Standard deck covers: [MAIN POINTS] Their specific situation: [WHAT YOU KNOW] Their priorities: [WHAT THEY CARE ABOUT] Recommend: 30. Slides to keep as-is 31. Slides to customize (and how) 32. Slides to remove 33. Slides to add 34. Order changes Demo Script Create a demo script for [PRODUCT] for [PERSONA]: Demo time: [MINUTES] Their pain points: [WHAT THEY CARE ABOUT] Features to show: [KEY FEATURES] Features to skip: [WHAT'S NOT RELEVANT] Structure: 35. Opening (connect to their pain) 36. Feature 1 (with story) 37. Feature 2 (with story) 38. Feature 3 (with story) 39. Questions to ask during 40. Closing (next steps) Include transition language. One-Pagers & Collateral Product One-Pager Create a product one-pager for [PRODUCT]: Audience: [WHO WILL READ IT] Goal: [WHAT YOU WANT THEM TO DO] Include: 41. Headline (value prop) 42. The problem (2-3 sentences) 43. The solution (2-3 sentences) 44. Key features (3-4 bullets) 45. Proof point (customer quote or stat) 46. CTA Keep it to one page. Make it scannable. Case Study Outline Create a case study outline for [CUSTOMER]: What they were doing before: [STATUS QUO] What they were struggling with: [CHALLENGES] Why they chose us: [DECISION FACTORS] What we implemented: [SOLUTION] Results: [OUTCOMES/METRICS] Format: 47. Customer profile (company, industry, size) 48. The challenge 49. The solution 50. The results (quantified) 51. Quote from customer 52. CTA Competitor Comparison Sheet Create a comparison sheet: [YOUR PRODUCT] vs. [COMPETITOR(S)]: Feature categories to compare: 53. [CATEGORY 1] 54. [CATEGORY 2] 55. [CATEGORY 3] 56. [CATEGORY 4] Include: ● Feature comparison table ● Positioning statement ● When to choose us ● Proof points Keep it honest. Don't just check every box. Pricing Presentation Present Pricing Create pricing presentation language for [PROSPECT]: Our pricing: [PACKAGES AND AMOUNTS] Their situation: [COMPANY SIZE, NEEDS] Value we provide: [EXPECTED OUTCOME] Create: 57. Setup language (before showing price) 58. How to present the options 59. Anchoring strategy 60. Handling "let me think about it" 61. Discount strategy (if any) Justify Premium Pricing Justify our pricing vs. cheaper alternatives: Our price: [AMOUNT] Cheaper option: [COMPETITOR AT $X] Why we're worth more: [REASONS] Create messaging that: ● Acknowledges the price difference ● Reframes value vs. cost ● Highlights TCO, not just price ● Uses proof points ● Doesn't trash competitor Email Attachments What to Send When Asked Prospect said "send me some info." Context: ● Stage: [WHERE IN PROCESS] ● What they care about: [IF KNOWN] ● Goal: [WHAT YOU WANT NEXT] Recommend: 62. What to send (and what NOT to send) 63. How to frame it in the email 64. Specific CTA 65. Follow-up strategy Follow-Up After Proposal Write a follow-up email to [PROSPECT] who received my proposal [X DAYS] ago. Proposal included: [WHAT YOU SENT] Next step discussed: [WHAT WAS SUPPOSED TO HAPPEN] Write an email that: ● References the proposal ● Adds something new (not just "checking in") ● Makes it easy to move forward ● Has a clear ask

Act as an expert "Prospect Intelligence Keyword Architect" specializing in B2B contact discovery optimization. TARGETING PARAMETERS: Primary Industry: [INDUSTRY_FROM_ICP] Sub-Industry Niche: [SPECIFIC_VERTICAL] Geographic Focus: [REGION_SPECIFICATIONS] Target Roles: [DECISION_MAKER_TITLES] Company Characteristics: [SIZE/STAGE/TECH_STACK_CRITERIA] Special Qualifiers: [PAIN_POINTS/COMPLIANCE/BUDGET_INDICATORS] KEYWORD INTELLIGENCE FRAMEWORK: Analyze the target market to identify search terms across these categories: JOB TITLE VARIATIONS (15-20 keywords): Executive level titles and variations Functional role descriptors Department-specific terminology Seniority indicators and modifiers Industry-specific title variations INDUSTRY & VERTICAL TERMS (10-15 keywords): Primary industry descriptors Sub-sector terminology Market segment language Regulatory classification terms Technology category identifiers SOLUTION & SERVICE KEYWORDS (10-15 keywords): Service category terms prospects search for Problem-solution language Technology implementation terms Outcome and benefit descriptors Vendor evaluation terminology PAIN POINT & TRIGGER INDICATORS (8-12 keywords): Challenge description language Urgency indicator terms Budget approval terminology Initiative and project descriptors Compliance requirement terms COMPANY & TECHNOLOGY DESCRIPTORS (5-10 keywords): Company stage and growth indicators Technology stack terminology Business model descriptors Market position indicators Operational scale terms INTENT & BEHAVIOR SIGNALS (5-8 keywords): Buying intent terminology Research behavior indicators Evaluation process language Implementation readiness terms Vendor engagement signals OPTIMIZATION REQUIREMENTS: Zero duplicate terms or close synonyms Character limit: Maximum 2,000 characters total Apollo/Clay search compatibility verified Match rate optimization prioritized False positive minimization focused KEYWORD TESTING MATRIX: Provide 3 keyword string variations: Broad Net: Maximum coverage with 45-50 terms Precision Focus: High-intent terms with 30-35 keywords Ultra-Targeted: Laser-focused with 20-25 premium terms FINAL OUTPUT: Three comma-separated keyword strings optimized for copy-paste implementation into lead sourcing platforms, with expected match rate estimates and quality predictions for each variation.

Write a set of 10 questions for a customer case study interview with [FILL IN customer name] at [FILL IN company]. Questions should surface: (1) the before state (problem + cost), (2) why they chose us, (3) implementation experience, (4) quantified outcomes, (5) what they'd tell a peer considering our solution.

Write a renewal email to [FILL IN contact name] at [FILL IN company] whose contract renews in [FILL IN days]. The email should: remind them of value delivered, make the renewal process simple, address any known risk proactively, and include a clear next step. Customer context: [FILL IN].

You are a post-sale revenue strategist supporting retention and expansion. Task: Create a renewal business case. Inputs: - Customer: [ACCOUNT] - Current footprint: [CURRENT PRODUCTS / USE CASES] - Stakeholders: [STAKEHOLDERS] - Business outcomes achieved: [RESULTS] - Risks or gaps: [RISKS / LOW ADOPTION AREAS] - Expansion hypothesis: [UPSELL / CROSS-SELL OPPORTUNITY] Requirements: - Focus on customer value realization first - Keep recommendations grounded in adoption, outcomes, and stakeholder alignment - Make it easy for the account team to turn this into action - Where appropriate, include retention risk signals Output: 1. Summary 2. Recommended actions 3. Messaging or questions to use with the customer 4. Risks to monitor

You are a post-sale revenue strategist supporting retention and expansion. Task: Create a churn prevention. Inputs: - Customer: [ACCOUNT] - Current footprint: [CURRENT PRODUCTS / USE CASES] - Stakeholders: [STAKEHOLDERS] - Business outcomes achieved: [RESULTS] - Risks or gaps: [RISKS / LOW ADOPTION AREAS] - Expansion hypothesis: [UPSELL / CROSS-SELL OPPORTUNITY] Requirements: - Focus on customer value realization first - Keep recommendations grounded in adoption, outcomes, and stakeholder alignment - Make it easy for the account team to turn this into action - Where appropriate, include retention risk signals Output: 1. Summary 2. Recommended actions 3. Messaging or questions to use with the customer 4. Risks to monitor

You are a post-sale revenue strategist supporting retention and expansion. Task: Create a stakeholder expansion. Inputs: - Customer: [ACCOUNT] - Current footprint: [CURRENT PRODUCTS / USE CASES] - Stakeholders: [STAKEHOLDERS] - Business outcomes achieved: [RESULTS] - Risks or gaps: [RISKS / LOW ADOPTION AREAS] - Expansion hypothesis: [UPSELL / CROSS-SELL OPPORTUNITY] Requirements: - Focus on customer value realization first - Keep recommendations grounded in adoption, outcomes, and stakeholder alignment - Make it easy for the account team to turn this into action - Where appropriate, include retention risk signals Output: 1. Summary 2. Recommended actions 3. Messaging or questions to use with the customer 4. Risks to monitor

Analyze this as if you were a sales expert. We want to understand the leading indicators for why we lost this deal. Identify the key moments that contributed to this loss, specifically the things that the rep did, or failed to do, to cause the prospect to not purchase [our solution]. This includes things like, but not limited to: failure to align with certain stakeholders, poor competitive positioning, lack of compelling differentiation, poor multi-threading, lack of certain feature/functionality, missed moments of discovery, misalignment on business outcomes, weak business case, and more. Identify other moments that came up that I didn’t mention, if applicable. Details matter, specifically *when* those plays/moments occurred in the deal (early in the deal, middle of the deal, later in the deal, etc). The goal is to understand the reasons we lose so other reps can avoid making the same mistakes. Be extremely comprehensive and specific about the details. Replace all adjectives like “poor” or “lack of” with numbers or context that supports the adjectives.

Analyze this as if you were a sales expert We want to understand the leading indicators for why we won this deal. Highlight the key moments that contributed to this win. Specifically, look for the plays the rep used to pre-empt/address problems and other things that were important to the customer, like: what challenge did the rep demonstrate that we could solve, what personas were involved, what is the degree of multi-threading on the customer side, what features and functionality were highlighted by the rep that were important, and what was the main obstacle that the rep had to overcome. Identify other factors that came up that I didn’t mention, if applicable. Details matter, specifically when those plays/moments occurred in the deal (early in the deal, middle of the deal, later in the deal, etc.). The goal is to build a playbook so other reps can replicate this success at scale. Be extremely comprehensive and specific about the details. Replace all adjectives like “high” or “strong” with numbers or context that supports the adjectives.

My market has many competitors. Help me position: Competitors and their positions: 1. [COMPETITOR A]: [HOW THEY POSITION] 2. [COMPETITOR B]: [HOW THEY POSITION] 3. [COMPETITOR C]: [HOW THEY POSITION] My product: [WHAT YOU SELL] Our strengths: [LIST] Suggest: 1. A unique position we can own 2. How to describe it simply 3. Proof points needed 4. What to avoid claiming

You will be writing a thought leadership article of 3,000+ words on an important topic for sales leaders in [YEAR]. The topic is: [TOPIC] Here are the steps to follow: 1. First, provide some context in 2-3 paragraphs on why this topic is highly relevant and important for sales leaders to understand in [YEAR]. Explain the key trends, challenges or opportunities related to this topic that sales leaders will be facing. 2. Next, outline the key points and high-level structure you plan to cover in the article. List out the main sections and subsections in a nested outline format, with 1-2 sentence descriptions summarizing what each section will cover. 3. Once you have outlined the structure, write out the full article content inside tags. Incorporate the key points from your outline, expanding on each one with deep insights, examples, data, quotes from experts, and actionable advice for sales leaders. Some important guidelines: - Write in a professional, authoritative, thought-provoking style suited for an executive audience - Conduct additional research as needed to substantiate key points with facts, statistics, and credible sources - Use clear section headings and formatting to organize the content logically - Provide specific, practical recommendations that sales leaders can implement - Aim for a total word count of 3,000-4,000 words for the full article - Ask clarifying questions before you begin writing to make sure you understand the topic and focus and if you need to do sections at a time to get to the 3000 words please do so and check in with me as you do. Focus on High quality, spartan conversational and professional tone with no yapping or jargon and varying sentence structure and length with no em dashes. Begin by providing the context on the importance of the topic, then outline the key points and structure, before writing out the full article content. Let me know if you need any clarification on the instructions.

Create a comprehensive account growth plan for an AM/CSM/rep. Analyze retention risk, stakeholder map, adoption gaps, whitespace, cross-sell and upsell opportunities, renewal plan, engagement strategy, and 30/90-day actions with metrics. Instructions: - Be clear, specific, and practical. - If information is missing or uncertain, say so directly instead of guessing. - Think step by step internally, but present only the final answer. - Use plain English and avoid filler. - Tailor the output to the user's stated context, constraints, and goals. - Follow the requested structure exactly. Output format: - Start with a concise executive summary or top-line answer. - Then use clearly labeled sections and bullet points where helpful. - End with recommended next steps or key takeaways.

You are an Ethical Sales Consultant. Your goal is to provide a list of persuasion techniques that focus on mutual benefit and transparency. Context: Selling high-value items requires deep trust. The user wants to persuade the buyer while keeping their integrity intact. Instructions: Define the ‘Consultative Selling’ approach for the specific product. Provide three ‘Labeling’ techniques (from Chris Voss) to acknowledge buyer fears. Create two ‘Calibrated Questions’ that lead the buyer to discover the value themselves. Suggest a ‘Transparency’ move where you admit a limitation to build credibility. Constraints: No ‘dark patterns’ or deceptive language. Focus on the long-term relationship. Reasoning: Ethical persuasion builds “Referent Power,” making the customer more likely to return and refer others. Output Format: Strategy Overview List of Techniques Sample Scripts for each technique User Input: [Insert product/service and common buyer objection here] Expected Outcome You get a set of conversational tools. These help you handle objections with grace. You will feel more like a partner and less like a vendor. User Input Examples Selling a 5,000 dollar coaching program; objection is “it is too expensive.” Selling a new office HVAC system; objection is “the installation takes too long.” Selling a corporate wellness retreat; objection is “we do not have the time.”

Write an email to a happy customer asking them to be a reference for a prospect in the [FILL IN same industry or use case]. Make the ask specific (a 20-minute call, not an ongoing commitment), explain why they specifically would be valuable, and make it easy to say yes. Customer: [FILL IN name and company].

You are a Sales Script Architect. Your objective is to write a conversational script that follows the psychological stages of a purchase decision. Context: The user is preparing for a live sales interaction and needs a guide that feels natural yet persuasive. Instructions: Break the script into: Opening, Discovery, Value Bridge, and Close. Use ‘Active Listening’ cues in the discovery section. Apply ‘Future Pacing’ to help the buyer visualize their life after the purchase. Create a closing section that uses ‘Assumptive’ psychology. Constraints: Use conversational language. Avoid robotic phrasing. Include pauses and check-in questions. Reasoning: Scripts based on buyer psychology work because they align with the natural way humans process new information and evaluate risk. Output Format: Complete Script Marginal notes explaining the psychological purpose of each section User Input: [Insert service type and the primary goal of the call here] Expected Outcome You will have a full script ready for use. It includes notes on why you are saying certain things. This makes you more confident during the call. User Input Examples Goal: Book a demo for a marketing analytics tool. Goal: Sell a 12-month gym membership to a busy professional. Goal: Schedule a consultation for home solar panel installation.