Our metrics weren't showing leadership the value of customer success

01 / The problem

Strong sales, and revenue still going backwards

Moove finances vehicles for drivers, electric and combustion, on a subscription model, working with partners like Uber and Careem. The sales team was doing an excellent job. New contracts kept arriving.

But retention kept falling, and customers were struggling to keep up with their subscription payments. So the recurring revenue figure was accurate on paper and much less accurate in the bank.

The deeper problem was that the way we measured customer success didn't demonstrate any of this to leadership. The reporting showed activity. It didn't show value, it didn't explain the gap between contracts signed and money collected, and it gave leadership nothing they could act on.

02 / What was actually happening

Proactive effort was pointed at the wrong end of the lifecycle

Customer success was engaging proactively with around a fifth of the portfolio, and that fifth was concentrated on accounts already in difficulty. The function was operating at the point of failure rather than ahead of it.

Upstream, a customer would buy the product and then hear very little about how to get the most out of it. There was no onboarding worth the name.

That matters more here than in most businesses, because the product is the thing the customer earns their living with. If you hand someone a vehicle and never show them how to make money with it, you shouldn't be surprised when the payment becomes difficult.

So this wasn't a payments problem. It was a value delivery problem, arriving late and disguised as a finance report.

03 / What I built

A function built to prevent, not to chase

I built the customer success function from the ground up, on one principle. Stop meeting customers at the point of failure. Meet them at the start.

• Real onboarding. Every customer learns how to get value from the product from day one instead of working it out alone.
• Systematic early identification. Find the customers drifting into difficulty while there's still time to change the outcome, rather than after the fact.
• Re-onboarding sessions. For customers already struggling, sessions built around carefully chosen topics that showed them value they weren't yet getting.
• Playbooks, KPIs and a roadmap. What the function is for, what it measures and what good looks like, written down so it didn't live in one person's head.
• Proactive coverage across the whole book, not a selected slice of it.

And critically, I rebuilt what we reported. Metrics that tied customer behaviour to money, so the function's contribution was visible rather than assumed.

04 / Results

Satisfaction up, difficulty down, collection improving

Time to value came down. Satisfaction went up, because customers finally understood what they had and what to do with it. Payment difficulty fell for the same reason, and cash collection improved with it.

05 / Taking it to leadership

The argument that changed the budget

I went back to leadership with a before and after. Where we started, what happened to satisfaction, what happened to payment performance, and what happened to collection once the function stopped operating as a recovery desk.

I ran it as a pilot in our South Africa market first, then worked with the UK market on applying the same approach.

The result was an action plan to invest more in customer success. More investment in the tools the team used, and investment goals set for the function itself, on the basis that what it protects is customer lifetime value.

06 / Why it worked

Same habit, different failure

Proactive coverage aimed at the customers already in trouble isn't a customer success strategy. It's an incident response rota.

The fix was the one I keep coming back to. Find the point where the failure actually starts, which here was the silence right after purchase, and design it out. Everything downstream was a symptom of that one gap.