---
title: "Customer Success When the Product Is Broken: A Playbook"
description: "Customer success when the product is broken: the four defect classes, what to promise, how to rank a defect in engineering's language, and when to stop."
topic: "Playbooks & Operations"
author: "Raj Bheda, Co-founder, GainTrace"
audience: "Customer Success Manager, Head of Customer Success"
published: 2026-09-18
modified: 2026-09-18
source: https://gaintrace.com/explore/playbooks/customer-success-when-the-product-is-broken
---

# How Do I Do Customer Success When the Product Is Broken?

*When you are the one apologising every week*

**Short answer:** Customer success when the product is broken comes down to three levers you still hold: rank every defect by the revenue it blocks instead of by engineering's own severity label, promise dates you control, not dates Product controls, and spend the customer's patience on the faults you cannot fix. You cannot repair the product from a customer call. You can stop the severity gap deciding your renewals.

**Key takeaways**

- Rank defects by blocked ARR and blocked workflow, not by the adjective in the ticket. Engineering ranks on reproducibility and blast radius, the customer ranks on what they cannot do this month, and the distance between those two numbers is where renewals are lost.
- Never pass on a fix date you did not get in writing from the person who will ship it. A missed date costs more credibility than the defect did, and our corpus has cases of a feature promised for a named date, still undelivered weeks later, with the deadline pushed back each time.
- Tag every churn and contraction with a defect id where one exists. Without that tag, product-caused churn stays an opinion, and an opinion never wins an engineering sprint.
- Give each broken account one owner for the fault and one owner for the relationship. The same person doing both is how a CSM ends up absorbing frustration from customers and from engineering in the same afternoon.
- Set a date by which the pattern has to change. A product that will not be repaired is a career decision, not a customer success problem, and where the people writing about it in our corpus state a tenure, it runs from two years to ten, not from week one.

Customer success when the product is broken is a different job from the one in the handbook. The renewal conversation is an apology. The quarterly review is a defect list. Your calendar fills with calls you did not book, about faults you cannot fix, with customers who have stopped believing the dates you pass on because the last three moved. Meanwhile the number you are measured on is retention.
This page is for the CSM or Head of CS carrying accounts on an unstable product. It sets out the four classes of defect and what each one needs, the words that hold a relationship together when the fix slips again, the way to rank a defect so engineering acts on it, the two numbers that turn product-caused churn from an opinion into a budget line, and the point at which the honest answer is to leave.

## How do I do customer success when the product is broken?

> **The severity gap:** The severity gap is the distance between the severity engineering assigned a defect and the severity the customer would assign it, expressed in blocked revenue, not in adjectives. Every priority argument between Customer Success and Product is that gap going unnamed. Put both numbers on the same row of the same list and the argument stops being about tone.

Customer success when the product is broken runs on three levers, and none of them is the product. Rank each defect by the ARR and the workflow it blocks, so Product is choosing between numbers instead of between personalities. Commit only to dates you control, which means status updates, workarounds and escalation slots, never a ship date somebody else owns. And ration the customer's patience: spend it on the faults that have no workaround, and buy back goodwill on the ones you can route around today.

> "I really need to vent and also hear from people who've been in a similar spot. I'm the only Customer Success Manager at a startup, and I'm already wearing a ton of hats. That part I can handle. The real issue is that our product that we sell is honestly in terrible shape... Almost my entire client base has open complaints or pending tickets."
>
> — r/CustomerSuccess, 2025

We read 33,600 Reddit posts from r/CustomerSuccess, r/SaaS, r/sales and r/startups covering May 2024 to September 2026, of which 7,100 sit in r/CustomerSuccess. Inside that subreddit 122 posts mention a bug, 163 mention an escalation and 39 mention firefighting. We also read 4,978 public G2 reviews of five customer success platforms: 122 of those reviews (2.5%) mention a bug, and 42 (0.8%) describe living on a workaround. Product quality is not a rare condition in this job. What varies is whether the company has a way to rank the damage.

> "It feels like half of my day is spent being yelled at by clients because the product is falling short, and the other half is spent being yelled at by my own engineering/product teams when I try to escalate the customers concerns."
>
> — r/CustomerSuccess, 2025

Two structural faults sit under most of these situations. Defect priority is set by whoever argues hardest, not by what the defect costs, so the loudest account wins and the largest exposure goes unfixed. And one person carries both the fault and the relationship, which means the CSM absorbs the customer's anger and engineering's defensiveness on the same day, with no authority over either.

## Which four classes of product defect need different handling?

Four classes of product defect show up on a broken product, and each one needs a different promise. Sort your open list into these before your next conversation with Product, because a blocker and an irritation argued in the same breath cancel each other out.

| Class | What the customer cannot do | Who owns the next step | What to promise |
| --- | --- | --- | --- |
| Blocker with no workaround | A contracted outcome stops. Month-end close, payroll run, client reporting: the work the product was bought for | Engineering, on an incident clock, with a named responder | A time for the next update, and the name of the person on it. Never a fix time you did not get in writing |
| Blocker with a manual workaround | The outcome happens, at a cost in hours the customer now pays every week | Customer Success owns the workaround, Support documents it, Product owns the retirement date | The workaround in writing today, the hours it costs counted, and that count sent to Product every month |
| Data or trust fault | The numbers are wrong or late, so the customer stops using the output even where it works | Engineering for the cause, Customer Success for the list of every report the customer has stopped trusting | A written statement of what was wrong, for which dates, and what the corrected figures are |
| Irritation | Nothing. It is slow, ugly or two clicks too long, and it is mentioned on every call | Product, through the normal feedback route | Honesty that it is logged and not scheduled. Bundling irritations with blockers devalues the blockers |

The classification matters because these four compete for the same sprint. A list of 30 open items with no classes reads to an engineering lead as noise from a CSM who wants everything. A list of two blockers with named accounts, blocked ARR and a dated workaround cost reads as a business case. [How to get customer feedback to product from CS, sales and support](https://gaintrace.com/explore/playbooks/customer-feedback-to-product-from-cs-sales-support) covers the intake side of the same pipe.

> "It is very glitchy, and often the automations will fail, leading to tasks getting missed or completely messed up."
>
> — Mid-Market reviewer, public G2 review

> "I run into 'limitations' or bugs every week and that is unacceptable."
>
> — CS Operations Manager, mid-market SaaS, public G2 review

## What do I say to a customer when the product is broken again?

Say the fault, the impact, the next update time and the person, in that order, before the customer asks. A CSM on a broken product loses the relationship to silence far more often than to the defect, because a customer who has to chase for news concludes that nobody inside the vendor is working on it.

1. **Name the fault in the customer's words, not the ticket's.** "Your Friday export has failed three weeks running" lands. "There is a known issue with the scheduled job service" does not. Use the workflow they lost, because that is the thing their own boss is asking them about.
2. **Give the impact number back to them before they give it to you.** Count the hours their team has spent on the workaround, or the reports they could not send. Bringing the cost yourself is the difference between a vendor who is paying attention and one who has to be told.
3. **Commit to an update time, never to a fix time you do not own.** "I will write to you at 4pm on Thursday whether or not there is news" is a promise you can keep every time. A ship date from a roadmap conversation is a promise somebody else can break for you.
4. **Offer the workaround as a decision, with its cost stated.** Two hours a week of manual work is a choice the customer should get to make with the number in front of them. Presenting a workaround as a fix is how a CSM loses the next conversation.
5. **Write it in one email the same day, and copy their sponsor.** The written record is what protects you when the date moves. It also gives the customer something to forward internally, which is usually what they need most and are least able to write themselves.
6. **When the date slips, send the news before the deadline passes.** A slip you report on Wednesday for a Friday date costs a fraction of the same slip discovered by the customer on Monday. Early bad news is the only kind that buys any credit.

> "After a few months, it became clear that the product has significant bugs. Support is slow to respond to issues, even after multiple follow-ups and escalating the impact these problems are having on customer operations. Development also consistently misses deadlines"
>
> — r/CustomerSuccess, 2025

One sentence to retire: any version of "the team is aware and it is on the roadmap". Reviewers in our G2 corpus use that phrasing as evidence that nothing is happening, which is exactly how your customers read it when you say it. If a fix is not scheduled, the honest sentence is that it is not scheduled, and this is what we will do instead in the meantime.

> "I do feel that we talk about a lot of great things coming on roadmap, but slow to materialize and MVPs are not up to usability."
>
> — Mid-Market reviewer, public G2 review

## How do I get engineering to fix what my customers care about?

Give engineering a number they can rank against, which means blocked ARR per defect, not a description of how angry the customer sounded. Engineering triage sorts on reproducibility, blast radius and effort. None of those fields contains revenue, so a defect affecting one account worth 400,000 a year sits below a cosmetic fault affecting hundreds of trial users, and no amount of escalation changes that until the revenue enters the ranking.

**Defect exposure**

```
Defect exposure = ARR of accounts blocked by the defect ÷ Total account ARR × 100
```

Where:
- Blocked: the account cannot complete a workflow it bought the product for, with or without a manual workaround. Slow or ugly does not count
- ARR of accounts blocked: the full contract value of each blocked account, not a guess at the share of the contract the broken feature represents
- What good looks like: under 5% of account ARR blocked at any time. Above 15% the company has a product problem that no retention playbook will cover, and the number belongs in front of the board

| Engineering ranks on | The customer ranks on | The field that closes the gap |
| --- | --- | --- |
| How many accounts hit it | Whether their own month stops | Blocked workflow, named: "month-end close", "client invoice run", "regulatory export" |
| Whether it reproduces reliably | Whether it happened to them on a day that mattered | Date and business event, so an intermittent fault that lands on quarter end is ranked as what it is |
| Effort to fix | How long they have already waited | Age of the defect in days, shown next to blocked ARR. A cheap fix that has waited 200 days ranks itself |
| Severity label in the tracker | Whether a workaround exists at all | Workaround hours per week, counted. Ten hours a week of manual effort is a cost, and costs get funded |
| The current sprint's theme | The renewal date in their contract | Days to renewal on the defect row, so Product can see which ones are about to become a cancellation |

Take that list to one recurring meeting with one owner from Product, not to a Slack channel. The corpus is clear on what happens without a standing forum: the CSM becomes the person who is shouted at from both directions, and the defect list becomes a mood rather than a queue. Where the relationship with Product is the deeper problem, [how to move to proactive customer success with a reactive team](https://gaintrace.com/explore/retention/proactive-customer-success-for-a-reactive-team) covers protecting the hours this takes.

> "I wonder if it is normal in CSM job that there are so many escalation come, the they are all related to product issues / performance."
>
> — r/CustomerSuccess, 2026

## How much of our churn is caused by the product, and how do I prove it?

Product-caused churn is measurable on your own accounts and nowhere else. No figure we can verify exists for the share of B2B SaaS churn caused by product defects: the B2B SaaS publishers that disclose a sample and a method, among them SaaS Capital, Benchmarkit, High Alpha and ChartMogul, report retention rates and never churn causes. The number you need is one you can produce in an afternoon from your own cancellations.

**Product-caused churn share**

```
Product-caused churn share = Churned ARR tagged to a defect ÷ All churned ARR × 100
```

Where:
- Tagged to a defect: the cancellation record carries a defect id that was open on the account at notice, or in the 90 days before it
- All churned ARR: cancellations and contractions over the same four quarters, so a customer who halved their seats counts for what they cut
- What good looks like: there is no published norm. The useful comparison is your own trend across four quarters, and the gap between this number and what your leadership believes it to be

> **Worked example:** A 60-account portfolio worth 4.2m ARR lost 7 accounts and contracted 3 over four quarters, 910,000 of ARR in total. Tagging each record against the defect list: 5 of the 10 carried an open blocker at notice, worth 520,000. Product-caused churn share is 520,000 divided by 910,000, or 57%. The same exercise found the two defects behind 4 of those 5 events had been open for 240 and 310 days, and neither had ever appeared in a sprint. Blocked ARR across the live accounts at the time was 690,000 of 4.2m, a defect exposure of 16%. These figures are illustrative; run it on your own accounts, and [the cost of churn calculator](https://gaintrace.com/tools/cost-of-churn-calculator) turns the result into the annual number your CFO will ask for.

Present the result once, in writing, with the defect ids attached. A share of churn with ids behind it survives the meeting where somebody says the customers were a poor fit anyway. If you want the leading version instead of the lagging one, [early warning signs of churn when data is scattered](https://gaintrace.com/explore/retention/early-warning-signs-of-churn-scattered-data) shows which signals move first, and [why SaaS customers cancel in 90 days](https://gaintrace.com/blog/why-saas-customers-cancel-in-90-days) covers the wider set of causes.

> "Churn due to bad product decisions and Sales closing deals with inappropriate customers is being counted against the CS group who had no input to those choices."
>
> — r/CustomerSuccess, 2026

## What do I do when the product will not be fixed in time?

Decide what the account is worth defending, then say so out loud to your manager with the numbers attached. A broken product creates three separate decisions and CSMs tend to make only the first: what to tell the customer, what to stop spending time on, and how long you personally give the company to change the pattern.

**Before you spend another quarter on a broken account**
- [ ] The blocker has a defect id, a blocked ARR figure and an age in days, all visible to Product.
- [ ] Somebody other than you owns the fix, by name, and that name is on the account record.
- [ ] The customer has the workaround in writing, with its weekly hour cost counted and agreed.
- [ ] Every commitment you have passed on came from the person who ships it, with a date they wrote down.
- [ ] The renewal conversation has been moved earlier, so the decision is made with the defect open rather than three days before expiry.
- [ ] The account's churn record is pre-tagged with the defect id, so the cause survives your memory of it.
- [ ] Your manager has seen the defect exposure figure for the whole account list, not only for the account that shouted.
- [ ] You have a date in your own calendar by which the pattern has to have changed.

The last item is the one people skip. A product that will not be repaired is a company decision that has already been taken somewhere above you, and no amount of relationship work converts it. Where the practitioners writing about this state a tenure, it runs from two years to ten, not from week one, and they describe the cost in the same terms every time: sales overselling at the front, product gaps in the middle, and the CSM holding both.

> "Sales oversells and sets unrealistic expectations, the product has severe gaps because leadership is more focused on new sales than resolving any existing customer pains, and I'm stuck in the middle taking heat from customers because they're failing and taking heat from leadership for churn risk that is due to factors entirely outside of my control."
>
> — r/CustomerSuccess, 2024

There is one thing worth holding on to while you decide. Customers do not expect a perfect product from a vendor of your size, and the G2 corpus is full of five-star reviews written by people whose product broke on them. What they rate is whether somebody took the problem seriously and came back with something. That is a standard you can hit on a bad product, and it is the only part of this that is inside your control.

> "My fantastic CSM will always try and find a workaround for our problem and if there isn't one she will ensure we have a conversation with their product team to get a solution on the roadmap."
>
> — Mid-Market reviewer, public G2 review

## How does GainTrace help when the product is broken?

GainTrace connects support, billing, CRM and product usage, so an open defect on an account sits next to that account's ARR, renewal date and usage trend without anyone building a spreadsheet. [Triage](https://gaintrace.com/platform/triage) ranks the accounts to work today by what is at stake, not by who wrote in last, which is the ranking a broken product makes hardest to do by hand. [Churn prediction](https://gaintrace.com/solutions/churn-prediction) shows the signals behind each call, so a churn that followed a defect is recorded as that at the time instead of reconstructed a year later.

## Frequently asked questions

### How do you do customer success when the product is bad?

Work the three things you control. Rank every defect by the ARR and the workflow it blocks so Product is choosing between numbers. Promise only what you own: update times, workarounds, escalation slots, never a ship date somebody else can move. And spend the customer's patience on the faults with no workaround. You cannot fix the product from a customer call, and pretending otherwise costs you the relationship twice.

### What do I tell a customer when a fix date slips again?

Tell them before the date passes, in writing, with a new update time and the reason. A slip reported on Wednesday for a Friday date costs a fraction of the same slip discovered by the customer on Monday. Do not offer a replacement date unless the person shipping the fix gave you one in writing. Offer instead what you can hold: a status update at a fixed time, and the workaround with its cost counted.

### How do I get engineering to prioritise my customer's bug?

Put revenue into the ranking. Engineering triage sorts on reproducibility, blast radius and effort, none of which contains money, so a defect blocking one large account loses to a cosmetic fault hitting many small ones. Give each defect a blocked ARR figure, the named workflow it stops, its age in days and the days to renewal on the affected accounts. Take that list to one standing meeting with one owner in Product.

### Is it normal for most CSM escalations to be product issues?

It is common. In the 7,100 r/CustomerSuccess posts we read from May 2024 to September 2026, 163 mention escalations and 122 mention bugs, and the threads with the most engagement describe exactly this pattern. Common does not mean acceptable. The measurable question is what share of your accounts' ARR is blocked by open defects at any time, and whether that share is falling.

### How much of our churn is caused by the product?

Only your own data answers that, and we could find no published figure for it with a sample and a method. Take every cancellation and contraction over four quarters, check whether an open defect sat on the account at notice or in the 90 days before, and divide the tagged ARR by the total. Do it with defect ids attached so the result survives the meeting where somebody argues the customers were a poor fit.

### Should I quit my CSM job if the product is broken?

Set a date rather than a feeling. Write down what has to change by when: a defect with a blocked ARR figure entering a sprint, the exposure number falling, somebody other than you owning fixes. If that has not happened by the date, the product decision was taken above you and no relationship work reverses it. Where the writers of these threads state a tenure, it runs from two years to ten, not from week one, which is worth knowing before you decide the problem is you.

## How this was researched

We read 33,600 Reddit posts from r/CustomerSuccess, r/SaaS, r/sales and r/startups covering May 2024 to September 2026, of which 7,100 are in r/CustomerSuccess, and counted the posts there mentioning a bug (122), an escalation (163) and firefighting (39). We also read 4,978 public G2 reviews of five customer success platforms, 29,027 sentences with the reviewer's role and company segment where G2 published it, and counted reviews mentioning a bug (122, or 2.5%) and a workaround (42, or 0.8%). We looked for a published figure on the share of B2B SaaS churn caused by product defects and found none with a disclosed sample, field date or definition: the B2B SaaS benchmark publishers that do disclose a method report retention rates and not churn causes, which is why this page gives a method instead. The four defect classes, the severity gap, the escalation ranking and both formulas are our own analysis; the worked example uses illustrative figures.

## Sources

- [r/CustomerSuccess: Only CSM, broken product, drowning in client issues, how to handle?](https://reddit.com/r/CustomerSuccess/comments/1npg4j6/)
- [r/CustomerSuccess: Tips for working as a CSM with a buggy product](https://reddit.com/r/CustomerSuccess/comments/1k9g1la/)
- [r/CustomerSuccess: Need to get out of customer facing roles](https://reddit.com/r/CustomerSuccess/comments/1jllko6/)
- [r/CustomerSuccess: How much time do you spend on firefighting and customer escalation?](https://reddit.com/r/CustomerSuccess/comments/1u8iluo/)
- [r/CustomerSuccess: How much should the average CSM deal with technical issues and bugs?](https://reddit.com/r/CustomerSuccess/comments/1dkefrq/)
- [r/CustomerSuccess: The ownership of customer realized value](https://reddit.com/r/CustomerSuccess/comments/1tjzygu/)

## Next steps

Sort your open defects into the four classes this week, put blocked ARR on each one, and take the list to a single owner in Product. [Start free](https://app.gaintrace.com/auth/login) or [book a demo](https://gaintrace.com/booking).