Rox is a destination.
Phoenix is a capability.
Rox wants to own the seller's workflow inside its own app. Phoenix is an MCP-native intelligence layer: 29+ proprietary data tools any AI client, agent, or CRM can call to ground its answers — no new tool to live in.
Your team works inside Rox's own surface rather than the tools they already use.
Any MCP client calls Phoenix's data tools over the open protocol — the tools your team already uses, grounded in first-party intelligence.
29+ proprietary data tools any AI client, agent, or CRM can call over the open Model Context Protocol. Rox is a closed app you work inside.
Technographics, IT spend, intent, install-base, and contracts feed every tool call — distinct from a public-web blend.
Bring your own model and extend in code. Rox is an OpenAI-centric, closed platform.
Phoenix vs Rox, dimension by dimension
| PPhoenix | Rox | |
|---|---|---|
| Architecture | Intelligence/context layer that runs inside your agents & CRM via MCP | Closed revenue OS that owns the workflow surface |
| Deployment | Agents run in your existing stack (Claude, Copilot, Bedrock) and any CRM | You work inside Rox's app |
| Data | HG proprietary technographics, IT spend, intent, install-base, contracts, SEC | CRM + public web blend; no first-party tech/spend data of its own |
| Interoperability | MCP-native, open and source-agnostic | Closed platform; no MCP server for your agents |
| Extensibility | Blueprints + SDK + code-defined tools, version-controlled in Git | Configurable workflows & templates (prompt-level only) |
| Model choice | Model-agnostic — bring your own (Azure OpenAI, Bedrock, on-prem) | OpenAI-centric; no bring-your-own-model path |
Based on publicly available Rox product materials, June 2026. Corrections welcome.
Four architectural choices your team will feel every day
Meet sellers where they work
Phoenix exposes its data tools over MCP, the open Model Context Protocol, so any client — Claude, Copilot, your CRM, or your own agents — can call them directly. Rox delivers its value inside the Rox app, so the value shows up once your team works there. Open tooling means there's nothing new to log into.
First-party intelligence, built in
Phoenix scores and researches accounts on HG's first-party technographics, IT spend, intent, install-base, contracts, and SEC data. Rox draws on a CRM-plus-public-web blend. Different inputs, and for account targeting the first-party signal is the differentiator.
Rox: CRM + public web blend
Extend in code, version it in Git
Phoenix ships Blueprints, an SDK, and code-defined tools you can review, test, and version-control. Rox focuses on configurable workflows and templates at the prompt level. If you want a code-level engineering surface for your platform team, that's where Phoenix fits.
// phoenix.blueprint.ts export tool scoreAccount( signals: HGSignals ) { /* your logic */ } $ git commit -m "v2 scoring"
Rox: prompt-level configuration
Your model, your region, your rules
Bring your own model and deployment region — Azure OpenAI, Bedrock, or on-prem — so Phoenix fits your security and EU compliance posture. Rox is OpenAI-centric today, so a bring-your-own-model requirement is worth confirming with them if that's a hard constraint for you.
Rox: OpenAI-centric today
Choose Phoenix when…
- You want intelligence inside the tools and agents you already run.
- You need first-party technographic, spend, and intent signals to score accounts before outreach.
- You need to extend the system in code and avoid single-vendor lock-in.
- You need model and CRM flexibility, including EU/Azure compliance.
Where Rox may fit
We'd rather be straight with you. Rox can make sense if:
- You have no CRM or agent standard yet and want one packaged app to start from.
- A fully self-contained, opinionated workflow appeals more than composability.
- Standardizing on OpenAI-only is fine for your security and compliance needs.
Questions buyers ask us
Do we have to rip out our current CRM or agents?
No. That's the point. Phoenix layers onto the CRM and agents you already run through MCP, so there's no migration project and no new destination app for reps to learn. Rox, by contrast, expects your team to work inside its own surface.
What data does Phoenix bring that Rox doesn't?
HG Insights' first-party signal graph: technographics, IT spend, intent, install-base, contracts, and SEC data. Rox scores on a CRM-plus-public-web blend, so the signal difference comes down to first-party depth versus publicly sourced data for your account targeting.
Can our engineers actually build on Phoenix?
Yes. Phoenix exposes Blueprints, an SDK, and code-defined tools you can review, test, and version-control in Git. Rox focuses on prompt-level configuration and templates, so if you need a code-level engineering surface to extend, that's where Phoenix fits.
We're on Azure / have EU data-residency requirements. Does that work?
Phoenix is model-agnostic and region-flexible — bring your own model on Azure OpenAI, Bedrock, or on-prem to meet your security and compliance posture. Rox is OpenAI-centric with no BYO-model path, which is often a blocker for regulated buyers.
How fast can we get value?
Connect the CRM and agents you already use, and Phoenix produces its first intelligence-backed briefing in minutes — no seat migration, no change-management program.
See Phoenix on your target list
Get intelligence inside the agents and CRM you already use — no new tool to live in. Request access and we'll show you how.