Book title: Customer Success: The Foundation of Repeat Purchases and Surging Profits (《客户成功：持续复购和利润陡增的基石》)
Author: Liu Hui
Reading time: about 8 hours
Number of notes: 562
1. Introduction: A Technical Support Practitioner’s Resonance
I chose to read this book for two reasons.
First, I have spent more than a decade doing technical support work myself—at cloud-computing companies and e-commerce companies alike—dealing with all kinds of customers, so I have first-hand experience of, and first-hand confusion about, what it means to “serve customers.” Second, when I turned to the author’s biography, I was surprised to find that Liu Hui’s very first job was also as a global technical support engineer at Huawei—the same starting point in the same profession gave me a natural sense of kinship with this book.
Technical support is a role with an extremely low ceiling and very little room to grow. Every day the work is tickets, troubleshooting, and building up the knowledge base. In the AI era, the replacement rate for customer service has already been maxed out, and technical support—this role that solves problems by repeatedly accumulating fixed troubleshooting workflows—will surely also have a large part of it replaced by AI Agents in the future. I once wrote about my thoughts on this role in another article, and the book Customer Success happened to give me a clear answer about the “way out.”
2. Customer Success ≠ Customer Service, and Even More ≠ Technical Support
This is the point in the whole book that hit me hardest, and it is also the concept that many companies most easily confuse.
2.1 The Difference in What the Work Covers
Customer service / technical support deals with product-level problems: the customer doesn’t know how to use the product, the product has broken down, they want a return or exchange—these are the passively reactive “trouble-solvers.”
Customer success deals with the customer’s business problems: a customer buys a CRM to improve the conversion rate of sales leads; they buy an expense-reimbursement system to shorten the approval cycle. What customer success must care about is not just whether the product’s features work, but even more whether the customer’s business goals have been achieved, whether the experience of using it is good, and whether there are still un-mined pain points.
As the author puts it: “The goal of customer success is to retain existing customers, so you need to help customers in every way and improve the customer experience.”
2.2 The Difference in How the Work Is Done
The core characteristic of technical support (including customer service) is passive response: the customer comes to you, and you solve it. The ticketing system is the center of the work, and the KPIs are response time and resolution rate.
The core characteristic of customer success is proactive engagement: proactively discovering problems, proactively defining success criteria, and proactively driving customers to achieve their business goals. The KPIs of customer success are retention rate, renewal rate, and NPS.
The author mentions that when he did technical support at Huawei, his daily work was solving the software problems encountered by overseas telecom-operator customers. I know that experience all too well—an excellent technical support engineer can indeed win customers’ goodwill through professionalism and patience, but if you always stay in the mode of “wait until the product breaks, then fix it,” the ceiling on your personal value is already locked in.
In my early years, right after joining Youzan to handle key-account customization. At the time I had thirty-some active customization merchants on my plate—the most in the whole group—perhaps because I was the most senior, so the TL handed me a slightly bigger share of the toughest nuts to crack. My initial feeling was that every day I was being chased by tickets and requirement schedules. The TL who mentored me had transferred over from customer service; he was very capable, and one point he stressed again and again left a deep impression on me: don’t just respond passively—proactively get to know how the customer has been using things lately and what their goals and needs are. Looking back now, that is exactly the core mindset of customer success—except that back then our team didn’t carry a renewal target, so the idea stayed at the level of “serve better” and never extended into the complete closed loop of “helping the customer succeed.”
3. Why Customer Success Has Become “Standard Equipment” in the SaaS Model
To understand customer success, you must first understand the business model of SaaS.
3.1 The Lesson of the Cash-Flow Curve
The book includes a typical cash-flow curve for a single SaaS customer: in the early stage of acquiring a customer the company runs at a loss (customer-acquisition cost > first month’s subscription fee), and it only starts making money from that customer in month 13 (in the example). If the customer churns before the break-even point, the company makes a pure loss on that customer.
This means: the strategic focus of a SaaS company must tilt toward “retaining existing customers.”
In the traditional software era it was a “one-and-done deal”—once the money was collected, whether the customer used it well had nothing to do with the vendor. But SaaS is a subscription model, and customers can “vote with their feet” at any time. Without a customer success team to continuously deliver value and ensure that customers achieve their business goals, the retention rate becomes a fatal wound.
3.2 BaaS: Business as a Service
The author raises a very interesting concept—BaaS (Business as a Service). It isn’t just software: flower subscriptions, membership services, education and training—any model billed by subscription or on demand—all require the mindset of customer success.
The five key metrics of BaaS are worth every practitioner memorizing:
| Metric | English | Meaning |
|---|---|---|
| Total contract value | TCV | Total contract revenue, not actual revenue |
| Annual fee | ARR | Annual Recurring Revenue |
| Lifetime value | LTV | The customer’s total value from the start to the end of the relationship |
| Customer acquisition cost | CAC | The cost of acquiring one closed customer |
| Churn rate | Churn Rate | The proportion of customers lost within a period |
A healthy SaaS business model = LTV > 3×CAC, and a churn rate low enough.
4. A Practical Methodology for B2B Customer Success
The chapters in the book about the day-to-day work of a Customer Success Manager (CSM) are very substantial. I’ll pick the three points that struck me most.
4.1 The Customer Lifecycle: Don’t Fixate Only on the Moment of Signing
The lifecycle of a B2B customer is usually divided into 6 stages: awareness → trial → purchase → rollout → stable use → repeat purchase.
The biggest difference from B2C lies in the “rollout” stage. After an enterprise buys software, often only a few people took part in the decision, while the end users are the whole company or a particular department. Between “we bought it” and “everyone is using it” looms a great mountain—internal rollout.
At this stage the Customer Success Manager has three things to do:
- Understand the concerns of the customer’s decision-makers and address them precisely;
- Help the customer set up rules, regulations, and reward-and-penalty mechanisms, using rules to forcibly change old habits;
- Respond to problems quickly, ensuring the user experience doesn’t fall apart during the rollout period.
4.2 Customer Stickiness: Activity + Health
Judging whether a customer will churn can’t be based on gut feeling—you have to look at the data.
Activity metrics: DAU/WAU/MAU, activation rate, login ratio, time online, client distribution, and so on.
Health metrics: whether the core modules are being used, the breadth of feature usage, whether there is integration with third-party systems, and so on.
The author divides health into four categories: record-keeping type, process type, integration type, and customization type. The higher a customer’s health, the lower its churn risk.
I once built a “churn-risk early-warning system” for my company, and its logic was exactly the same as in the book—monitoring the customer’s basic information, tiering, sales volume, usage data over the last 1 month / 3 months / 1 year, last login time, and so on; if it fell below a certain threshold it was deemed unhealthy, and the corresponding Customer Success Manager and salesperson were automatically notified to follow up.
4.3 Renewal Is Not the Finish Line—It Starts the Moment You Sign
“You can’t wait until a customer’s contract is about to expire before you start thinking about renewal; you have to start from the very moment of purchase.”
The author shares three insights on renewal:
- Start laying the groundwork from the very first contact, so the customer feels the ongoing value of the service;
- Proactively help the customer plan for the long term, making yourself “a partner suited to long-term joint development”;
- Kick off the renewal process 3 months before the contract expires, to avoid the commercial process dragging on so long that service is interrupted.
When facing low-price competition, the author’s advice is also very practical—don’t cut your price; instead, help the customer do four calculations: the cost account, the data account, the effectiveness account, and the risk account. The time cost of switching systems, the data-migration cost, the cost of employees re-learning, and the uncertainty of results—added together these often far exceed the price difference.
5. Company-Wide Customer Success: Breaking Down the Departmental Walls
Customer success isn’t the business of one department; it’s a philosophy for the whole company.
5.1 The Coordination Between Sales and Customer Success
After sales signs a customer, the relationship of trust needs to be handed over smoothly. The author’s three suggestions are very concrete:
- The salesperson must give the CSM a detailed briefing on the customer’s situation, ensuring the information is passed on completely;
- The salesperson must arrange and accompany the CSM in a face-to-face meeting with the customer’s decision-maker;
- Give a detailed introduction of the CSM’s responsibilities, so that the customer’s decision-maker correctly understands the CSM’s role and value.
How should the revenue from existing customers be allocated? The author recommends a “first-year renewal bonus incentive” for sales, while second-round selling is jointly carried out by the CSM and sales with shared commission—this both protects the sales team’s motivation and keeps the CSM from becoming a “pure service” role that loses the drive for second-round selling.
5.2 The Coordination With the Product and R&D Team
The three most common conflicts between customer success and the product/R&D team:
- Customer feedback doesn’t form a closed loop;
- The priority of requirements raised by the CSM doesn’t match the product manager’s;
- The two sides don’t share a unified goal.
The solution is to build a requirement-feedback closed loop and a problem-feedback closed loop, and to establish a regular communication mechanism. Product managers can show new-feature prototypes at review meetings, letting CSMs judge from the customer’s perspective whether they truly meet the need.
5.3 A Unified Goal: Sales Performance + Renewal Rate + NPS
The author suggests making three metrics the unified goal of the whole company:
- Sales-performance attainment: getting the product/R&D team to also care about “why the product isn’t selling”;
- Customer renewal rate: making customer success no longer the KPI of the CSM department alone;
- NPS (Net Promoter Score): measuring customer word-of-mouth, which affects the growth of the whole company.
6. Personal Reflection: The Way Out for a Technical Support Practitioner
After reading this book, I gained a clearer understanding of my own career path.
A technical support engineer and a customer service rep are essentially no different—it’s just a senior customer-service role that understands technology and business. The ceiling of this role means that—if you’ve been at it for three years and are still handling tickets, then it’s time to be on guard.
For a technical support practitioner, customer success is a very natural transition path:
- You already have the ability to quickly pinpoint problems and to communicate with customers;
- What you need to add is business acumen (understanding the customer’s business goals), solution-delivery ability (translating product capabilities into business value), and a proactive service mindset (moving from passively waiting for tickets to proactively reaching out to customers).
The author also mentions in the book that customer success can later move sideways into sales or into product management, and can even reach the position of VP or CEO—because the CSM comes into contact with every role inside the company and on the customer’s side, and understands real business logic best of all.
Of course, for colleagues still doing technical support, my advice is: even if the job title isn’t “customer success,” cultivate the mindset of customer success. Don’t just care about “whether this bug is fixed”—care about “why the customer uses this feature, what their business goal is, and whether I can help them do it better.”
7. Conclusion
The subtitle of this book is “The Foundation of Repeat Purchases and Surging Profits,” but to me it reads more like a career guide for people working in SaaS enterprise services.
For someone in technical support, this book answers a key question: when AI starts to take over ticket handling, where is your value?
The answer may be: turn from “the person who fixes the product” into “the person who helps the customer succeed.” Products will become commoditized, tools will get simpler and simpler, but how to combine tools with the business, how to solve business pain points, how to continuously deliver value—that is the real moat.
As the author says: “The more popular SaaS model of the future will be an integrated delivery approach of ‘consulting + tools.’”
And customer success is the person who turns “tools” into “solutions.”
Recommended readers:
- Technical support, customer service, and implementation consultants in the SaaS / IaaS / PaaS industries
- Practitioners who are transitioning, or preparing to transition, into customer success
- SaaS entrepreneurs and product managers
- Anyone interested in the subscription business model
评论
0 条评论