# Custom CRM Stages

The new **Custom CRM Stages** feature in Reo.Dev enhances your CRM integration by enabling precise mapping of custom account and deal stages for our customers using either **HubSpot or Salesforce CRM**. This upgrade empowers GTM teams to tailor their sales workflows and target accounts more effectively, overcoming prior limitations where only default lifecycle stages were supported.

By aligning Reo.Dev’s lifecycle stages with your custom CRM fields, you can segment accounts, track deal progress, and generate actionable insights for your teams.

***

### **Previous Limitations and the Solution**

Previously, Reo.Dev relied on default deal/opportunity stages in HubSpot and Salesforce. However, most customers utilized custom CRM field objects for account and deal stages, leading to mismatched data and inefficient filtering.

{% hint style="info" %}
To learn more about **Lifecycle Account Stages** in Reo.Dev, [check out this guide.](/accounts/account-lifecycle-stage.md)
{% endhint %}

The **Custom CRM Stages** feature now addresses this by allowing the mapping of your **custom picklist fields** from HubSpot or Salesforce to Reo.Dev’s lifecycle stages. This ensures accurate filtering and segmentation that are aligned with your CRM setup.

***

### **Setting Up Custom CRM Stages**

{% hint style="info" %}
**Prerequisite:** Ensure your CRM is connected to Reo.Dev before setting up **Custom CRM Stages.** For integration setup, [refer to this guide.](broken://pages/GxZCaSBLZu9qFqp44DXu)
{% endhint %}

**1) Navigate to CRM Integrations**\
Go to **Integrations** → **CRM** and click on the **Gear Icon**.

![](/files/YDj6ssCoE3piOfN7ikRU)

**2)** Click on the **Edit Field Mapping** button for the **Accounts Card** to configure **Custom CRM Account stages.**

![](/files/NPCRnUxX8JYLb5rErwvI)

**3) Map Account Stages**

Select the **"Stages"** subtab in the Account Mapping section.

![](/files/MFswhBoC8cx0uJmHw4RT)

Choose a **Custom Account CRM** field to map as the **Account Lifecycle Stage**.

{% hint style="info" %}
**Note:** Only fields classified as **"Picklist"** in your CRM are available for selection.
{% endhint %}

![](/files/lH1V5WmE6CDckMKCYwAi)

Pick all Custom CRM Account Stages you want to define as **"Customer"** in **Reo.Dev**. Multiple stages can be mapped as "Customer" to fit your sales cycle. For example, classify accounts by product line (Cloud vs. Open Source) or customer size (Enterprise vs. SMB).

![](/files/8vn6rrVdIlKA4Bu6nLl8)

**4) Save the Configuration**

<figure><img src="/files/glw3Fj1gWohWCT15e0pu" alt=""><figcaption></figcaption></figure>

After mapping, click **Save.**

{% hint style="info" %}
**Note:** Backend updates are applied immediately, but changes in the UI reflecting the new mappings will take up to **24 hours** to refresh.
{% endhint %}

**1) Map Deal Stages**

![](/files/VC63ikIra7wEbWfQEGz4)

**a)** For **HubSpot:**\
Select a **Pipeline** from the dropdown, as HubSpot supports custom pipelines tied to deal stages.

![](/files/AR2scNXPoJNd3g3R5iPL)

**Next,** select the corresponding deal stage field for the selected pipeline.

![](/files/eKSz3N13vaW1ADw9cTtS)

**b)** For **Salesforce:**\
You can directly choose the **Stage** field to map as Opportunity stages in Reo.Dev.

{% hint style="info" %}
**Note:** HubSpot users must select a pipeline as part of the setup. For Salesforce users, this step is not required and will not appear in the UI.
{% endhint %}

**2) Save the Configuration**

After mapping, click **Save.**

![](/files/BLbMxptZDaqFxUJ1k6UQ)

{% hint style="info" %}
**Note:** Backend updates are applied immediately, but changes in the UI reflecting the new mappings will take up to **24 hours** to refresh.
{% endhint %}

***

### **Using the New Filters in Reo.Dev**

Once mapping is complete and synced, you can leverage the **CRM Account Stage** and **CRM Deal Stage** filters to create powerful segments. These filters pull dynamic dropdown options directly from your CRM.

**1) View Lifecycle Stages on Account Profiles**&#x20;

After mapping, visit any account in Reo.Dev. Under the **Firmographics** section, you'll see the mapped **CRM Account Stage** and **CRM Deal Stage**, offering actionable insights at a glance.

![](/files/vNY3ZoRF2UPxbQk9mrX2)

**2) Create Segments Using New Filters**

Go to **Segments** → **Create Segment** and select either **CRM Account Stage** or **CRM Deal Stage** from the **Sources** section.

![](/files/abKGaWLuYYQidGX0IyO8)

Add criteria to refine your segment. Dropdown options mirror your **CRM’s custom stages.**

![](/files/rycl5Vil7Q05gzeBXmfz) ![](/files/l2Mc5nHu34xKuHnL6rTA)

***

### **Example Use Case:** Revive Cold SQL Leads with Developer Activity Insights

As an SDR or AE, your day is packed. Quotas are looming, new leads are piling up, and you’re constantly juggling priorities. Among the chaos, you face a frustrating challenge—how to know *when* to reengage those promising SQL leads that were once hot but have since gone cold. You know these leads showed interest, maybe even viewed your pricing, but now they’ve dropped off the radar. Without a way to detect if and when their interest reignites, you’re left guessing, and deals that could close end up slipping through the cracks. Sound familiar?

This scenario is even more pronounced in developer-focused GTM strategies, where traditional sales cycles don’t apply, and timing is everything. The buying journey here is often indirect, and intent signals can be hard to pinpoint.

Here is where you can le the **CRM Account Stage**, **CRM Deal Stage**, and the powerful **Developer Activity Surge** filter, you now have a way to surface those high-intent accounts exactly when they’re showing renewed interest.

**Here’s how you can turn this challenge into an opportunity:**

1. Create an Account segment to identify accounts marked as **SQL Cold** in the CRM Account Stage.
2. Combine this with the CRM Deal Stage set to **Pricing Discussed**.
3. Add the filter **Has Activity Surge = YES** to highlight accounts with recent spikes in developer activity. Reo.Dev's AI algorithm calculates this surge by tracking GitHub activity, product usage, website visits, code interactions, form fills and more.

   ![](/files/6kdXPrjTk0kKrP3SmPiV)
4. Save the segment and optionally set **Slack/Email Alerts** to get real-time updates whenever new accounts meet these criteria.

   ![](/files/o0wdyDmLgQzlw1K9Rv32)

{% hint style="info" %}
**Note:** For detailed instructions on setting up your Slack/Email notifications, [refer to this guide.](broken://pages/E1T9E3wdKAsefpSTdS59)
{% endhint %}

**Why this is valuable:**\
With this segment, you can instantly identify accounts that have re-entered the buying journey, giving you the perfect opportunity to reinitiate conversations and close the deal—without wasting time on manual guesswork.

This approach not only prioritizes your outreach but also ensures you don’t miss out on valuable opportunities hiding in plain sight. By taking a data-driven approach, you’re one step closer to hitting your quotas and converting high-intent leads into customers.

***

### **Additional Use Cases and Recommendations**

This use case is just the beginning! Get creative with the new filters and tailor them to your unique sales cycles. For example:

* Track accounts transitioning between deal stages.
* Identify high-priority leads with multiple custom filters.

Set these up today and see immediate improvements in your outreach strategy & deal closures.

***

### **Need Help?**

If you need assistance with the implementation, contact your **Customer Success Manager** via the Slack channel or email us at [**support@reo.dev**](mailto:support@reo.dev)


---

# Agent Instructions: 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:

```
GET https://docs.reo.dev/accounts/custom-crm-stages.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
