Free Tool
The Customer Signal Stack Audit.
Fifteen questions about your CS data stack. Three minutes. At the end you get your signal map: which sources you're reading, which ones you're blind to, and where the cheapest wins are.
“There is no single place where those signals come together.” Start by finding out how many places yours are scattered across.
0 of 15 answered · Be honest — this only works if you are.
1 · CRM
Do you track champion and stakeholder role changes per account?
Title changes, sponsor departures, new economic buyers appearing.
2 · CRM
Do you monitor renewal close-date pushes as a risk signal?
A pushed close date is often the first commercial sign of trouble.
3 · CRM
Do you track days since last meaningful champion activity?
Not any activity — activity by the people who decide the renewal.
4 · Call transcripts
Are your customer calls recorded and transcribed?
Gong, Chorus, Fireflies — or any transcript pipeline.
5 · Call transcripts
Do you track who stops showing up to recurring calls?
Absence patterns appear before complaints.
6 · Call transcripts
Do you trend sentiment per account over time?
Tone shifts before language does — but only visible across 90 days.
7 · Support tickets
Do you track ticket sentiment, not just volume and CSAT?
Written frustration is deliberate — volume alone misses it.
8 · Support tickets
Do you compare ticket volume against each account’s own baseline?
A spike means nothing without the account’s normal.
9 · Support tickets
Do you flag cancellation-adjacent language in tickets?
“We’ve asked three times”, export questions, contract mentions.
10 · Product usage
Do you track per-account usage against its own peak?
Not logins — the account’s core workflow against its best month.
11 · Product usage
Do you monitor power-user activity individually?
Averages hide the two users whose departure predicts churn.
12 · Product usage
Do you track feature breadth — distinct features touched per month?
Breadth without depth is shelfware; depth without breadth is fragile.
13 · Billing
Do you track days-to-pay against each account’s own history?
Process delays vs intent changes — the history tells them apart.
14 · Billing
Do you monitor seat or ARR contraction before renewal?
Contraction usually precedes the churn conversation.
15 · Relationship
Do you track champion responsiveness — reply latency or participation patterns?
Responsiveness is a measurable proxy for priority.
Answer all 15 questions to see your results.
Questions, answered honestly.
What does the audit actually measure?
Coverage across the six sources where churn, renewal, and expansion signals live: CRM, call transcripts, support tickets, product usage, billing, and the relationship layer. Each question maps to real detection logic — the same logic in our signal library.
Is my data uploaded anywhere?
No. The entire audit runs in your browser. Nothing is sent to any server — close the tab and it is gone.
What do I do with the results?
The three blind spots are ordered by impact, each linked to the signal guide for that source with concrete detection logic. If you want the full version — us reviewing your actual stack instead of a questionnaire — that's the $1,500 Signal Stack Audit engagement, delivered in 3 business days.
How honest should I be?
Completely. 'Partially' means it exists but nobody trusts it, or it covers some accounts but not others. The audit only works if the answers reflect reality, not the roadmap.