A standing AI agent for every account in a rep's book, reading the CRM, calls, calendar and email to hand back research, meeting briefs, deal risk and drafted follow-ups.
What is
Rox
Monday morning, an AE opens a deal that has gone quiet and starts hunting through Salesforce, the last call recording and three browser tabs to rebuild the story. Rox puts a standing AI agent on every account in that book, so the research, the meeting brief and the follow-up draft are already waiting. The agents read from a knowledge graph Rox builds out of your CRM, calendar, email, Slack, call recordings and warehouse tables, then add public research on top. Specialised agents cover account research, discovery, outreach, meeting prep, deal risk and CRM autofill, and the write-back to Salesforce or HubSpot runs both ways. Rox sells to the Global 2000 and names MongoDB, Cloud Software Group and BetterUp as customers, which tells you the shape of the buyer. There is a sequencer inside it with multiple mailboxes and AI-written steps, though the centre of gravity is an enterprise seller working a named account list rather than a cold list. Rox earns its price where AEs sit on big named accounts with years of CRM history behind them, and it does little for a team nobody has heard of yet. We have not run it at Nebor, and the ambition in its own docs, where Rox eventually becomes the CRM, is the part we would negotiate hard.
Integrations and the modern GTM stack
Rox does not sit next to your stack, it ingests it. The connectors feed one knowledge graph that every account agent reads from, and most of the org-wide ones are switched on by an IT admin rather than a rep, which makes the integration list a procurement conversation as much as a technical one.
Salesforce | Scheduled pull of Accounts, Contacts, Opportunities and Products into Rox, with optional write-back of fields and activities. Rox recommends a dedicated Salesforce user on a full licence with the System Administrator profile, because activity write-back is not supported on the API-only integration licence. |
HubSpot | The second supported CRM, running the same three-layer model of field mappings, real-time write-back with a conflict check against live CRM state, and a batch reconciler on a roughly fifteen minute cron. Other CRMs are described as possible with configuration rather than supported today. |
Google Workspace and Microsoft 365 | Org-wide email and calendar ingestion authorised by an IT admin for every user at once, through Google Workspace or Microsoft Graph. This is what powers meeting briefs, activity logging and the smart email rules, and it is the connector most security teams will want to review first. |
Slack | Individual users can connect their own account, and org-wide connection is Enterprise only and set up by the Rox team. Rox maps users by email address, so anyone whose Slack address differs from their Rox address will silently fail to link. The bot also has to be invited into each channel. |
Call recorders | Gong, Avoma and Attention connect with an API token from the Settings page, while Zoom Cloud and Microsoft Teams have their own org-wide flows for transcripts and meeting metadata. Anything outside that list needs a conversation with the Rox team. |
Snowflake, Databricks and BigQuery | Warehouse connectors that let the graph read structured enterprise data from your own tables. Rox is open that it sees warehouse-native as the destination and the CRM as the current stop on the way, so this is the connector that matters most if you want to keep the source of truth on your side. |
Enrichment providers | Rox resells sixteen named vendors including People Data Labs, ContactOut, Prospeo, Findymail, Hunter, RocketReach, Wiza, CrustData, PredictLeads and HG Insights. Enterprise customers can supply their own API keys for those providers, while self-serve accounts can only bring a key for HG Insights. |
Sending mailboxes | Sequences send from connected Gmail or Outlook mailboxes, with multiple mailboxes per user, per-mailbox daily limits and custom tracking domains that Rox recommends matching to each sending domain. A mailbox can belong to only one Rox user at a time. |
What is missing | We found no public REST API reference and no Zapier or n8n listing, so programmatic access outside the product means outbound webhooks fired from an agent workflow. There is no Clay integration either, so a Clay-run enrichment layer and Rox would exchange data through the CRM or the warehouse. |
Pro’s
The unit of the product is an account rather than a campaign, so an AE holding thirty named logos gets research and monitoring across all thirty without anyone building a list first.
CRM write-back is engineered rather than bolted on, with per-field mappings, a sync direction on each field, a live conflict check against Salesforce before every write, and an audit entry afterwards.
It ingests the messy private data most tools skip, pulling Slack threads, calendars, mailboxes and transcripts from Gong, Avoma, Attention, Zoom and Microsoft Teams into the same graph the agents reason over.
Warehouse connectors for Snowflake, Databricks and BigQuery mean the account context can come from your own tables rather than a vendor's private copy of your business.
Metering is by agent action with a free tier of 2,000 and a $50 individual plan, so a curious rep can test the research quality before anyone books an enterprise call.
Rox publishes the sixteen enrichment vendors behind its data, from People Data Labs and Prospeo to Findymail and HG Insights, and Enterprise accounts can point those columns at their own API keys.
Cons
The pricing page shows four cards and no feature comparison, the Teams card at $255 repeats the Free card's description and its 2,000 action allowance, and the FAQ underneath still explains plans called Starter and Core, so you cannot price a team from it.
Agent actions are burned by always-on monitoring as well as work you asked for, unused actions expire every cycle, and the docs tell you to tune the Insights settings to stay inside the allowance, which makes monthly spend a moving target.
The recommended Salesforce setup is a dedicated user holding a full licence and the System Administrator profile, because activity write-back fails on the API-only integration licence, and that hands one vendor admin reach over every object and field.
Independent evidence is thin for something this central, since the headline results of 90% less prep time and a 40 to 50% higher selling price come from Rox's own customer stories, and the company was valued at $1.2 billion on a projected $8 million of 2025 ARR.
Rox's own CRM documentation describes customers graduating to a warehouse-native future in which Rox is the CRM, and a system that holds your accounts, opportunities, activity history and enrichment is expensive to walk back out of.
Pricing
Free
$0 No subscription, self-serve signup
2,000 agent actions a month
Account agents, research and monitoring
Sequences from a connected Gmail or Outlook mailbox
HG Insights is the only provider key a self-serve account can add
Work stops when the monthly allowance runs out
Individual
$50/month Starts at, billed monthly, allowance resets on the renewal date
5,000 agent actions a month
Account research, monitoring and contact discovery
Clever Columns and account briefs
Early renewal to reset actions mid-cycle
Rox states the feature set matches the entry plan, with more capacity
Teams
$255/month Starts at, billed monthly. The card duplicates the Free plan description and shows 2,000 actions, so confirm the real allowance with sales
Action allowance printed as 2,000 on the pricing card
No published feature comparison against Individual
Sequence sharing, shared views and admin usage tracking exist in the product
Team management, propagated views and configurations
Scales with seats on request
Enterprise
Custom Contact sales, annual agreement
Org-wide Google Workspace, Microsoft 365, Slack, Zoom and Teams ingestion
Salesforce and HubSpot sync with field mappings, write-back and audit logs
Snowflake, Databricks and BigQuery warehouse connectors
Bring your own enrichment provider API keys
SSO through Auth0, data retention controls, SOC 2 Type II
How it fits your stack
Alternatives
At a glance
One always-on agent per account
Knowledge graph over CRM, email, calendar, Slack
Salesforce and HubSpot two-way write-back
Snowflake, Databricks and BigQuery connectors
Gong, Avoma, Attention, Zoom and Teams transcripts
Sequences with multiple sending mailboxes
Agent workflows on schedules and triggers
Free tier with 2,000 agent actions
Read some of our client stories
GTM Workflows
Learn how to use GTM tools in workflows
Guides and tutorials to get the most from your workflows
Ready to get started?
By clicking Sign Up you're confirming that you agree with our Terms and Conditions.
