With 6+ years of leading end-to-end product development, I design and build SaaS experiences that turn complexity into clarity. I believe products should feel intuitive, fast, and human; not overwhelming.

What I’ve Owned & Built
Impact of My Product Work
What Changed Because of the Product
Recognitions:



Worked With:


How I Approach Product Problems
When I take ownership of a product, my focus shifts quickly from features to decisions.
The real work begins long before anything is built.
I spend time understanding:
This clarity shapes everything that follows.
How I Handle Product Ownership
In my product roles, I’ve consistently worked across three critical layers:
1. Problem Framing
Breaking broad, messy challenges into solvable product questions —
so teams don’t build fast in the wrong direction.
2. Prioritisation & Trade-offs
Choosing what not to build is as important as choosing what to ship.
I prioritise based on user pain, effort-to-impact ratio, and long-term clarity.
3. Execution with Feedback Loops
Shipping is not the finish line.
I rely heavily on real usage, support signals, and behaviour patterns to guide iteration.
See in the Detailed Case Studies
These aren’t feature showcases.
They’re decision stories.
The human behind the product
Before strategy decks and product releases, there is a person — me — curious, driven, obsessed with better.
I didn't arrive in product through shortcuts or titles. I started where many builders start — at the surface — designing landing pages, understanding structure, testing what converts.
From landing page designer to Product Director in the SaaS industry.
A journey built not on theory, but on curiosity, iteration, and years of real execution.
My growth was shaped by a pattern I still follow every day:
See the gap. Ask the question. Build the solution.
I'm a product thinker who believes in:
My work is my expression. My products are my voice. My impact is my message.
And I'm not done building — not even close.
How I Stay Sharp as a Product Thinker
Some of my most valuable product learning hasn’t come from roadmaps or sprints —it’s come from building small things fast.
I experiment to stay close to real problems, real users, and real constraints.
No long approvals.
No polished launches.
Just ideas turned into working products.
This is where I test assumptions, explore behaviour, and sharpen judgment.
What I Experiment With
My side projects usually fall into three categories:
1. Utility & Problem-Solving Tools

Quotation Calculators - For Online and Onground

Wedding Budget Planner
Small tools built to reduce friction in everyday workflows — pricing calculators, planners, automation helpers.
2. Interaction & Behaviour Experiments

Check out - MazeChase Game

Check out - ClickMe Game
Simple games and interactive builds that help me observe:
3. Product Thinking & Systems

Check out - AIPM Guidebook

Get Json File of N8N WhatsApp Flow
Writing, playbooks, and frameworks where I break down:
Each experiment answers one question:
“What happens when someone actually uses this?”
Why This Matters to My Product Work
These projects aren’t hobbies.
They’re practice.
They help me:
I don’t experiment to show range.
I experiment to improve product judgment.
See in the Projects Below:








Sai Prasad
Product Designer
"Balanced tech with user needs—and made us think bigger, practically."

Javed Rahman
Cloud Expert
"AI automation was a game-changer—ambitious and meticulously executed."

Tanishq Bachani
Support Lead
"He transformed our support team and the customer experience."
Because I don't just join teams — I build with them.
I think deeply. I build fast. I lead with clarity.
If you're creating something ambitious, meaningful, something that simplifies life instead of complicating it; then our paths aren't crossing by accident.
Whether it's product leadership, SaaS scaling, early-stage zero-to-one building, or improving what already works; I'd love to talk.
Let's create the next shift in how technology feels.
Think. Build. Lead.
Together.
