> For the complete documentation index, see [llms.txt](https://www.mlcompendium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mlcompendium.com/ai-product/business.md).
# Business
Data scientists still need go-to-market vocabulary before they can talk to the people who sell what they build. The page points at one field guide as that introduction and then shows its index and two of its sections.
The same notes are in [Growth](/ai-product/growth.md).
[Unusual Ventures](https://www.field-guide.unusual.vc/) - "A tactical field guide provides you with all of the best practices and tools founders need to solve the most challenging early-stage problems". However, I see this as a guide for a data scientist who wants to understand what go-to-market, product-led growth, and other topics in that space are, and who needs a good introduction.
The index below shows how the guide is laid out, and the two figures after it are the product field guide and the modern GTM field guide, the two parts a data scientist will read first.
Unusual Ventures Field guide Index
Unusual Ventures Product Field guide
Unusual Ventures Modern GTM Field guide
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://www.mlcompendium.com/ai-product/business.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
