Get the brief
CX Ventures Weekly

← The Briefing

The Great CI Split: Why revenue and risk tools are diverging

Market map of the conversation intelligence split between revenue and compliance tools. Follow the investment trends in automated QA and sales coaching.

The Great CI Split: Why revenue and risk tools are diverging

The market for conversation intelligence (CI) is no longer a single category; it has split into two distinct tracks: revenue-generation tools for sales and risk-mitigation tools for compliance. This divergence is driven by a fundamental shift in how enterprises value data, moving from anecdotal coaching to 100% automated auditing. While sales CI focuses on deal velocity and 'golden paths,' compliance CI prioritizes total coverage and regulatory safety.

Key takeaways

Why the CI market is splitting in two

For years, conversation intelligence was marketed as a broad tool for 'understanding the customer.' However, as the technology matured, the requirements for a sales manager and a compliance officer became irreconcilable. Sales teams need real-time suggestions and deal-risk alerts, often powered by platforms like Gong or Cresta. In contrast, compliance and QA teams require a rigorous audit trail that can withstand regulatory scrutiny in sectors like fintech and healthcare.

This split is reflected in how IDC tracks the Future of Customer Experience research program, which increasingly distinguishes between engagement platforms and the underlying data-protection layers. The 'Revenue Stack' is about the 'what next' of a conversation, whereas the 'Risk Stack' is about the 'what happened' and 'was it legal.'

The Revenue Stack: Coaching and deal signals

In the revenue-focused segment of the market map, the goal is to replicate the behaviors of top-performing agents. These tools analyze transcripts to find the specific phrases, objection-handling techniques, and talk-to-listen ratios that correlate with closed deals.

Founders in this space are increasingly building 'agentic workflows' that don't just analyze the call but trigger subsequent actions in the CRM. As we explored in our guide on how agentic workflows turn chatbots into autonomous workers, the future of revenue CI is less about a dashboard and more about an autonomous loop that updates Salesforce or HubSpot and suggests the next email draft. For these teams, a 'good enough' transcription is acceptable if the strategic insight is high.

The Risk Stack: Automated QA and compliance

For the compliance-focused segment, 'good enough' transcription is a liability. In highly regulated environments, missing a single 'mini-Miranda' warning or a disclosure statement can lead to significant fines. This is where the market is seeing the most aggressive 'follow the money' movement, as enterprises move away from manual QA—which typically covers less than 2% of calls—toward 100% automated coverage.

This shift is creating a massive opportunity for a conversation-intelligence layer like Hear.ai, which focuses on giving QA teams total coverage across all calls rather than samples. By flagging compliance risk automatically, these tools allow human auditors to focus only on high-risk exceptions. This specialized focus on risk is a key component of the broader mapping the CX-AI landscape, where the gap between 'general AI' and 'domain-specific compliance' is widening.

The Infrastructure Layer: LLMs as a commodity

The underlying technology for CI—speech-to-text and sentiment analysis—has been commoditized by Tier-1 providers like OpenAI, Google Cloud, and AWS. When transcription is a utility, the 'moat' for a startup is no longer its ability to turn audio into text.

Instead, the value has moved to the 'context layer.' Gartner notes in its Hype Cycle for Customer Service & Support that the maturity of speech analytics is high, but the application of domain-specific insights is where the 'Plateau of Productivity' lies. For a startup, this means choosing a side: are you building the best engine for closing a mortgage, or the best engine for auditing a mortgage disclosure? Trying to do both often results in a product that serves neither persona well.

The CCaaS Integration Play

As CI tools become more essential, the major CCaaS (Contact Center as a Service) providers are moving to bring these capabilities in-house. We have seen NICE, Genesys, and Five9 expand their native AI offerings to include conversation analytics. The logic is simple: if the intelligence layer lives outside the telephony platform, the platform becomes a 'dumb pipe.'

This trend is detailed in our analysis of why CCaaS giants are buying their way to AI relevance. For the independent CI vendor, this means the 'exit' is likely either an acquisition by a CCaaS incumbent or a deep integration that makes them the 'system of record' for a specific vertical, such as healthcare or collections.

FAQ

How does compliance CI differ from standard call recording?

Standard call recording merely stores the audio for manual review, while compliance CI, such as Hear.ai, uses AI to automatically analyze 100% of those recordings for specific regulatory violations, script adherence, and risk signals.

Why are investors moving toward 'defensive' CI tools?

Revenue-focused tools are often viewed as discretionary 'nice-to-haves' during budget cuts, whereas compliance and risk tools are considered 'must-haves' to avoid legal exposure and regulatory fines, making them more resilient in a down market.

Can one tool handle both revenue and risk?

While some platforms attempt to do both, the technical requirements differ significantly. Revenue tools prioritize speed and 'agent coaching' interfaces, while risk tools prioritize high-accuracy transcription, long-term audit logs, and integration with legal/compliance workflows.

What role does Forrester’s CX Index play in this market?

Forrester’s CX Index tracks how customer experience impacts brand loyalty; CI tools help brands maintain high scores by ensuring that agents follow the 'best practices' that lead to positive customer sentiment and trust.

As the CI market continues to bifurcate, founders and investors must decide if they are building for the 'offensive' revenue stack or the 'defensive' risk stack. To see how these categories fit into the broader ecosystem, explore our Mapping the CX-AI landscape: Categories and gaps.