[ PLATFORM | CAUSE & EFFECT ]

Cause and effect, on one clock.

Competitor moves above the line, customer reaction below, and the measured lag between them. When RingCentral launched a free tier, SMB pricing complaints rose 31 mentions 8 days later, touching $214K of ARR.

LAG IS MEASURED, NOT ASSUMED · 8 DAYS · +31 MENTIONS · $214K ARR TOUCHED
[ 01 | WHAT CAUSE & EFFECT SHOWS ]

The one view no single-purpose tool can draw

Moves and reactions on one timeline

Recon's detected moves sit above the line. Chorus's mention volume sits below. The link between them is measured.

The lag, in days

Not “days later”. Eight days, measured from the move to the peak of the reaction, per theme.

The exposure, priced

Every reaction is tied to the accounts that raised it, so the exposure is an ARR figure and a renewal list, not a feeling.

[ 02 | HOW IT IS BUILT ]

Three agents, one clock

01 —

A competitor moves

Recon detects the move and scores it. It lands above the timeline the day it happens, dated and sourced.

COMPETITOR MOVEMAYJUNJULAUGRingCentral22 MAYFree RingEX tier for teams under 20 usersSCOREDCRITICAL
02 —

Customers react

8 days later, SMB pricing complaints rise by 31 mentions. Chorus links the reaction to the move that caused it.

CUSTOMER REACTION8 DAYSPEAK · +31 MENTIONSSMB pricing complaints31 MENTIONS · 12 ACCOUNTSLAG MEASURED, NOT ASSUMEDMENTIONS PER DAY · 90 DAYS
03 —

The exposure is priced

Atlas ties the reaction to $214K of ARR and the accounts renewing inside 60 days, each with an owned action.

ARR EXPOSURE$214KARR TOUCHEDTied to RingCentral's free tier, 22 May — not assumed.ACCOUNTS12RENEWING < 60 DAYS4OWNED ACTIONS3
[ 03 | INSIDE THE SURFACE ]

Built for the argument about why

Themes, competitors and accounts on the dashboard

Per-theme lag

Each theme gets its own measured lag, so you know which reactions are fast and which build over weeks.

Ninety days on one clock

Scroll back through every move and every reaction, with the links between them intact.

ARR touched

The revenue behind each reaction and the accounts renewing inside your window.

Owned actions

From a reaction to a drafted play, with an owner, in the Signal Desk.

Every point sourced

Click a move to see the competitor's page. Click a bar to see the mentions.

Ask about the cause

“What is behind the pricing spike?” The Signal Desk answers with the move, the lag and the exposure.

[ 04 | WORKS WITH ]

Connect a source, and it is on the orbit that night

Six of the 76 connectors this surface reads from. Each connects once over OAuth and is read continuously.

  • G2Connected
  • RedditConnected
  • Zendesk SupportConnected
  • IntercomConnected
  • SalesforceConnected
  • GongConnected
[ 05 | FAQ ]

Before you connect

How is the lag measured?

From the date Recon detects a move to the peak of the related theme's mention volume in Chorus. It is computed per theme, not assumed from a rule of thumb.

What if a reaction has no competitor behind it?

Then Cause & Effect says so. A rising theme with no cause is shown as exactly that, and the Signal Desk flags it for a human read.

Where does the ARR figure come from?

From Atlas. The accounts whose records make up the reaction are priced from your CRM and grouped by renewal window.

Can I export the view?

Every move, reaction and exposure is available in the case notes and through the API, with the sources attached.

Every signal, on one orbit

Connect your first source in an afternoon. The first pass lands before your next standup.

Book a demo