> ## Documentation Index
> Fetch the complete documentation index at: https://docs.endgame.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Ask Better Questions

> Master advanced prompting techniques to unlock Endgame's full potential

## Introduction

Endgame isn't just another search tool. It's your strategic thinking partner designed to help you build intuition and make better decisions about your accounts. The key to unlocking Endgame's full potential lies in how you communicate with it.

Think of Endgame like your most experienced sales colleague: the more context you provide and the more thoughtfully you frame your questions, the more valuable insights you'll receive.

## Core principles

<CardGroup cols={2}>
  <Card title="AI helps you think, not just do" icon="brain">
    The best teams use Endgame to think through their account strategy and what to do next. Don't just ask for information. Ask for analysis, recommendations, and strategic insights.
  </Card>

  <Card title="You'll get what you ask for" icon="lightbulb">
    The more context-rich your question and the clearer you are about the outcome you want, the more useful Endgame will be. Specificity drives quality.
  </Card>

  <Card title="Conversation, not just search" icon="messages-square">
    Treat Endgame like a teammate: probe, clarify, and iterate within one thread so insights compound. Your best results come from building on previous exchanges.
  </Card>

  <Card title="Human judgment matters" icon="search-check">
    Endgame provides the information and analysis you need, but you should always review, test for accuracy, and frame your own narrative.
  </Card>
</CardGroup>

## Prompting framework

Different situations call for different prompting strategies. Use this framework to choose the right approach:

<Frame caption="Choose your prompting strategy based on clarity of exploration and desired outcomes">
  <img src="https://mintcdn.com/endgame-e965a12c/daZRHwDo5t3xCpPA/images/endgame-prompting.png?fit=max&auto=format&n=daZRHwDo5t3xCpPA&q=85&s=ec592b28c5938d208774fb52f59d5e3d" alt="Endgame Prompting 2x2 Framework" className="rounded-lg" width="1536" height="1024" data-path="images/endgame-prompting.png" />
</Frame>

### Flexible exploration for discovery

This approach is useful early in your account research, when you're not sure what you're looking for, or when you want to uncover unexpected opportunities.

<Card>
  **Approach:** Start broad, then narrow down based on what you discover.

  **Example Pattern:**

  * **Initial**: "What expansion opportunities exist at \[Company]?"
  * **Clarify**: "Tell me more about the digital transformation angle you mentioned"
  * **Refine**: "How urgent is this digital transformation for them specifically?"
</Card>

### Structured exploration for research

This approach is useful when you want to systematically explore multiple angles or need comprehensive coverage of a topic.

<Card>
  **Approach:** Use frameworks and structured questions to ensure thorough analysis.

  **Example Pattern:**

  * **Initial**: "Analyze \[Company] across financial health, growth initiatives, and technology investments"
  * **Dive deeper**: "Focus on their technology investments—what patterns do you see?"
  * **Get tactical**: "Based on those patterns, what's our best entry point?"
</Card>

### Flexible outcomes for strategizing

This approach is useful when you have a specific goal but are open to various approaches to achieve it.

<Card>
  **Approach:** State your objective clearly, then let Endgame suggest multiple paths.

  **Example pattern:**

  * **Initial**: "I need to get a meeting with their CTO. What approaches could work?"
  * **Choose direction**: "I like the industry trends approach. What specific trends should I focus on?"
  * **Get tactical**: "Draft a LinkedIn message using that angle"
</Card>

### Structured outcomes for execution

This approach is useful when you know exactly what you need and want a specific deliverable.

<Card>
  **Approach:** Use the Intent → Context → Ask structure for precision.

  **Example of the framework:**

  * **Intent**: "I want to help my champion convince their CTO to pilot us"
  * **Context**: "I know we've helped our champion build a tight ROI case, but we need the CTO to get excited by tying to near-term business priorities"
  * **Ask**: "Can you write a 1-page business case that combines priorities, quotes, and ROI that my champion could email to her CTO?"
</Card>

## Advanced techniques

<Steps>
  <Step title="Building context over time">
    Each conversation builds context. Reference previous insights: "Based on what we discussed about their Q3 priorities..." or "How does this new information change our approach from earlier?"
  </Step>

  <Step title="Using constraints creatively">
    "I have 5 minutes with their CEO. What's the one thing I should say?" or "Explain this technical concept to a non-technical executive"
  </Step>

  <Step title="Iterative refinement">
    Don't settle for the first response. Push for better with: "Make it more specific to their industry" or "Add more urgency to the messaging"
  </Step>

  <Step title="Ask Endgame for help">
    Tell Endgame what you're trying to achieve and give it a draft prompt, then ask Endgame what it'd recommend the prompt should be
  </Step>

  <Step title="Reverse prompting">
    Ask Endgame to tell you what it recommends you should be focusing on to inform what you should ask. "How can I best utilize you to be more effective in my role?"
  </Step>
</Steps>

## Common pitfalls to avoid

<Tabs>
  <Tab title="Being too vague">
    <Danger>
      **Bad:** "Tell me about this company"
    </Danger>

    <Check>
      **Better:** "What are the top 3 business challenges \[Company] is facing that our solution could help address?"
    </Check>
  </Tab>

  <Tab title="Not enough context">
    <Danger>
      **Bad:** "Write me an email"
    </Danger>

    <Check>
      **Better:** "Write a follow-up email to the CTO I met last week who expressed interest in our security features but was concerned about implementation time"
    </Check>
  </Tab>

  <Tab title="Accepting first responses">
    <Danger>
      **Bad:** Taking the first answer and moving on
    </Danger>

    <Check>
      **Better:** "This is helpful. Can you make the business case more specific to their retail operations?"
    </Check>
  </Tab>

  <Tab title="Forgetting the human element">
    <Danger>
      **Bad:** Using AI output without review
    </Danger>

    <Check>
      **Better:** Reviewing, fact-checking, and adding your own insights before using
    </Check>
  </Tab>
</Tabs>

## Conclusion

Successful use of Endgame comes from strategic conversations. Stress-test your thinking, explore new angles, and build conviction in your approach.

<Note>
  **Endgame is designed to help you think better, not just work faster**. Start with these frameworks, experiment, and find your own style. Your goal isn't to become a perfect prompter. It's to become a more strategic thinker who uses AI as a force multiplier for your expertise and judgment.
</Note>