> 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/master-goals.md).

# Master goals (the 6)

The six master goals map to the ways B2B teams grow. Pick one primary and up to two secondary; the system tailors its plays to each.

* **Pipeline Growth** — more qualified pipeline via outbound, inbound, and partner motions.
* **Product-Led Growth** — self-serve adoption, activation, and in-product conversion.
* **Retention & Expansion** — reduce churn, lift NRR, and drive upsell in existing accounts.
* **Partner & Ecosystem** — channel and tech partnerships for scalable distribution.
* **Brand & Community** — category authority through thought leadership and community.
* **GTM Efficiency** — optimize CAC, sales velocity, and conversion across the funnel.

Under each, you set time-bound [Targets](/using-audience-loop/overview/master-goals-and-targets/targets.md) to aim at.


---

# 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/master-goals.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.