Her name was Elena and she had been a customer for two years and four months. The CEO did not know this on the morning the email arrived. The CEO learned it afterward, when the email had been read and the account had been pulled and the history had been reviewed in the way that histories get reviewed when something has happened that makes the history suddenly relevant. Elena's email arrived on a Wednesday morning at eight forty-seven. It was addressed to the general customer contact address and had been forwarded to the CEO's inbox by Dom, the account coordinator from the provider, with a brief note that said: thought you should see this one. The CEO read Dom's note first and then opened the email. The email was long. Not angrily long. The kind of long that comes from someone who has thought carefully about what they want to say and has said all of it because they have decided this is the last time they are going to say it and they want it to be complete. Elena had been a customer since the early days. She had found the company through a recommendation, had tried the product and had stayed because of two things: the product itself, which did what it said it would do and kept getting better in ways that reflected someone was actually listening to what customers needed, and the support, which she described in specific and generous terms that the CEO recognised as the texture of the thing that was now gone. Elena wrote: I want to tell you about the last three times I called. The first time was four months ago. Elena had a question about a feature that had recently changed. The agent she spoke to gave her an answer that was incorrect. Not obviously incorrect. Plausible enough that Elena had acted on it and had spent two hours doing something in the wrong way before discovering the error. She had called back. The second agent had given her the correct answer. Elena had not complained. She had put it down to a new person having a bad day. The second time was six weeks ago. Elena had an issue that she described in careful detail, the kind of detail that comes from someone who has already done their own research before calling and who knows what the problem is and what the solution probably is and who is calling not because they need to be told what to do but because the solution requires access to the account on the company's side. The agent Elena spoke to had not understood the issue immediately. Elena had explained it a second time, patiently, and then a third time in different language, and by the end of the call Elena knew more about the issue than the agent did and the resolution had required the agent to escalate to a team lead who had taken a further twenty minutes to implement what Elena had already identified as the correct solution. Elena wrote: I am not telling you this to complain about the agent. I am telling you because at the end of the call the agent thanked me for my patience and I realised that the patience they were thanking me for was the patience I had used to explain my own problem to someone who should have understood it without needing it explained. That is a different thing from what I was used to. The third time was two weeks ago. Elena had a billing question. Simple, she thought. She had been charged for something she did not recognise on her invoice. The agent she spoke to could see the charge on the system but could not explain it. The agent put Elena on hold for four minutes and came back and said the charge was correct. Elena asked why. The agent said the system indicated it was correct. Elena asked again, differently, what the charge was for. The agent said they would need to raise a query with the billing team and someone would be in touch within five to seven business days. Elena wrote: I have been a customer for two years and four months. In that time I have spoken to perhaps fifteen or twenty people in your support team. I knew most of their names. I knew which ones to ask for when I had a particular type of question. There was one woman, I do not know if she is still there, who once spent the better part of an hour on the phone with me working through something that was complicated and that she did not have to stay on the line for and that she stayed on the line for anyway because she seemed to genuinely want it resolved. That call happened eighteen months ago and I still remember it because it is the kind of thing you remember. I am writing because I am not sure I am going to stay. Not because the product has gotten worse. The product is still good. I am not sure I am going to stay because the company I am dealing with now feels different from the company I signed up with, and the difference is in exactly the places that matter most when something goes wrong. I thought you should know.

The CEO read Elena's email three times. The investigation had been running for two weeks by the time Elena's email arrived. The investigator was an external HR specialist brought in specifically because the company did not have the internal expertise for a formal harassment investigation and because the external perspective was, in any case, the right one for a process that needed to be seen as impartial by everyone involved. She had interviewed Iris. She had interviewed Marco. She had interviewed Devin. She had interviewed two colleagues who had observed aspects of the situation. She had asked to interview the CEO. The CEO sat across from her in the meeting room with the whiteboard and the four chairs. The investigator was methodical. She asked about the company's culture around interpersonal relationships. About how complaints were handled. About whether there was a formal process for reporting concerns of this kind and whether that process was clearly communicated to employees. The CEO answered honestly. The honest answer was that the process existed and was in the employee handbook and had not been discussed in any all-hands meeting or team briefing in the previous twelve months. The investigator wrote this down. She asked what the CEO knew about the specific situation between Iris and Marco and when the CEO had first become aware of it. The CEO said when Sandra had raised it. The investigator asked how much time had elapsed between Iris's first conversation with Devin and the CEO becoming aware of it. "About three weeks," said the CEO. The investigator wrote this down. She asked what action had been taken when the CEO became aware of it. The CEO said that Sandra had been managing it and that the CEO had trusted Sandra's management. The investigator wrote this down. She thanked the CEO and closed her notebook, a slim dark grey notebook with a rubber band around it, the practical notebook of someone who takes notes in order to use them rather than in order to have them. The CEO forwarded Elena's email to Jonathan with a note that said: I want to talk about this today if possible. Jonathan called within the hour. The call was professional and Jonathan was appropriately concerned and said the right things about taking customer feedback seriously and about reviewing the specific interactions Elena had described and about using this as a learning opportunity for the team. The CEO listened to Jonathan say these things and then said: "Jonathan, I want to ask you something directly." "Of course," said Jonathan. "In your experience, across the forty-three transitions you have managed, how often does a customer like Elena come back?" said the CEO. Jonathan was quiet for a moment. "It depends on the product and the competitive environment," said Jonathan. "In most cases customers like this, long-tenure high-engagement customers, respond well to a personal outreach and a concrete demonstration that the feedback has been heard." "That is not what I asked," said the CEO. "I asked how often a customer like Elena comes back. Not how often the outreach works. How often does a customer who has been with you for two years and four months, who remembers a specific call from eighteen months ago, who is telling you the company feels different in the places that matter most, how often does that customer come back once they have decided to leave?" Jonathan was quiet again. "Not often," said Jonathan. "Thank you for being honest about that," said the CEO. "I want to be clear that we are not at the point of losing Elena," said Jonathan. "This is recoverable." "I know," said the CEO. "I will respond to Elena personally. But I want you to understand that Elena is not the issue. Elena is the signal. Elena is the customer who took the time to write two pages explaining what she has noticed. For every Elena there are customers who noticed the same things and did not write." "I understand," said Jonathan. "I want to know how many of them there are," said the CEO. "The churn data," said Jonathan. "The churn data tells me how many of them have left," said the CEO. "I want to know how many of them are thinking about it." "We can look at the satisfaction scores below three and the repeat contact rate as leading indicators," said Jonathan. "Do that," said the CEO. "Send me the analysis by end of week." "Of course," said Jonathan.

The CEO wrote back to Elena that afternoon. Not a template. Not a customer service response drafted by the provider and approved by the communications team. A personal email, written by the CEO, that said the following. Dear Elena, thank you for writing. I read your email carefully and I want you to know that I did not forward it to anyone or ask anyone else to respond to it. I am responding to it myself because what you have described deserves a direct response from the person who is responsible for the decisions that led to the experience you are describing. You are right that the company feels different. I made a decision earlier this year to transition our support function to an external provider. I made that decision for reasons that seemed sound at the time and that I am now looking at more carefully in light of what you and others have told me. I cannot promise you that the experience will immediately return to what it was. I can tell you that I am taking what you have said seriously in the way that matters, which is not by reviewing the agents who handled your calls but by reviewing the decision that created the conditions for those calls to go the way they did. I am also going to personally look into the billing charge you mentioned. You should not have had to wait five to seven business days for an explanation of something that appeared on your invoice. I will have an answer for you by the end of tomorrow. Thank you for two years and four months. And for writing. The CEO sent the email and then pulled up Elena's account and spent forty minutes working through the billing history until the unexplained charge was identified, which it was, as an automatic renewal for an add-on feature that Elena had trialled six months earlier and had not been clearly informed would renew automatically. The CEO issued a refund and added a note to the account and wrote a second email to Elena explaining what had happened and apologising for the lack of clarity in the original communication about the trial renewal terms. Elena responded the following morning. She said: thank you for looking into this and for responding personally. The refund is appreciated but it is not the main thing. The main thing is that someone looked. That is what I was not sure would happen when I wrote. She said she would stay. The CEO read this and felt something that was not quite relief. Relief would have been the right response if Elena's decision to stay had resolved something. It had not. It had paused something. The decision to stay was Elena's response to a personal email from the CEO and a forty-minute account review and a refund. It was not a response to the support experience that had produced her original email. That experience had not changed. The next time Elena called she would get the same forty-three-page script and the same agents working within the same model that had produced the three calls she had described. The CEO knew this. What the CEO had done for Elena was real and it was right. It was also not scalable. There were thousands of customers. The CEO could not read every email and review every account and write every personal response. The model required the provider to do those things and the provider was doing them within the parameters of the contract and the script and the quality assurance framework and the coaching programme and the six-week supplementary training and the revised escalation pathway. All of which produced a three point six out of five. And a customer who remembered a forty-minute call from eighteen months ago and was not sure she was going to stay. The investigation concluded its findings on a Friday. The investigator presented them to the CEO in the meeting room with the whiteboard and the four chairs. The findings were clear and specific. The investigation had found no evidence of harassment as defined by the applicable framework. Marco's behaviour, while causing genuine distress to Iris, had not met the threshold for a harassment finding. The investigation noted that the situation had been mishandled at the team lead level, not through malice but through insufficient experience and insufficient support, and that the company's policy framework around interpersonal complaints had not been clearly communicated to the people who needed it. The investigator recommended three things. A formal conversation with Marco about boundaries and the impact of his behaviour, regardless of intent. A review of how complaints of this kind were escalated and supported at the team lead level. And mandatory training, for the whole company, on what harassment was and what it was not and what to do when something was close enough to the line that the difference was not immediately clear. "It was not harassment," said the CEO. "Not in the formal sense," said the investigator. "But it was close enough to the line that the outcome could have been different in different circumstances. The lesson is not that nothing happened. The lesson is that the conditions existed in which something could have." The CEO thought about Marco and Iris. About a friendship that had been real and that was now something different. About Devin, who had tried and had not had the tools to succeed. About the weeks in which the situation had been moving toward the filing of a formal claim and the company had not had a structured way to intervene earlier. "Thank you," said the CEO. The investigator closed her slim dark grey notebook and put the rubber band back around it. Iris and Marco both stayed. Not because the investigation had resolved anything between them. Because the company was honest about the finding and what it meant and because both of them, separately and for their own reasons, decided that leaving would cost them more than staying. They were not friends after that. The specific ease of the friendship, the lunches and the easy conversation and the sense of mutual understanding that had made the three years before feel like a kind of family, that was gone. They were professional. They were courteous. They occupied the same building without occupying the same space. It was a loss that did not appear in any report. Marco attended the harassment training. He sat in the second row. He did not say much. He listened to the case studies and the definitions and the examples and the specific framework for understanding the difference between behaviour that causes harm and behaviour that is intended to harm and why the difference matters and why it does not make the harm less real. At the end of the session he stayed behind. He talked to the facilitator for twenty minutes. The conversation was private and nobody reported its content. But he left the room with the expression of someone who has understood something they did not understand before and who is deciding what to do with the understanding.

The analysis Jonathan sent at the end of the week showed the following. Of customers who had given a satisfaction score of two or below in the previous quarter, forty-one percent had not contacted the company again. This could mean they had no further need. It could mean they had resolved their issue through another channel. It could mean they had already made the quiet decision that Elena had been describing and were in the process of leaving without announcing it. The repeat contact rate for customers who had given a score of two or below was significantly lower than the historical baseline, which Joel had told the CEO meant that customers who were unhappy were not giving the company another chance to fix it. They were simply not calling again. The CEO read the analysis and then looked at the churn figure from the quarterly business review. Two point three percent. A number that Jonathan had described as within the range of normal quarterly variation. The CEO wrote a note and put it in the top drawer of the desk, next to Sandra's summary from the first day of the provider's operation. The note said: two point three percent is not variation. It is Elena, multiplied. It is Ruth, who did not write. Three weeks after Elena's email the product had a failure. Not a catastrophic failure. Not the kind of failure that produces news coverage or regulatory attention or the specific crisis that requires a public statement and an emergency response team and a person standing in front of a camera taking accountability on behalf of an organisation. The quieter kind of failure. A processing error that affected a specific subset of accounts for a period of four days before it was identified and corrected. The affected customers received an automated notification. The notification was accurate and informative and had been drafted by the communications team and approved through the correct process and sent within the correct timeframe. Then the affected customers called. Forty-seven percent of the affected customers called within twenty-four hours of receiving the notification. They called because they had questions the notification had not answered. Because they wanted to understand what had happened to their account specifically. Because they were worried about data that had been processed during the error period. Because they wanted to talk to someone who could tell them, with genuine understanding of their specific situation, that everything was alright. The provider's team handled the calls. The CEO listened to six of them. The agents were following the script that had been supplemented with a specific addendum for the processing error, drafted by the provider in consultation with the product team and approved the previous day. The addendum was accurate. It covered the most common questions. It described what had happened and what had been corrected and what customers could expect going forward. What it did not cover was the question that five of the six customers the CEO listened to were really asking, which was not a question about the error itself but about whether the company they had trusted with their data and their time and their ongoing business was still the company they had thought it was. That question cannot be answered by a script addendum. It can only be answered by a person. By the accumulated weight of a relationship in which the customer has experienced, repeatedly and directly, that the company is the kind of company that can be trusted. That when something goes wrong the person on the phone will stay with it until it is sorted because leaving it unsorted is not something they consider. The CEO listened to the sixth call and thought about Priya. About the forty-minute call. About the customer who had written a paragraph about it. About a woman who had been a customer for two years and four months and who had remembered, eighteen months later, the specific texture of being genuinely helped. The CEO closed the call recordings and opened the top drawer of the desk. Sandra's summary. The note about Elena and Ruth. Took out a fresh piece of paper and wrote three words. It is time. Then picked up the phone and called Joel.

End of Chapter 9

Writer's Thought:

Elena stays. The CEO knows it is not enough. I know it too.

Here is What is Broken. The CEO. The Customer Who Knows More.

MarvinPro | March 2026

marvinpro.com

marvinpro.com

Think Simple.