Table of Contents
Churn is one of the most important signals product teams track.
PostHog makes it easy to see when churn happens.
Typical signals include:
• subscription cancellations
• declining retention
• users becoming inactive
• subscription downgrade patterns
Analytics clearly shows when users leave.
But it rarely explains why they leave.
Most teams try to investigate churn by:
• analyzing user segments
• reviewing support tickets
• sending cancellation surveys
• guessing what went wrong
The problem is that by the time feedback arrives, the user has already left and context is lost.
A better approach is to ask users why they cancelled at the moment churn happens.
This playbook shows how to use PostHog workflows and short interviews to capture real churn reasons from users.
• SaaS founders
• Product managers
• Growth teams
• Product analytics teams
Setup time
• about 5–10 minutes
Churn events appear clearly in analytics dashboards.
For example:
• subscription_cancelled
• trial_expired without conversion
• subscription_downgraded
These events show that users leave, but they do not explain the user’s decision.
Without direct feedback, teams often speculate about whether churn is caused by:
• pricing concerns
• missing features
• poor onboarding
• unclear product value
Understanding the real reason behind churn requires hearing directly from users.
This workflow starts when a cancellation event occurs.
Example event:
subscription_cancelled
This event typically fires when:
• a user cancels their subscription
• billing is terminated
• the cancellation confirmation page is completed
When the event fires, a PostHog workflow sends a short interview request to the user.
The workflow looks like this:
• subscription_cancelled event fires
• PostHog workflow sends a message to the user
• user receives a short interview link
• the user explains why they cancelled
• responses are summarized automatically
Instead of guessing the cause of churn, teams receive direct explanations from users who just left.
Even a few churn interviews can reveal clear patterns.
Teams often discover insights such as:
• pricing did not match perceived value
• a key feature was missing
• onboarding never delivered value
• the product was too complex for the user’s needs
These patterns are rarely visible through analytics dashboards alone.
A handful of conversations can quickly reveal the real drivers behind churn.
Keep cancellation interviews short so users can respond easily.
Example questions:
• What made you decide to cancel today?
• What problem were you hoping the product would solve?
• What could have made you stay?
These interviews typically take two to three minutes.
Short interviews capture richer context than traditional churn surveys.
Your PostHog workflow can send a short message when the cancellation event occurs.
Example message:
Subject: Quick question about your cancellation
• We noticed you recently cancelled your subscription.
• Could you share what led to that decision?
• It only takes about two minutes.
Include the interview link in the message.
Users can then quickly explain why they decided to leave.
Many products rely on cancellation surveys to understand churn.
However, surveys often produce limited insights.
Survey responses are shallow
Users frequently choose generic answers such as:
• too expensive
• missing features
• switching tools
These responses rarely explain the deeper context.
Short interviews allow follow-up questions that reveal more detailed motivations.
Survey responses are inconsistent
Some users skip surveys entirely, while others select the first option available.
Short conversational interviews tend to produce more thoughtful responses.
This workflow is especially valuable when:
• churn suddenly increases
• pricing changes are introduced
• new competitors enter the market
• retention metrics decline
Product teams can quickly investigate churn by capturing feedback at the moment users leave.
If you use PostHog, you can experiment with triggering short interviews when users cancel their subscription.
Even a small number of conversations can reveal patterns behind churn.
Try this workflow
Create a short interview and add the interview link to your PostHog workflow.
Create a short cancellation interview and add the interview link to your PostHog workflow.
Once users respond, you’ll begin seeing clear patterns behind churn.
Create interview
You can apply the same workflow approach to investigate other product signals:
• Investigate onboarding drop-off using PostHog workflows
• Understand feature abandonment using PostHog workflows
• How to Use PostHog Workflows to Understand User Behavior
Together, these playbooks help product teams move from tracking churn to understanding the reasons behind it.
