Pugazheanthi Palani Archives

Untold Story of Pugazheanthi Palani — Part 2

Pugazheanthi Palani / January 15, 2026

The Engineer Before the Founder Story 1 was about consistency.Story 2 is about capability formation—before titles, before companies, before visibility. Before Napblog.Before NapOS.Before “Founder & CEO.” There was engineering work that never went viral, never raised funding, and never had an audience—yet quietly built the operating discipline that everything else stands on today. The Phase Most People Never See Between 2017 and 2019, my life was not about startups. It was about: While blogging trained my thinking, engineering trained my patience. This was the period where execution mattered more than expression. Tracer Arm Machine (TAM): Not a College Project TAM—Tracer Arm Machine—was not built to impress evaluators.It was built to solve a personal performance problem. I was a cricket player.I needed repetition.I needed precision.I couldn’t afford imported bowling machines. So I did what engineers do when systems don’t exist:I designed one. From concept to fabrication, TAM was executed as a full-stack mechanical system: No outsourcing.No shortcuts. The result was India’s first fully indigenous, low-cost tracer arm bowling machine, capable of delivering variable pace, swing, spin, and bounce—designed to be adjustable for users aged 8 to 50 Pugazh Story 2 . This wasn’t innovation theatre.It was applied engineering under constraint. Why Manufacturing, Not Software (At the Time) I chose manufacturing deliberately. Not because it was easy.Because it was unforgiving. Manufacturing exposes reality: There is no abstraction layer to hide behind. That period trained something critical:respect for systems that must work in the real world. This mindset later became foundational to how NapOS is designed: Those principles did not come from startup books.They came from machines that either worked—or didn’t. Early Entrepreneurial Thinking (Before the Word Meant Anything) The IIT Madras bootcamp application captured something important—not ambition, but intent clarity. Even then, the goal was explicit: The TAM roadmap already included: In hindsight, this was product thinking—long before software entered the picture. Research, Not Just Fabrication Alongside fabrication, I was writing. Not blogs—but academic research: The theme was consistent: Systems should adapt to individuals, not force individuals to adapt to systems. This idea later became core to NapOS: The philosophy was already forming—years before the platform existed. What This Phase Really Built This chapter didn’t build a company.It built operating credibility. It trained: Most importantly, it built the ability to stay consistent without external validation. That is the real compounding advantage. Why Story 2 Matters Many people meet founders at the visibility stage.They rarely see the capability stage. Story 2 exists to document that: Before I built platforms, I built machines.Before I built audiences, I built discipline.Before I built systems for others, I learned to operate one myself. Story 3 will cover the transition—from engineering systems to writing systems—from individual execution to public accountability—from projects to platforms. This is not nostalgia.This is architectural history. Because systems make sense only when you know what they were built on.

Pugazheanthi Palani

Pugazh as Blogger – Part 1 {Founder & CEO of Napblog.com}

Pugazheanthi Palani / January 3, 2026

Founder & CEO, Napblog — More Importantly, a Blogger I am writing this with quiet pride. Not because of a title.Not because of a company.But because I am completing my 100th month of blogging — more than 3,000 days of writing. On August 17, 2017, I published my first blog article.The topic was simple: “What is Blogging?”The platform was basic: Google Blogger. No strategy deck.No monetization plan.No personal brand framework. Just a young mechanical engineering student, a blue diary, and a need to think clearly. Eight-plus years later, here I am — founder of Napblog — still writing.Not because I have to.But because I cannot not write. This article is not advice.It is not motivation.It is not storytelling for engagement. This is evidence. Before Blogging: The Blue Diary Phase Before the internet saw my words, paper did. In 2016–2017, I maintained a small blue diary.Every day, I wrote: At that time, my immediate goal was clear:Shortlist universities for Summer 2017. But something else was happening subconsciously. Writing gave me: I didn’t know the term metacognition then.I was simply thinking by writing. That habit never left me. Blogging was not a leap.It was a natural extension. The First Blog: August 17, 2017 My first blog was not confident.It was not polished.It was not SEO-friendly. But it was honest. I wrote about: I used Google Blogger because it removed friction.No domain obsession.No design paralysis. Just write. That single decision — choosing ease over perfection — shaped the next 100 months. Discovering a Mentor Without Meeting Him Around the same time, I discovered Deepak Kanakaraju, founder of DigitalDeepak.com. I did not meet him.I still haven’t. But I learned from him extensively through: What stood out was not tactics. It was clarity. His work demonstrated something critical: Marketing is not manipulation.It is structured communication. That principle quietly embedded itself into my thinking — long before Napblog existed. Falling in Love With Writing (Without Realizing It) I did not “decide” to become a writer. I became one by repetition. Every blog post helped me: I strongly dislike hallucination writing — content without grounding.I never wanted to sound smart.I wanted to be accurate. Writing forced accountability. If I claimed something, I had to: That discipline shaped not just my blogging — but my leadership later. Flow State: Writing for Its Own Sake There is a psychological concept called Flow State: Being completely involved in an activity for its own sake. That is how I write. Not for: But because writing places me in deep focus. Time disappears.Noise fades.Only thought remains. That is why consistency became natural. Evidence Over Imagination Over the years, I have: You can see the evidence: I am not embarrassed by them. They prove continuity. From Mechanical Engineering to Marketing Thinking My background in mechanical engineering shaped how I blog. I think in: Blogging became my sandbox. Each article was a test: That mindset later became Napblog’s first principle: Marketing is providing the right information, at the right time, to the right people. The Compound Effect of Daily Actions From Month 1 to Month 100: I contacted people via: This went against my childhood conditioning. But I intentionally practiced: Not to appear like a leader —but to become one. Blogging Was the Training Ground for Napblog Napblog did not begin as a company. It began as: Before there were interns, clients, or platforms —there were blog posts. That is why I say this clearly: I am a founder because I was a blogger first. Why This Matters (Even If No One Reads It Today) I do not know who will read this: But I know this: Daily actions compound.Outcomes become predictable. If even one aspiring marketer reads this and realizes: Then this 100-month journey has already paid off. Closing Thought I am proud — not of success — but of continuity. Titles will change.Companies will evolve.Markets will shift. But the habit of sitting down and writing honestly —that stays. This is Part 1. The story continues. —PugazhFounder & CEO, NapblogMore importantly, a Blogger