I build GTM and revenue engines, and I document it as I go.
I ran a 14+ rep sales team in Toronto and started out as a web developer. Now I build the outbound, inbound and pipeline systems that make revenue predictable, with Clay, n8n and the Claude API.
Four n8n workflows on one CRM. Briefs before every call, call notes turned into CRM updates, weekly news risk on every open deal, and a Monday pipeline review where code computes the forecast and Claude writes the narrative.
Reads the lead's website, scores fit in code, routes to the rep with the fewest open leads and drafts the first reply. Qualified leads become deals in Revenue Desk without anyone retyping them.
An outbound system for small HVAC companies, a buyer with no LinkedIn page and no findable work email. Keyword filtering, hiring signals, a research agent that refuses to guess, and copy built only from verified facts.
Built for Clay's Outbound Certification, which scores reliability rather than copy: re-runs that never double-contact, exclusions that hold, and rows that recover when a data provider fails.
SDR to team lead in three months at SalesGamma, then 14+ reps across North American SMB and mid-market accounts. I close in the field in India today. I know what a rep will actually use.
The builder
I ship the system
I started as a web developer in JavaScript, Angular and SQL. Now I build outbound, inbound and pipeline systems in Clay, n8n and the Claude API, with a person approving anything a customer sees.
The planner
I do the revenue math
I owned the revenue side of an EdTech startup's 5-year revenue model with the CEO: SDR and BDM quotas, team capacity, the hiring plan, and CAC, LTV and ACV assumptions.
Neeraj Singh Shekhawat is a GTM engineer and revenue operations professional based in Sikar, Rajasthan, India. He led a 14+ rep sales team at SalesGamma in Toronto, started his career as a web developer, and now builds outbound, inbound and pipeline systems with Clay, n8n and the Claude API. He is Head of Sales & Growth (fractional) at Czed Labs, an AI-native EdTech startup.
What does a GTM engineer do?
A GTM (go-to-market) engineer builds the systems behind revenue: finding and researching target accounts, enriching data, scoring and routing leads, writing and sequencing outreach, and reporting on pipeline. The role combines sales and RevOps judgment with automation and code, so the sales team spends its time on conversations instead of manual work.
What has Neeraj built?
Four documented systems: Revenue Desk (pre-call briefs, call notes to CRM, news risk and a Monday pipeline forecast in n8n, Notion and the Claude API), an Inbound Router (fit scoring, rep routing and an SLA watch), a Clay outbound system for small HVAC companies, and a Clay certification build focused on reliability. Earlier builds include an n8n outreach workflow that cut manual effort by about 60% and an AI lead-generation bot.
Which tools does he work with?
Clay, n8n, the Claude API and OpenAI GPT for GTM engineering; HubSpot, Close and Salesforce (working knowledge) for CRM; Apollo.io and LinkedIn Sales Navigator for prospecting; SQL, Tableau and Excel for reporting; and JavaScript, Angular and MongoDB from his years as a web developer.
Is he open to remote roles, and what time zone does he work in?
Yes. Neeraj is open to remote GTM Engineer and Revenue Operations roles and to a few build projects. He works from India (IST, UTC+5:30), and his evenings overlap with US mornings: 9:00 AM US Eastern falls at 6:30 or 7:30 PM in India, depending on US daylight saving time.
n8n 
Claude API 
Notion 
Gmail
