> For the complete documentation index, see [llms.txt](https://docs-vnext.kiflo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-vnext.kiflo.com/manage-partners/recruit-partners/partner-prospection.md).

# Partner Prospection

## Overview

You can manage partner prospection within Kiflo to recruit new potential partners and grow your partner ecosystem. The prospection pipeline aims to structure your prospection process to ensure you don’t miss necessary steps and close the best partners. Search for top partners on LinkedIn, Google, your personal network, and more, add them to the prospection pipeline, and follow the steps you’ve defined to recruit them successfully!

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-5d1085d471aa7a6ee2d0828d0e1a3ef2af1c7cb4%2F648986181211660f0912da31.png?alt=media)

## How to use the prospection pipeline?

The prospection pipeline can easily be customized based on your processes.

For instance, if you are searching for new partners on LinkedIn, you could have a prospection pipeline with the following stages:

1. New: you can use this stage to add all potential partners you want to work with
2. Connecting: when you’re trying to contact potential partners
3. Connected: this is when potential partners have answered your email or LinkedIn message.
4. Good fit: this is after you have had a discovery call and determined that a partnership might be a good fit.
5. Won: when you and the partner think a partnership is possible and want to make it real.
6. Not qualified: when the partnership is not feasible because it wasn’t a good fit.

{% hint style="info" %}
[What’s the difference between the prospection and the onboarding pipeline?](/manage-partners/recruit-partners/difference-between-prospection-and-onboarding.md)
{% endhint %}


---

# 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-vnext.kiflo.com/manage-partners/recruit-partners/partner-prospection.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.