The first 3 interviews are free · Start free or see the prices

Churn Reasons Codebook: How to Code Why Customers Cancel

Use this codebook to code exit interviews, cancel form answers and cancellation emails. It separates the event that started the cancellation from the root cause, so the fix goes to the right team.

Analyze a transcript free

Use it for

  • Transcripts of exit interviews with customers who cancelled in the last 60 days.
  • Free-text answers from the cancel form, with the reason that the customer selected.
  • Account data for each customer: plan, tenure, seats, and usage in the last 30 days before the cancellation.

Steps

  1. Make one record per account

    Join the interview, the cancel form answer and the account data for each customer. Code the account, not each sentence. A churn analysis must answer why each account left.

  2. Find the trigger first

    Mark the event that started the cancellation, with its date if the customer gives one. Write it in a short free-text field. Do not code it yet.

  3. Code the root cause

    Ask why the trigger led to a cancellation. Choose the code that, if fixed, would most likely have kept the account. Give each account one primary code and at most two secondary codes.

  4. Check the selected reason against the story

    Compare the code with the reason the customer selected on the cancel form. Record where they differ. A form that says "Too expensive" often hides Value not realized or Budget removed.

  5. Check usage before you trust the story

    Look at usage in the 30 days before the cancellation. Low usage with a Product gap code can mean the customer never adopted the product. Recode to Low adoption if the interview supports it.

  6. Count by segment

    Count primary codes per segment: plan, tenure band and company size. Report which reasons each segment has. A reason that is rare in total can be the main reason for your largest accounts.

Codebook

Copy the codebook as a table. It pastes into a spreadsheet with one row for each code.

Value not realized

The customer never got the main outcome that they bought the product for.

Include
The product did not deliver the expected result, and the customer cannot name a time it worked.
Exclude
The customer got some value but judged it too small for the price. Use Price above value for that.
Example
“We set it up but we never got a single report out of it that our team used.”

Price above value

The customer got some value but decided it was less than the price.

Include
The customer compares the price with what they got, and the product worked at least in part.
Exclude
The customer had no money to spend, whatever the value. Use Budget removed for that.
Example
“It was nice to have, but not 80 dollars a month nice. We used maybe one feature.”

Budget removed

The company or person cut spending, and the product lost its budget without a judgment on value.

Include
The customer mentions a cost cut, a hiring freeze, a lost client or a general rule to cancel tools.
Exclude
The customer chose to move the budget to a competitor. Use Switched to competitor for that.
Example
“Finance told every team to cancel any tool that was not in the core list. Nothing personal.”

Need ended

The task or project that the product supported no longer exists.

Include
The project finished, the business closed, the role changed or the season ended.
Exclude
The need still exists but the customer meets it another way. Use Switched to competitor or Built in house for that.
Example
“The wedding is over, so we do not need a guest list tool anymore.”

Switched to competitor

The customer moved to another vendor's product for the same need.

Include
The customer names another product they now use, or moved to a tool bundled with another purchase.
Exclude
The customer replaced the product with a spreadsheet or something they built. Use Built in house for that.
Example
“Our CRM added a basic version of this, so we just use theirs now.”

Built in house

The customer replaced the product with their own tool, a spreadsheet or a manual process.

Include
The customer says they now do the task with internal code, an existing general tool or by hand.
Exclude
The replacement is another vendor's product. Use Switched to competitor for that.
Example
“One of our developers wrote a script in two days that does the part we needed.”

Product gap

A missing or weak capability that the customer needed and that the product did not have.

Include
The customer names a specific function, integration or limit that stopped them, and they tried to use it.
Exclude
The capability exists but fails or is slow. Use Reliability problem for that.
Example
“We needed approvals with two steps. You only have one, so legal would not sign off.”

Reliability problem

The product did not work as designed: bugs, downtime, data errors or slow performance.

Include
The customer describes failures, outages, lost data or slowness that affected their work.
Exclude
The product works as designed but does not do what the customer needs. Use Product gap for that.
Example
“Sync failed three times during our busiest week. After that nobody trusted the numbers.”

Low adoption

The team or the person did not build the product into their routine, so it went unused.

Include
The customer says people forgot it, did not log in, did not finish setup or went back to old habits.
Exclude
The person who owned the product left, and adoption fell after that. Use Champion lost for that.
Example
“I invited the team but they kept sending me updates by email, so after a while I gave up.”

Champion lost

The person who bought, set up or defended the product left the company or changed role.

Include
The customer mentions that the owner or main user of the product left, and nobody took over.
Exclude
The team never adopted the product, even while the owner was there. Use Low adoption for that.
Example
“Our ops lead was the one who loved it. When she left in March, it just sat there.”

Service failure

A bad experience with support, billing or account management that pushed the customer to leave.

Include
The customer names a slow or unhelpful support reply, a billing error or a broken promise from the vendor.
Exclude
The support case was about a bug and the bug was the main problem. Use Reliability problem for that.
Example
“I asked three times for an invoice with our VAT number and got the same template answer each time.”

Report outline

  1. The primary reasons for churn, with the number of accounts for each, split by segment.
  2. Triggers: the events that most often started a cancellation, and how long before the cancellation they happened.
  3. Gaps between the cancel form and the interviews: which selected reasons hide which root causes.
  4. One section per top reason: 2 or 3 quotes, the usage pattern and the team that owns the fix.
  5. Reasons you cannot prevent, such as Need ended, reported apart so they do not hide reasons you can fix.
  6. Recommended actions and the metric that will show each one works.

Mistakes to avoid

  • Do not code the cancel form reason and stop. "Too expensive" is a label. The interview shows if it means Price above value, Budget removed or Value not realized.
  • Do not give an account more than one primary code. If two reasons seem equal, ask which one, if fixed, would have kept the account.
  • Do not mix preventable and non-preventable churn in one chart. Need ended and Budget removed need a different response from Product gap.
  • Do not code only the customers who agreed to talk. Code the cancel form answers of all accounts too, and compare the two groups.

Guides that use it

Questions

A trigger is the event that started the cancellation, such as a renewal email or a price change. The reason is why that event led to a cancellation. Fix the reason. You often cannot remove the trigger.

Code each account for the main reason. Then code sentences only if you need quotes for the report. The decision is per account, so the count must be per account.

Failed payments are not a decision by the customer. Remove them from this codebook and report them apart. If a customer let a payment fail on purpose, code the real reason.

Yes. Reports in User Evaluation have a Churn drivers template. It lays out the themes and claims of the study reports with their clips. You can use this codebook to check the themes by hand.

Ask real people your question

The AI moderator interviews screened people by voice or text. Each claim in the study report links to its clip. The first 3 interviews are free.

Start free