> For the complete documentation index, see [llms.txt](https://visi-digital-internasional.gitbook.io/geo-prospector/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://visi-digital-internasional.gitbook.io/geo-prospector/prospecting-workflows/target-and-location.md).

# Choose your target and location

## Target Category

Choose the category that best describes your intended prospects, such as:

* Software Company
* Web Design Company
* IT Consultant
* Marketing Agency
* Construction Company

## Geography

Configure location from broad to specific:

1. Country
2. Region or Province
3. City

More specific geography usually improves relevance but can reduce the number of available records.

## Data Count

Data Count is the desired number of final records. The final count can be lower when:

* The selected market has limited public data
* Duplicate Filter removes many candidates
* Categories overlap
* Records fail final validation
* The process is stopped early


---

# 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://visi-digital-internasional.gitbook.io/geo-prospector/prospecting-workflows/target-and-location.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.