Track & Get Slack Alerts for Purchase Intent Signals for your Assigned Deals
📌 Need help at any point? If you need support implementing this playbook end to end, contact your Account Manager or write to us at support@reo.dev.
Introduction
For an AE, the hardest part of managing a pipeline is not the deals you are actively working. It is knowing what is happening inside the deals you are not actively in front of on any given day. This playbook helps you stay on top of every assigned deal without the manual check-ins.
Set up purchase intent signals for your accounts in Reo.Dev and get alerted in Slack the moment something significant happens, so you always follow up when the timing is right rather than a week after the moment passed.
Let's set this up in three simple steps.
Step 1: Create a Segment of your “Target Accounts”
Before you can track purchase intent signals, you need to tell Reo.Dev which accounts to monitor. There are two ways to do this depending on how your team defines SDR/AE territories.
Create Segment of Target Accounts — Option 1: Upload a CSV file of Your Target Accounts
If you manage your own book of business in a spreadsheet or have a defined Target Account list outside your CRM, this is the fastest way to get started.
How to upload your list:
Go to Tools and click on Lists from the sidebar.
Click Import and select Accounts as the list type.
Give your list a clear name, for example
"John’s Target Accounts - Feb 26", and click Next.Upload your CSV file. Make sure your file includes a Company Domain Name column, as this is the primary key Reo.Dev uses to match and enrich your accounts.
Map the Company Domain Name column and any other columns you want to bring in, then click Done.
For a detailed walkthrough of the CSV upload process, refer to the Custom Lists guide.
Your list will be processed and enriched with developer activity. You will receive an email once the import is complete.
Create Segment:
Once your list is ready, create a segment from it by following these steps:
Go to Segments in the navigation bar and click Create Segment.
Select Basic as the segment type and choose Accounts.
Name your segment, for example
"John’s Target Accounts - Feb 2026".Click Add Filters and under Source, select Lists.
Pick the list you just uploaded from the dropdown.
Click Save and Exit.
Pro Tip: While creating this segment, check the"Set as Default Segment"option. This means every time you log in to Reo.Dev, you will land directly on your target account view, no extra clicks needed. Learn how to configure your default segment.
Important Note:
Once your segment is created, you may notice that the account count is lower than your original account list uploaded via CSV.
This is expected. Reo.Dev surfaces accounts where developers have shown some form of activity across the first-party or third-party sources you have connected to the platform, such as your documentation, product, GitHub repositories, website, etc.
Accounts with no recorded developer activity will not appear in the segment yet. This does not mean those accounts are excluded permanently.
As developers from your Target Accounts start engaging with your docs, website, Github repo, community, etc. and start showing intent — Reo.Dev will automatically add those Accounts to your Target Account segment over time.
In Step 2, we will define the specific purchase intent signals you want to track across these accounts, so you are only alerted when the activity that actually matters to you happens.
Create Segment of Target Accounts — Option 2: Use the CRM Owner Filter (For HubSpot and Salesforce Users)
If your Reo.Dev instance is connected to HubSpot or Salesforce and your CRM owner field is consistently updated, you can pull your assigned accounts directly into a segment without uploading a CSV.
Before you begin: This option only works if your CRM is already connected to Reo.Dev and your account ownership data is properly maintained. If your CRM is not HubSpot or Salesforce, or if your CRM owner field is incomplete or not regularly updated, go with Option 1 instead.
If your CRM is not connected yet, set that up first before creating the segment:
Once your CRM is connected properly, here is how to create the segment:
How to set it up:
Go to Segments and click Create Segment.
Select Basic and choose Accounts.
Add a filter for CRM Owner and select your name.
Name your segment and save it. Reo.Dev will now surface all accounts where you are the assigned owner in your CRM and there is Developer Activity detected by Reo.Dev
💡 Pro Tip: Same as above, you can set this segment as your default landing view while creating it. Every time you log into Reo.Dev, you will see your assigned accounts front and centre. Learn how to configure your default segment.
Once your segment is set up, you are ready for Step 2.
Step 2: Setup Purchase Intent Signals
Your segment from Step 1 gives you a working list of target accounts that have been assigned to you. Now it's time to go one level deeper and identify which of those accounts are showing actual purchase intent, so you know exactly where to focus your outreach first.
Reo.Dev lets you do this through two types of signals: (a) System signals that the platform generates automatically, and (b) Custom signals that you configure based on what purchase intent looks like for your specific GTM motion.
2.1: System Signals
Reo.Dev automatically generates a set of system-level signals that are available to all users out of the box. These are surfaced as Tags in the platform.
Tags in Reo.Dev are labels that get applied to accounts, developers & buyers automatically based on activity patterns the system detects, and they are what power your segment filters and automation conditions throughout this playbook.
If you are interested in checking out the full list of system generated signals/tags, you can see it here.
The system signal most relevant for purchase intent tracking is the Activity Surge tag.
Activity Surge
The Surge tag is applied to an account when its Activity Score increases sharply by more than 40 points within a 7-day window. Activity Score is calculated by Reo's ML models across all the developer intent signals you have connected to the platform, including your docs, product, GitHub repositories, and website.
A sudden spike like this is typically a strong proxy for an active evaluation happening at that account.
🎯 Action Step
Go to the segment you created in Step 1. In the Accounts view, click Add Filter and select Tags. Filter by Surge. The accounts that appear are the ones showing the strongest early intent signals in your list right now. Start your inspection here.
2.2: Custom Purchase Intent Signals
System signals give you a strong baseline, but the most precise prioritization comes from defining what Purchase Intent actually looks like for your product.
Custom signals let you configure this directly in Reo.Dev based on the specific behaviours that matter to your GTM motion.
These are the four purchase intent patterns GTM teams most commonly track using Reo.
Exploring Enterprise Features
Buyer Involved
Team-Level Evaluation Activity
Troubleshooting Signals
Together with the Surge system signal, they give you solid coverage of the signals that actually matter.
Configuration Note
Each custom signal depends on the data sources you have connected in Reo. Website and docs activity requires the JavaScript tracking snippet to be installed.
CLI command tracking requires your developer docs to be configured. Product usage thresholds require the Product API integration. GitHub issues tracking requires your GitHub repos setup & so on.
If you are unsure what is already set up or need help configuring a specific signal, reach out to your Account Manager or write to us at support@reo.dev with the signals you want to track and they will handle the integration and tag creation with you.
Here is how to think about each one, what it signals and how to set it up:
A) Exploring Enterprise Features
When developers at a Target Account are visiting or repeatedly interacting with Documentation pages explaining your ENTERPRISE or PREMIUM features, it indicates the account is evaluating whether your product can meet an Enterprise level need, such as Scalability, Security, Team Collaboration, etc. This goes beyond casual exploration and developer curiosity. This is a revenue opportunity.
How to set it up:
Prerequisite: Your website and docs tracking beacon must be installed for Reo.Dev to capture page-level activity. If this is not done yet, set it up first before configuring key pages.
Step 1: Configure your enterprise and pricing pages as Key Pages
Go to Settings → Integrations and navigate to your website and documentation configurations. Identify all Docs and Website pages that represent Enterprise features, Advanced capabilities, Pricing, etc. and add them as Key Pages.
Step 2: Create a segment to surface accounts hitting these pages
Go to Segments and create a new Advanced segment for Accounts.
Segment Criteria:
Segment: Advanced
Segment Type: Accounts
Tag Name: Enterprise Interest (or similar)
Segment Filters (OR across both groups):
Filter Group 1: Enterprise and Pricing Pages on Website
Key Pages: Website — Includes any — select your enterprise and pricing key pages pages configured above
AND Date of Activity — set to ‘Last 30 days’: how recently the visit must have occurred to qualify (a shorter window keeps the list tight, a longer window captures accounts that may be in a slower evaluation cycle)
AND Activity Score (Developer) — High or Medium (optional but recommended: this filters out sporadic one or two page visits and surfaces only developers with sustained engagement on your first-party assets)
Filter Group 2: Enterprise and Pricing Pages on Docs
Key Pages: Docs — Includes any — select the relevant documentation key pages configured above
AND Date of Activity — same window as above
AND Activity Score (Developer) — High or Medium (optional but recommended: same reasoning as above)
An account qualifies if developers visited any of these pages across either your website or docs within the time window you set.
When saving the segment, give it a descriptive Tag Name such as Enterprise Interest. This tag will then be available as a filter across your segments and automation conditions, which is how you will use it in Step 3 of this playbook.
B) Buyer Involved
When Reo.Dev identifies and de-anonymizes activity from an economic decision maker at a target account, such as a CXO, Founder, or VP, it has an implication that the evaluation might have moved beyond the technical team.
A buyer engaging with your assets alongside developers is one of the strongest signals that an account is approaching a purchase decision.
How to set it up:
Go to Segments and create a new Basic segment for Accounts. Under the Developer section in your filters, select Developer Attributes and choose Buyer from the dropdown.
When saving the segment, give it a descriptive Tag Name such as Buyer Active.
This tag will then be available as a filter across your segments and automation conditions in Step 3 of this playbook.
C) Team-Level Evaluation Activity
When multiple developers from a Target Account are active across your assets within a defined time window, it points to a coordinated evaluation rather than individual exploration. A single developer exploring is interesting. Three or four developers - active in the same week could be a serious buying signal.
How to set it up:
Go to Segments and create a new Basic segment for Accounts. Add the # Active Developer filter and set the condition to Greater Than 2.
This surfaces accounts where more than two developers have been active, indicating a group evaluation rather than individual curiosity.
You can raise the threshold to Greater Than 3 or 4 depending on how strictly you want to define team-level activity for your product. When saving the segment, give it a descriptive Tag Name such as Multiple Devs or Group Evaluation.
This tag will then be available as a filter across your segments and automation conditions in Step 3 of this playbook.
D) Troubleshooting Signals
When developers are posting bugs on Github, Community Slack or repeatedly visiting your Support / Troubleshooting documentation, it often means they are deep enough in an evaluation to hit real friction. Accounts troubleshooting actively are invested. Requires your GitHub repository and Troubleshooting Docs to be connected.
How to set it up:
Go to Segments and create a new Advanced segment for Accounts. The logic here uses three separate filter groups, each covering a different source of troubleshooting activity, with a recency filter applied inside each group.
Segment Criteria:
Segment: Advanced
Segment Type: Accounts
Tag Name:
Troubleshooting(or something along these lines)Segment Filters (OR across all three groups):
Filter Group 1: Troubleshooting Docs Activity
Key Pages: Docs — Includes any — select your troubleshooting and support documentation pages
Last Activity Date — Last ‘60 days’
✏️ Set to how recently activity must have occurred to qualify as a purchase intent signal. A shorter window like 30 days keeps the signal tight, a longer window like 90 days casts a wider net.
Filter Group 2: GitHub Activity on Your Repository
Repository Owner — Includes any — select your own GitHub repository
Activity Type: GitHub — Includes any — ‘Fork’ & ‘Opened Issue’, ‘Comment’ and any other relevant actions
Last Activity Date — Last ‘60 days’
✏️ The Repository Owner filter is required here. Adding Activity Type: GitHub alone would also capture activity on any competitor or complementary repositories you have configured in Reo.Dev. Scoping it to your own repository ensures only activity on your GitHub assets qualifies.
Filter Group 3: Community Slack Activity
Activity Type: Slack — Includes any — Posts, and any other relevant actions
AND Last Activity Date — Last 60 days
✏️ Only add the Slack filter group if your community Slack is set up specifically to offer help and support to developers. If it is a general community channel, the signal quality here will be lower when you are looking at from a purchase intent signal POV.
When saving the segment, give it a descriptive Tag Name such as Troubleshooting or Help Needed. This tag will then be available as a filter across your segments and automation conditions in Step 3 of this playbook.
🎯 Action Step
Now that your Custom Signals are set up, go to your segment from Step 1. In the Accounts view, click Add Filter, select Tags, and choose the Custom Signals + System Surge signal.
This will surface the subset of your target accounts that have crossed the specific intent thresholds you defined.
💡 In your list of Target Accounts — you now have a Priority set — the ones showing real, measurable purchase intent right now. These are the accounts to go after immediately.
✏️ Note for Companies with bottoms-up PLG Motion or Free Plan:
If you’re running a bottoms-up PLG motion or offering a free plan or trial, product usage becomes one of the strongest purchase intent signals you can track.
By passing your product or telemetry data to Reo via the Product API, you can set up product usage threshold signals, for example feature activation, usage frequency, seat expansion, or hitting plan limits. These thresholds help you identify when an account is moving from exploration to real evaluation.
In PLG models, usage is one of the key purchase intent signals. Setting up product usage thresholds allows you to qualify accounts based on actual in-product behavior, not just external signals, and prioritize the ones most likely to convert. But these four are a strong foundation to start with.
Now in Step 3, we will set up Slack alerts so you are notified the moment a new account shows any of these Purchase Intent signals, without having to check the platform manually.
Step 3: Set Up Slack Alerts Automation
Now that your System Signals and Custom Signals are configured in Step 2, this step turns them into real-time Slack alerts using a clean and repeatable automation workflow.
The approach here is straightforward. You will create five focused segments, one for each purchase intent signal, and set up a simple automation on each.
Every segment combines your Target Account list with one specific Purchase Intent Signal Tag. The automations themselves are simple: when a new account enters the segment, send a Slack alert.
This way, every alert you receive already tells you exactly why it fired, based on which segment triggered it.
Before you begin, make sure your Slack workspace is connected to Reo.Dev. You can set that up under Settings → Integrations. If it is already connected, you are good to go.
Step 3a: Create Your Five Signal Segments
For each of the five purchase intent signals from Step 2, create a new Basic segment for Accounts with two filters set to Matches All:
Filter 1 (your base account list):
If you uploaded a CSV in Step 1: Source → Lists → select your uploaded list (e.g.
John's Target Accounts)If you used the CRM owner filter in Step 1: Source → CRM Account Owner → select your name
Filter 2 (the signal tag):
Source → Account Tags → Includes any → select the relevant signal tag
Repeat this for all five signals. Your five segments should look like this:
Segment Name
Base Filter
Signal Tag
John - Enterprise Interest
List / CRM Owner
Enterprise Interest
John - Buyer Involved
List / CRM Owner
Buyer Involved
John - Multiple Devs
List / CRM Owner
Multiple Devs
John - Troubleshooting
List / CRM Owner
Troubleshooting
John - Activity Surge
List / CRM Owner
Surge
Step 3b: Set Up an Automation on Each Segment`
Navigate to Tools → Automations and click Create Automation. You will repeat this process once for each of the five segments above.
📌 Note: You can only build automations on segments that you own, meaning segments you created yourself.
We will walk through one example in full. The same steps apply to all five.
Example: Enterprise Interest Alert on John’s Account
This automation fires the moment an account from your target list starts visiting your enterprise or pricing pages, crossing the threshold you defined in the Enterprise Interest segment.
Automation Name:
John - Enterprise Interest AlertSource: Select the
John - Enterprise Interestsegment
Trigger: New Account Added to the Segment
Conditions: None
Action: Get Alerts via Slack, delivered to your personal Slack DM
Click Save and Publish.
💡 For a full reference on how automations work, visit the Automations guide.
Repeat this process for the remaining four segments, naming each automation to match its segment so you can identify the intent type directly from the Slack notification.
📌 Need help at any point? If you need support implementing this playbook end to end, contact your Account Manager or write to us at support@reo.dev.
Step 3c: Two Bonus Automations Worth Setting Up
The five automations above cover your core purchase intent signals. These two additional automations layer on top of that and catch signals that the tag-based segments alone will not surface.
Bonus Automation 6: New Developer Identified in Your Target Accounts
This one requires creating a sixth segment, but it is a simple one.
Create a new Basic segment, this time with Segment Type set to Developers instead of Accounts.
The filter criteria is the same base filter you have been using throughout: List includes your uploaded target account list, or CRM Account Owner is your name if you took that route in Step 1.
Name it something like Developer Leads in John's Target Accounts.
What this segment gives you is a live view of every de-anonymized developer Reo.Dev identifies across your target accounts.
On this segment, create an automation with the following setup:
Source: Your developer segment above
Trigger: New Developer Added to a Segment
Conditions: None
Action: Get Alerts via Slack
Click Save and Publish.
When this fires, it is not telling you about a signal threshold being crossed. It is telling you that a new lead just surfaced inside one of your target accounts.
That on its own is worth knowing, and it is a signal type none of the five tag-based automations are set up to catch.
Bonus Automation 7: New Buyer Identified Anywhere in Your Target Accounts
This automation goes back to the original base segment you created in Step 1, the one with just the list or CRM owner filter and no signal tag added.
On this segment, create an automation with the following setup:
Source: Your base target accounts segment from Step 1
Trigger: New Buyer Added to an Account in a Segment
Conditions: None
Action: Get Alerts via Slack
Click Save and Publish.
How is this different from the Buyer Involved automation that we covered above?
The Buyer Involved automation fires once when an account first qualifies for that tag. This one fires every time a new buyer is identified at that account, regardless of when the account entered your segment.
So if three different decision-makers become active at the same account over say two weeks, you get three separate alerts.
That matters because a buying committee forming around your product is a meaningfully stronger signal than a single buyer appearing once.
Once these are live, your automation runs continuously in the background.
Every time a target account crosses a purchase intent signal you have defined, you will receive a Slack notification with the account details, so you can review the context and reach out while the signal is fresh.
Next Steps
Once an alert lands in your Slack and you have identified that the account is worth pursuing, the next move is to dig into the account before reaching out.
Use Reo-Copilot to get a summary of the Developer Activity, whether the Account is ready for Sales outreach, understand their Top use case, generate a personalised message to be used for Email / Linkedin outreach, etc.
This context is what separates a generic cold outreach from a message that actually lands.
From there, find the right buyer contacts to reach out to in those accounts and add them to your email or LinkedIn outreach sequences.
The next playbooks in this series will walk you through each of these steps in detail.
Last updated
Was this helpful?