What customer success is, and how it differs from support.

Many tech startups say they do customer success when what they really have is a support inbox. The difference matters. Support is reactive: a customer raises a problem and you solve it. Customer success is proactive: you know what outcome each customer bought, you track whether they are getting it, and you step in before they decide to leave.

For any subscription business, revenue from existing customers compounds. A customer who stays three years is worth three times a customer who stays one, at almost no extra acquisition cost. That is why retention sits at the heart of your lifetime value and your unit economics.

Support, success and account management

In a small company one person may cover all three. Keeping the questions separate stops the urgent (support tickets) crowding out the important (outcomes and renewals).

Setting it up, step by step

1. Write down the outcome for each segment. For every type of customer, complete the sentence: “This customer is successful when…”. Make it measurable, such as “sends their first 50 invoices through us within 30 days” rather than “loves the product”.
2. Map the journey. List the stages from signed contract to renewal: handover from sales, kickoff, setup, first value, regular use, review, renewal. Note who owns each step and what the customer must do.
3. Choose a coverage model. High-touch (a named person, regular calls) suits large contracts. Low-touch (group webinars, pooled support) suits mid-sized accounts. Tech-touch (in-product guides, automated emails) suits small or self-serve customers. Most tech startups need a mix by contract value.
4. Pick three numbers. One for onboarding (time to first value), one for health (active usage of the core feature) and one for retention (monthly revenue churn). Review them every week.
5. Decide who owns it. Until you have perhaps 20 to 30 paying business customers, a founder should personally own customer success. You learn more from those conversations than from any dashboard. As a rule of thumb, hire or assign a dedicated person once the founder cannot speak to every customer at least once a quarter.

A worked example

Pellow Analytics, a fictional Sheffield tech startup, sells stock forecasting software to independent retailers. With 40 customers, its founder answered every support email but rarely spoke to customers who stayed quiet. Three customers cancelled in one month, all of whom had never connected their till system.

Pellow defined success as “forecasts generated from live till data within 14 days of signing”. It split customers into two groups: chains with more than five shops received a named contact and monthly calls, while single-shop retailers received a guided setup and automated check-in emails. Within two quarters, every new customer was connected inside 14 days, and the quiet cancellations stopped being a surprise.

Common mistakes

• Treating success as a nicer name for support. If all your team does is answer tickets, nobody is watching the customers who never raise one.
• Defining success as usage alone. Logins are a proxy. The customer bought a result, not a login.
• Hiring a customer success manager before you know the journey. They will build a process around guesses. Do it yourself first, then hand over a documented process.
• Putting success under sales targets too early. If the role is judged on upsell, customers will notice and trust drops.

What to measure

• Time to first value for each new customer.
• Percentage of customers with a documented success outcome.
• Monthly gross revenue retention and logo churn.
• Number of customers the founder or success lead spoke to this month.