Software Growth

Customer success

Customer success is the practice of helping customers reach the outcome they bought your software for, which drives retention, expansion and referrals.

Customer success is both a philosophy and a job function. The philosophy is that your revenue depends on customers getting what they came for. The function is the people, processes and tools that make it happen after the sale. In a subscription business that matters more than in any other, because the customer can leave every month.

Definitions that are worth knowing

Lincoln Murphy, who founded Sixteen Ventures and is one of the field's early voices, defines customer success as the state where a customer achieves their desired outcome through their relationship with you, which leads them to stay longer, buy more and advocate for you. He breaks the desired outcome into a goal and an appropriate experience, meaning the kind and frequency of interaction that suits that customer. He also warns about a success gap, where customers complete every task in your product and still miss their real business goal.

Gainsight, the company that built a business around the field, describes it as achieving business growth through a customer-focused approach: build healthy relationships, give customers a good experience, and track metrics to measure how it is going.

Customer success versus support

  • Support reacts. A customer has a problem and asks for help.
  • Customer success is proactive. It looks at usage and goals and reaches out before the problem shows up.

Both matter. Support fixes an issue. Success makes sure the customer reached the result.

What customer success does

How to measure it

The clearest scorecards are retention numbers. A simple one:

Example: you start the year with $20,000 MRR from existing customers. They add $3,000 in expansion, reduce by $500 and cancel $2,000 worth. That gives (20,000 + 3,000 - 500 - 2,000) / 20,000 = 20,500 / 20,000 = 102.5%. Customer success is judged on whether that number is above 100% and rising. Add satisfaction and NPS as supporting signals.

Common mistakes

  • Treating it as a team that appears after a first big churn event, rather than a habit from the first customer.
  • Measuring activity (calls made) rather than customer outcomes.
  • Giving it to everyone and no one. Someone has to own retention.

For small SaaS

You do not need a team. Before hiring, you can do the work yourself: personally email each new customer, ask what they hoped to achieve, and check in after 30 days. Then build simple automation, such as alerts for accounts that stop logging in. Murphy's idea that success means a customer's desired outcome applies at any size, and the founder who talks to every customer in the first year will learn more than any dashboard can show.

Sources

Back to the SaaS glossary