About
Hey, I'm Ganesh. I'm 21, and this is not something I usually write.
I don't talk about myself much. But if you're here, you deserve the real version — not the polished bio, not the founder headline, just the story behind all of it.
I come from a small town where there was no real tech scene, no startup culture, and no clear path into any of this. Nobody around me was talking about products, startups, funding, scale, systems, or building something from scratch. Most people followed the same track, and for a while, I thought maybe I would too.
Then Covid happened during my 12th, and everything slowed down.
After that, I took a drop year for engineering entrance. Engineering always felt exciting to me — not because of the title, but because of what it represented. Whenever teachers asked me what I wanted to become, I would say engineer. Not just an engineer by degree, but a good engineer — someone who can solve things practically, not just theoretically.
But during that drop year, something shifted.
Instead of only preparing for exams, I started coding. Late nights, tutorials, confusion, small projects, broken code, fixing things, building again. Slowly, something clicked.
I wasn't trying to become a developer at first. I was just trying to build something real.
And once that feeling hit, it stayed.
The more I built, the more I realised I didn't want to only write code. I wanted to understand the full journey of a product— the idea, the design, the user experience, the backend, the deployment, the performance, the small details nobody notices when they work, but everyone feels when they don't.
That's when building stopped feeling like a skill and started feeling like a direction.
In December 2023, while I was still in college, I started Codence Studio. At first, it was just a freelance side thing — a way to take work, build websites, ship projects, and learn by doing. But slowly, it became more than that.
Codence became the place where I learned how serious execution really works.
Over time, I shipped 35+ products for founders, startups, and businesses — sometimes solo, sometimes with small teams. Every project taught me something different. Some taught me speed. Some taught me patience. Some taught me how important communication is. And some taught me that writing code is only one part of building something people actually trust.
Along the way, I also worked across different roles — frontend at Growero, devops with MP Police, and product/software work at Viral Konnect. Each one gave me a different lens. Frontend taught me how users feel a product. DevOps taught me how systems behave when things go live. Product work taught me that building the right thing matters more than just building fast.
In December 2024, my team and I won Smart India Hackathon. It was one of those moments that looked clean from the outside, but inside, it was pressure, confusion, unclear requirements, tight timelines, and serious competition. We had to figure things out while moving. No perfect plan, no comfort zone, no time to overthink.
We executed anyway.
That experience stayed with me because it showed me what pressure does. It either exposes you or sharpens you. For me, it became proof that when the situation gets serious, I can still build, lead, and deliver.
Outside client work, I kept building my own things too.
AuthKit, an auth platform I wanted to exist. Mockd, a mock API tool to make frontend workflows faster. LSMDB, a database engine I built from scratch just to understand how storage works under the hood.
Not all of these were built to become companies. Some were built because I wanted to understand things deeply. And honestly, those projects taught me more than any course could have. Because when you build something yourself, you don't just learn the concept — you feel the problem.
Right now, I'm running multiple bets in parallel.
I'm growing Codence Studio into a proper product engineering brand — not just a portfolio, not just a service page, but a studio with taste, execution, systems, and a clear identity.
I'm building Redmark Studios for creators and content-led brands, because I believe content, design, and distribution are becoming just as important as product.
I'm exploring new ideas, experimenting with products, learning how capital works, and slowly understanding what it really takes to build something that can scale.
Some days, it feels like too much.
But I'd rather be building too many things than sitting still and waiting for the perfect moment. Because coming from where I come from, there was no perfect moment. There was only a decision to start before things made sense.
My standard is simple: If something is worth doing, it's worth doing properly.
Not perfectly. But seriously.
Full effort. Clear thinking. Attention to detail. No half-work. Small things matter, especially in development. A small bug, a small delay, a small careless decision — these things compound. So when it's work, it's serious.
But the biggest thing I've learned so far is not about code, products, or business.
It's about people.
There are people who trusted me before I had enough proof. People who gave me work when I was still figuring things out. People who believed in the direction before it looked obvious. People who joined, supported, referred, helped, guided, and gave me a shot when they didn't have to.
I haven't forgotten any of them.
If things go well, they benefit first.That's not a strategy. That's just how I'm wired.
Maybe that's also why I care so much about building something that lasts. Not just for myself, but for the people who believed early, for the team growing with me, and someday, for the kind of kids who come from places like mine — kids who have potential, but no clear guidance, no exposure, and no one telling them that they can build too.
So that's the honest version.
Nothing dramatic. No overnight success story. No perfect roadmap.
Just someone who started from scratch, learned by building, kept showing up, and is trying to create something meaningful enough to last.
Thanks for stopping by. Let's build something meaningful.
