I connect websites, campaigns, CRM workflows, analytics, data extraction and AI-assisted operations into practical systems that make growth work easier to track and scale.
Data extraction
Python / Apify
Ops layer
CRM / Analytics
Current focus
GTM Engineering
The operating layer is how data is sourced, cleaned, scored, routed, tracked and reported across the systems where teams actually work.
Tools already used across marketing operations, CRM, analytics, campaign execution and asset workflows.
Tools and patterns being used in portfolio systems, demos and proof trails.
The broader tool landscape I design around, evaluate or build compatible workflows for.
The site still looks designed, but the substance is operational: data pipelines, workflow handoffs, CRM logic, tracking infrastructure and AI-assisted review loops.
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.
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.
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.
Structured CRM logic and dashboards for long-cycle global sales activity across B2B and B2G markets.
Proof to show
Sanitized CRM workflow map, lifecycle structure and pipeline reporting view.
Campaign tracking and reporting workflows connecting paid acquisition activity with performance visibility.
Proof to show
Blurred reporting dashboard, tracking structure, source mapping and campaign performance view.
My strongest lane is not making marketing louder. It is making the operating layer cleaner: source data, CRM logic, tracking, reporting views, API-ready handoffs and campaign operations.
See the lab layerEvery project is more than a card. Each lab system is mapped with the files, workflows, datasets, screenshots and demo proof needed to make the build traceable.
A Python-based workflow for testing fallback logic across multiple enrichment and verification sources.
Proof target
Fallback script, API handler, input schema, output parser and terminal run proof.
> reading raw_contacts.csv...
A lab version of the sourcing workflow, focused on public procurement and business signals.
Proof target
Source map, extraction log, CRM-ready schema, n8n workflow draft and sanitized output structure.
Webhook-based routing for form submissions, rule checks and instant team alerts.
Proof target
Webhook listener, routing rules, Slack payload, CRM update schema and speed-to-lead demo.
GPT-4o API workflow for evaluating company profiles against defined ICP criteria.
Proof target
Prompt spec, ICP rules, company inputs, JSON output and human review notes.
Shows how raw prospect records move through provider checks, fallback logic, verification steps and clean output generation.
Read raw contact CSV
Query Provider A
Check response quality
Route missing records to Provider B
Run verification step
Export enriched record with source tag
The card shows the idea. This panel shows what sits behind it: repo, workflow, backend logic, data, screenshots and demo proof.
Build Assets
The technical files, workflows and datasets that make the system real.
GitHub Repo
Clean README, setup steps, sample script and .env example.
Provider Fallback Script
Python routing logic for moving from one provider to the next.
REST API Response Handler
Normalizes provider responses and handles missing fields safely.
CSV Input Schema
Small anonymized dataset with name, company and domain fields.
JSON Output Parser
Structured output for enriched records and provider metadata.
Source Tagging Logic
Tags which provider returned the usable contact data.
Verification Step
ZeroBounce / MillionVerifier-style validation layer before export.
Rate Limit Notes
Basic safeguards for retries, delays and provider limits.
Waterfall Architecture Diagram
Visual map of provider fallback flow.
Proof Assets
The visible evidence that shows the workflow has been built, tested or planned honestly.
Terminal Run
Screen capture showing fallback routing and export.
Clean Output CSV
Enriched output with provider source tag and verification state.
Code Log
Short development notes and commits.
Demo Walkthrough
Short video showing input, run and output.
Publishing Rule
Available means it can be shown. Building means in progress. Planned means it is not claimed as completed.
A compact operating view for the work behind campaigns: routing, tracking, hygiene and reporting readiness.
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.
Controlled visual workflows for turning technical products and industrial complexity into credible campaign assets, launch visuals and sales-supporting media.
CODEC
PRORES_422_HQ
COLOR_SPACE
S-LOG3_NATIVE
Image direction focused on material clarity, product credibility and the small visual details that shape trust.
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.
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
2023 - PRESENT
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.
If your marketing stack depends on manual research, disconnected CRM data, unclear attribution or slow lead handling, I can help think through a cleaner system.
Start a Systems Conversation