Dharmesh Shah recently wrote about "SHIPpers" — people who see problems, take initiative, and turn ideas into reality.
One line stayed with me:
"SHIPpers are builders who don't let their lack of building experience stop them."
That felt personal.
For almost eight years, I was an analyst.
I studied Computer Science, but I never learned coding the traditional way. Instead, I built my career in analytics and operations at Freshworks and Atlan.
Data became my comfort zone.
But those eight years taught me something valuable: how GTM teams actually work.
Revenue operations. Marketing. Business Development. Pipeline generation. Process gaps. Broken handoffs. The small inefficiencies that slow teams down.
A few months ago, before joining Everstage, I spoke to Siva Rajamani, our CEO.
His vision of building Everstage into the revenue operating system for companies globally really stayed with me because I had felt that problem firsthand.
That conversation gave me clarity. I didn't want to just analyze GTM problems anymore.
I wanted to build solutions for them.
It's been about two months since I joined Everstage as a GTM Engineer, and the shift has been energizing.
I started by working closely with our outbound team. The last two months have been a deep learning sprint: nearly 80 million Claude tokens spent experimenting, building, and turning ideas into usable GTM workflows to build:
• Scoring and prioritization dashboards for BDR teams
• Activity-gap views to catch high-intent accounts slipping through
• n8n workflows to analyze SQLs, document deal context, and create learning loops
I'm also learning areas I had never touched before: automated outbound campaigns, personalized sequences, workflow automation, email systems, and the GTM infrastructure behind scalable pipeline generation.
Grateful to be building this next chapter at Everstage.