Nitya Chidambaram

Operator.
Builder.
Systems thinker.

I’m a co-founder of HeyAmos, helping teams turn AI visibility into a growth channel.

Nitya Chidambaram

Co-founder, HeyAmos. Operator. Systems thinker.

I work on the messy challenges that sit between growth, product, GTM, and scale.

Over the last decade, I’ve worked across marketplaces, healthtech, fintech, rewards, and now AI search. My work has usually sat in the middle of ambiguity: new markets, new products, new revenue models, and teams figuring out what to prioritize next.

I care deeply about adoption because a product only matters if it fits into how people actually work.

What I’m Building

I’m a co-founder of HeyAmos, a platform that helps you turn AI visibility into a growth channel.
We give marketing and go-to-market teams the analytics and insight to win in AI search, without spending years acquiring the skill first.

The Journey

Over the last 12 years, I’ve scaled teams, functions and businesses across 15 markets at Amazon, Practo, and ShopBack.
I’ve thrived in the messy middle of sales, ops and marketing, solving for the engine that makes companies grow and quietly breaks when they grow too fast.

The Pattern I Keep Seeing

The most capable people slow down the moment they lack context and access. They know exactly what to do but can’t act without data, tools, or context that lives with someone else.
So they wait. The best person for the decision becomes the slowest link in the chain.

What I Believe

Most of the time, skill is just context plus the specific action to take, delivered the moment you need it.
Hand people that, and they act on their own judgment from day one instead of waiting weeks or learning for years. With AI, that is the biggest leverage we have.

One belief I keep coming back to: adoption is not a downstream problem. It is a product and systems problem. When a platform is poorly adopted, it usually means the product has not met users where they are, fit naturally into their workflow, or made the value clear enough at the moment they need it.

How I Think

I start from first principles, always. Not “what’s the best practice” but “what is actually true here.” What worked? What broke? Why?
I pull a problem apart until I hit the part that doesn’t move, then build back up from there. I ship fast, kill faster, and measure ROI over activity.
And I stay close to the customer, two or three levels into their workflow, because that is where the real answer always hides.

Where I Sit

Somewhere between operations, product, and business strategy.
It’s the messy middle, and it’s my favourite place to be. If that’s your world too, we’ll probably have a lot to talk about.

Explore work → Read essays →