> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/getting-started/introduction-to-reo.dev.md).

# Introduction to Reo.Dev

Reo.Dev is a revenue intelligence tool tailored for developer-focused Go-To-Market teams. It identifies intent signals from a variety of **developer-specific sources** including GitHub interactions, package manager installations (e.g., npm, pip, helm), open-source telemetry, cloud sign-ups, and technical documentation and converts it into accounts and developer leads who are active around the customer’s product.

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/1a0785e6-9de1-4308-95d5-e3df92a003df/54617afc-e46d-4f70-9166-7baa24dc66ae/images/da86ab58-40d3-41ae-97dd-e3dc19633565.png)

### How can you use Reo.Dev's intent data?

1. **Deanonymise your full pipeline**: Many developers who interact with your product remain invisible to traditional sales tracking methods. Reo.Dev helps you:
   * Reveal the **80% of developers** who engage with your documentation or product without signing up.
   * Surface **anonymous sign-ups** (e.g., Gmail or GitHub IDs) to gain more clarity on your pipeline.
2. **Generate More Pipeline**

   Reo.Dev utilizes **third-party intent signals** from platforms like:

   * **GitHub** (including competitor and complementary project engagement)
   * **LinkedIn**
   * **StackOverflow**
   * **Reddit** (via keyword monitoring)

   This allows you to identify potential leads early in their journey.
3. **Prioritize Accounts by Dev Funnel Stage:** Reo.Dev identifies where accounts are in the Dev Funnel by analyzing developer activity patterns, enabling you to focus on high-intent, high-value prospects for better conversion rates.
4. **Build Target Lists**

   Reo.Dev enables Go-To-Market teams to build more precise target lists at both the company and individual levels:

   * **Company-level targeting**: Identify companies based on their tech stack, size, developer team composition, and more.
   * **Person-level targeting**: Tap into Reo.Dev’s vast **database of 25 million developers** with 50,000 different skill sets, allowing you to pinpoint high-potential leads.
5. **Increase Sales Outreach Effectiveness**

   By tracking the **developer’s journey**, Reo.Dev enables better qualification and targeted outreach. Key benefits include:

   * **Improved account qualification** for outreach
   * **Finding key buyers** among developer leads
   * Highlighting **high-value activities** performed by an account, allowing SDR teams and AEs to personalize their outreach for maximum impact.


---

# 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.reo.dev/getting-started/introduction-to-reo.dev.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.