In 2023, Kushan Randeni came to me with an idea for a business focused on making professional mental healthcare more accessible in Sri Lanka. He wanted to build what would eventually become HappyMind, and my role was to help shape the technical side of that vision. Together, we worked through the initial product architecture, and Purple Software went on to design and develop the platform. I was involved throughout the process, from early planning and product decisions to design and development.
The challenge was not simply to build another appointment-booking system. HappyMind needed to support a much more sensitive and personal journey. Someone using the platform may be looking for support during a difficult period in their life, so the experience had to feel simple, trustworthy and easy to navigate. At the same time, therapists needed a reliable way to manage their availability, sessions and clients. The technology had to support both sides without adding unnecessary complexity.
Building the platform around the user
We designed HappyMind to reduce the friction between someone deciding they need support and actually speaking to a professional. Users can browse therapists, understand the services they provide, select a suitable session, book according to availability and attend therapy online through the platform. HappyMind has since grown into a broader mental-health services platform focused on connecting people with qualified professionals in a more accessible way.
What made the project particularly interesting was how much the technical decisions were connected to the business itself. The architecture, user flows, therapist management, booking experience and overall product design all had to support the way HappyMind intended to operate. This is one of the reasons I enjoy getting involved early in a company or product. Technology decisions made at the beginning can either make a business easier to scale later or create limitations that become expensive to fix.
When technology should stay in the background
HappyMind also reinforced something I strongly believe about software: the technology should not always be the thing people notice.
In a product like this, nobody should be impressed by how complicated the system is. The user should simply be able to find the right therapist, make a booking and get the support they need. When the product is dealing with something deeply human, the software should quietly remove friction rather than create more of it.
That is what we tried to achieve with HappyMind. The platform itself is important, but the real value is what it enables: making the distance between someone who needs help and someone qualified to provide it shorter.
What I took away from HappyMind
HappyMind was different from many of the systems we had built at Purple because the impact was much more personal. We were not just reducing operational work or improving a business process. We were building infrastructure that could make it easier for someone to access mental-health support.
Projects like this are a useful reminder that technology is only valuable because of what it allows people to do. The most technically impressive system is not necessarily the most meaningful one.
Sometimes the best software simply makes an important part of someone’s life a little easier.