Nikhil Raj PK
Nikhil Raj PKGrowth Engineer · Marketing Ops & GTM Systems
Growth Engineering — Proven in Production

Marketinginstinct.Engineeringdiscipline.Livesystems.

I'm a digital marketer who builds the systems growth runs on — pipelines, CRM logic, qualification and reporting that hold up in production.

5 systems in production79 workflow executions37/37 tests passing
Who am I

A decade of marketing, rebuilt on an engineering base.

Most growth engineers started with code and are learning marketing. I went the other way — B.Tech in Computer Science, ten years of marketing judgment, now building the systems growth actually runs on.

2016–2021

Marketing Foundations

Campaigns, landing pages, creative ops

2022–2023

Acquisition & Analytics

Google Ads, GA4, tracking architecture

2023–Now

Growth Engineering

Data pipelines, AI qualification, human-in-loop outbound — live in production

GTM Stack Map

Tools matter less than the handoffs.

I'm a digital marketer at the core — campaigns, paid media, creative. The chain below is what I've built around that craft, so every campaign runs on clean data and clear handoffs.

01

Source

Find the signal

Python Apify Apollo LinkedIn

02

Enrich

Complete the record

REST APIs Waterfall logic CSV/JSON

03

Qualify

Score against ICP

LLM APIs Prompt specs JSON output

04

Approve

A human decides

Airtable Review console

05

Send

Reach out, carefully

Instantly Smartlead n8n Webhooks

06

Track

Measure what matters

GA4 GTM MS Clarity

07

Report

One version of truth

Power BI Custom CRM SQL

The marketing craft

Where I come from — and still operate daily.

Google Ads Meta Ads LinkedIn Campaign Manager GA4 GTM MS Clarity Landing Pages / CRO Email Campaigns Figma Adobe Suite Content & Creative Ops

The systems ecosystem

What I build with, integrate, or design workflows around.

Salesforce Zoho HubSpot Clay ZoomInfo Clearbit Make Zapier 6sense Gong Snowflake BigQuery Google Ads Meta Ads Figma GitHub Supabase Next.js FastAPI
Core Systems

The operating layer.

Three lenses on the same job — data, automation, and revenue. Switch between them to see how I approach each layer.

Marketing Ops / GTM Systems

Data becomes useful only after it is cleaned, shaped and routed.

I focus on the layer before campaigns and CRM handoffs: public signals, CSV/JSON structure, source normalization, enrichment prep and data hygiene.

CSV / JSON

Data Shape

Technical Insight

Source Normalization

Python and Apify workflows used to turn scattered public B2B/B2G information into cleaner operating records.

Built Work // Production Systems

Production work,
kept factual.

Real work across data extraction, CRM workflows, paid acquisition and reporting. No fake metrics, no invented outcomes, only systems that can be explained and shown with sanitized proof.

Built

B2G Procurement Data Extraction Workflow

Automated workflows for sourcing and structuring defense and procurement-related contact data from public sources.

Proof to show

Architecture diagram, sanitized extraction log, source map and cleaned output sample.

Read the full system breakdown
PythonApifyLinkedIn AdsCRM Workflows

How it flows

01Identify target sources
02Run Python/Apify extraction
03Clean fields
04Prepare CRM-ready output
05Campaign handoff
Measurement & Attribution

The work is the system.

Every system above ships with its measurement wired in: GTM events, GA4 conversions, source-to-CRM attribution and reporting views leadership actually opens. That discipline comes from years of running paid acquisition — where untracked spend is just spending.

Next: the lab — these patterns, rebuilt in the open
GTM Events
Configured per campaign
GA4 Conversions
Mapped to pipeline
Source Attribution
Campaign → CRM
Reporting Views
Built in Power BI
Google AdsGA4GTMMS Power BI

5

Systems in production

Breakdowns above

79

Workflow executions logged

n8n, July 2026

37/37

Tests passing

Tender engine v1

14

Production stages tracked

Vehicle tracker

GTM Systems Lab

Production patterns, rebuilt in the open.

Each of these systems already runs in production — their full breakdowns are above. The lab versions are sanitized rebuilds I'm publishing so the code itself can be read. "In progress" means the public version isn't ready yet, not that the pattern is unproven.

Proven in production
Public rebuild in progress

Enrichment Waterfall

Fills in missing contact data by trying one provider, then falling back to the next — so incomplete records get completed and you only pay for lookups that work.

Runs in production as the enrichment stage of the outbound pipeline.

enrichment_waterfall.py

> reading raw_contacts.csv...

Python / REST APIs / CSV + JSONProduction version
Public rebuild in progress

Procurement Signal Harvester

Watches public procurement and tender sources, and turns announcements into structured, CRM-ready records — instead of someone finding them by accident.

Runs in production as automated tender discovery inside the CRM.

Public signal monitor
source_urlqueued
rfp_keywordqueued
company_domainqueued
Python / Apify / n8nProduction version
Public rebuild queued

Inbound Signal Router

Takes an incoming lead, applies routing rules to decide who owns it, updates the CRM and alerts the team — in seconds, not next-morning.

The same event-driven pattern powers the production approval-to-send flow.

WEBHOOK
Slack Alert
Lead parsedroute: gcc
Webhooks / n8n / Slack APIProduction version
Public rebuild queued

LLM Account Qualification

Scores a company against a written ideal-customer profile and returns structured JSON with its reasoning. A human still makes the final call — by design.

Runs in production as the AI qualification stage of the lead pipeline.

{ "fit_score": 78,
"reason": "fleet and procurement signal present" }
LLM APIs / JSON / ICP rulesProduction version
Interface Layer // Conversion Systems

Visual trust,
engineered for action.

The interface is part of the GTM system. I use visual hierarchy, landing page structure, proof placement and production detail to make complex B2B offers easier to understand, trust and act on.

Asset Workflow

Visual Asset Systems.

Controlled visual workflows for turning technical products and industrial complexity into credible campaign assets, launch visuals and sales-supporting media.

STBY // RAW_LOG
TC: 00:14:52:18

CODEC

PRORES_422_HQ

COLOR_SPACE

S-LOG3_NATIVE

Toggle Visual System

Product & Detail Imagery.

Image direction focused on material clarity, product credibility and the small visual details that shape trust.

Detail_Audit_Active
Scan for Detail Integrity
UX / UI & CRO

Conversion
Interface.

Landing pages and campaign interfaces work best when message, hierarchy, proof and form logic are aligned. This layer connects design decisions with marketing operations and lead flow.

FigmaHTML/CSSForm LogicClarity ReviewAI Asset Direction
Base_Layout_v1
STATE:BASE
Background

A marketing path with a technical base.

My career has moved through campaign execution, websites, acquisition, CRM workflows, analytics, and data systems. The common thread is operational: making the visible parts of marketing work through cleaner systems underneath.

Root Foundation

B.Tech in Computer Science

Mar Athanasius College of Engineering

Systems LayerUAE (Global Markets)B2B / B2G Defense Solutions

2023 - PRESENT

Marketing & Digital Transformation

Mahindra Emirates Vehicle Armouring

Working across digital marketing, CRM workflows, data extraction, and global campaign operations for high-consideration markets.

B2G Lead Sourcing

Focus Area

CRM Workflow Support

Focus Area

Relevant Work:

Worked with custom CRM workflows and pipeline visibility requirements.

Used Python and extraction workflows to support targeted lead sourcing.

Supported digital campaigns and assets for Middle East, Africa and global market activity.

PythonApifyCRMPower BI
Contact

Let’s map it.

Connect