I was born and raised in Mummigatti, a village near Dharwad in Karnataka.

For the first part of my life, that was my whole world. Familiar roads, familiar faces, a close community, and a simple life where everyone knew everyone. I was the second child out of three, and until my 10th Standard, I grew up there without fully understanding how big the world outside could be.

But even as a kid, I could sense one thing clearly: if we stayed where we were, our options would be limited.

Not because the village lacked heart. It gave me my roots. But education, exposure, and opportunity were harder to reach.

So I asked my parents if we could move to Dharwad.

In my head, the reason was simple: “If we move to the city, it will help all of us study better.”

Looking back, that was not a small ask. My parents were not formally educated. Moving from a village to a city meant more expenses, more uncertainty, and more responsibility. But they listened. And eventually, we moved.

At that time, I did not know any fancy words like entrepreneurship, risk-taking, or opportunity cost. I only knew that if we wanted a better future, we had to move closer to opportunity.

That became a pattern in my life.

I was not the smartest kid in the room, but I liked challenging myself. Sometimes it was participating in drama, dance, sports and academics. I did not always know whether I could win, but I wanted to try. I wanted to see what would happen if I pushed myself beyond what felt comfortable.

When I chose engineering, the path was not easy. I completed my Bachelor of Engineering in Computer Science with the help of an education loan. I wanted to pursue higher education after that, but money was a real constraint. I had already taken a bank loan, and I knew I could not keep adding more pressure on my family.

My parents had already done everything they could in their own way. Even today, they continue to work hard through small businesses like food catering to support themselves financially, and I try to support them whenever I can.

That background taught me something I still carry today: when resources are limited, you learn to become resourceful. You learn not to waste opportunities. You learn that nobody is coming to hand you a perfect roadmap. You have to build one while walking.

During college, one of the biggest turning points came through a state-level competition at SAP Labs India.

Two of my college friends and I participated in it, and we eventually became runners-up at the state level. At that time, I did not fully understand how important that moment was. But looking back, it was one of the first times I realised the power of building something and letting the work speak for itself. You can watch the presentation of our working prototype in the final round here: https://www.youtube.com/watch?v=g55l4japZ5k

That competition changed how people saw us. More importantly, it changed how I saw myself.

I eventually got a job out of college without going through the usual interview process because industry leaders had already seen what we were capable of through that event.

That was a powerful lesson: sometimes opportunities do not come because you ask nicely. They come because you build proof.

After college, life gave me another challenge - this time, a personal one.

During my Bachelor of Engineering, I had met the love of my life. After I got my first job, I did not have a settled future, financial stability, or a big background to lean on. But I knew one thing clearly: I wanted to build my life with her.

Convincing her family, especially my father-in-law, was not easy. I was not walking in with wealth or certainty. I was walking in with belief - belief in myself, belief in our future, and belief that I could take responsibility for the life we wanted to build.

That phase taught me something I still value deeply. When something truly matters, you cannot just hope quietly. You have to stand up, communicate, earn trust, and prove through your actions that your words mean something.

Looking back, that was also a form of building. Not building software, but building trust, building a future, and building a life with someone.

A few years later, I started feeling the pull toward a bigger professional stage.

That eventually led me to Germany.

But moving from India to Germany was not easy. It did not happen because someone randomly opened a door for me. I had to find the door first.

I started networking with my college seniors who were already ahead in their careers. I asked questions. I listened. I tried to understand what kind of skills startups outside India were looking for.

Then I started upskilling myself. After office hours, I would sit with my laptop and learn new technologies, startup-style development, better engineering practices, and interview preparation.

Some days it felt exciting. Some days it felt impossible.

But I kept going because I knew one thing clearly: if I wanted a different life, I could not prepare like everyone else.

Eventually, the effort paid off. I cracked the interview and landed in Berlin.

That move changed my life again. From a village –> Dharwad –> engineering, and now from Bengaluru –> Germany - every step felt like entering a bigger room where I had to prove myself again.

Berlin gave me confidence that a boy from village, who studied engineering through an education loan, could build a career on a global stage.

From Germany, the journey later took me to the UK. Over the years, I worked with startups, engineering teams, and product teams. I built mobile apps, solved technical problems, learned from talented people, and kept putting myself in unfamiliar environments.

Every move felt uncomfortable in the beginning. But every time, I came back to the same question: if others can figure it out, why can’t I?

That question has followed me for most of my life. It helped me ask my parents to move from village to Dharwad. It helped me get into engineering. It helped me prove myself through SAP Labs. It helped me build my first career opportunity. It helped me convince my father-in-law to trust the future I wanted to build with his daughter. It helped me move to Germany. It helped me grow in the UK.

And now, after nearly a decade abroad, it has brought me back to Bengaluru.

This time, I am building Naapy.

The idea did not come out of nowhere.

For years, I built mobile apps professionally. I also built apps for clients through freelancing. Many clients came to me with ideas that sounded simple at first, but once we discussed the product properly, the same problem appeared again and again.

They did not just need a mobile app. They needed a backend, a database, APIs, authentication, payments, dashboards, and all the invisible pieces that make a product actually work.

That was always the blocker for me.

My strength was mobile. I knew how to build Android apps. I understood mobile architecture, user flows, app quality, performance, and delivery. But when someone asked me to build a complete full-stack product, I would hit a wall.

Before AI, that gap was not easy to close. You either needed a backend engineer, a larger team, more budget, or much more time.

But AI changed something for me.

It gave me the ability to move beyond only mobile. It helped me understand, build, debug, and connect more parts of the software stack - mobile, backend, database, APIs, testing, and deployment.

For the first time, the thing that used to block me started becoming possible.

That is where Naapy became personal.

Naapy is not just another product idea for me. It comes from a problem I have felt directly: knowing someone has a good idea, knowing I can build part of it, but also knowing that a real product needs far more than a mobile interface.

It needs product thinking, architecture, backend systems, databases, authentication, payments, testing, deployment and continuous improvement.

For years, building all of that meant assembling a team of specialists before the idea could be properly tested.

AI is beginning to change that.

The first wave made code easier to generate. But generating code is not the same as building a product people can depend on.

I believe the next shift will be bigger: mobile engineers/freelancers will be able to direct specialised AI agents that work together like a product team, taking an idea through product definition, architecture, development, testing and release.

After more than a decade of mobile engineering, that is the future I want to help build.

Naapy is my attempt to make it possible for mobile engineers/freelancers with a clear idea to move much further before needing to assemble a full engineering organisation.

In many ways, Naapy feels like the next chapter of the same pattern I have followed since childhood: see the gap, move closer to opportunity, pick something ambitious, learn fast, build proof, earn trust, and keep going.

I have always been drawn to building.

Not because it was easy.

But because building gave me a way to change my own story.