ArcGlass vs. Catalyst
Company data compiled from public sources; figures are approximate and may have changed since publication.
TL;DR. Catalyst is a Customer Success platform — CS-team workbench, account health scores, renewal forecasting, automated playbooks for CSMs. ArcGlass is a cross-channel signal-and-routing layer for Leadership, Product, and Sales. ArcGlass is intentionally not a CS platform. The category, buyer, and product surface are different. If you're evaluating a CS platform, evaluate Catalyst (or Gainsight, Totango, Vitally) against each other. ArcGlass solves an adjacent problem.
Strategic positioning
| ArcGlass | Catalyst | |
|---|---|---|
| Category | Conversation signal & action-routing layer | Customer Success platform |
| Buyer | Leadership, Product, Sales (cross-functional) | Head of Customer Success, CCO, CS Ops |
| Headline value | “Signals from every conversation, routed to every team, nothing falling through the cracks.” | “The customer-led growth platform for CS teams.” |
| Center of gravity | Cross-channel signals → team-routed actions | Account health → CSM workflow → renewal motion |
| Primary success metric | Signals captured, actions routed, follow-ups closed | NRR, GRR, churn, renewal rate |
The categories are genuinely different. We position ArcGlass for organizations whose problem is “signals are firing everywhere and nothing's getting routed in time,” not for organizations whose problem is “our CSMs need a workbench to manage book of business.”
Where the two products do not compete
1. CSM workbench Catalyst (out of scope for ArcGlass)
Catalyst's core surface: a CSM-facing workbench. Account 360, health-score visualization, task queues, renewal pipeline, playbook execution, NPS surveys. ArcGlass does not build this surface and is not aiming to.
2. Health scoring Catalyst (out of scope for ArcGlass)
Catalyst builds account health scores from product-usage data, support tickets, engagement, billing, and CSM-entered signals. ArcGlass produces relationship-engagement metrics from conversation signals only — not a renewal-anchored health score.
3. Renewal pipeline Catalyst (out of scope for ArcGlass)
Catalyst tracks the renewal motion: stages, forecast, at-risk accounts, automation around renewal cadence. ArcGlass does not.
Where the two products overlap
1. Conversation signal capture ArcGlass wins
- ArcGlass: ten conversation surfaces with working pipelines — Slack, email, Discord, community, social, support, meetings — with per-conversation sentiment, emotion, intent, topic, risk, resolution, action items, engagement.
- Catalyst: ingests conversation summaries from connected tools (support, calls, email) as signals into the health score. Does not extract per-conversation signals as a primary product surface.
2. Action routing ArcGlass wins for cross-team
- ArcGlass: 30+ verbs across six team functions, plus eight AI agents that fire actions on signal trigger.
- Catalyst: playbooks and tasks for CSMs. Action surface is CS-workflow-shaped. Not built to fire Jira tickets for product, alerts for sales, escalations for engineering.
3. Champion detection ArcGlass wins
Catalyst tracks customer contacts and roles. ArcGlass surfaces composite-scored company champions (your top responders) and customer champions (their advocates) from conversation data.
Coverage areas only one side has
Only ArcGlass
- Multi-source conversation ingestion (10 surfaces)
- Cross-team action routing across six teams
- Two-sided champion detection
- Ghost Detector / stale-thread enforcement
- Free-text rule engine with override provenance
- Eight AI agents on signals
- Per-conversation early-warning risk composite
- Independent pipelines per customer / use case
Only Catalyst
- CSM workbench and task queue
- Account health scoring tied to renewal
- Renewal pipeline and forecasting
- CS playbook automation (CSM-cadence-shaped)
- NPS / survey collection and rollup
- Product-usage join for account health
- CS-team-specific reporting (NRR, GRR, churn cohorts)
- Native Salesforce CS-data sync model
Takeaways
- Different categories. Catalyst is a CS platform; ArcGlass is a signal-and-routing layer. If you're shopping for a CS platform, Catalyst belongs in your evaluation against Gainsight, Totango, and Vitally — not against ArcGlass.
- Natural composition. An organization running both would let Catalyst own the CSM workbench, health score, and renewal motion. ArcGlass would feed Catalyst with structured conversation signals and route cross-team actions Catalyst doesn't try to fire (Jira tickets, AE alerts, engineering escalations).
- If you're choosing between them: pick Catalyst if your problem is “our CSMs need a workbench to manage book of business and forecast renewals.” Pick ArcGlass if your problem is “signals are firing across every customer surface and the right team isn't seeing them.”
How ArcGlass thinks about the overlap
We don't position ArcGlass as a CS platform and we don't compete with Catalyst on its category. Catalyst is solving the CS-team workbench problem; ArcGlass is solving the cross-channel signal → cross-team action problem. The two compose: ArcGlass produces structured signals from conversations that a CS platform like Catalyst can consume, while routing actions to product, engineering, sales, marketing, and docs that fall outside the CS workflow.
Questions about this comparison? Reach out at [email protected] — we're happy to dig into specifics for your stack.