The boy from Thuckalay who learned to see at the edges.

I grew up in Thuckalay, a small town near the southern tip of India, in a district where three seas — the Arabian Sea, the Bay of Bengal, and the Indian Ocean — meet. When I was growing up, I didn't think there was anything particularly unusual about where I came from. It was simply home.

My father worked as a system administrator at Sony in Saudi Arabia for several years, and when I was small he would bring home broken keyboards, dead mice, and old computer parts for me to play with. Other kids had toys. I had computer parts. By the time I was twelve, he had taught me HTML and I had built my first website.

At fourteen, I was charging neighbours four hundred rupees to reinstall Windows on their computers. My first real paying client was my brother-in-law, who asked me to design an advertisement for the family business. Soon I was making brochures, wedding cards, business cards, websites, and animated banners — whatever somebody needed and I could figure out how to build.

I didn't have a name for it then. I simply loved taking something complicated, understanding how it worked, and finding a simpler way to make it useful. That instinct never really left me.

After college I joined Tata Consultancy Services and was placed on a project for Singapore Airlines. A few years later, a Singapore-based role came up that I very much wanted. The interviewer rejected me. Twice. I was a year or two short on the specific technology experience they needed.

I couldn't accept that as the end of the conversation. So I followed up and said: send me whatever project you want. Any specification. I'll build it and show you. Two weeks later I had the offer. One week after that I was on a plane to Singapore.

"Most of the doors I thought were closed were actually just heavy."

Since then, I have spent more than fifteen years working inside some of the most demanding institutions in the region — including Singapore Airlines, Bank Julius Baer, and Bank of Singapore. Today I work in data science and advanced analytics in private banking.

Along the way, I have built models that predict client behaviour, analytics that help bankers understand relationships more deeply, real-time alert systems for front-office teams, and programmes that have helped hundreds of colleagues become more confident working with data and AI.

I've been fortunate to receive recognition for some of that work — including training, teamwork, service, and technical excellence awards. I'm grateful for them. But the awards aren't the important part of the story. The important part is what building all of those systems taught me.

Long before I started thinking about business operating systems, I tried building businesses myself. I started a technology company. It failed. Then I started a consulting business called Growth Bamboo, and I became obsessed with learning how businesses grow.

I read the books. I attended the events. I hired coaches. I learned marketing, sales, funnels, advertising, positioning, and copywriting. And parts of it worked. Sometimes spectacularly. There were campaigns that generated hundreds of leads, landing pages that converted far better after we rebuilt them, businesses where changing one part of the marketing system produced an immediate commercial result.

For a while, I thought that was the answer. Better marketing. Better funnels. Better sales. More leads.

Eventually I realised I had been improving individual parts of businesses without understanding the machine connecting them. A company could generate more leads and still have weak positioning. It could improve sales and still lose customers. It could increase revenue while producing very little retained profit. And the founder could become better at everything while becoming an even bigger dependency inside the business.

That was the lesson I missed the first time around. A business is not a collection of tactics. It is a system. And improving one component of an unmapped system often just moves the constraint somewhere else.

That realisation changed the way I thought about business. Years later, it would become one of the foundations of Business Maximizer.

These days I work in data science and advanced analytics at Bank of Singapore, building production-grade data and AI systems for wealth management. And I care deeply about the difference between something that works in a demonstration and something that works in the real world.

The hardest part is rarely making a model produce an answer. The hard part is connecting that intelligence to real workflows, real decisions, real controls, and real human judgment. The technology has to understand enough context to be useful. People have to trust it. Someone has to know when it is wrong. And ultimately it has to fit into the reality of somebody's working day.

The work I find most meaningful is where the technology almost disappears and the decision becomes better. A relationship manager notices the right client at the right moment. A signal buried inside millions of records becomes visible. A colleague who once found AI intimidating understands how to use it intelligently.

Over time, I started noticing something. The problems I had encountered building small businesses and the problems I was solving with data and AI inside large institutions looked very different on the surface. Underneath, they were remarkably similar. Both depended on turning knowledge that lived inside people's heads into systems that could be seen, measured, improved, and eventually executed.

If you took everything I have learned from twenty years of building things — businesses that worked, businesses that didn't, models that shipped, models that stayed in presentations, people, clients, teams, and decisions — and asked me to compress it into one idea, it would be this:

The most important things in business often live at the edges, not at the averages. Trust. Potential. Judgment. Risk. Loyalty. They rarely reveal themselves in the middle of a distribution. They appear in exceptions, outliers, context — the details that disappear when we zoom too far out.

A coastline has no single true length; it depends on the size of your ruler. A team has no single true capability; it depends on who you are asking about, what you're asking them to do, and under what conditions. A client has no single true value; it depends on which relationship, which moment, and which time horizon you are measuring.

The leaders, analysts, bankers, and founders I admire are able to hold two things at once: rigorous mathematics and rigorous humanity. Neither is enough alone. Data without empathy loses context. Empathy without evidence risks becoming intuition disguised as truth.

I call this way of seeing the Fractal Lens. It influences almost everything I build.