> For the complete documentation index, see [llms.txt](https://docs.aloop.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aloop.icustomer.ai/using-audience-loop/overview/master-goals-and-targets.md).

# Master goals & targets

Everything the system does points at goals you choose.

**Master goals** are your standing focus. Pick one primary and up to two secondary from the six:

* Pipeline Growth
* Product-Led Growth
* Retention & Expansion
* Partner & Ecosystem
* Brand & Community
* GTM Efficiency

The system tailors its plays to the goals you pick — see [Master goals (the 6)](/using-audience-loop/overview/master-goals-and-targets/master-goals.md) for what each one drives.

**Targets** are specific, time-bound objectives under a master goal — like "200 demos in 60 days." You set them in [Chat](/using-audience-loop/meet-chat.md), or the Harness proposes them; then the always-on loop paces toward the deadline and [Measurement](/using-audience-loop/overview-1/pace-to-target.md) tracks progress. See [Targets](/using-audience-loop/overview/master-goals-and-targets/targets.md).


---

# 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://docs.aloop.icustomer.ai/using-audience-loop/overview/master-goals-and-targets.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.