Hello everyone, I'm Ajai Jayakumar.
I'm a software engineer with over 12 years of experience helping startup founders build their vision into reality. I've architected systems that handle millions of requests, debugged production issues at 3 AM, shipped critical features under impossible deadlines, and scaled products from zero to thousands of users.
Give me a vision, and I could write the code to make it exist. I was damn good at it.
But as I was spending my life building the foundation for other people's dreams, a quiet voice kept whispering the same question:
"What if you built something that was truly yours?"
That idea wouldn't leave me alone. I didn’t want to just tinker with another weekend side project that would die in a GitHub repo. I wanted to build a real SaaS business, one that solved an actual problem, brought in actual users, and could eventually grow into a sustainable business I could call my own.
It sounded simple. God, was I wrong.
Like any good engineer, I fell right into the classic engineer’s trap: I picked problems I personally struggled with, started coding, and poured late nights into clean architecture, solid tests, and blazing-fast performance. I told myself the greatest lie in software development:
"If it solves my pain, it'll solve it for others too."
Then I launched.
And... silence.
No users. No feedback. No traction. Nobody cared.
That moment hit hard. I could build the product flawlessly, but I couldn't make anyone care about it.
The hardest part wasn't writing the code. The real challenge was discovering whether anyone else actually felt the same pain, and whether they cared enough to do something about it.
After 12 years of being an expert at turning ideas into software, the silence taught me a brutal lesson. I was missing the one skill that mattered most: how to find, and truly understand, my own users.
So I changed my approach.
Instead of starting with code, I started with validation. I scoured Reddit, X, and every community I could find, searching for signals that other people felt the same pain I did. That process generated five different SaaS ideas.
This time, following advice from indie hackers I respected, I decided to validate the market first. But that introduced a whole new problem.
I took to Reddit to pitch my concepts. Within hours, my posts were deleted and my accounts banned by auto-moderators.
- Karma too low.
- Self-promo flags.
I was approaching this all wrong. I didn't even know the rules of the game.
That was my first real lesson in audience building. I watched non-technical founders on X and Reddit hitting thousands in MRR while I, the engineer with 12 years under my belt, sat there doubting myself. Was I just not cut out for this?
I realized something painful.
"A good idea isn't enough. Even a good post fails if you don't understand the platform."
So I decided to test the waters differently. Instead of another complex product, I would build a complete, free tool in a single weekend and pour 100% of my energy into learning how to market it.
The Idea That Led to KodeSnippet
I knew my audience was people like me. I'd noticed a trend on X and LinkedIn: developers love sharing code snippets. But while there are plenty of "code to image" tools, creating an engaging, multi-slide carousel for LinkedIn usually means fighting with generic design tools like Canva.
That sparked an idea. What if there was a simple way to create polished, LinkedIn-ready slides specifically for code?
I explored the space and narrowed further. Instead of building a full design tool, I focused on one niche - helping developers turn code into clean, shareable LinkedIn carousel content.
That's when KodeSnippet was born.
Using AI for the PRD and design tools to shape the experience, I spent one weekend coding. The result is a simple tool that does one thing perfectly turn code with explanations into beautiful LinkedIn carousel PDFs.
The product is live at https://kodesnippet.com.
What I'm Learning Now
But honestly, the real challenge begins now. I'm in the feedback stage, and my goal isn't immediate monetization. It's learning how to gather feedback, iterate based on real user behavior (Product-Led Growth), and figure out how to actually drive traffic. If I can learn to market this weekend project, I'll have the blueprint for the bigger SaaS ideas I want to chase.
I also learned that being technical isn't the same as being a solopreneur. Product thinking, marketing, positioning, and patience matter just as much as clean code.
I'm still early in this journey, but for the first time I feel like I'm learning the right lessons.
- I shipped something real.
- I faced rejection.
- I narrowed the scope.
- I kept moving.
Try It and Share Your Feedback
If you're a developer who shares knowledge on LinkedIn, give it a try. Export a carousel, post it, and tell me how it feels. Your feedback will shape the next version and, honestly, fuel the bigger ideas I'm finally ready to build.
