Walkthrough steps
Follow 1–4 below. Toggle signals, press Run evaluation, then read a task aloud—same rhythm as a customer call.
Who uses this
RevOps owns the signal pack and trust line. AEs / CS consume tasks in the inbox. VP Sales / CRO funds outcomes—expansion and risk conversations earlier—not another dashboard.
Before
The scoreboard lives in the warehouse. The team plays in Salesforce. Two worlds—late expansion, surprised churn, reps guessing who to call.
After
The same facts become one next step in the CRM: who, why now, suggested move—with a run log so RevOps can tune noise.
Account facts (read-only snapshot)
These rows are your account facts—usage change, seats, tickets, last active—in pilot they come from a scoped Snowflake view.
| Account | MRR | Usage Δ 30d | Seats | Last active | Open tickets | Owner |
|---|
Signal pack (your definitions)
These are your rules for “ready” and “at risk”—plain thresholds plus a sentence each so reps recognize the story. Toggle rules, then run. In production this runs on a schedule and is monitored.
Run evaluation — scan accounts and create or update tasks.
Salesforce-style tasks
One next step per moment—expansion or risk—not another feed. Reps live here; RevOps proves value from the run log.
Loading…
Audit trail
When rules ran, what fired, and for whom.
Runs appear here after each evaluation—this is the paper trail RevOps defends in QBRs.