Where It All Began: The Story Behind Darwin Corp

I was born in 1994, which means my entire childhood ran in parallel with the internet's own. I do not remember a version of growing up that did not involve watching some new piece of technology arrive and completely rearrange what was possible. Dial-up internet, then broadband. The first mobile phones that felt like magic just for sending a text. Social media appearing out of nowhere and suddenly making every teenager a tiny publisher. Video games that kept getting more ambitious every single year. I was not a spectator to any of this. I was exactly the right age to grow up inside it, and looking back, I think that timing shaped almost everything about who I became.

The earliest version of that shape was simple curiosity. I was the kid who wanted to understand how the poster looked good, why one social media post got more attention than another, what made a video game's interface feel satisfying to touch. I started making my own creatives, nothing serious at first, just design work I could post online and watch people respond to. That feedback loop, make something, put it out into the world, see what lands, is probably the first real education I ever had, and I did not even realise at the time that it was one.

The first real jobs, and the parts nobody glamorises

My first proper job was at Innodata, a data entry company based in Sri Lanka. I worked on a project connected to Apple's iBookstore, entering and processing data for hours at a time. It was not creative work in any obvious sense, and I will not pretend it was glamorous. But there is something underrated about starting your career doing precise, unglamorous, detail-heavy work. It teaches you a kind of discipline that design school never quite manages to, the discipline of getting something exactly right, over and over, when nobody is watching and nobody is going to praise you for it. I did not know it then, but that habit of caring about the tiny, invisible details would end up becoming the entire foundation of how I approach design years later.

From there, I was welcomed into a role as a graphic designer at Virtubil, a Sri Lankan company that mainly built ERP systems. This was the real beginning of my design career, the first time I was being paid specifically because of my eye rather than my patience. ERP software is about as far from glamorous creative work as you can get, dense, functional, built for efficiency rather than beauty, but designing inside that world taught me something I still carry with me: even the most utilitarian product deserves a considered visual language. Nobody expects an ERP system to be beautiful, which is exactly why making even part of it thoughtful stood out.

After Virtubil, I moved to Ceylon Technology Corp, another Sri Lanka based company with its own suite of products, including Where, a GPS tracking system, and Pineapple, an ERP platform that included a customer loyalty and rewards component. Within that same company sat Brandfactory, a sub-service focused on SEO and digital marketing, and that is where I spent real time. It was the first place I had to think about design not as a standalone deliverable but as part of a larger machine, how a brand shows up in search results, how visual identity connects to marketing performance, how creative work has to serve a measurable business goal rather than just looking good in a portfolio. That shift in thinking, from designer to someone who understands the systems design sits inside, turned out to matter more than almost anything else I picked up early on.

2019, and the start of something that was actually mine

In 2019, everything changed direction. I met Leonardo Vieira, a Brazilian designer, through Upwork, and what started as a working relationship turned into a genuine creative partnership. Together we formed a company specialising in brand identity, the kind of full, considered brand systems I had been circling for years without ever having the chance to build one from the ground up, on my own terms. We called it Sequoya at first. Later, we renamed it Carthagos.

That name change matters more to me now than it probably should on paper, because it represented something real: the company was not static, it was allowed to grow into itself, to become a more accurate name for what we were actually building as we understood it better. Carthagos was where I learned what it meant to own a creative business rather than simply work inside one, pricing, client relationships, the discipline of delivering brand work that could actually hold up under a client's scrutiny, not just mine.

Learning to build the thing, not just design it

Somewhere in that same stretch of years, I started teaching myself CMS based web development, and WordPress became my entry point into actually building the things I had spent years only designing. That was a real turning point. Up until then, my creative work always ended at a handoff, a file passed to a developer who would turn it into something real, with all the inevitable loss of intent that happens in translation. Learning to build meant I no longer had to hand anything off. The idea and the execution could live in the same hands, mine, and nothing got lost between the two anymore.

By early 2025, that instinct had evolved again. I started using Webflow to connect creative design directly with websites and applications, no-code tooling that let me move at the speed my ideas actually demanded rather than the speed a traditional development handoff allowed. And not long after that, I turned to vibecoding with Claude Code, genuinely building software through conversation with an AI model, watching the gap between imagining something and having it exist shrink down to almost nothing. If you had told the kid entering data at Innodata that one day he would describe entire products into existence, he would not have believed you. I am not sure I entirely believe it myself, even now, having lived through every step that led here.

The agency that taught me what I did not want

Somewhere in this period, I also co-founded another creative agency, one I would rather not name here. It is not something I regret, every part of that experience taught me something, but it ended because I genuinely disagreed with the direction the company was heading and the culture that had formed around it. I will not pretend that was an easy thing to walk away from. It rarely is. But I have come to believe that knowing exactly what you do not want to build is sometimes just as valuable as knowing what you do want to build, and that experience sharpened both in equal measure.

Darwin Corp

Everything before this was, in hindsight, a long apprenticeship I did not fully recognise as one while I was living through it. The data entry work that taught me discipline. The ERP design work that taught me restraint. The SEO and marketing work that taught me how design serves a larger system. Carthagos, which taught me ownership. WordPress, which taught me to build. Webflow and Claude Code, which taught me that the distance between an idea and its execution can keep shrinking for as long as you are willing to keep learning.

Darwin Corp is where all of that finally converges. It is named, quite deliberately, after the idea of evolution, the belief that a brand, a creative practice, and a person are all the same kind of thing: systems that are supposed to keep adapting rather than settling into something fixed. Everything I do now, the strategy, the visual systems, the websites, the way art and advanced technology sit together in the same sentence instead of two separate ones, comes directly from that decade spent moving between data entry, ERP interfaces, brand identity, code, and now AI-assisted creation. I did not plan that path in advance. Nobody really does. But looking back at it now, every step was quietly building toward the same thing: a studio where creative vision and the technology behind it are never treated as separate disciplines, because in my own life, they never actually were.