Why are customers churning?

Find which accounts are at risk and why, with the evidence to back it. Before the renewal call, not after.

Connect your data free

You find out why an account churned in the offboarding call, when it no longer matters. The warning signs were there for weeks, spread across calls that sounded fine and usage nobody was watching. The evidence existed. It was just never in one place.

Sample workspace
Which accounts are at risk of churning, and why?
PothAnalysis complete · 37 of 412 calls in the analysis cohort

This illustrative workspace flags onboarding risk before renewal. In the sample cohort, 12 of 19 current accounts are stalled, concentrated among accounts that never connected a data source .

Accounts at risk 12 stalled of 19

AccountRiskWhy
Brightquay TravelHighCall sounds fine; usage shows 0 imports in 21 days
Fernwell ClinicsHighStalled on CSV import; no data source connected
Copperline FreightElevatedWorkspace permissions request still sitting in IT review
Veldt & ChristyElevatedIT will not approve access until SSO is in place
Ostrander MediaWatchData connected, but nobody on their side knows the next step
+ 7 more stalled accounts, lower risk
  1. The riskiest account contradicts its own call. Brightquay Travel said onboarding went smoothly, but their usage shows zero imports in 21 days .
  2. Half of stalled accounts hit CSV import friction. Fernwell Clinics gave up when half their columns did not map and pushed the import to next sprint .

Priority: Review the missing data connection at Brightquay Travel and Fernwell Clinics before their renewal conversations. The joined sample records show that both accounts are stalled .

Calls sound fine. Usage tells the truth.

The call

Dan KowalskiBrightquay Travel

Onboarding call · Aug 3 · 22:05

“Honestly, onboarding went smoothly on our end.”

The usage

Imports per week · Brightquay Travel

0 imports in 21 daysusage contradicts call

Poth joins what every account says with what it actually does, at the account level. That join is where churn risk shows up early.

How it gets to your data

  1. Plug in what you already have

    Connect a supported source or import bounded files. Access follows the account, scope, and settings you authorize.

  2. Poth maps the evidence

    Imported calls, tickets, and rows get mapped to the customer they belong to.

  3. Ask your first question

    Answers come back cited, so you can check them.

GmailSlackNotionHubSpotSentryStripePostHog
Guided connectionPermission-bounded importsYour data stays yours

Your calls already have the answers