← All Examples
📊SaaS / ProductStandard

Churned Customer Exit Interview

Understand why customers leave before you can fix what's broken.

Sender: Product Manager at B2B project management SaaS
Participant: Head of PMO — Former customer, churned after 14 months, 35-seat account
This is an illustrative example showing how Willit could be used in saas / product. All names, quotes, and data are fictional. We never use real customer interviews for marketing purposes.
1

The Brief

The sender described what they wanted to learn. Willit's AI refined these instructions into a natural interview flow.

We just lost a 35-seat account that was with us for 14 months. This was a meaningful contract and we need to understand what happened — not just the surface reason they gave in the cancellation flow, but the actual story. The account lead's name is in the system. They were the primary champion internally and the person who ran our renewal conversation, which didn't go well. Please don't be defensive — I want this to feel like a genuine conversation, not a retention call we're too late to make. **Real reason for leaving:** The cancellation reason they selected was "switching to a competitor" — but I want to know what was actually going on. Was it a product issue, a budget issue, a champion change, a failed feature that mattered to them? Get to the specific thing that broke the relationship. **The trigger event:** Was there a specific moment when they decided to leave? A conversation, a bug, a missing feature, a support ticket that didn't get resolved? **What they actually used:** Which features were core to their workflow? Which ones did they never touch? I want to understand whether we lost them because we didn't deliver on something they cared about, or because they outgrew us. **Support experience:** Any significant support interactions? Did they feel heard when they reported issues? **What the competitor offered:** I'd love to know what specifically made the alternative compelling. Was it pricing, a specific feature, integrations? **What would have kept them:** Be direct with this one. If we'd done X differently, would they still be a customer? I want a real answer, not a consolation.
2

The Interview

Willit's AI detective conducted a standard interview with a Head of PMO. The conversation explored 5 topic areas through natural follow-up questions, adapting in real-time based on the participant's responses.

Understand the real reason for leavingIdentify the trigger eventUnderstand what features they usedUnderstand the competitor's appealDetermine what would have kept them
3

The Report

Willit automatically extracted structured insights from the conversation — scores, goal coverage, key quotes, and red flags.

Interview Scorecard

EngagementSentimentDepthQualityCoverageCoherence

Metric Averages

Engagement
74
Sentiment
45
Depth / Accuracy
81
Info Quality
83
Goal Coverage
85
Coherence
78

Summary

The customer churned primarily due to the absence of a native Jira integration, which became a hard requirement when their engineering team scaled from 8 to 25 people. The trigger event was a 6-week-old feature request going unanswered, which the Head of PMO interpreted as a signal that the product roadmap was not aligned with enterprise needs. The competitor (Linear) was chosen primarily for its developer-native workflow, not pricing.

Goal Coverage

Covered

Understand the real reason for leaving

  • Root cause was the lack of a native Jira integration — they built a Zapier workaround that broke repeatedly and eventually became untenable
  • Budget was not a factor — they explicitly said they would have paid more for the right tooling
Covered

Identify the trigger event

  • Filed a feature request for native Jira sync in month 11, marked as 'under review' — never received an update
Partial

Understand what features they used

  • Heavily used the timeline view and workload balancing features — these were cited as best-in-class
  • Never used reporting dashboards — felt they required too much manual setup

Gap: Did not explore usage of automation or template features

Covered

Understand the competitor's appeal

  • Chose Linear because it's developer-native — engineering team adopted it without being asked to change their workflow
Partial

Determine what would have kept them

  • A Jira integration shipped within the next 30 days would likely have prevented the switch

Gap: Did not explore whether a direct conversation with the PM would have made a difference before the switch decision was made

Key Quotes

“It wasn't about money. If you'd had the Jira integration working, I wouldn't even be talking to you right now, I'd just still be a customer.”
“Six weeks and not even an email. I started to feel like we were too small for you to care about.”
“The timeline view is still the best I've seen anywhere. That part I'll genuinely miss.”

Red Flags

  • Feature request process has no SLA or follow-up mechanism — customers submit requests into a black hole
  • AE misdiagnosed churn as price sensitivity when the actual driver was a missing integration — indicates a gap in discovery quality during renewal
  • Customer began evaluating alternatives 6 weeks before cancelling with no detection or intervention from the account team

Follow-up Suggestions

  • Audit feature request pipeline for requests older than 4 weeks with no status update — reach out proactively to those customers
  • Review all accounts using Zapier as a Jira bridge — they are at-risk
  • Have the AE team listen to this recording before their next renewal conversations to recalibrate what 'reasons for leaving' actually sound like

Ready to run your own AI interviews?

Set up your first interview in under 5 minutes.

Get StartedMore Examples