Before the pre-mortem fires, arm the AI with real-world context. This step transforms generic output into deal-specific intelligence.
How this step works
This prompt instructs the AI to search the web for the client company's recent context — earnings, press releases, competitive moves, regulatory shifts, executive changes. It also has an optional section where you can paste internal documents (emails, Teams threads, transcripts, CRM notes) to give the AI insider signal. The more context you provide, the sharper every subsequent step becomes.
Internal Documents Optional — High Value
If you have access to any of the following, paste them into the prompt where indicated. These dramatically improve the quality of the pre-mortem because they reveal emotional signals — who's enthusiastic, who's deflecting, who's gone silent.
Email threads with/about the client (especially internal forwards)
Teams/Slack messages about this deal
Meeting transcripts or call notes
CRM activity logs or deal notes
SharePoint/internal docs about this client or their industry
Previous proposals or RFP responses
You are an expert B2B enterprise sales strategist preparing for a complex, multi-stakeholder deal. Before we begin the analysis, I need you to build a comprehensive intelligence picture of this deal.
DEAL CONTEXT:
- Client Company: [COMPANY NAME — e.g., Saudi National Bank (SNB)]
- Product/Solution We're Selling: [WHAT YOU ARE SELLING — e.g., Visa Direct cross-border API integration for merchant payouts]
- Champion: [CHAMPION'S ROLE + NAME + INTERNAL STANDING — e.g., Head of Digital Payments — Amina. Strong internal reputation, reports to CEO.]
- Buying Committee:
[PERSON 1 — ROLE + BEHAVIORAL SIGNAL — e.g., CFO — Khalid. Has blocked two tech investments this year citing 'unproven ROI.'][PERSON 2 — ROLE + BEHAVIORAL SIGNAL — e.g., CTO — Dr. Faisal. Protective of core banking systems, prefers in-house builds.][PERSON 3 — ROLE + BEHAVIORAL SIGNAL — e.g., Head of Cards — Sara. Aggressive growth targets, frustrated with slow innovation.][PERSON 4 (optional) — ROLE + BEHAVIORAL SIGNAL]
- Current Status Quo: [WHAT SYSTEM/PROCESS THEY USE TODAY + WHY IT "WORKS" — e.g., They use SWIFT for cross-border settlements. Slow (T+2) and expensive (1.5% fees), but familiar and compliant.]
- What the Champion Has Already Tried: [CONVERSATIONS THAT HAVE HAPPENED + RESPONSES — e.g., Presented an ROI deck to the CFO in March. Got a 'let's revisit in Q3.']
- Market/Region: [YOUR MARKET — e.g., Saudi Arabia / Gulf region]═══ EXTERNAL RESEARCH (MANDATORY) ═══
Search the web and provide a brief intelligence briefing on:
1. COMPANY CONTEXT (2-3 sentences each):
- Recent earnings, annual reports, or investor presentations — what are their stated strategic priorities?
- Recent press releases or news — any major initiatives, partnerships, or leadership changes?
- Their competitive position — who are their main rivals and what are those rivals doing in this space?
2. MARKET DYNAMICS (2-3 sentences each):
- Regulatory environment — any upcoming mandates, compliance deadlines, or policy shifts relevant to this deal?
- Industry trends — what structural changes are reshaping this sector?
- Customer behavior shifts — how are end-customers' expectations changing?
3. STAKEHOLDER INTELLIGENCE (1-2 sentences each):
- For each named committee member, search for any public information: LinkedIn profiles, conference talks, published articles, quoted statements. What do they publicly care about?
- Any recent executive hires/departures that signal strategic direction changes?
4. COMPETITIVE INTELLIGENCE (2-3 sentences):
- Has a competitor already approached this client with a similar solution?
- What alternatives exist in this market? What's the "do nothing" cost trajectory?
═══ INTERNAL DOCUMENTS (OPTIONAL — PASTE BELOW IF AVAILABLE) ═══[PASTE ANY INTERNAL DOCUMENTS HERE — emails, Teams threads, meeting transcripts, CRM notes, call summaries, previous proposals. If none available, write "None available." The AI will use these to detect emotional signals, political dynamics, and hidden objections that aren't visible from external research alone.]═══ OUTPUT FORMAT ═══
Produce a structured "Intelligence Briefing" with clear headers for each section above. For each finding, note your confidence level (High/Medium/Low) based on source quality. Flag any GAPS where you couldn't find information — these gaps themselves are useful signals about what we don't know.
End with a section called "THREE THINGS YOU MIGHT NOT HAVE CONSIDERED" — based on your research, identify three factors that could influence this deal that the seller likely hasn't thought about:
- A competing internal initiative that might be consuming the same budget
- A stakeholder who isn't on the named committee but has informal influence
- A timing factor (fiscal year end, board meeting, regulatory deadline) that creates hidden urgency or hidden delay
What to do with the output: Save the entire Intelligence Briefing. It becomes the foundation for every subsequent step. The AI will reference this context throughout the remaining prompts. If any findings surprise you or feel wrong, correct them before moving on — the quality of everything downstream depends on this intelligence being accurate.
2
The Pre-Mortem
Fast-forward 6 months. The deal died — not to a competitor, but to "no decision." What happened?
Before you paste this prompt
Continue in the same conversation thread (the AI already has the Intelligence Briefing from Step 1). Paste this prompt directly. The pre-mortem now includes a mandatory Assumption Audit that forces the AI to surface your blind spots.
Now fast-forward 6 months. The deal has COMPLETELY DIED. It was NOT lost to a competitor — it was lost to "no decision." The buying committee simply never aligned, and the initiative quietly disappeared from the priority list.
Using the Intelligence Briefing you just produced, generate:
1. THE AUTOPSY (200 words max)
Write a single narrative paragraph describing exactly how this deal died. Rules:
- Do NOT blame the product or the seller's pitch quality.
- Blame conflicting internal priorities, political dynamics, and decision-making inertia.
- Be brutally specific — use the actual roles, context, and intelligence gathered.
- Write in present tense as if narrating the autopsy.
- Factor in cultural decision-making norms for the market/region.
- Reference at least ONE finding from the external research that contributed to the death.
Identify:
- The single most likely "Invisible Veto" — which specific persona killed this deal, and in what forum? (An email thread? A budget review? A risk committee? A hallway conversation?)
- Which of the Three Fears of Indecision drove the veto:
• Fear of Wrong Choice ("What if there's a better option?")
• Fear of Lack of Homework ("Have we done enough due diligence?")
• Fear of False Promises ("Will this actually deliver what they claim?")
- The exact moment the champion lost control of the narrative.
2. THE ASSUMPTION AUDIT (Mandatory)
Now challenge the seller's thinking. Identify THREE blind spots they likely haven't considered:
BLIND SPOT 1 — THE MISSING STAKEHOLDER:
Who else has informal influence over this decision that ISN'T on the named committee? (Based on your research: board members, regional heads, external advisors, procurement, legal, the CEO's trusted lieutenant.) Why do they matter?
BLIND SPOT 2 — THE COMPETING PRIORITY:
What other initiative inside this company is competing for the same budget, executive attention, or implementation bandwidth? (Based on your research into their stated strategic priorities.) How does this create a "silent no"?
BLIND SPOT 3 — THE HIDDEN TIMELINE:
What timing factor (fiscal year, board cycle, regulatory deadline, competitor move, leadership transition) is either creating hidden urgency the seller hasn't leveraged, OR creating hidden delay they haven't anticipated?
FORMAT: Write the Autopsy as a narrative paragraph. Write the Assumption Audit as three clearly labeled sections with specific, actionable findings — not vague possibilities.
What to do with the output: Read the Assumption Audit carefully. Does it surface anything you hadn't considered? If so, you may want to do additional discovery before proceeding. Save the full output — the Red Team Simulation in Step 3 will use both the Autopsy and the blind spots.
3
The Red Team Simulation
Simulate the internal alignment meeting you'll never be invited to. Watch your deal die in real time.
Before you paste this prompt
Continue in the same conversation thread. The AI has the Intelligence Briefing, the Autopsy, and the Assumption Audit. This simulation now includes a Pattern Interrupt — at least one persona will raise a concern from an unexpected angle based on the external research.
Now simulate the internal alignment meeting that I will NEVER be invited to. This is the meeting where the deal actually lives or dies.
Use everything you know from the Intelligence Briefing, the Autopsy, and the Assumption Audit to make this simulation brutally realistic.
RULES FOR THE SIMULATION:
1. The Champion opens by trying to push the deal forward. They use the language they currently have — which is INSUFFICIENT. They pitch features and ROI, not a shared mission. They fail to address the Shared Threat.
2. Each other persona must express one of the Three Fears of Indecision, grounded in their SPECIFIC KPIs and mandate:
- Fear of Wrong Choice: "What if we pick the wrong vendor/approach?"
- Fear of Lack of Homework: "Have we evaluated enough alternatives?"
- Fear of False Promises: "Their case studies are from different markets/contexts."
3. Personas must argue WITH EACH OTHER — not just with the champion. Their KPIs must visibly conflict:
- Budget constraints vs. proper implementation costs
- Speed-to-market vs. risk management
- Revenue opportunity vs. technical debt
- Short-term metrics vs. long-term positioning
4. THE PATTERN INTERRUPT: At least ONE persona must raise a concern from a completely UNEXPECTED angle — something that came from the external research or the Assumption Audit that the champion clearly hasn't prepared for. This could be:
- A competing internal initiative they didn't know about
- A regulatory change that shifts the risk calculus
- A competitor move that changes the urgency equation
- A board-level directive that overrides local decision-making
5. Include at least ONE "silent skeptic" moment — a persona who says nothing but whose body language (described in [stage directions]) signals disagreement or disengagement.
6. The debate must end in a realistic STALL — not a "no," but a deflection: "Let's revisit next quarter," "Let's get more data," "Let's form a working group," or the most dangerous: enthusiastic agreement with no action items.
7. Each persona must speak in a voice consistent with their role — the CFO speaks in numbers, the CTO in systems language, the business owner in market terms.
8. Adjust communication styles for the market/region's cultural norms (e.g., indirect disagreement in Gulf cultures, relationship-first framing in African markets, consensus-seeking in Asian contexts, direct challenge in Western European contexts).
FORMAT:
Write this as a meeting transcript with character names in CAPS and [stage directions in brackets]. Approximately 500 words. Make it feel uncomfortably realistic — like reading a transcript of a meeting you've always suspected happens but could never witness.
After the transcript, add a brief "DIRECTOR'S COMMENTARY" (3-4 sentences) explaining the key dynamics: What was the real conversation happening beneath the surface? What was never said out loud but determined the outcome?
What to do with the output: Read the simulation carefully. Does it feel realistic? Do the dynamics match what you suspect is happening? If the Pattern Interrupt surprised you — good. That's a blind spot you need to address. If something feels off, tell the AI to adjust. Then save the output — you'll use it in Step 4.
4
The Diagnosis
Identify the dominant fear, map each blocker, and select the urgency pivot frame that will unite this committee.
Before you paste this prompt
Continue in the same conversation thread. The AI has all context from Steps 1-3. Paste this prompt directly.
Now analyze the simulation and the full intelligence picture to produce a structured diagnosis.
PRODUCE THE FOLLOWING:
1. INDECISION DIAGNOSIS
Which of the Three Fears is DOMINANT for this committee as a whole?
- Fear of Wrong Choice
- Fear of Lack of Homework
- Fear of False Promises
Explain in 2-3 sentences why this fear dominates, citing specific moments from the simulation AND specific findings from the intelligence research.
2. THE BLOCKER MAP
For EACH persona on the committee, produce a table:
| Persona | Their Specific Blocker | What "Safe" Looks Like to Them | The Research Signal That Confirms This |
Be specific — "budget concerns" is not acceptable. "Unwilling to approve >$200K without a board-level mandate because they were burned by the [X] project in 2023" is.
The "Research Signal" column must reference something from the Intelligence Briefing or internal documents that confirms this blocker is real, not assumed.
3. URGENCY FRAME RECOMMENDATION
From these six Pivot Frames, select the ONE most likely to unite this specific committee:
- FOMO / Competitive Threat (Loss Frame): "A competitor already moved"
- Window of Opportunity (Gain Frame): "A structural opening exists NOW"
- Structural Inevitability (Neutral Frame): "This is happening with or without you"
- Aspiration Gap (Hope Frame): "You committed to X. Your current path can't get you there."
- Accumulating Cost of Delay (Quantified Frame): "Every month costs $X"
- Customer Expectation Drift (Empathy Frame): "Your customers compare you to the best experience anywhere"
Explain in 3-4 sentences WHY this frame works for this specific committee. You MUST:
- Reference the dominant fear and how this frame addresses it
- Reference a specific finding from the external research that makes this frame credible (not just a generic claim)
- Explain how this frame balances URGENCY with HOPE — it must create discomfort AND paint an aspirational future
- Explain why this frame blames the SITUATION, never the people
4. THE COST OF INACTION STATEMENT
Draft the exact sentence the Champion should use to create urgency. One sentence, maximum two. It must:
- Use the selected Pivot Frame
- Be specific to this deal (reference real data from the intelligence research)
- Create situational pressure without blame
- Include an element of hope or aspiration
- Be something a human would actually say out loud in a meeting (not corporate-speak)
5. ALTERNATIVE FRAME (Insurance)
Select a SECOND Pivot Frame as a backup — in case the primary frame doesn't land. Explain in 1-2 sentences when the Champion should switch to this alternative (what signal would indicate the primary frame isn't working).
FORMAT: Use the headers and table format specified above. Be concise and actionable.
Checkpoint: Review the Diagnosis carefully. Does the Urgency Frame feel right? Does the Blocker Map match your instincts? Does the research evidence feel credible? If anything feels off, tell the AI to adjust before moving to Step 5. Everything downstream builds on this foundation.
5
The Shared Why Construction
Transform fragile individual "yeses" into a resilient Collective Yes — one mission the entire committee owns.
Before you paste this prompt
Continue in the same conversation thread. If you made any adjustments to the Diagnosis in Step 4, note them in the [USER ADJUSTMENTS] placeholder. Otherwise, write "None."
Now generate the Shared Why package — the core alignment language that unites this buying committee under a single, unassailable mission.
USER ADJUSTMENTS TO THE DIAGNOSIS (if any):
[ANY CORRECTIONS OR ADJUSTMENTS YOU WANT TO MAKE — or write "None" if the Diagnosis feels accurate]
GENERATE THE FOLLOWING:
1. THE SHARED THREAT
One sentence that unites the disparate fears of the committee. Rules:
- It must name an EXTERNAL enemy or environmental force — never an internal failure.
- It must be something ALL personas on the committee fear, not just one.
- It must be specific to this client — not a generic industry trend.
- It must be grounded in evidence from the Intelligence Briefing (cite the specific finding).
2. THE SHARED WHY
A 2-sentence mission statement. Format:
"We are executing [specific action] to protect [specific position] against [shared threat]. This secures [shared aspiration]."
Rules:
- Sentence 1 = the defensive move (protecting against threat)
- Sentence 2 = the aspirational outcome (what success looks like)
- Must be specific enough to fail the Name-Swap Test (see below)
3. THE SHARED LEGACY
One sentence of "collective credit" language. Format:
"When this succeeds, [this team/committee] will be known as the group that [shared achievement]."
Rules:
- Must distribute status ACROSS the committee — no single hero
- Must be something each persona would be proud to claim on their CV
- Must connect to the company's publicly stated strategic ambitions (from the research)
───────────────────────────────────────────────────────
MANDATORY QUALITY GATE — SELF-AUDIT
───────────────────────────────────────────────────────
After generating the above, you MUST run these three tests against your own output. Show your work.
TEST 1: THE NAME-SWAP TEST (Specificity)
- Take the Shared Why statement. Replace the client's context with a generic competitor's.
- Does it still make sense? If YES → FAIL. Rewrite until it passes.
- Show: "[Original] → [Swapped version] → PASS/FAIL"
TEST 2: THE VETO TEST (Comprehensiveness)
- For EACH persona on the committee, ask: "Can this persona see their specific fear mitigated in the Shared Why?"
- If ANY persona cannot → FAIL. Rewrite to address their concern.
- Show: "[Persona]: [Their fear from Blocker Map] → [How the Shared Why addresses it] → PASS/FAIL"
TEST 3: THE HEADLINE TEST (Resilience)
- Imagine a major external shock hits tomorrow (competitor breach, regulatory change, budget freeze, market crash).
- Does the Shared Why still hold true? Would the committee still rally behind it?
- If NO → FAIL. Rewrite to be more resilient.
- Show: "[Shock scenario] → [Does Shared Why survive?] → PASS/FAIL"
If any test fails, REVISE the Shared Why and re-run all three tests until all pass. Show the revision history.
TRANSLATION LAYER:
After all tests pass, rewrite the Shared Why one more time in the language the Champion would ACTUALLY use in a hallway conversation — not boardroom polish, but authentic, human language that sounds like them.
FORMAT: Use clear headers for each section. Show the Quality Gate results transparently.
Why the Quality Gates matter: Without them, the AI produces generic alignment language that sounds good but doesn't survive contact with a real committee. The Name-Swap Test catches vagueness. The Veto Test catches blind spots. The Headline Test catches fragility. If the AI can't pass all three, the Shared Why isn't strong enough.
6
The SCARF Alignment Map
Translate the Shared Why into role-specific language that respects each stakeholder's neurological needs.
Before you paste this prompt
Continue in the same thread. The AI has all the context it needs from Steps 1-5.
Now translate the Shared Why into a per-persona alignment map using David Rock's SCARF model (Status, Certainty, Autonomy, Relatedness, Fairness).
FOR EACH PERSONA ON THE BUYING COMMITTEE, generate this table:
| SCARF Domain | What the Champion Must Do | Exact Language to Use | Research Basis |
|---|---|---|---|
| Status | How does this project elevate THIS persona's standing? (Not just the champion's.) | "This positions you as..." | [What from the research supports this framing] |
| Certainty | What is the concrete, sensory-rich future state this persona can visualize? Week 1, Week 3, Week 8 — NOT vague "seamless ecosystem" language. | "By Week 3, you'll see..." | [What evidence makes this timeline credible] |
| Autonomy | What part of the execution does this persona OWN? Lock the Why; free the How. | "I'd love you to own the..." | [Why this ownership aligns with their known priorities] |
| Relatedness | How does the Shared Threat connect to THIS persona's world specifically? | "You and [other persona] both face..." | [What shared risk connects them] |
| Fairness | How is risk/burden/credit distributed equitably FOR this persona? | "We'll ensure that..." | [What imbalance would trigger their veto] |
RULES:
- "Certainty" must include SPECIFIC timelines and sensory details — not abstractions.
- "Autonomy" must genuinely give ownership, not just lip service. The champion cannot dictate the How.
- "Fairness" must explicitly address the risk/reward imbalance that would trigger a shadow veto.
- "Status" must use "shared legacy" language — never "you'll be the hero" (which threatens others).
- "Research Basis" must cite a specific finding from the Intelligence Briefing that makes this framing credible.
- Every cell must contain language the Champion can literally say out loud.
THEN GENERATE:
THE EMPATHY BRIDGE SCRIPT
For the MOST SKEPTICAL persona (from the Blocker Map), generate a 3-step script:
Step 1 — Acknowledge: Validate their specific constraint without arguing.
Example: "I hear that — [specific concern]. That's a real constraint, especially given [reference to their context from research]."
Step 2 — Reframe: Shift from feature/product to business impact. Connect their objection back to the Shared Threat.
Example: "The reason this matters is [connection to shared threat], which affects [their specific KPI]. [Reference to external evidence that confirms this risk]."
Step 3 — Path Forward: Propose a specific, contained, de-risked next step.
Example: "What if we [specific small action] so you can [see/validate/confirm] before any commitment? That way [their specific 'safe' outcome] is protected."
THE DE-RISKING OFFER
Generate a SPECIFIC recommendation that takes risk off the table for the most fearful persona. Rules:
- Must be CONCRETE: "5% of lowest-risk portfolio for 60 days" — not "a phased approach"
- Must specify: What exactly is being piloted, for how long, with what success criteria, and what happens if it fails (the exit ramp)
- Must include a "safety net" clause that makes saying yes feel reversible
- Must address the dominant Fear of Indecision identified in Step 4
- Must reference what competitors or peers have done (from the research) to normalize the risk level
FORMAT: Use clear headers and the table format specified. Every piece of language must be copy-paste ready for the Champion to use verbatim.
What to do with the output: This is the tactical playbook. The Champion should review the SCARF table for each persona and rehearse the Empathy Bridge script before their next internal meeting. Save the De-Risking Offer — it goes into the final toolkit.
7
The Champion's Toolkit
Three copy-paste-ready artifacts your champion can use in meetings where you are NOT present.
Before you paste this prompt
Continue in the same thread. This is the final step — it packages everything into deliverables the Champion can use immediately. These artifacts are designed to be used without you in the room.
Now package everything into three copy-paste-ready artifacts my Champion can use in meetings where I am NOT present.
IMPORTANT: These artifacts must be grounded in the intelligence research. Every claim must be defensible. The Champion will be challenged — they need to be able to point to evidence, not just assertions.
GENERATE THREE DELIVERABLES:
───────────────────────────────────────────────────────
DELIVERABLE A: THE INTERNAL ALIGNMENT EMAIL
───────────────────────────────────────────────────────
A draft email from the Champion to the buying committee. Rules:
- Subject line must create curiosity, not sell ("Re: [Shared Threat topic]" — not "Re: Visa proposal")
- Opens with the Shared Threat — NOT the product or vendor name
- Second paragraph uses the Cost of Inaction statement (Urgency Pivot Frame), grounded in specific data from the research
- Third paragraph proposes the De-Risking Offer as the specific next step
- Includes one line of Autonomy language for each persona: "I'd love [Name/Role] to own [specific piece]"
- Closes with the Shared Why as the rallying statement
- Tone: Direct, collegial, slightly urgent — like a trusted peer raising a flag, not a salesperson pushing
- Length: 150-200 words maximum
- Must NOT mention the vendor/seller by name in the first half of the email
- Must include at least ONE specific data point or market fact from the intelligence research
───────────────────────────────────────────────────────
DELIVERABLE B: THE ONE-PAGE BUSINESS CASE
───────────────────────────────────────────────────────
A structured one-pager the Champion can attach to the email or bring to a meeting. Format:
[Title: Action-oriented, references the Shared Threat]
THE CHALLENGE (2 sentences)
- The Shared Threat, stated plainly with supporting evidence
THE COST OF WAITING (2-3 sentences)
- The Urgency Pivot Frame, quantified where possible using real data
- What happens in 6/12 months if nothing changes (cite competitive or market evidence)
THE PROPOSED PATH (3-4 sentences)
- The De-Risking Offer: what, how long, success criteria, exit ramp
- Why this is low-risk and reversible
- Reference to peer/competitor precedent if available
THE MISSION (2 sentences)
- The Shared Why statement (hallway version)
- The Shared Legacy statement
WHO OWNS WHAT (table)
| Role | Their Contribution | Their Benefit | Timeline |
- One row per persona, using Autonomy and Fairness language from the SCARF map
- Timeline column adds accountability without pressure
───────────────────────────────────────────────────────
DELIVERABLE C: THE OBJECTION PRE-LOAD
───────────────────────────────────────────────────────
For EACH persona on the committee, generate:
[Persona Role — Name]
> They will say: "[Predicted objection based on their blocker from the simulation + research signals]"
> Champion responds: "[Empathy Bridge response: Acknowledge → Reframe → Path Forward]"
> Evidence to cite: "[Specific data point, market fact, or peer example the Champion can reference to make their response credible]"
> Why this works: [1 sentence explaining the principle — so the champion learns, not just copies]
> If it doesn't land: "[Fallback response using the Alternative Urgency Frame from Step 4]"
Rules:
- Objections must be SPECIFIC to this deal — not generic ("too expensive")
- Responses must use the Empathy Bridge structure (Acknowledge → Reframe → Path Forward)
- Each response must end with a concrete, small next step — not a philosophical argument
- Include the "silent skeptic" persona if one was identified in the simulation
- The "Evidence to cite" field is critical — it gives the Champion ammunition, not just scripts
- The "If it doesn't land" fallback ensures the Champion isn't left speechless if Plan A fails
FORMAT: Use the exact headers and formatting specified above. Everything must be immediately usable — no placeholders, no "[insert here]" markers. Write as if the Champion is going to copy-paste this into their preparation notes tonight.
You're done. You now have: (A) an email the Champion can send tonight, (B) a one-pager they can attach or print, and (C) a cheat sheet for handling every objection in the room — complete with evidence and fallback responses. Coach your Champion on the Empathy Bridge structure so they can adapt in real time, and remind them: the goal isn't to "win" the meeting — it's to make saying yes feel safer than saying nothing.
Fill in your deal context, then generate all prompts at once
Deal Context
Fill this in once. The tool will inject your details into all 7 prompts — no brackets to fill manually. Nothing leaves your browser.
The AI will search for recent news, earnings, and competitive intelligence about this company
Be specific: product name, use case, integration type
Role + Name (if known) + any context on their internal standing
List 2-4 roles. For each, add any behavioral signal you've observed (what they've said/done).
What system/process are they using today? Why does it "work" (even if poorly)?
What conversations have happened? What was the response?
Adjusts for cultural decision-making norms
Paste any email threads, Teams messages, meeting transcripts, CRM notes, or internal docs about this deal. These reveal emotional signals and political dynamics invisible from external research.
Your Prompts Are Ready
Paste each prompt into your Copilot in order. Each step builds on the previous output.