> For the complete documentation index, see [llms.txt](https://huntingalice.gitbook.io/about/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://huntingalice.gitbook.io/about/best-practices-and-playbooks.md).

# Best practices and playbooks

To get the most out of Hunting Alice, you need to think less like a keyword scraper and more like a hunter. The quality of your "Alice" (Ideal Customer Profile) definition directly impacts the quality of the leads our AI finds.

## The Art of "Signal" Engineering

A **Signal** is the specific topic, problem, or question that indicates buying intent. Low-quality signals generate noise; high-quality signals generate revenue.

{% hint style="warning" %}

#### ❌ Bad Signals (Too Broad)

* "Marketing"
* "Software"
* "Need help"

Result: You will be flooded with students, job seekers, and irrelevant discussions.
{% endhint %}

{% hint style="success" %}

#### ✅ Good Signals (Specific Intent)

* "Looking for B2B marketing agency"
* "Best alternatives to Salesforce"
* "How to automate invoice processing"

Result: You find decision-makers actively comparing solutions.
{% endhint %}

## Playbook: The "Problem-First" Approach

Instead of searching for who they *are*, search for what they *suffer from*.

{% stepper %}
{% step %}

### Identify the Pain Point

What keeps your customer up at night?

Example: "Compliance audit deadline"
{% endstep %}

{% step %}

### Identify the Trigger Event

What happens right before they buy?

Example: "Posting a job for 'Head of Compliance', complaining about 'manual spreadsheets'."
{% endstep %}

{% step %}

### Craft the Signal

Examples:

* "Manual SOC2 audit pain"
* "Automating compliance workflows"
* "Hiring VP of Security"
  {% endstep %}
  {% endstepper %}

## Industry-Specific Examples

### For SaaS Sales

* Signal: "Competitor pricing too high"
* Signal: "Migrating away from \[Competitor Name]"
* Signal: "API integration issues with \[Category Software]"

### For Agencies

* Signal: "Recommendations for SEO audit"
* Signal: "App developer needed urgent"
* Signal: "Budget for website redesign"

### For Logistics

* Signal: "Shipping delays China to US"
* Signal: "3PL provider recommendations"
* Signal: "Freight forwarder reliable"

## Optimizing Your Reach

* **Iterate**: If your agent returns too much noise, make your keywords more specific (longer phrases).
* **Monitor**: Check your leads daily. If you see a pattern of irrelevant results (e.g., people selling *to* you instead of buying *from* you), add those keywords to your **Negative Keywords** list in the agent settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://huntingalice.gitbook.io/about/best-practices-and-playbooks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.