Attached is a [call transcript / meeting notes document]. Read the entire thing and extract: 1. Every commitment made by the prospect (dates, actions, people) 2. Every objection or concern raised — direct quotes where possible 3. Technical environment details mentioned 4. Buying signals vs. stall signals 5. Names and roles of anyone mentioned who isn't on the call 6. One thing we missed asking about that we should follow up on Format this so I can paste it directly into Salesforce notes.

I'm attending [CONFERENCE] on [DATES] in [CITY]. Build me a 4-post LinkedIn content arc: - Post 1 (2-3 days before): Announcement / why I'm going - Post 2 (day before): Thought leadership tied to the conference theme - Post 3 (day of): Live from the event — something authentic, not a booth selfie caption - Post 4 (1-2 days after): Key takeaway or follow-up reflection For each post, give me the full draft. Keep them consistent in voice but different in angle. Short, no emoji walls, no generic conference hype.

You are a competitor research and marketing expert who is a pro at creating battlecards. I represent [FILL IN my company]. I want to compare us to [FILL IN competitor]. Please: (1) research both companies, (2) produce a full SWOT analysis for each, (3) outline 5 strategies where we have the edge, (4) name 3 areas to avoid direct comparison, (5) list 5 possible objections about our competitor and how we counter them, (6) build a feature comparison table, (7) identify 4 competitive landmines to plant, (8) suggest 5 follow-up strategies. My company URL: [FILL IN]. Competitor URL: [FILL IN].

You will be helping me identify the top 20% of accounts from my book of business that are expected to bring in 80% of the pipeline and revenue. This is based on the Pareto principle or the 80/20 rule, which states that roughly 80% of effects come from 20% of causes. First, please ask me to provide the list of accounts with relevant information like account name, total pipeline value, and any other details that can help assess their revenue potential. Once you have the account list, here are the steps to follow: 1. Think through and outline your analysis approach here. Some potential strategies: - Sort accounts by pipeline value from highest to lowest - Calculate the cumulative pipeline value starting from the top account - Identify the set of top accounts that make up ~80% of the total pipeline value - Alternatively, calculate 20% of the total number of accounts to get the top X accounts 2. Perform the necessary calculations and analysis to identify the 20% of accounts that contribute to 80% of the total pipeline/revenue potential, based on the strategy you decided in the scratchpad. 3. Prepare the list of top 20% accounts you identified through the analysis. 4. In your response, first explain the Pareto principle and how you applied it to analyze the account list. Then provide the list of top 20% accounts inside tags. 5. Justify why you selected those particular accounts as the top 20% by walking through your analysis approach and strategy inside tags. Please begin by asking me: "Can you please provide the list of accounts with details like account name, total pipeline value, and any other relevant information?"

Build a multi-channel prospecting sequence for [PERSONA] around trigger [TRIGGER]. Include: 5-touch email cadence, 3 LinkedIn messages, 2 call scripts (opener + voicemail). All touchpoints should build a cohesive narrative around our product [PRODUCT].

Create value propositions for each persona involved in buying [PRODUCT]: Persona 1 (Champion): [TITLE] Persona 2 (User): [TITLE] Persona 3 (Economic Buyer): [TITLE] Persona 4 (Technical): [TITLE] For each: - What they care about most - Value prop in their language - Proof point format they prefer - Objection they'll raise

I just learned that [COMPETITOR] has entered my deal with [COMPANY]. I'm currently at [DEAL STAGE]. Give me: 1. Real-time talking points for an immediate call 2. 3 questions to ask to learn their evaluation stage 3. How to find out what gap in my POV opened the door for the competitor 4. A revised follow-up strategy to reassert my position

Generate 5 sharp pipeline inspection questions a manager should ask a rep about [FILL IN specific deal name/context]. The questions should surface real deal health — not just confirm the rep's optimism. Deal details: [FILL IN].

“From this call transcript [CALL TRANSCRIPT] and our internal stage definition [STAGE DEFINITION], extract all next steps and structure them into a mutual action plan: items, owner (buyer/seller), due date, and dependency. Separate seller actions (‘I will…’) from buyer actions (‘You will…’).

I have a meeting with 4 stakeholders at [FILL IN company]: [FILL IN list names and titles]. For each person, provide: (1) their likely priorities and motivations, (2) their likely concern about our solution, (3) one thing to say that will resonate with them specifically. Our product: [FILL IN]. Deal stage: [FILL IN].

Help me prioritize my account list for outreach. MY ICP: - Target company size: [EMPLOYEE COUNT OR REVENUE] - Industries: [LIST INDUSTRIES] - Key signals we look for: [HIRING, FUNDING, TECH STACK, etc.] - Disqualifiers: [THINGS THAT MAKE THEM NOT A FIT] ACCOUNTS TO PRIORITIZE: [Paste a list of companies with any context you have] For each account, provide: 1. PRIORITY SCORE (1-10) - Based on ICP fit and likely timing 2. PRIORITIZATION RATIONALE - Why this score - Key signals present 3. RECOMMENDED APPROACH - Best entry point - Messaging angle to lead with 4. RESEARCH NEEDS - What else to find out before reaching out Sort the list by priority score.

I am working a deal with [prospect company name]. My primary contact is [primary contact name and role] and we are proposing [proposed solution] with a target go-live date of [target go-live date]. We have already completed the following milestones: [key milestones already completed] (e.g., "initial discovery call," "technical demo with IT team"). The known stakeholders and approvals required are: [known stakeholders and approvals required] (e.g.,"Legal review of contract," "CFO budget sign-off," "IT security assessment"). Potential risks or blockers include: [potential risks or blockers] (e.g., "budget freeze in Q3," "competing initiative from another vendor"). Generate a Mutual Action Plan that includes: 77. **Milestone Table:** A reverse-engineered timeline from the target go-live date to today, with each milestone listed as a row containing: Step, Owner (Buyer or Seller), Target Date, and Status. 78. **Buyer-Side Actions:** Specific internal steps the prospect must complete (e.g., security review, legal redline, executive sponsor briefing) with suggested owners. 79. **Seller-Side Actions:** Specific steps my team must deliver (e.g., custom demo, ROI analysis, reference call, SOW delivery) with suggested owners. 80. **Risk Mitigation:** For each identified risk or blocker, suggest a specific mitigation action and when it should be addressed. 81. **Next Steps:** The immediate next 2-3 actions both sides should take this week to keep the plan on track. Format the milestone table in Markdown so I can share it directly with the prospect. Example Input: ● Prospect Company: Acme Manufacturing ● Primary Contact: Sarah Chen, VP of Operations ● Proposed Solution: Warehouse automation platform (3-year SaaS contract) ● Target Go-Live: June 1, 2026 ● Milestones Completed: Discovery call, on-site assessment, technical demo with warehouse team ● Stakeholders/Approvals: CFO budget approval, IT security review, Legal contract review, VP of Supply ● Chain alignment Risks: Q2 budget cycle may delay CFO approval; IT team is mid-migration on another system Output: Mutual Action Plan — Acme Manufacturing × [Your Company] Objective: Go live with warehouse automation platform by June 1, Milestone Table # | Step | Owner | Target Date | Status 1 | Finalize business case & ROI analysis | Seller | Feb 24 | In Progress 2 | Present ROI to Sarah + VP of Supply Chain | Joint | Mar 3 | Not Started 3 | IT security questionnaire submitted | Seller | Mar 5 | Not Started 4 | IT security review completed | Buyer (IT) | Mar 19 | Not Started 5 | Reference call with similar manufacturer | Seller | Mar 10 | Not Started 6 | Executive sponsor briefing with CFO | Buyer (Sarah) | Mar 24 | Not Started 7 | CFO budget approval | Buyer (CFO) | Apr 1 | Not Started 8 | SOW / contract delivered | Seller | Apr 7 | Not Started 9 | Legal redline and review | Buyer (Legal) | Apr 21 | Not Started 10 | Contract signed | Joint | Apr 28 | Not Started 11 | Implementation kickoff | Joint | May 5 | Not Started 12 | Go-live | Joint | Jun 1 | Not Started Buyer-Side Actions ● **Sarah Chen (VP Ops):** Schedule executive sponsor briefing with CFO; align VP of Supply Chain on ● business case. ● **IT Team:** Complete security review within 2 weeks of questionnaire submission; confirm no conflicts ● with current migration timeline. **Legal:** Complete contract redline within 2 weeks of SOW delivery. **CFO:** Approve budget allocation before Q2 cycle lock. Seller-Side Actions ● **Account Executive:** Deliver finalized ROI analysis; coordinate reference call; draft and deliver SOW. ● **Solutions Engineer:** Complete and submit IT security questionnaire; support any technical follow-up ● questions. **Customer Success:** Prepare implementation kickoff plan and onboarding timeline. Risk Mitigation Risk | Mitigation | Timing Q2 budget cycle delays CFO approval | Accelerate executive briefing to early March; provide pre-built budget justification memo for Sarah to share | Week of Feb 24 IT mid-migration conflicts | Schedule a 30-min call with IT lead to confirm security review bandwidth and flag any scheduling conflicts early | Week of Mar 3 Next Steps (This Week) 82. **Seller:** Send draft ROI analysis to Sarah for review by Friday. 83. **Sarah:** Confirm availability for joint presentation with VP of Supply Chain the week of Mar 3. 84. **Seller:** Send IT security questionnaire to Sarah's IT contact. Tips ● Share the MAP with your prospect as a collaborative document — it should feel like a joint plan, not a ● seller's checklist. ● Review the MAP together on every call and update statuses in real time. This keeps accountability on both ● sides. ● Work backward from the go-live date. If a milestone slips, immediately adjust downstream dates and flag the impact. Use the MAP to uncover hidden steps. Ask your prospect: "What internal steps am I missing that could surprise us?" A MAP that only has seller actions is a project plan, not a mutual plan. Ensure genuine buyer-side ownership.

Build me a 30-day prospecting plan for [VERTICAL: financial services / healthcare / insurance / government] in my Midwest and Great Plains territory. Primary goal: Book net-new discovery meetings. Lead product: [PK Protect data discovery / PEM encryption / DSM]. Regulatory triggers to leverage: [e.g., PCI DSS 4.0 enforcement, NYDFS Part 500, HIPAA updates]. Give me: 1. Top 15 named target accounts with brief rationale for each 2. A week-by-week execution cadence 3. Email template for cold outreach (under 100 words) 4. LinkedIn connection request template (under 300 characters) 5. Conference or event tie-ins I should leverage this month 6. Performance targets — how many meetings should I expect from this effort?

Create cold call scripts for different scenarios. Context: ● My product: [WHAT YOU SELL] ● Target title: [WHO I'M CALLING] ● Average call goal: [BOOK MEETING / QUALIFY / INFO GATHER] Generate scripts for: 1. Gatekeeper navigation (getting past the EA) 2. Direct connect opener (they picked up) 3. Referral-based call (someone recommended) 4. Follow-up to email call (they received your email) 5. Event-triggered call (after their news/announcement) 6. Competitor displacement call (they use competitor) Each script includes: ● Opening line (first 10 seconds) ● Value statement (next 20 seconds) ● Interest gauge question ● Common objection responses ● Meeting ask ● Voicemail version (if they don't answer)

I am a [YOUR ROLE] preparing for a live product demo with [prospect company name] in the [industry] industry. Demo logistics: ● Date: [demo date and duration] ● Deal stage: [deal stage and deal size] Attendees and their priorities: [attendees — names, titles, and known priorities] (e.g., "Sarah Chen, VP Ops — cares about reducing manual work; James Liu, IT Director — focused on security and integrations; Mark Torres, CFO — needs ROI justification") Discovery insights (pains, current state, desired outcomes): [discovery insights — pains, current state, desired outcomes] (e.g., "Currently using spreadsheets for inventory tracking, losing ~$200K/year in stockouts, goal is realtime visibility across 12 warehouses") Competitive alternatives being evaluated: [competitive alternatives prospect is evaluating] (e.g., "Evaluating CompetitorX and building in-house") Key product capabilities I plan to show: [specific product capabilities to showcase] (e.g., "Real-time dashboard, automated reorder rules, API integrations with their ERP") Generate a comprehensive Demo Preparation Checklist covering the following sections: 66. **Pre-Demo Research & Intel:** A list of specific research tasks I should complete before the demo — company news, earnings, org changes, LinkedIn research on each attendee, and any industry trends I should reference to demonstrate credibility. 67. **Stakeholder-Specific Game Plan:** For each attendee, provide: - Their likely top question or concern - The 1-2 product moments in the demo that will resonate most with them - A tailored "so what" statement connecting our capability to their specific priority 68. **Demo Storyline & Flow:** A narrative arc for the demo structured as: - Opening Hook (2 min): A compelling opening that references their specific pain and sets the agenda around outcomes, not features - Current State → Pain (3 min): How to reflect back what I learned in discovery to build emotional buy-in before showing anything - Product Walkthrough (core of demo): The recommended sequence of product capabilities to show, ordered by impact — lead with the capability that solves their #1 pain, not a feature tour - Competitive Differentiation Moment: One specific moment in the demo where I should organically highlight what we do that the competition cannot - ROI / Value Anchor: A point in the demo to pause and quantify the value of what they just saw, using their own numbers from discovery - Close & Next Steps (3 min): A specific closing sequence to drive commitment to a next step 69. **Objection & Risk Preparation:** The top 3-5 objections or tough questions likely to come up during or after the demo (based on the attendees, competitive landscape, and deal stage), with a prepared response framework for each. 70. **Technical & Environment Checklist:** A pre-demo technical readiness checklist including: - Demo environment setup and data requirements - Backup plan if a live demo fails (screenshots, recorded walkthrough) - Screen-sharing and AV check reminders - Any custom configuration or sample data to load that mirrors the prospect's world 71. **Post-Demo Playbook:** A plan for the 24 hours after the demo, including: - A follow-up email template personalized to the demo conversation - Stakeholder-specific follow-ups (e.g., send the security whitepaper to IT, send the ROI model to the CFO) - Internal debrief questions for my team (what landed, what didn't, what's the next blocker) Format the output with clear headers, bullet points, and checkboxes (using - [ ]) so I can use it as a working checklist. Example Input: ● Prospect Company: BrightPath Health Systems ● Industry: Healthcare SaaS ● Attendees: Dr. Lisa Patel, CMIO — clinical workflow efficiency; Tom Andersen, VP of IT — integration ● with Epic EHR and SOC 2 compliance; Rachel Kim, CFO — cost reduction and ROI timeline ● Discovery Insights: Currently using 3 disconnected point solutions for care coordination; nurses spend ● ~40 min/shift on redundant documentation; goal is a unified platform that reduces documentation burden ● by 50% and improves care team communication ● Deal Stage: Stage 3 — Evaluation / $280K ACV Competitive Alternatives: CompetitorX (incumbent, poor UX) and an internal IT build option Key Capabilities: Unified care coordination dashboard, real-time handoff alerts, Epic EHR integration, SOC 2 + HIPAA compliance, configurable clinical workflows Demo Date: March 5, 2026 — 45 minutes via Zoom Output: Demo Preparation Checklist — BrightPath Health Systems 1. Pre-Demo Research & Intel ● [ ] Review BrightPath's latest earnings call or press releases for strategic priorities (look for mentions of ● "digital transformation," "clinician burnout," or "operational efficiency") ● [ ] Check LinkedIn for all three attendees — note recent posts, shared connections, tenure, and career ● trajectory ● [ ] Research Dr. Patel's published work or conference talks — referencing a specific insight builds instant ● credibility with a CMIO [ ] Confirm BrightPath's Epic EHR version and deployment model (hosted vs. on-prem) — ask Tom's team pre-demo if needed [ ] Review CompetitorX's latest product updates and known weaknesses (especially UX complaints in G2/KLAS reviews) [ ] Pull one relevant industry stat (e.g., "Nurses spend up to 35% of shift time on documentation — JAMA 2025") to anchor your opening 2. Stakeholder-Specific Game Plan Dr. Lisa Patel, CMIO ● **Likely top question:** "How does this actually reduce documentation time for my nurses without ● adding another screen to their workflow?" ● **Key demo moments:** Unified care coordination dashboard (show a nurse's single-pane view); configurable clinical workflows (show how documentation auto-populates from handoff data) **"So what" statement:** "Dr. Patel, instead of your nurses toggling between three systems and reentering the same patient data, they'll see one unified view that pulls forward context from the last handoff — that's how we get you to that 50% reduction in documentation time." Tom Andersen, VP of IT ● **Likely top question:** "How deep is the Epic integration, and what does the implementation timeline ● look like?" ● **Key demo moments:** Epic EHR integration (show live FHIR API data flow); SOC 2 + HIPAA compliance overview (show audit log and access controls) **"So what" statement:** "Tom, this isn't a screen-scrape or a bolt-on. We have a certified Epic integration using FHIR R4 APIs, and we'll hand you a SOC 2 Type II report and a pre-built security questionnaire before your review even starts." Rachel Kim, CFO ● **Likely top question:** "What's the payback period, and how does the cost compare to what we're ● spending on three tools plus the internal build option?" ● **Key demo moments:** ROI / Value Anchor moment (pause after the dashboard demo to quantify); consolidation narrative (show how one platform replaces three contracts) **"So what" statement:** "Rachel, you're currently paying for three separate platforms plus the IT overhead to maintain them. At $280K ACV, we project a payback period under 9 months based on the documentation time savings and the contract consolidation alone — and that's before you factor in the cost of the internal build you'd be avoiding." 3. Demo Storyline & Flow (45 min) Opening Hook (2 min) ● "Dr. Patel, when we spoke last month, you told me your nurses lose about 40 minutes every shift to redundant documentation across three systems. Today, I want to show you exactly how we eliminate that — and how BrightPath could become a reference site for care coordination. We're going to focus on three outcomes: reducing documentation burden, unifying your care team communication, and doing it in a way that Tom's team can deploy and secure with confidence." Current State → Pain (3 min) ● Reflect back the discovery: "Right now, your care coordinators open System A for patient context, System ● B for task assignments, and System C to document the handoff. That's three logins, three data entries, and zero real-time visibility for the charge nurse. You told us this is contributing to burnout and missed handoff details." Let Dr. Patel confirm or expand — this builds emotional buy-in before showing product. Product Walkthrough (30 min, ordered by impact) 72. **Unified Care Coordination Dashboard (10 min)** — Lead with the #1 pain. Show a nurse logging in once and seeing patient context, task list, and handoff notes in a single view. Use sample data that mirrors BrightPath's workflow. 73. **Real-Time Handoff Alerts (5 min)** — Show a shift-change scenario where the incoming nurse gets an automated alert with critical patient context. Highlight what CompetitorX cannot do: real-time push notifications with escalation logic. 74. **Configurable Clinical Workflows (5 min)** — Show how Dr. Patel's team can modify documentation templates without IT tickets. This is the "build vs. buy" killer — show the speed of configuration. 75. **Epic EHR Integration (5 min)** — Show live data flowing from Epic into the dashboard. Address Tom's concern head-on. 76. **Compliance & Security (5 min)** — Quick walkthrough of audit logs, role-based access, and the SOC 2 / HIPAA documentation. Don't linger — just build confidence. Competitive Differentiation Moment ● During the handoff alerts demo, say: "I know you've seen other solutions handle care coordination. What's different here is that this isn't a static task list — it's a real-time, context-aware alert system that escalates based on clinical priority. That's something we hear is a gap in the tools you've been evaluating." ROI / Value Anchor ● After the dashboard walkthrough, pause: "Dr. Patel, you mentioned 40 minutes per nurse per shift. With 200 nurses across your system, that's over 1,300 hours per week of redundant documentation. If we cut that in half — which is what our similar-sized health system clients see — that's 650 hours back to direct patient care every single week. Rachel, at a blended nursing rate, that's roughly $1.7M in annual recovered capacity." Close & Next Steps (3 min) ● "Based on what you saw today, does this align with what you need to solve the documentation and handoff challenge? ... Great. Here's what I'd recommend as next steps: First, Tom, I'll send over the security questionnaire and our SOC 2 report so your team can start their review this week. Second, Dr. Patel, I'd love to schedule a 30-minute session where two of your charge nurses can get hands-on with the product in a sandbox — nothing sells this better than clinician feedback. And Rachel, I'll send over a detailed ROI model with BrightPath-specific numbers. Can we lock in a follow-up for March 12 to regroup?" 4. Objection & Risk Preparation # | Likely Objection | Prepared Response 1 | "We're considering building this in-house with our IT team." | "That's a path some health systems explore. The question I'd ask is: what's the total cost of building, maintaining, and keeping it current with Epic API changes — and how long until your nurses actually see relief? Our customers typically go live in 8 weeks. An internal build is usually 12-18 months before v1, and that's 12-18 months your nurses are still losing 40 minutes a shift." 2 | "CompetitorX is already embedded in our environment." | "That's actually an advantage for you in this evaluation — you know firsthand what it can and can't do. The feedback we consistently hear from health systems migrating from CompetitorX is that the UX creates its own documentation burden. I'd suggest we let your nurses compare side-by-side in a sandbox — their feedback will tell you everything." 3 | "How do we know the Epic integration won't break with updates?" | "Great question, Tom. We maintain a certified Epic integration and we're part of the Epic App Orchard program, which means we're tested against every quarterly release before it ships. We also have a dedicated integration support team that monitors your connection proactively." 4 | "$280K is a big line item. Can you sharpen the pencil?" | "Rachel, I completely understand. Let's make sure the ROI model is airtight first — because if the value case is $1.7M in recovered nursing capacity, the conversation isn't about whether $280K is too much, it's about how fast we can get to that return. If the numbers work, I'm confident we can find a structure that fits your budget cycle." 5 | "We need to see a reference from a health system our size." | "Absolutely — I'll set up a call with [Reference Customer], a 200-bed system that went live 6 months ago. They saw a 45% reduction in documentation time in the first 90 days. I'll have that scheduled before our next meeting." 5. Technical & Environment Checklist Demo Environment Setup ● [ ] Load sample data that mirrors BrightPath's setup: multi-unit health system, 200+ nurses, Epic EHR ● integration active ● [ ] Create 2-3 realistic patient scenarios for the handoff demo (shift change, escalation, routine ● coordination) [ ] Configure clinical workflow templates to resemble BrightPath's documentation requirements (ask Dr. Patel's team for a sample form pre-demo) [ ] Verify Epic sandbox integration is live and returning data — test the FHIR API calls the morning of the demo Backup Plan ● [ ] Record a 5-minute backup walkthrough of the dashboard and handoff flow in case of live demo failure ● [ ] Prepare 4-5 high-resolution screenshots of key screens as a static fallback ● [ ] Have the backup video and screenshots loaded in a separate browser tab, ready to switch in under 10 seconds AV & Screen Sharing ● [ ] Test Zoom screen sharing 30 minutes before the demo — confirm resolution, frame rate, and audio ● [ ] Close all non-demo tabs, notifications, and Slack — nothing kills credibility like a ping during a demo ● [ ] Use a clean browser profile with no autofill or bookmarks visible ● [ ] Confirm attendee calendar invites are accepted and include the Zoom link Team Coordination ● [ ] Brief the Solutions Engineer on the demo flow, which features to highlight, and which to skip ● [ ] Assign a "chat monitor" if the demo is virtual — someone to capture questions in real time so the ● presenter stays in flow [ ] Align on who handles each objection if it comes up live (AE owns business objections, SE owns technical) 6. Post-Demo Playbook (First 24 Hours) Follow-Up Email (send within 2 hours) ● [ ] Send a personalized recap email to all attendees with: - A 3-bullet summary of the key outcomes discussed (not features — outcomes) - Specific next steps with owners and dates (from the close section of the demo) - Attachments tailored by stakeholder (see below) Stakeholder-Specific Follow-Ups ● [ ] **Dr. Patel:** Send a link to the clinician sandbox environment with a 2-minute video showing how to ● log in and explore ● [ ] **Tom:** Send the SOC 2 Type II report, HIPAA compliance documentation, and the pre-filled security questionnaire [ ] **Rachel:** Send the BrightPath-specific ROI model (Excel) with the nursing capacity numbers discussed live Internal Debrief (same day) ● [ ] Huddle with SE and manager to answer: - What landed? Which moment got the strongest reaction? - What didn't land? Where did we see skepticism or disengagement? - Who is the real power in the room? Did that change from our assumption? - What is the next blocker to advance this deal? - Do we need to add or remove anyone from the next meeting? ● [ ] Update CRM with demo notes, next steps, and revised close date if needed Tips ● Never start a demo with "Let me show you our platform." Start with their pain. The first two minutes ● determine whether you have the room's attention or their laptops do. ● Sequence your demo by impact, not by product menu. The #1 mistake average reps make is giving a ● feature tour. Presidents Club reps tell a story where the product is the resolution to the prospect's specific ● problem. ● Pause after your biggest "wow" moment and anchor value in their numbers. Silence after a value statement is more powerful than another feature. Prepare for the demo to go sideways. If an attendee derails with questions early, welcome it — engagement is better than a polished monologue. Adjust the flow in real time. The demo is not the close. The demo is the vehicle to earn the next step. Always leave with a specific, calendar-confirmed action. If you can get the prospect's own data or documents into the demo environment, do it. Nothing converts like seeing your own world inside the product.

You are an enterprise account research analyst supporting a strategic seller. Task: Build a pain hypothesis generator for the target account. Inputs: - Company: [COMPANY] - Industry: [INDUSTRY] - Geography: [REGION] - Target solution area: [SOLUTION AREA] - Relevant context: [NOTES, NEWS, KNOWN INITIATIVES, COMPETITORS] Requirements: - Focus on what matters to a seller, not a generic company summary - Separate facts, likely inferences, and open questions - Surface business priorities, risk areas, likely stakeholders, and buying triggers - Identify where our offering could align and where resistance may come from - Be skeptical, do not overstate certainty Output: 1. Executive summary 2. Key findings 3. Sales implications 4. Open questions to validate on the next call

Create a champion enablement package for my internal sponsor. Context: ● Champion: [NAME, TITLE] ● Economic buyer: [NAME, TITLE] ● Other stakeholders: [WHO ELSE NEEDS TO APPROVE] ● Champion's motivation: [WHY THEY WANT THIS] ● What they need to prove: [BUSINESS CASE REQUIREMENTS] ● Objections they'll face: [LIKELY INTERNAL PUSHBACK] Create: 1. One-pager they can share with their boss 2. Email they can forward to stakeholders 3. Talk track for their internal meeting 4. Responses to likely internal objections 5. ROI calculation framework 6. Competitive comparison talking points Make it easy for them to copy-paste and look good internally.

Generate discovery questions using Chris Voss negotiation psychology. Context: - Prospect: [NAME, TITLE at COMPANY] - Industry: [THEIR INDUSTRY] - What I'm selling: [YOUR PRODUCT] - Known situation: [WHAT YOU KNOW] Chris Voss Discovery Techniques: 1. LABELS (statements that identify emotions): - "It seems like..." - "It sounds like..." - "It looks like..." 2. MIRRORS (repeat last 1-3 words as a question): - Them: "We've been struggling with this for months." - You: "For months?" 3. CALIBRATED QUESTIONS (How/What questions): - "How does this affect your team?" - "What happens if this doesn't get solved?" - "How would you like me to proceed?" 4. NO-ORIENTED QUESTIONS: - "Would it be ridiculous to think that..." - "Is it a bad idea to..." - "Have you given up on..." Generate a discovery call script with: - 3 opening labels - 5 calibrated questions (How/What) - 2 no-oriented questions - Instructions on when to mirror The goal is to make them feel deeply understood while uncovering their real pain.

Act as a top enterprise SaaS AE. Create a 25-question discovery call framework for selling [product] to [ICP]. Organize into 5 phases: (1) Situation, (2) Problem depth, (3) Impact/cost of the problem, (4) Decision process, (5) Timeline & urgency. Each question should be open-ended and designed to uncover buying signals. Include one 'trap door' question per phase that reveals if they're a real buyer.

Act as a world-class sales strategist who leads with the MEDDIC methodology. I want you to read this call transcript carefully: [PASTE TRANSCRIPT] I work at [COMPANY]. This is what I sell: [SOLUTION]. Please: 1. Rate me on a scale of 1 to 10 for each MEDDIC element and explain why 2. Identify what I missed or should have asked 3. Give me three specific recommendations for what I need to do next to advance this deal Format: MEDDIC scorecard + action items

After a group demo with [FILL IN company], write separate follow-up emails for: (1) the economic buyer ([FILL IN title]) — focus on business outcomes and ROI, (2) the technical evaluator ([FILL IN title]) — focus on integration and implementation, (3) the end user ([FILL IN title]) — focus on ease of use and daily workflow improvement.