Signal-based list building
Lists built from real buying signals (hiring posts, tech stack, funding, ad activity), enriched through provider waterfalls and pushed through a 5-step QA gate before a single email goes out.
I'm Hari, a GTM engineer based in Bengaluru (Bangalore), India. I've built outbound and RevOps systems for 100+ SaaS companies worldwide: signal-based lists, Clay enrichment, cold email infrastructure at fleet scale, and AI agents that run the ops so your team can sell.
AI, fintech, adtech, marketplaces and recruiting · teams in the US, UK, Europe and India
Stale data, disconnected tools, inboxes that quietly burn and sequences that treat every lead the same. I build the layer underneath the motion that fixes it, and the tooling that keeps it fixed.
Lists built from real buying signals (hiring posts, tech stack, funding, ad activity), enriched through provider waterfalls and pushed through a 5-step QA gate before a single email goes out.
Domains, DNS, Google and Microsoft inboxes, warmup, rotation, capacity math and daily blacklist checks. Set up properly once, then monitored and healed automatically.
Persona-locked campaigns, deep spintax that still reads human, suppression on every list, lead recycling and reply handling, so volume never costs you your domain reputation.
Research agents that qualify accounts with a source URL for every claim, a Slack analyst that answers pipeline questions from live data, and MCP servers so Claude can run your outbound.
n8n workflows, webhooks and APIs connecting Clay, your sequencer, CRM, Slack and Notion, so data moves on its own and nobody copies rows between tabs.
HubSpot and Salesforce kept clean, lead routing that makes sense, and weekly reports with reply, positive and meeting rates that leadership can actually trust.
Not slideware. These are systems I designed and shipped, AI-native and built with Claude Code, running daily for a GTM agency and its 10+ B2B clients. Read the full case studies
The team asks in plain English ("send me last week's report for a client", "is the new campaign ready to launch?") and it answers from live data across the sequencer, Notion, the infra command center and enrichment APIs. One tool-calling agent routes every message, code renders the numbers, and the model is never allowed to invent a metric.
A command center so nobody has to live inside Smartlead. Every inbox gets a health score, every domain is tracked from registrar to campaign, and a deliverability doctor flags problems before they cost a send. Drive it from the web app, a natural-language command palette, or Claude over MCP.
The whole command center exposed over MCP, so Claude Code, Codex or claude.ai can run the operation in plain English. Reads run instantly. Writes return a preview with up to three ranked options and wait for confirmation. It never buys and never launches a campaign on its own.
A state machine that turns a client's website into live sending infrastructure: brand-safe domain ideas, purchase hand-off, nameservers and DNS, Google and Microsoft split, provider connect, forwarding and persona inboxes. Retries, idempotency and manual override at every step.
A daily pre-send job scans every domain and inbox, fixes DNS, and pulls broken senders out of live campaigns before the day's sends. Autopilot then graduates newly warmed inboxes in and syncs leads per day to real capacity. Drain-safe, so a follow-up is never orphaned.
Signal-based list builds waterfalled across data providers, then forced through QA: title recheck, normalization, two-stage email verification, email-to-company affiliation and geography. A list isn't done until it passes.
Four trained Claude subagents, one per campaign, source and qualify accounts for a fintech client. Every company has to prove one qualifier with a source URL, gets deduped against suppression, and the agents keep a self-learning ledger of what worked.
Reads SaaS verification records, MX and SPF to prove which tools a company actually uses, without paying for technographic data. It answers questions vendors can't, like which software companies already use Anthropic or OpenAI, or whether a prospect runs Teams or Slack.
Pulls GTM-role postings from public job boards, dedupes across boards and cities, adds an AI "why now" angle and pushes only net-new jobs into Clay, so reps reach out the week a team starts hiring.
A spreadsheet-native GTM workspace: waterfall enrichment across data providers, verified email finding, company discovery and AI research agents in a familiar sheets interface. The tool I wished existed while running enrichment at scale.
Active ads from Meta, Google and LinkedIn for any domain, batch-run across whole account lists, so outbound can open with what a prospect is actually running right now.
Live credit balances for every data vendor, a daily blacklist and DNS diff to Slack that never reports a false "clean", and a cost ledger for rented inboxes with AI invoice extraction.
Cool problems beat big budgets.
I'll say it plainly: budget is never my first filter. If the problem is interesting and you care about doing it properly, I'm in, whether you're a funded scale-up or a two-person team testing outbound for the first time.
That isn't charity, it's confidence. I trust the quality of what I ship, and a client who sees the system working matters more to me than the size of the first invoice. It's why a lot of my work comes from founders who reached out with a lean budget and a real problem.
Cold email infrastructure, a Clay enrichment workflow, a signal-based list engine or a custom AI agent. Fixed scope, fixed price, handed over with docs.
Ongoing list building, campaign launches, infrastructure and reporting on a monthly retainer, for teams that need the output without the full-time hire.
A teardown of your data, sending infrastructure, copy and CRM, with a prioritised fix list you can run yourself or hand to me.
From managing 18-person research teams in Bengaluru to engineering the systems that replace the manual work entirely.
Engineering the outbound machine for a GTM agency serving 10+ B2B clients across AI, fintech and adtech. Built the cold email command center, an AI GTM analyst in Slack, a 100+ tool MCP server, the domain-to-inbox orchestrator and the list QA gate featured above, and run list building and campaign launches for clients like BuildBetter, Cascade Debt, Booyah and Experiential Labs.
Building and maintaining the outbound infrastructure for Runway's fintech go-to-market motion, including the cfo.ai launch. Clay workflows for enrichment and ICP scoring, n8n automations connecting data signals to outreach triggers, cold email execution through Outreach and EmailBison, and HubSpot kept clean, structured and actionable.
Led the research function for a US-based recruitment firm. Rebuilt research from manual spreadsheet work into a systematic, Clay-driven workflow for enrichment and verification: faster lead turnaround, better data quality and higher ICP match rates delivered straight to the client's sales team.
Lead generation for Scienaptic's fintech sales team: identifying decision-makers at credit unions, community banks and lending institutions, with research, enrichment and list building for outbound campaigns.
Ran data intelligence operations for a confidential engagement: large-scale data collection, validation and delivery pipelines.
Led the research function for Instawork, the San Francisco gig-economy platform, from Bengaluru. Research workflows for target identification, contact validation and market coverage tracking by geography and vertical, supporting US business development.
Managed a team of 18+ research executives at one of the world's leading startup intelligence platforms, headquartered in Bengaluru. Rebuilt SOPs for data collection and validation, introduced objective KRI tracking, and doubled average team productivity within the first year.
80+ tools across data, signals, sending, infra, AI and cloud. The value is in how they're wired together, and in building the piece that's missing.
Looking for a GTM engineer in Bangalore, or anywhere else? Start here. More on the GTM engineer in Bangalore page.
Hariprasad Sivakumar (Hari) is a GTM engineer based in Bengaluru (Bangalore), India, with 10 years in data and revenue operations. He has built outbound, enrichment and RevOps systems for 100+ SaaS companies worldwide, including Runway, BuildBetter, Cascade Debt, Booyah, Experiential Labs, Instawork and Tracxn. He currently works as a GTM engineer at Opflow (Tuuma) and Runway. More about Hari.
Yes. I'm a GTM engineer in Bengaluru (Bangalore) and I take on project builds and monthly retainers for SaaS teams in India, the US, the UK and Europe. Book a 30-minute call or email hello@hariprasadss.com.
A GTM (go-to-market) engineer builds the systems behind pipeline: the data, automation and infrastructure that take a lead from first signal to booked meeting. That covers signal-based list building, Clay enrichment waterfalls, cold email infrastructure and deliverability, AI research agents, CRM hygiene and reporting, so a small team can do the work of a large SDR floor.
Yes. Budget is never my first filter. If the problem is interesting and you care about doing it properly, I'll find a scope that fits, often a smaller first build that pays for itself before we expand.
I trust the quality of my work, and a client who sees the system working matters more to me than the size of the first invoice.
Yes, most of my clients are outside India, mainly in the US, UK and Europe. Working from Bengaluru (IST), I overlap with European business hours and US mornings, and builds move forward overnight while US teams sleep.
Yes, the full stack: domain selection, DNS (SPF, DKIM, DMARC), Google Workspace and Microsoft inboxes, warmup, sender rotation, capacity planning and daily blacklist monitoring. I've run fleets of 5,000+ inboxes across 400+ domains and built the tooling that provisions and heals them automatically.
80+ tools. The core: Clay, Apollo, LeadMagic, AI Ark and TheirStack for data and signals; Smartlead, Instantly, EmailBison, Outreach, Lemlist and HeyReach for sending; Zapmail, Hypertide, InboxKit and GlockApps for infrastructure and deliverability; n8n, HubSpot, Salesforce and Attio for automation and RevOps; Claude Code, Claude, OpenAI and MCP for AI agents; and Vercel, Neon, Supabase, Railway and Cloudflare to ship custom tools. When a tool hits its ceiling, I build the missing piece.
It depends on scope rather than a rate card. A focused build, such as cold email infrastructure or a Clay enrichment workflow, is a fixed-price project. Ongoing campaign and infrastructure work runs as a monthly retainer. Lean budgets are welcome: tell me what you're working with and I'll tell you what's realistic.
30 minutes. Bring your current stack and your number, and I'll show you where the system is leaking and how I'd fix it. Big budget or lean, if the problem is interesting, let's talk.