About Netdata
Netdata is an open-source observability platform that helps DevOps, SRE, and infrastructure teams monitor and troubleshoot their systems in real time.
The product has been around for over a decade and has built a large community of engineers and infrastructure teams. With ~2 million agent downloads and 300–400 cloud sign-ups every day, Netdata now operates a massive product-led funnel.
The Challenge
Netdata didn't have a demand problem. It had a prioritization problem.
Its open-source product and large community generate hundreds of new sign-ups every day, largely through word of mouth and organic adoption. But anyone can sign up, which means genuine businesses evaluating an observability solution sit alongside individual users, casual explorers, and accounts that may never progress beyond initial sign-up.
Netdata already had much of the underlying behavioral data across its product, CRM, PostHog, and BigQuery. What it lacked was a unified way to bring those signals together at an account level and determine which organizations were worth Sales' attention - and when.
For Netdata, the opportunity was to turn this enormous inbound funnel into a much more focused sales motion: identify the handful of accounts showing real buying intent, recognize the right moment for Sales to step in, and give reps the context to engage meaningfully.
How Netdata Uses Reo.Dev
Netdata uses Reo.Dev as an intent and prioritization layer across its PLG funnel - bringing together product usage, developer activity, website and documentation engagement, account fit, and buyer intelligence to help its GTM teams identify where to focus.
- Prioritizing the Right Accounts Across a Massive PLG Funnel
With 14.8K accounts showing activity in the last 30 days alone, Netdata doesn't need more accounts to pursue. It needs to identify which ones are showing enough fit and intent to warrant Sales attention.
Reo.Dev helps Netdata narrow this pool using signals across product usage, developer activity, website and documentation engagement, ICP fit, and CRM context. Instead of asking Sales to manually investigate thousands of active accounts, Netdata can surface a much smaller set of high-potential accounts for reps to focus on.
This prioritization now feeds a daily focus workflow for the Sales team. Accounts are filtered based on ICP and CRM criteria and enriched with Reo.Dev intelligence, giving reps a focused set of accounts to investigate and engage each day.
- Turning Anonymous Product Activity Into Account-Level Intelligence
Beyond prioritization, Reo.Dev helps Netdata understand the people and behaviors behind account-level activity.
By connecting product usage with website and documentation engagement, developer identities, and account information, Reo.Dev gives Netdata a more complete picture of how organizations are evaluating its platform. Today, Reo.Dev has deanonymized developers across 7,244 Netdata accounts, helping the team connect developer activity to the companies behind it.
This becomes particularly valuable when multiple developers from the same organization are evaluating Netdata. Instead of seeing individual users in isolation, Sales can understand how engagement is developing across an entire account.
Reo.Dev gives the ability to look at an account with dozens of users and quickly understand “why did they come, when did they come, what did they do?”
- Building an AI-Native Intent Engine with Reo.Dev MCP
Netdata has taken the integration a step further by connecting Reo.Dev to Neda, its internal AI agent, through Reo.Dev's MCP Server.
Neda connects Netdata's CRM, BigQuery, product systems, code repositories, and Reo.Dev, allowing the team to query intent intelligence conversationally rather than manually moving between dashboards.
For example, one can ask Neda which accounts have demonstrated meaningful activity over the previous week or which ones warrant further investigation. The integration also supports daily focus lists, account research, segment and audience scanning, developer identification, and high-intent account ranking.
Neda can also work backwards after a customer converts, pulling information from Reo.Dev, PostHog, BigQuery, and other systems to reconstruct the account's journey without manually piecing together data from multiple tools.
4. Powering Signal-Based Outbound and ABM
While Netdata's primary focus is converting its large inbound funnel, the team is also using Reo.Dev to build a more targeted outbound motion.
Reo.Dev helps Netdata identify accounts showing relevant developer activity and combine those signals with its ICP criteria to build targeted audiences.
The intelligence also flows into Netdata's existing GTM stack. Through its HubSpot integration, Reo.Dev populates 25 custom contact and company properties, including activity scores, developer funnel stages, customer fit, and segment membership. The team also uses Encharge for personalized outreach and Slack alerts to surface high-intent accounts.
This allows Netdata to prioritize outbound outreach based on actual developer activity and buying signals, rather than relying on static account lists alone.
Business Outcomes
Reo.Dev is helping Netdata turn an enormous PLG funnel into a more focused, signal-driven GTM motion:
- 63.8K accounts tracked, bringing product, developer, website, documentation, and account signals into one intelligence layer.
- ~3 qualified leads per day from its prioritized account workflow.
- Sales triage reduced from ~3 hours to ~30 minutes a day, allowing reps to focus on a fraction of the accounts they previously would have contacted.
Netdata is still refining which combinations of signals best predict when Sales should intervene. But the immediate value is already clear: Sales no longer needs to treat every sign-up equally. Reo.Dev gives the team a way to systematically narrow thousands of signals into the accounts where human attention can matter most.
Reo's MCP integration lets us bring developer intent directly into Neda, our internal AI agent. Instead of manually going through Reo segments, I can ask Neda to identify the accounts our Sales team should focus on. It also combines Reo's signals with data from PostHog, BigQuery, and our other systems to piece together the entire customer journey. I don't need to pull data from ten different places anymore. — Satyadeep Ashwathnarayana,CBO, Netdata
