25 JTBD Switch Interview Prompts for Churn (Script)

As an Amazon Associate I earn from qualifying purchases. Product links on this page are affiliate links — they cost you nothing extra.

⏱ 37 min read

The Core Mechanics of a JTBD Churn Switch Interview

A Jobs to be Done (JTBD) churn switch interview diagnoses customer defection by treating cancellation as an active decision to hire a different solution. Instead of recording opinion scores, an interviewer reconstructs the chronological timeline of events, emotional milestones, and trade-offs that pushed a buyer from your product toward an alternative. Uncovering the exact causal triggers along this timeline reveals why your product failed to deliver progress, showing product teams exactly what to fix.

A switch interview is a structured qualitative research method developed by Bob Moesta and Chris Spiek that unpacks the precise chain of events leading a customer to fire one product and hire another. Standard cancellation workflows fail to capture this reality. According to Bain & Company research on customer experience, over 60% of defecting customers claim to be "satisfied" or "neutral" on traditional exit surveys right before leaving.

When a user clicks a cancellation radio button marked "Too expensive" or "No longer needed," they give you a polite rationalization. It is the path of least resistance during an awkward exit. A customer rarely leaves solely because a price increased by $10 a month. They leave because a critical workflow broke three weeks earlier, an internal stakeholder demanded a custom report your tool could not generate, and a competitor offered a native integration that saved their team 5 hours every Friday. Traditional exit surveys capture the final excuse; a 60-Minute JTBD Switch Interview (Script & Canvas) captures the systemic failure.

To build an accurate churn diagnostic, you must track the four simultaneous forces that govern every switching decision, formulated by the Re-Wired Group:

     PUSH OF CURRENT PAIN
               +
    PULL OF NEW SOLUTION
               v
     [SWITCH DECISION]
               ^
               +
     ANXIETY OF THE NEW
               +
      INERTIA OF HABIT

Two forces promote the switch, while two forces hold the user back:

1. The Push of Current Situation: The acute frustrations, software bugs, or workflow bottlenecks with your product. A single bad day rarely causes churn, but three consecutive billing cycles with recurring export errors generate an irresistible push.
2. The Pull of the New Solution: The appeal of an alternative approach, whether that is a competitor like HubSpot, a dedicated spreadsheet, or hiring an external agency. The user imagines a better reality where their operational friction disappears.
3. The Anxiety of the New Solution: The buyer’s fear of switching costs, onboarding delays, team pushback, or learning curves. You can isolate these doubts using a focused JTBD Anxiety Script: Uncover Hidden Fears (Cheat Sheet) during customer conversations.
4. The Inertia of Habit: The gravitational pull of current routines, existing data setups, and sunk setup time. Inertia keeps unhappy customers paying for your software for an average of 4 to 6 months after they first consider cancelling.

A customer cancels only when the combined energy of the Push and the Pull overpowers the combined resistance of Anxiety and Inertia. By viewing churn through these forces, product leaders stop guessing at feature requests and begin diagnosing genuine Customer Needs and JTBD.

Unpacking these four forces requires asking precise chronological questions that pull real memories past the customer’s polite social filters, starting with the exact prompt that exposes their first thought of leaving.

Table of Contents

• The Core Mechanics of a JTBD Churn Switch Interview
• Mapping Customer Cancellation Timelines from First Thought to Action
• Setting the Stage to Extract Objective Behavioral History
• Deconstructing the Initial Push Away from Your Product
• Evaluating the Pull of Competing Solutions and Workarounds
• Capturing the Breaking Point and Cancellation Moment
• Translating Switch Data into Retention and Product Strategy
• The Complete 25-Prompt Churn Interview Cheatsheet and Script
• Sources & Further Reading

Mapping Customer Cancellation Timelines from First Thought to Action

Mapping a customer cancellation timeline requires reconstructing six sequential milestones between the initial moment of friction and the final account deactivation. Customers rarely cancel software or services on a whim. The decision builds across distinct psychological stages over weeks or months, following the behavioral mechanics codified by Bob Moesta and Chris Spiek at The Re-Wired Group.

The six milestones occur in a predictable order:

1. First Thought: The very first time a user feels a pinch, disappointment, or friction with the current solution.
2. Passive Looking: The user does not search actively, but their radar is up; they notice competitor ads, colleague recommendations, and industry chatter.
3. Event One: A specific operational catalyst occurs—a failed export, an unexpected price increase, or a team re-org—that converts low-grade frustration into an active assignment.
4. Active Looking: The customer dedicates time to research alternatives, signs up for trials, and books sales demonstrations.
5. Deciding: The customer selects a replacement, navigates budget or stakeholder approvals, and decides how to handle the cutover.
6. The Final Switch: The customer exports their data, cancels their subscription, and starts running work in the new tool.

[First Thought]
      |
      v
[Passive Looking]
      |
      v
 [Event One]
      |
      v
[Active Looking]
      |
      v
  [Deciding]
      |
      v
[Final Switch]

To reconstruct these six phases accurately, you must bypass customer rationalisations using episodic memory reconstruction.

Episodic memory reconstruction is a cognitive recall technique where an interviewer prompts a subject to retrieve specific autobiographical events by anchoring questions to physical locations, times, and sensory cues rather than general impressions.

Cognitive psychologist Endel Tulving established that human memory separates semantic memory (general facts and opinions) from episodic memory (concrete events tied to time and place). When you ask a churned customer, "Why did you cancel?", they access semantic memory. They hand you polite, canned abstractions: "It was too expensive," or "We lacked adoption." These answers are useless for product innovation.

Instead, ask: "Where were you sitting when you first realised you needed an alternative?" or "What was on your screen right before you told your manager this wasn’t working?" When a respondent recalls that it was a rainy Tuesday afternoon in October, that they were looking at a broken CSV export, and that their desk fan was buzzing, their brain accesses the exact sensory trace of the event. The real sequence of motives emerges intact. You can structure this interview pacing directly using a 60-Minute JTBD Switch Interview (Script & Canvas).

To capture accurate episodic data, your recruiting window must be precise: target accounts that cancelled between 30 and 60 days prior.

Accounts that cancelled under 30 days ago are still experiencing the emotional residue of the cutover or dealing with pending billing items; their feedback is defensive and reactive. Accounts that cancelled over 60 days ago suffer rapid decay in episodic memory detail. Within that 30-to-60-day window, customers have fully adopted their new alternative and can objectively contrast the two realities without cognitive drift. Aim for a sample size of 10 to 12 completed interviews per customer segment to achieve theoretical saturation.

Before scheduling your calls, classify the cancellation speed to calibrate your timeline probes.

Sorting churned accounts through this matrix prevents you from treating a three-month multi-stakeholder migration the same way as an overnight platform crash. It also helps you isolate the emotional push factors from the pull of a competitor, especially when paired with a targeted JTBD Anxiety Script: Uncover Hidden Fears (Cheat Sheet).

Understanding whether a customer simmered for 90 days or jumped ship in 48 hours determines which questions you must ask to unlock the exact words they used when deciding to walk away.

Setting the Stage to Extract Objective Behavioral History

A successful churn interview requires you to act as an unattached crime-scene investigator rather than a product representative defending a platform. When customers cancel a contract, exit surveys capture polite rationalizations rather than operational facts.

A switch interview is a structured qualitative research method designed to reconstruct the exact timeline, emotional triggers, and trade-offs that caused a customer to abandon one solution and purchase another. In research conducted by Bob Moesta and Chris Spiek at The Rewired Group, buyers routinely reported price or missing features as their cancellation reason, yet detailed timeline reconstruction revealed the true catalyst was an internal workflow breakdown that started months earlier.

To extract the unvarnished sequence of events, tell the customer directly that you are not there to win them back or defend previous roadmap decisions. Explain that your role is to document the raw operational history so the organization understands where systems fail in daily use. When a user realizes you will not counter their objections with product pitches, their defensive guard drops.

Gaining genuine behavioral data requires explicit psychological safety. Enterprise buyers hide rogue spreadsheets, shadow IT subscriptions, and team political disputes because these workarounds violate company policy or reflect poorly on their leadership. Clarify in the first 3 minutes that all answers are anonymized and that imperfect processes are standard across every industry. When uncovering operational trade-offs, standard survey questions fail; you must isolate the gap between organizational intention and actual behavior, a core principle in Customer Needs and JTBD.

Run these first 5 verbatim prompts to establish the initial operational baseline and expose the early fractures in the account:

• Prompt 1 (Anchor to the buy): "Take me back to the week you first signed the contract for this product—what exact problem was keeping your team late at the office that Friday?"
• Prompt 2 (First-day reality): "On the first Monday your team was supposed to log into the software, walk me through what actually happened versus what you planned in your rollout schedule."
• Prompt 3 (Shadow systems): "When the primary tool did not handle a specific edge case during those first 30 days, what Excel sheet, Google Doc, or secondary tool did the team quietly build to keep work moving?"
• Prompt 4 (Internal friction): "Who on the team pushed back hardest against using this tool during the first 60 days, and what specific task were they trying to protect from disruption?"
• Prompt 5 (Initial compromise): "What was the very first compromise you made where you said, ‘This isn’t ideal, but we can live with it for now’?"

These baseline prompts build on the sequencing in the 60-Minute JTBD Switch Interview (Script & Canvas) to anchor the conversation in verifiable actions rather than hindsight opinions. When users describe workarounds, probe for the emotional friction that accompanied them; you can systematically map these doubts using the JTBD Anxiety Script: Uncover Hidden Fears (Cheat Sheet).

Tracking the customer’s initial trade-offs exposes the fault lines that eventually cause an account to collapse. The moment an employee opens an untracked spreadsheet to bypass a core platform workflow, the clock on customer churn begins ticking.

Once you establish this operational baseline, the next step is uncovering the sudden micro-events that turn minor team frustrations into an active search for a replacement product.

Deconstructing the Initial Push Away from Your Product

Customers do not decide to cancel an enterprise contract on the renewal date; they make the emotional decision months earlier during a specific triggering event called the First Thought.

The first thought is the initial moment an individual user realizes their current situation is no longer acceptable, creating a mental marker that transforms ordinary product friction into an active desire for change.

Research by retention analytics firm ProfitWell shows that the average B2B subscription switch takes 84 days between that initial moment of dissatisfaction and the actual cancellation. During those 12 weeks, the customer enters what Bob Moesta, co-creator of the Jobs to Be Done framework, defines as passive looking. In this state, an account executive does not book demos or review competitors, but they notice alternative software names on LinkedIn, scan competitor booths at conferences, and talk to peers over coffee about how their teams solve reporting bottlenecks.

Platform Friction vs. Structural Business Shifts

Interviews frequently fail because product leaders confuse a minor software defect with a root cause. You must determine whether the push came from acute platform friction or a fundamental shift in the customer’s operating model.

Acute friction is tactical: an export timed out on a quarterly closing day, or a user interface redesign hid the bulk-tagging button. When acute friction occurs in a stable business, users log support tickets or complain in Slack.

[Trigger Event Occurs]
       |
       v
[Acute Friction?]
       |-- YES --> Logged ticket, annoyed
       |
       v NO
[Shift in Core Priority?]
       |-- YES --> First Thought of leaving
       |
       v
[Passive Looking Phase: ~84 Days]
       |
       v
[Active Vendor Evaluation]

Structural shifts are strategic: a new vice president joins, company leadership cuts headcount by 20%, or the executive team mandates a consolidation onto Microsoft Azure. In Gartner’s 2023 B2B Buyer Survey, Gartner reported that 61% of software buyers initiated vendor reviews due to internal organizational restructurings rather than direct product performance failures. When organizational priorities shift, software that worked adequately yesterday suddenly fails to align with today’s operational mandate.

Connecting these organizational pivots to the initial customer journey requires running a disciplined 60-Minute JTBD Switch Interview (Script & Canvas) that reconstructs the timeline before the customer’s memory fades.

Verbatim Prompts: Isolating the First Push (Prompts 6–11)

To uncover the precise origin of the switch, treat the customer as an eyewitness in a courtroom reconstruction. General summaries ("our reporting was slow") provide zero actionable product intelligence. You need the calendar date, the physical room, the monitor setup, and the task that failed.

To anchor these timelines, practitioners rely on structured interview protocols outlined in Bob Moesta and Chris Spiek’s foundational demand-generation guides.

Use these verbatim prompts in sequence:

Prompt 6: Anchoring the Chronology

"Cast your mind back to the very first moment you thought, ‘We might need to find another way to do this.’ What month was that, and where were you physically sitting?"

Goal: Force the respondent away from generic complaints and into episodic memory. Look for physical markers: a home office desk, a hotel room during an offsite, or a whiteboard room at 7:00 PM.

Prompt 7: The Immediate Trigger

"Take me to the 10 minutes immediately before that thought crossed your mind. What specific deliverable were you trying to complete?"

Goal: Isolate the direct workflow. Customers do not churn on "analytics"; they churn because an executive needed a board slide showing regional pipeline conversions by 9:00 AM and the export button stripped out the custom fields.

Prompt 8: The Interpersonal Context

"Who else was in the room or on the Slack thread with you right then, and what did you say to them?"

Goal: Identify the social dimension. Churn is rarely a solo decision in business-to-business environments. The push solidifies when a user vents to a colleague, because verbalizing dissatisfaction commits them to finding a fix. For deeper social and emotional discovery, cross-reference the JTBD Anxiety Script: Uncover Hidden Fears (Cheat Sheet).

Prompt 9: Platform Friction vs. Business Pivot

"At that exact time, had the product changed, or had what your leadership demanded of your team changed?"

Goal: Cleanly separate internal business shifts from platform deficiencies. If the buyer says, "Our team doubled and we had to split accounts across three regions," the failure was an administrative scale limitation, not an interface bug.

Prompt 10: The Workaround Audit

"What quick patch or workaround did you build that afternoon to get past the problem so you could finish your day?"

Goal: Uncover competitive indicators. When customers start pasting your application’s data into Google Sheets, Airtable, or custom Python scripts, they have formally decoupled from your product’s core value proposition.

Prompt 11: The Shift to Passive Looking

"Right after that happened, what was the very first action you took to see what else existed, even if you weren’t ready to buy yet?"

Goal: Pinpoint where they look for alternatives. Did they ask a peer community, search a term on Google, or open a cold outbound email they had ignored for three weeks?

Pinpointing this initial push clarifies why the customer drifted away, setting up the exact sequence of events that led them to evaluate a competitor.

Evaluating the Pull of Competing Solutions and Workarounds

Customers evaluate competing solutions against their current hacks and non-consumption, not just direct commercial rivals. In his foundational research at the Clayton Christensen Institute, Clayton Christensen defined non-consumption as the state where individuals cannot resolve a problem because existing solutions are too expensive, complex, or inaccessible. When a buyer decides to churn, they rarely jump straight to your closest software competitor. They weigh vendor demos against a Google Sheet, an existing enterprise license, or simply tolerating the error rate.

A consideration set is the small group of viable alternatives a buyer seriously evaluates when trying to resolve a specific operational bottleneck. This group regularly combines enterprise commercial software, internal manual habits, spreadsheet workarounds, and the baseline choice to do nothing at all.

Gartner’s research into B2B buying journeys found that a typical buying group involves 6 to 10 decision-makers, each armed with 4 to 5 pieces of information they gathered independently. When team members bring competing tools to the table, internal politics shape the outcome far more than product feature checklists. One manager defends their custom 4-year-old macro, while a department head pushes for an enterprise vendor they used at a previous job. To run an effective 60-Minute JTBD Switch Interview (Script & Canvas), you must reconstruct how these internal factions argued, tested, and eliminated options during the trial.

Tracking Internal Champion Defense and Workflow Inertia

Every replacement software threatens someone’s established expertise. When an employee spends 3 years mastering an awkward tool, their mastery gives them institutional authority. That employee will actively defend the legacy process against outside software, even when the legacy process costs the business 15 hours of manual work every week.

In their Switch Framework research at the Re-Wired Group, Bob Moesta and Chris Spiek established that "Habits of the Present" create an intense drag against any new purchase. During churn discovery, your objective is to pinpoint the exact moment this defense broke down. Did the legacy champion leave the company? Did an executive issue a hard mandate? Or did a single catastrophic failure, like a missed compliance audit or a lost $50,000 client, strip away their credibility? When you use JTBD for Identifying Unmet Needs in Innovation, uncovering these friction points reveals the true threshold required to force an account to switch.

Verbatim Prompts 12 Through 17: Consideration, Trials, and Bake-Offs

Deploy these 6 prompts in sequence once you establish the first moment of dissatisfaction. They unpack how the buyer surveyed the market, who defended the old way, and how the bake-off played out.

• Prompt 12 (Discovery Channels): "Take me back to the day you opened a browser tab to look for alternatives. What exact terms did you type into the search bar, or who was the first person you messaged on Slack?"
• Prompt 13 (Workarounds vs. Software): "Before you looked at commercial tools, what internal hacks, spreadsheets, or manual handoffs did the team build to fix this on your own?"
• Prompt 14 (Status Quo Defense): "Who on the team pushed back the hardest against bringing in something new, and what specific nightmare scenario did they predict would happen if you switched?"
• Prompt 15 (Trial Setup Friction): "During the 14-day trial period of the product you evaluated, what was the very first piece of real company data you imported to prove it could handle your workload?"
• Prompt 16 (The Bake-Off Dynamic): "When you put [Your Product] and [Competitor] side by side, what was the single test scenario where one clearly failed while the other passed?"
• Prompt 17 (The Concession Moment): "What was the tipping point where the colleague who defended the old process threw their hands up and agreed to abandon it?"

Pair these questions with targeted follow-ups from our B2B Discovery Interview: 15 Questions (With Script) to separate product defects from change-management fatigue.

INTERVIEWER: "You mentioned you didn't look at other tools. 
When [INCIDENT] happened, what would have occurred if 
leadership told you that you had $0 budget for software?"

RESPONDENT: [Explains their manual fallback or Excel sheet]

INTERVIEWER: "Walk me through that manual process. 
How many hours each week did [ROLE] spend 
copying data between [SOURCE A] and [SOURCE B]?"

RESPONDENT: [Quantifies hours or error rates]

INTERVIEWER: "Who built that sheet, and why was 
management comfortable running a core process on it 
until [MONTH]?"

INTERVIEWER: "When [DEPARTMENT HEAD] voiced concerns 
about migrating away from [OLD SYSTEM], what were 
they personally worried about losing control over?"

RESPONDENT: [Describes pushback or security/operational fear]

INTERVIEWER: "At what point in the trial did they agree 
to test real data? What exact proof did they demand 
before granting access to the team?"

RESPONDENT: [Identifies the gating criteria]

INTERVIEWER: "Did they ever fully buy into the switch, 
or were they overruled by [EXECUTIVE ROLE]?"

INTERVIEWER: "Set the scene for the final decision meeting. 
Who was in the room, and which two tools were on the table?"

RESPONDENT: [Names the final vendors and attendees]

INTERVIEWER: "When you drew the final comparison, what was 
the single deal-breaker feature that disqualified 
[LOSING VENDOR] in the final 48 hours?"

RESPONDENT: [States the critical technical or commercial flaw]

INTERVIEWER: "If [LOSING VENDOR] had matched that capability, 
would the team have stayed, or was the decision already made?"

Once you determine how the customer evaluated alternative options, you must isolate the final push that made staying impossible. The next diagnostic layer requires examining the specific event that broke the customer’s patience and made renewal completely off the table.

Capturing the Breaking Point and Cancellation Moment

Customers do not cancel software contracts because of general frustration; they cancel because a distinct operational shock forces an immediate administrative decision. In Jobs to Be Done theory, this turning point is known as Event Two.

In Jobs to Be Done theory, Event Two is the acute operational crisis, deadline, or budget shock that forces a customer to permanently abandon their current solution and commit to a change.

While Event One creates the initial curiosity to look for alternatives, Event Two breaks the customer’s inertia. A study of 2,100 subscription companies conducted by ProfitWell found that 72% of non-payment voluntary cancellations were precipitated by an acute budget review or a high-visibility operational failure within the preceding 14 days. When running a churn analysis, you must pinpoint the calendar date, the people in the room, and the failure that caused the cancellation.

Isolating Event Two: The Operational Shock

To uncover Event Two, ask the customer to recreate the 48 hours leading up to their final cancellation. Customers often default to vague summaries such as "the software was too expensive" or "we needed more features." Push past those summaries to isolate the mechanical failure.

Was it a quarterly board presentation where a dashboard failed to render? Did a billing run fail on the 1st of the month, locking out 350 active accounts? Did the Chief Financial Officer issue a mandate to cut SaaS expenditure by 15% before Friday at 5:00 PM?

You can map these moments cleanly against the complete timeline outlined in the 60-Minute JTBD Switch Interview (Script & Canvas). As Bob Moesta and Chris Spiek documented in their foundational switch research at The Re-Wired Group, customers often endure terrible software for months. They only switch when the cost of enduring the problem suddenly exceeds the friction of switching.

Documenting the Physical Exit Mechanics

Once you identify the catalyst, document the physical mechanics of the cancellation. Software churn does not happen inside an abstract vacuum. It involves specific browser tabs, export buttons, procurement tickets, and internal resistance.

Track the administrative route the customer took. Did they search the application settings for 20 minutes trying to locate a hidden "Delete Account" button? Did your platform require them to schedule a mandatory 15-minute exit phone call with a customer success manager?

According to research published by the Harvard Business Review on customer experience, deliberate friction in cancellation paths increases customer resentment and permanently eliminates referral opportunities. Capturing the operational pain of exiting exposes gaps in your product governance and clarifies true customer needs and JTBD.

Trigger: Event Two Occurs
       │
       ▼
Internal Sign-off Required
       │
       ▼
Data Export & Migration
       │
       ▼
Physical Cancellation Action
       │
       ▼
Immediate Emotional Reaction

Verbatim Prompts 18 Through 22

Use these exact prompts to unpack the operational breaking point and offboarding reality.

• Prompt 18 (The Tipping Event): "Take me back to the exact day you decided you were finished with the product. What task failed five minutes before you said, ‘We are done’?"
• Prompt 19 (The Internal Clearance): "Whom did you have to convince inside your company before you could pull the plug, and what specific evidence did they require?"
• Prompt 20 (The Physical Cancellation): "Walk me through the actual steps you took to cancel: who clicked the button, what page were you on, and did you have to contact support?"
• Prompt 21 (The Offboarding Friction): "What happened to your historical data when you left? What friction or data loss did you encounter while exporting your records?"
• Prompt 22 (The Immediate Aftermath): "In the 15 minutes immediately after the cancellation confirmation hit your inbox, what was the dominant feeling: relief, anxiety, or regret?"

Prompt 22 uncovers the residual anxiety of the switch. If the dominant emotion was anxiety about data loss, examine the safety nets in your offboarding flow using the strategies in the JTBD Anxiety Script: Uncover Hidden Fears (Cheat Sheet). If the dominant emotion was pure relief, your product had become an active obstacle to their workday weeks before they clicked cancel.

Once you have documented these cancellation mechanics, the next step is calculating the net energy cost required to push that churned user into their replacement solution.

Translating Switch Data into Retention and Product Strategy

Raw switch interview transcripts become operational retention strategy only when you categorize customer quotes into the four dynamic tensions of the Forces of Progress framework. The Forces of Progress matrix is a diagnostic tool created by Bob Moesta and Chris Spiek that maps two opposing energies: the push of current problems and pull of a new solution against the inertia of old habits and anxiety of change. Without this structure, product teams treat churn feedback as an unstructured complaint list.

Mapping Quotes to the Four Forces

To make raw qualitative quotes actionable, sort every statement from your interview transcripts into four distinct quadrants. Review your notes from the 60-Minute JTBD Switch Interview (Script & Canvas) and tag each customer statement:

1. The Push (Current Pain): The internal frustration with the old way. Example: "Generating weekly pipeline reports in Salesforce took our team 4 hours every Monday."
2. The Pull (New Solution): The appeal of the alternative product. Example: "Their automated HubSpot dashboard promised instant reporting without manual exports."
3. The Anxiety (Hesitation): The worry felt before switching. Example: "We were terrified that 6 months of historical lead attribution would be lost in migration."
4. The Inertia (Habit): The comfort of existing behavior. Example: "Our reps already knew the keystrokes and refused to learn another interface."

[ PUSH ] (Old Pain)  -->
                      \
                       [ DECISION TO SWITCH ]
                      /
[ PULL ] (New Hope)  -->

[ INERTIA ] (Old Habit)   <-- Blocks
[ ANXIETY ] (Fear of New) <-- Blocks

A switch only occurs when the combined energy of Push and Pull outweighs Inertia and Anxiety. In their 2016 book Competing Against Luck, Clayton Christensen and co-authors noted that customers do not simply buy products; they "hire" them to make progress in specific circumstances. When a user churns, your product either failed to generate enough pull or spiked their anxiety during execution.

Diagnosing the Root Cause: Onboarding, Pricing, or Marketing

Most churn surveys show "too expensive" or "missing features" as the top cancellation reasons. In practice, these surface tags conceal three operational breakdowns: onboarding gaps, pricing misalignment, or false marketing expectations.

Differentiate them by examining the customer’s timeline:

• False Marketing Expectations (Day 1 to 14): The buyer cancels early because the software solves a different job than advertised. If the customer bought based on an ad promising "automated financial reconciliation" but found out the tool requires manual CSV mapping, the root cause sits with growth marketing. The marketing team manufactured an artificial pull that the product cannot satisfy.
• Onboarding Gaps (Day 15 to 45): The customer understood the promise, but implementation stalled. ProfitWell analyzed 25,000 subscription software companies and found that customers with poor onboarding experiences display a 10% to 16% drop in retention within the first two months. When an interview reveals quotes like "We never figured out how to set up the webhooks," product and customer success must patch the setup workflow rather than adding new features. Use a targeted JTBD anxiety script to uncover hidden fears when users get stuck mid-setup.
• Pricing Misalignment (Day 60+): The user extracts value, but the pricing metric does not scale with their internal metrics. If an agency adds 15 clients and their software cost jumps by 400% before client revenue clears, they will defect to an enterprise competitor with flat licensing. The problem is not the total dollar amount; it is the charging mechanism.

Verbatim Prompts 23–25: Measuring Competitor Delivery and Regret

The final phase of the switch interview investigates the customer’s current reality. By asking about their immediate experience with the replacement provider, you identify where the competitor succeeded and where they left an opening for a win-back campaign. This is essential for uncovering customer needs through JTBD.

Prompt 23: The Reality Check

"Now that you have been using [Competitor Product] for a few weeks, what task turned out to be harder to do than you expected during the demo?"

This prompt bypasses the buyer’s honeymoon bias. When users justify a vendor change to their leadership, they defend their decision publicly. Prompt 23 asks for functional friction, revealing where the competitor oversold. If 8 out of 10 churned customers cite complex permission settings in the new tool, your marketing team gains an immediate counter-positioning hook.

Prompt 24: The Unresolved Friction

"Think back to the exact problem that caused you to start shopping. How much of that specific issue is actually resolved today versus simply moved somewhere else?"

Most software switches merely trade one set of operational headaches for another. A company leaving Zendesk for Front might solve collaborative email drafting while losing enterprise SLA tracking. Identifying the remaining gap lets you track latent industry requirements.

Prompt 25: The Regret Test

"If your team was forced to reverse this decision tomorrow morning, what specific capability from our product would you fight hardest to keep?"

This question identifies your true core value. Churned customers often dismiss your entire application during cancellation surveys. When pressed on what they genuinely miss, they single out specific micro-features—such as single-click exports or specific sub-second search speeds—that you can protect on your product roadmap.

Synthesizing these responses gives you the exact trade-offs driving your market right now, which directly informs how you score and prioritize upcoming features on your roadmap.

The Complete 25-Prompt Churn Interview Cheatsheet and Script

A successful churn switch interview extracts the chronological narrative of why a customer fired your product, tracing the decision back to the very first moment of friction.

A switch interview is a structured qualitative research technique that treats customer churn or adoption as an event-driven purchase journey rather than a satisfaction score. It pinpoints the exact forces that pushed a buyer away from an existing product toward an alternative.

According to research published by Bob Moesta and Chris Spiek in their foundational work with The Rewired Group, customer switches are never impulse decisions. They are systemic progressions driven by four competing forces: the push of the current situation, the pull of a new solution, the anxiety of the new choice, and the habit of the present. When analyzing churn, standard exit surveys fail because they collect post-rationalized opinions rather than forensic facts. To uncover the real operational triggers, you need to reconstruct the timeline using our 60-Minute JTBD Switch Interview (Script & Canvas) and the verbatim prompts detailed below.

The 25-Prompt Verbatim Churn Script

Run this interview within 14 to 30 days of a customer cancellation. If you wait past 45 days, memory decay degrades the factual accuracy of their timeline. Conduct the conversation as an investigative reporter would: avoid asking "why" directly, because "why" invites rehearsed theories. Instead, ask "what happened next" to uncover actionable facts about uncovering latent needs with JTBD.

SWITCH TIMELINE FLOW
│
▼
[1. First Thought]
│
▼
[2. Passive Looking]
│
▼
[3. Active Looking]
│
▼
[4. Deciding to Switch]
│
▼
[5. Post-Switch Reality]

Phase 1: The First Thought (Prompts 1–5)

Capture the baseline and identify the very first crack in the relationship.

1. "Take me back to the day you first realized this tool was no longer working for your team. Where were you, and what were you working on?"
2. "What was the specific task or deliverable on your desk that afternoon that stalled?"
3. "Who was the first colleague you spoke to about that problem, and what did you say to them?"
4. "Before that moment, how long had that specific issue been happening without anyone mentioning it?"
5. "What was the workaround your team built to keep working that day?"

Phase 2: Passive Looking (Prompts 6–10)

Map the period where dissatisfaction grew, but inertia kept the customer in place.

6. "After that day, what other small inconveniences started piling up during normal operations?"
7. "When you noticed those problems, did you search for other software, or did you assume you were just using our system incorrectly?"
8. "Did you read any articles, ask peers on LinkedIn or Slack communities, or attend a webinar around that time to see how other teams solved this?"
9. "What was the internal conversation when renewal or invoice payment came up during this period?"
10. "What kept you from canceling right then and there?"

Phase 3: Active Looking (Prompts 11–15)

Isolate the catalytic event that converted passive annoyance into dedicated budget and calendar time.

11. "What happened on the exact day you decided: ‘We must replace this system now’?"
12. "Did an executive mandate this change, did a project fail, or did a team member resign?"
13. "What were the first two or three alternative tools you opened in your browser that week?"
14. "Who set up the evaluation criteria, and what specific capability sat at the top of that list?"
15. "How did you balance the time spent vetting replacements against your everyday project workload?"

Phase 4: Deciding and Switching (Prompts 16–20)

Document the evaluation hurdles, the trade-offs made, and the financial transition. For deeper analysis of buyer hesitation during this step, review our JTBD Anxiety Script: Uncover Hidden Fears (Cheat Sheet).

16. "When you tested the replacement solution, what almost stopped you from moving forward with them?"
17. "What internal approvals, security reviews, or budget reallocations were required to execute the switch?"
18. "What did the new vendor show you in their demo that made your team say, ‘That solves it’?"
19. "What existing workflows or data did you have to leave behind or manually rebuild during migration?"
20. "Walk me through the literal conversation or email where you told your team you were officially turning our tool off."

Phase 5: Ongoing Use and Post-Switch Reality (Prompts 21–25)

Compare the buyer’s original expectations against their current operational reality to separate true product gaps from misaligned positioning.

21. "Now that your team has used the new system for 30 days, what task is genuinely faster?"
22. "What unexpected friction or new headaches surfaced with the replacement tool that you did not anticipate?"
23. "If you could bring one specific workflow from our product over to your new setup, what would it be?"
24. "How is your leadership team evaluating whether the switch was worth the migration cost?"
25. "If our software had solved that single original breakdown, would you still be paying for our subscription today?"

The 1-Page Timeline Tracking Grid

Do not take standard narrative meeting notes during the call. Place this four-quadrant matrix on a single sheet of paper in front of you. As the customer speaks, map their comments into the quadrants established by the Jobs to Be Done framework described in Clayton Christensen’s Competing Against Luck. This separates internal resistance from external pull factors in real time.

During the call, keep your pen moving between these quadrants. If your grid shows 10 notes under "Push" but zero notes under "Anxiety", pause the chronological march and ask prompt 16. A switch never happens without overcoming anxiety; missing it means the customer is giving you an abridged, polite story. To structure these inquiries across enterprise accounts, reference our framework for the B2B discovery interview: 15 questions.

Choose-Your-Path Scenario: The Mid-Market Churn Crisis

The 30-Minute Post-Interview Analysis Protocol

A customer switch interview loses 50% of its utility if raw notes sit unread in a customer relationship management (CRM) database. To convert narrative data into roadmap priorities, gather one product manager, one customer success lead, and one product designer for a synchronized, 30-minute debrief immediately following the call.

POST-INTERVIEW TIMELINE
│
├── 00:00 - 00:05 (Clean Verbatim Quotes)
│
├── 00:05 - 00:15 (Map The Four Forces)
│
├── 00:15 - 00:25 (Isolate The Firing Trigger)
│
└── 00:25 - 00:30 (Assign Product Action)

Minutes 00:00–00:05: Clean the Verbatim Quotes

The interviewer reads aloud the three most significant quotes captured during the call. Team members write down factual observations on individual sticky notes or digital cards. Discard speculative remarks like "The client felt overwhelmed" and replace them with observable events like "The client had to export 4 CSVs every Monday morning because the scheduled report failed." For continuous discovery alignment, ground these observations in your ongoing work with customer needs and JTBD.

Minutes 00:05–00:15: Map the Four Forces

Place the observations into the four-forces quadrant. Measure the tension:

• Did the Push build over 6 months or snap in 24 hours?
• What specific promise created the competitor’s Pull?
• What Anxiety almost saved the account? (This highlights your product’s strongest retention moats).
• What Habit finally broke?

A study on software switching dynamics by ProfitWell (now Paddle) analyzing over 2,000 subscription companies found that price increases accounted for less than 18% of actual software cancellations; operational friction and value stagnation drove the remaining 82%. Mapping the four forces ensures your team addresses that 82% rather than defaulting to discounting.

Minutes 00:15–00:25: Isolate the Single Firing Trigger

Answer this single question as a group: "What was the exact moment this customer fired us?"

Customers hire software to make progress and fire it when progress halts. Identify the structural breaking point. For example: "The customer did not fire our billing engine; they fired our system when our sync latency caused their payroll run to miss its 5:00 PM deadline on the 1st of the month." This rigorous distinction is essential when utilizing the JTBD framework for creative product development.

Minutes 00:25–00:30: Assign the Single Countermeasure

Close the meeting by making one decision. Avoid logging a list of 12 minor bugs. Instead, determine which of the three product levers must be pulled to prevent the next identical switch:

1. Product Change: File a single engineering ticket to fix the structural breakpoint identified in minute 20.
2. Onboarding / Success Intervention: Build an automated usage alert triggered when a customer runs into that specific workflow failure.
3. Positioning Update: If the customer switched to a tool designed for a totally different use case, notify marketing to adjust qualification criteria so sales stops closing bad-fit accounts.

Take the 25 prompts above, open your calendar, and schedule your first switch interview with a customer who canceled this month. Run the 30-minute protocol immediately after hanging up the phone.

Sources & Further Reading

Jobs-to-be-Done churn analysis relies on the empirical study of consumer trade-offs, behavioral economics, and the mechanics of demand generation rather than passive exit surveys. A Switch interview is a structured qualitative research method designed to reconstruct the timeline, emotional energy, and competing trade-offs that drove a customer to abandon one solution and purchase an alternative.

The prompts across this guide build on foundational research from The Rewired Group, where co-creators Bob Moesta and Chris Spiek formulated the Four Forces of Progress framework. Their field research established that buyers do not leave products due to isolated feature gaps; rather, churn occurs only when the combined energy of the push from the current situation and the pull of a new solution overcomes both the inertia of habit and the anxiety of switching. In operational practice across subscription models, conducting a cadence of 10 to 12 switch interviews reveals the recurring functional and emotional catalysts behind more than 80% of preventable cancellations.

For practitioners applying these 25 prompts across churned accounts, consulting the original texts clarifies how customer progress differs from conventional customer feedback collection.

Featured image by John Taran on Pexels