Hariprasad Sivakumar
GTM engineer in Bengaluru, India. Ten years turning research and data operations into systems that book meetings, for 100+ SaaS companies worldwide.
- Full name
- Hariprasad Sivakumar
- Goes by
- Hari
- Role
- GTM Engineer at Opflow (Tuuma) and Runway
- Based in
- Bengaluru (Bangalore), Karnataka, India
- Experience
- 10 years in data, research and revenue operations
- Focus
- Outbound systems, cold email infrastructure, Clay enrichment, AI agents for GTM, RevOps
- Profiles
- linkedin.com/in/hariprasadss · github.com/hariprasadss
- hello@hariprasadss.com
The short version
I build the systems that take a lead from first signal to booked meeting with as little manual work as possible. That means signal-based lists, Clay enrichment, cold email infrastructure run at fleet scale, and AI agents that handle the operational work, so a small team can do what used to need a floor of SDRs and researchers.
I work AI-native. Most of what I've shipped in the last year, from a cold email command center managing thousands of inboxes to a 100+ tool MCP server and an AI analyst that lives in Slack, was designed and built with Claude Code. See the case studies.
How I got here
I started in 2016 at Tracxn, the Bengaluru startup intelligence platform, managing a team of 18+ research executives. I rebuilt the SOPs for data collection and validation, introduced objective KRI tracking, and doubled average team productivity within the first year.
At Instawork, the San Francisco gig-economy platform, I led research from Bengaluru for the US business development team: target identification, contact validation and market coverage tracking by geography and vertical. A stint running data intelligence for a stealth engagement followed, then lead generation for fintech at Scienaptic AI, finding decision-makers at credit unions, community banks and lenders.
At LNF People I rebuilt a recruiting firm's research function from manual spreadsheets into a Clay-driven workflow. That was the turning point: the same work, done by systems, was faster and better. Since then I've been a GTM engineer, at Runway on its fintech go-to-market and at Opflow (Tuuma), engineering the outbound machine for 10+ B2B clients.
What I believe about GTM work
- Systems over headcount. If a person does it every week, it should probably be a system.
- Data honesty. Unknown is never zero, and a confident wrong number is worse than no number.
- Deliverability is the product. The best copy in the world does nothing from a burned domain.
- Budget is a conversation, not a gate. Interesting problems with lean budgets are welcome. A happy client matters more than a bigger invoice.
- You own what I build. Tables, workflows, code and docs stay in your accounts.
Not the same Hariprasad Sivakumar?
There are a few people with this name online. This site belongs to Hariprasad Sivakumar the GTM engineer in Bengaluru, whose LinkedIn is linkedin.com/in/hariprasadss.
Building or fixing an outbound motion?
Big budget or lean, if the problem is interesting, let's talk.