Every customer success team has a mental model of what a churn risk looks like. The angry email. The escalation to the VP. The support ticket with the subject line written in capital letters. These are the customers who consume the most energy, who dominate pipeline review meetings, who show up in red on every health score dashboard. And yet, according to David Becerra – a CS leader who has managed accounts from startup through SAP enterprise – these are not the customers you should be losing sleep over. The ones who keep him up at night are the ones who say nothing at all. In a conversation with Thibaut de Lataillade, he explained why silence is the most dangerous signal in customer success, and what his team learned about turning noise into loyalty.
The Counterintuitive Truth About Angry Customers
Becerra’s framing is blunt and, once you hear it, almost impossible to argue with. An angry customer is a customer who cares. They bought the product for a reason. They had expectations. Those expectations are not being met, and they are telling you about it – loudly, possibly rudely, definitely with urgency. That noise is not a problem. It is information. It is a customer raising their hand and saying, “I need help, and I need it now.”
The customer who responds “everything’s fine” to every check-in, whose usage is flat or declining, who never opens a ticket and never asks for a meeting – that customer has already made a decision. They have decided that the product is not worth the effort of complaining about. They are not angry. They are indifferent. And indifference, in the customer success universe, is terminal.
“The secret killers, the people that are just silent – those are the ones that are really hard to turn around.”
The distinction matters because it inverts the instinct of most CS organizations. The natural tendency is to pour resources into the loudest fires – the escalated accounts, the at-risk flags, the customers threatening to cancel. And those situations do require attention. But the silent accounts get deprioritized precisely because they are not making noise, and by the time someone thinks to check on them, the decision has already been made. The renewal date arrives, and the customer has already signed with a competitor, and nobody quite knows when it happened because there was no single moment of failure. Just a slow, quiet drift toward the exit.
Building a Culture Around Turning Complaints Into Advocacy
At Roambi, Becerra’s startup, the support team developed what he describes as an ethos around converting angry customers into advocates. This was not an accident. It was a deliberate strategy led by the director of support, AJ Duty, who recognized that the gap between a furious customer and a loyal champion was, paradoxically, narrower than the gap between an indifferent customer and an engaged one.
The logic works like this. A customer who is angry enough to escalate has experienced both the promise of your product and the failure of your delivery. If you can close that gap – if you can resolve their issue with genuine speed, genuine care, and genuine competence – you create a contrast that the customer remembers. They have seen the worst. Now they have seen the best. And the emotional trajectory from frustration to relief to gratitude is a powerful arc that builds loyalty in a way that steady, unremarkable service rarely does.
Becerra is careful to say that this was partly a luxury of scale. At a startup, you can have the director of support personally handle an escalation. You can make a customer feel like the most important person in the building, because at a 50-person company, they might actually be. But the principle scales, even if the execution has to be adapted. The principle is: treat complaints as opportunities, not as problems. The customer who is yelling at you is handing you an invitation. The customer who is saying nothing is handing you nothing.
Why Silence Is So Hard to Diagnose
The difficulty with silent churn is that it does not register on any of the traditional early warning systems that CS teams rely on. Health scores tend to weight observable behavior: support tickets opened, meetings attended, survey responses submitted, executive sponsor engagement. A customer who does none of these things might look healthy – or, more accurately, might look like nothing at all. They are invisible in a system designed to detect signals, because they are not producing any.
This is where the data signal work Becerra did at SAP becomes directly relevant. The implementation of product usage analytics through Mixpanel gave the team a way to see what customers were doing even when those customers were not talking to anyone. A customer who has stopped using a key feature is producing a signal – it is just not a signal that shows up in Salesforce or in a support queue. It shows up in the product telemetry, and if nobody is watching that telemetry, it goes unnoticed until the renewal conversation, at which point it is too late.
The combination of usage data and proactive outreach is Becerra’s answer to the silent churn problem. You cannot wait for quiet customers to come to you. You have to go to them, armed with specific, contextual observations about their usage patterns, and start a conversation they were not going to initiate on their own. “I notice you have not used feature X in the last two months – is there something we can help with?” is a fundamentally different engagement than a generic check-in email that the customer deletes without reading.
The Advocacy Flywheel
The converted angry customer does not just stay. They become an active asset. Becerra describes a pattern where customers who went through a difficult period – a rocky implementation, a product issue, a misaligned expectation – and then experienced a genuine resolution became some of Roambi’s strongest advocates. They referred other customers. They provided testimonials. They showed up to user groups and told their story, which was always more compelling than a case study written by the marketing department, because it included the part where things went wrong and the part where the company made it right.
This is the flywheel that silent churn never feeds. A customer who drifts away without complaint produces no advocacy, no referral, no story. They produce a line item on a churn report and a vague sense among the CS team that something went wrong, somewhere, at some point that nobody can quite identify. The angry customer who gets converted, by contrast, produces a story with an arc – and stories with arcs are how organizations learn and how brands build reputations that survive beyond the next quarterly review.
For the full interview breakdown, see our complete Expert Insight with David Becerra.
Tools Mentioned in the Interview
The following tools and platforms were referenced during this conversation.
Related Content
Customer Success From Startup to Surf Camp: Expert Insights with David Becerra
David Becerra has built customer success organizations from startup to SAP enterprise to a surf retreat in Indonesia. He breaks down what actually drives retention, why your quietest customers are your biggest risk, and what hospitality teaches SaaS about onboarding.
What Running a Surf Camp Taught a CS Leader About Onboarding
David Becerra left enterprise SaaS to manage a surf retreat in Indonesia and discovered that the principles of customer success -- onboarding activation, setting boundaries, and building advocacy -- transfer to hospitality with unsettling precision.
How Data Signals Transformed a Low-Touch Customer Success Team
David Becerra built a low-touch CS organization at SAP that scaled from 10-20 accounts per CSM to 60-80, driven by Mixpanel usage data that reduced churn by 10%.
