LogoLogo
API DocsChangelogPlaybooksLoginBook a Demo
  • Getting Started
    • Introduction to Reo.Dev
    • For Users
      • Step 1: Find active accounts to target
      • Step 2: Track developer activity on your target accounts
      • Step 3: Identify developers engaging with your product
      • Step 4: Build custom segments that are most likely to convert
      • Step 5: Use filters to spot high-intent leads
    • For Admins
      • Step 1: Identify active accounts to target
      • Step 2: Track developer activity on your target accounts
      • Step 3: Find developers engaging with your product
      • Step 4: Create custom segments that are most likely to convert
      • Step 5: Integrating data sources with Reo.Dev
      • Step 6: Integrate Slack and set up notifications
      • Step 7: Add Customer Fit Criteria
  • Accounts
    • Account Lifecycle Stage
    • Custom CRM Stages
    • Developer Funnel Stages
    • Account Activity Score
    • Tags
    • Customizing Tags
    • Custom Lists
    • Using the Lists API in Reo.Dev
    • Managing CRM Owners in Reo.Dev
    • Follow an Account
    • How to Set Up Notification Alerts for Accounts, Developers & Segments in Reo.Dev
    • Flag incorrect data
  • Developers
    • Interpreting Intel on the Developer view page
    • Developer Activity Score
    • How to Find Inbound Developers in Reo.Dev
  • Segments
    • Creating Segments
    • Basic & Advance Segments
    • Filters 101
    • Segment Actions
    • My Segments
    • Shared Segments
    • Magic Segments
    • Favourite Segment
    • Add notes for better collaboration and context
    • CSV Exports for Segments
    • 10 Advanced Segments to create to spot high-intent opportunities
  • Buyers
    • Find Buyer Contact
    • How to Find, Segment & Engage Decision-Makers in Reo.Dev’s Buyer Section
    • Buyer Persona Configuration in Reo.Dev
  • Enrichment
    • Enrichment
  • Audiences
    • Buyer Audience
  • Integrations
    • Connect GitHub repositories
    • Reo.Dev Zapier Integration Guide
    • Webhooks
    • Developer Docs
      • Docusaurus
      • GitBook
    • CRM
      • HubSpot
      • Salesforce
      • Pipedrive
      • Zoho
      • Freshworks
      • Leadsquared
    • Tracking Beacon
      • Install JavaScript for Documentation
      • Install JavaScript for Product
      • Install JavaScript in Website
      • Install JavaScript in Local Product
      • Track Code Interactions
      • Install JavaScript for Documentation through Google Tag Manager
      • Reo.Dev JavaScript Cookies and Consent Guide
    • Product Usage API
      • Overview
      • How to Configure Product Usage Metrics in Settings
      • Telemetry Data
      • Product API
      • Examples of Product Usage Metrics
      • Data Collected for Product Usage
    • Communities
      • Open Communities
      • Owned Communities
        • Slack
        • LinkedIn Company Page
    • Email
      • Apollo.io
      • How to Integrate and Use Outreach.io with Reo.Dev
      • How to Integrate and Use Salesloft with Reo.Dev
    • Website Tracking
      • RB2B
  • Analytics
    • Impact Dashboard
  • Campaigns
    • Run bulk email campaigns
    • Testing Your Email Integration with Reo.Dev
  • Settings
    • Add Customer Fit Score Criteria
    • Add Firmographic and Technographic Filters
    • Configure Slack & Email Notifications
  • Account and Contact Usage Limit
    • Manage Account and Contact Limit Usage
  • User Management
    • Invite a teammate to Reo.Dev
    • Manage CRM Permissions
    • Roles and Permissions: Admin vs User
    • What Happens to Data When a User Is Deleted in Reo.Dev?
  • FAQs/Troubleshooting
    • How to Exclude Competitors from My Segments in Reo.Dev?
    • How to Sync a Segment to Salesforce/HubSpot?
    • Why Is the 'Sync to CRM' Button Greyed Out?
    • I Synced My Accounts, But They Are Not Showing in My CRM – What to Do?
    • Why Am I Seeing More Accounts in CRM Than I Synced?
    • Why Can't I Find My Account in the Dashboard Search Bar?
    • Resolving Caching Issues in Reo.Dev
    • Understanding Score Discrepancies Between Account and Developer Activity Score
    • Reo.Dev Credit-Based Pricing: FAQs
Powered by GitBook
LogoLogo

Resources

  • Changelog
  • Playbooks
  • DevGTM Conversations
  • Support
  • API Docs

Company

  • Blog
  • Contact Us
  • Book a Demo

Policies

  • Privacy Policy
  • Terms of Service

© 2025 All rights reserved Reo.Dev

On this page
  • Reo.Dev’s Dev Funnel
  • Activities we track
  • How to action on the Dev Funnel intel
  • Editing Dev Funnel Stage in Reo.Dev
  • Filtering accounts based on Dev Funnel Stage
  • Creating Segments based on Dev Funnel

Was this helpful?

  1. Accounts

Developer Funnel Stages

PreviousCustom CRM StagesNextAccount Activity Score

Last updated 12 days ago

Was this helpful?

Reo.Dev’s AI-based Dev Funnel feature visualizes where each account is in their buying journey based on developer activities. It identifies which accounts are ripe for sales opportunities by collecting developer activity signals and feeding them into our proprietary AI model, which predicts the buying stage.

Reo.Dev’s Dev Funnel

To effectively guide sales and marketing strategies, we have categorized the developer account journey into distinct buying stages based on developer engagement:

  • Exploring: At this initial stage, developers have recognized a problem and began their search for solutions. They discover your product and start to assess its relevance and potential utility. This phase is crucial for making a strong first impression and positioning your product as a viable solution.

  • Evaluating: As interest grows, developers enter a more advanced stage where they investigate your product thoroughly. This involves a deep dive into features, performance, and compatibility to ensure it aligns with their specific requirements.

  • Building : Once preliminary assessments are positive, developers move to experiment with the product by building proof of concepts (POCs). This stage is pivotal as they test various use cases to validate the product's effectiveness and adaptability to their environments.

  • Deployed: This stage marks the transition from testing to adoption, where developers have committed to integrating the product into their production systems. They continue to evaluate its performance, particularly focusing on scalability and reliability in a live environment.

Activities we track

We track a variety of activities to gauge developer engagement and interest, categorized under Documentation and GitHub Activities. For Documentation, we monitor the number of package manager installations, CLI commands executed, documentation page visits, and the count of developers involved. On GitHub, we track the cumulative number of issues created and comments made, as well as the count of GitHub stars and forks. These metrics help us understand how developers interact with our product and their level of investment in its capabilities.

Let’s take an example to understand how we determine the stages better.

In this image, Atlasssian is categorized in the 'Evaluating' stage. This classification is based on activities including the execution of CLI commands, documentation reviews, and the involvement of multiple developers. The green dots adjacent to each activity visually represent the proximity of these activities to the predefined threshold range of the Evaluation stage.

Compared to this the image below show Simple Machines is categorized in the 'Exploring' stage, primarily due to the fewer green dots next to their activities. These green dots quantitatively represent the level of engagement with the product, such as the number of documents reviewed and repositories forked on GitHub. The lower intensity of these activities, compared to accounts like Atlassian, suggests that Simple Machines is still in the early phases of engagement and evaluation.

How to action on the Dev Funnel intel

Reo.Dev's Buying Stage feature enhances:

1. Account Prioritisation

2. Triangulate funnel data with other sources.

Account Prioritization

Reo.Dev's Buying Stage feature enables precise account prioritization by providing each team — Marketing, DevRel, and Sales — with critical insights into where customers are in the buying journey. This allows for targeted engagement strategies that efficiently allocate resources and efforts to the accounts most likely to move the account from one buying stage to another.

DevRel:

  • Building developer community: DevRels can identify and engage with developers in the Exploring and Evaluation phases, fostering a community that supports detailed product exploration.

  • Cultivating champions: By understanding which developers are deeply engaged, DevRel can nurture these individuals into champions through educational content, social proofs within their organizations, facilitating smoother transitions through the buying stages.

  • Warm introductions to buyers: As developers move deeper into the Evaluation and Trial stages, DevRel can make warm introductions to sales.

Marketing:

  • Product discovery and awareness: The marketing team can use insights from the Buying Stage to enhance strategies around product discovery and initial customer engagement to build a robust top-of-funnel pipeline. By understanding where a customer is in their journey, they can tailor content and campaigns to raise awareness effectively.

  • Funnel progression: They can track how accounts move from initial interest (Exploring) to actively evaluating the product (Evaluation), employing targeted strategies to nurture leads through these phases.

  • Revenue opportunities: Identify accounts that are transitioning from evaluating to decision stages helps focus efforts on MQLs that are more likely to convert, optimizing resource allocation.

Sales:

  • Buyer outreach and relationship uuilding: Sales teams can use the insights from the Buying Stage to initiate outreach at the right time, ensuring that their efforts are met with interest rather than resistance, especially as accounts move into the POC and Deployment stages.

  • Customizing sales pitches: Understanding the specific stage of the buyer’s journey allows sales representatives to personalize pitches and demonstrations to address the unique needs and concerns at each stage.

  • Reduce sales cycles: By knowing when an account is in the Deployment phase, sales can apply closing strategies tailored to the final concerns of decision-makers, leveraging all preceding interactions and engagements.In the evaluating stage, developers' interest grows, leading them to thoroughly investigate the product, its features, performance, and compatibility.

Here’s a teardown of how each team can effectively impact every stage of the Buying Funnel.

Triangulate funnel data with other sources

  • Segments in Reo.Dev: By uploading a LIST of accounts to Reo.Dev, you can combine this with Buying Stage insights to refine your focus on preferred accounts, enhancing targeted strategies.

  • CRM: Merge Buying Stage insights with CRM data and deal pipeline information. This allows for a comprehensive view of each account's engagement and potential readiness to buy, facilitating more informed decision-making and strategic allocation of resources.

Editing Dev Funnel Stage in Reo.Dev

Step 1: If the defined developer stages need editing, click the edit icon.

Step 2: Select the correct stage from the drop down, add comments and submit.

Filtering accounts based on Dev Funnel Stage

Step 1: To search or narrow down accounts based on certain developer funnel stages, add a filter.

Step 2: Select Dev Funnel

Step 3: Select the required funnel stage.

Note: We also provided to see accounts that have recently moved from one stage of the funnel to another.

Creating Segments based on Dev Funnel

You can create Segments based on Dev Funnel in Reo.Dev by selecting Dev Funnel from the filter list.

Then choosing the required funnel stage to create a segment of accounts based on the selected stages.