I did not start out thinking I would work in Customer Success. I started out doing the kind of work that teaches you how to deal with people before you even realise you are learning it.
For years, I worked in administration and customer support. At the University of Nigeria, Nsukka, I supported people using Turnitin, and over time, I onboarded and helped more than 20,000 students and faculty members navigate the platform.
At first, it was simple. Someone had a problem. They needed help. I figured it out. But after doing that for nine years, I started noticing something.
The problem was rarely just the problem someone came to report. Sometimes a customer did not understand the product. Sometimes they had never been properly onboarded. Sometimes they were using a feature the wrong way because nobody had shown them a better way. And sometimes, what looked like a technical problem was really a communication problem.
I became interested in that gap. What happens after someone buys? What makes them actually use what they paid for? What makes them trust the product enough to keep using it? And what makes a customer say, “This is worth it”?
That question gradually pulled me beyond support. I moved into sales and client-facing work, where I learned the other side of the relationship. I learned how businesses acquire customers, how sales conversations happen, what companies promise before a deal closes, and how important it is for that promise to survive after the contract is signed.
That changed how I looked at Customer Success. I stopped seeing it as simply helping customers. I started seeing it as the bridge between what a company sells and what a customer actually achieves.
That is the work I enjoy now. Helping customers get started. Helping them adopt the product. Finding the friction that gets in the way. Understanding why engagement drops. Working with teams to improve the customer experience. And ultimately, making sure the customer has a reason to stay.
Today, my work involves Customer Success, account management, customer support and SaaS. I bring the perspective of someone who has been on different sides of the customer relationship, from supporting users, to selling, to managing client relationships, to thinking about retention and long-term value.
I call the way I think about this Outcome Architecture. Because I don't think Customer Success is about keeping customers happy for the sake of it. It is about helping them get to the outcome they believed they were buying in the first place.
That's the work I want to keep getting better at. And that is what Promise Delight is building around.
