Marketing Operations & RevOps — Bengaluru, India
Real systems. Real scale. Real outcomes.
Four years owning the full MarTech stack — from funnel architecture to platform administration. Here’s what that looks like in practice.
Projects
V4 New Contact Marketing Funnel
Problem: BDRs worked across two objects with no unified view. Inbound leads weren’t matching to contacts, creating duplicates and missed follow-ups.
Built: Dual-trigger RingLead configuration covering 5 match scenarios. Every lead auto-converts to a Contact, matches to an Account, and routes to the correct BDR.
Scale: 852,306 leads · 591,566 accounts · 7+ sources · 10 Salesforce change requests.
Account Enrichment Programme
Problem: Prospect accounts missing key firmographic fields — silently mis-routing leads in territory splits.
Built: Two ZoomInfo Company API enrichment paths — real-time on every account create/update, plus a quarterly batch for dormant records. Diagnosed and fixed a recursive trigger loop in sandbox without vendor help.
Scale: 500,000+ Prospect accounts in scope.
Job Title Segmentation
Problem: Raw free-text job titles — 539+ variations of CEO alone. Marketing couldn’t segment by function. Sales couldn’t prioritise by seniority.
Built: Two RingLead segment libraries — 11 seniority tiers and 10+ functional personas stamped automatically at point of entry.
Scale: 12,800+ title variants mapped.
Lead Scoring Rescue
Problem: Failing scoring project. Demographic and firmographic layers not working, score updates taking hours.
Built: Demographic and firmographic scoring in RingLead, combined with the existing behavioural layer into a single Lead Score field in Salesforce. Became the foundation for the company’s Pardot scoring rebuild in 2025.
Lead Routing Architecture
Problem: Lead assignment entirely manual. No territory logic, no automation, no fallback path.
Built: The company’s first automated routing system. 7 products, 7 regions, multiple business units. 352 rules delivering 95–96% accuracy with a 100% catch-all path.
Salesforce Org Migration
Problem: Consolidating multiple Lead Record Type IDs accumulated through acquisitions into a new Salesforce org.
Built: Full RingLead migration — re-established authentication, remapped all Object, Field, and User IDs, and updated every trigger and routing rule. Handled internally without the CSM.
AjayOps.com — Live GTM Pipeline Live
What it is: This site runs a fully operational GTM automation pipeline. The contact form on this site is the entry point — every submission is a live test of the system.
How it works: Form submission → n8n webhook → HubSpot contact created (dedup-checked) and Salesforce lead created in parallel → added to campaign → UTM data captured automatically.
Why it exists: Built as a personal sandbox to test automation logic, validate pipeline architecture, and demonstrate GTM engineering capability end-to-end before deploying similar patterns at scale.
Stack: WordPress.com · n8n · HubSpot · Salesforce Dev Edition · Claude API · Groq
Platform Administration
| Platform | Level | Key work |
|---|---|---|
| RingLead | Full Admin | Trigger architecture, segment libraries, scoring models, routing, deduplication, lead-to-account matching, enrichment triggers |
| ZoomInfo Operations OS | Full Admin | Company API enrichment, industry mapping, NAICS crosswalk |
| Salesforce | Power User | Requirements authoring, Jira user story writing, sandbox UAT, field specification, cross-team delivery coordination |
| HubSpot | Admin | CRM, workflows, contact properties, private app integrations |
| ChilliPiper | Admin | Migrated legacy platform to new Fire platform (September 2024) |
| Pardot | Config | Scoring model foundation, email operations |
| Captello / Swoogo | Admin | Event lead capture to BDR follow-up reduced to under 24 hours |
| n8n | Builder | Multi-system orchestration workflows, webhook handlers, API integrations, error logging |
Want to connect or learn more about this work?