GTM Engineer in Building

Markets are
systems.
I instrument
them.

Building GTM infrastructure for the AI era — activation funnels, PLG signals, and growth loops that compound. The gap between a good product and revenue is always a systems problem.

gtm_lab — experiment_runner

/ thought process

The signal beneath the noise

I read military history to understand systems under pressure. Rommel in the desert. Sherman's march. What strikes me isn't the violence — it's the information architecture. The side that moves signal fastest wins. Not the side with more resources.

I came up through marketing at a Europe-based remote startup and a year on the ground at Vedanta BALCO — one of India's largest industrial operations. Two very different environments, one consistent lesson: the gap between signal and action is where value compounds or dies.

The AI era changed what GTM engineering means. Distribution is a technical problem. Activation is a measurement problem. Virality is a systems problem. I build at this intersection — for Seed-to-Series B SaaS teams that need GTM to scale without burning headcount.

war history
Systems under pressure reveal design flaws. GTM is a campaign — won in the instrumentation layer before the first touchpoint.
stoicism
Stay calibrated when data contradicts the hypothesis. The experiment doesn't lie. Your model might. Update the model.
absurdism
A product failing to find its market is not bad luck. It's a signal that the instrumentation layer is missing. That's fixable.
product thinking
Every GTM motion is a product. It has users, flows, drop-off points, a north star metric. Build it like one.

/ active experiments

Things I've shipped

PLG Analysis live
PLG Scanner

Paste any SaaS URL. Get back a structured GTM breakdown — motion classification (PLG / Hybrid / Sales-Led), aha moment hypothesis, activation sequence, growth loop identification, and the biggest friction point. Validated on Notion, Linear, and 20+ products. Experiment #1 running: curiosity gap above the email gate.

Next.js Cheerio Claude API PostHog Supabase Vercel
plg-scanner.prateekkatare.com ↗
Dev Tools live
Koven

Builders ship real things. Then send a GitHub link to a hiring manager. Koven fixes that gap. Paste your GitHub URL, X handle, and product link — it reads your commit history, build-in-public posts, and product metadata, then generates a shareable case study page in under 5 minutes. Not a template. Your actual story.

Next.js Claude API Supabase Vercel
trykoven.com ↗

/ gtm engineering stack v1

How I build

build
Next.js
Python
Cursor + Claude Code
data & experiments
Supabase
PostHog
Experiments table
intelligence
Claude API
Cheerio (v1)
Apify (v2 — planned)
deploy
Vercel
distribution
X (primary)
Shareable slug URLs
PostHog funnels
methodology
Hypothesis → Baseline
Build → Instrument
Measure → Iterate

/ field notes

Where I've operated

Jun 2025 — Aug 2025
Marketing Manager
Exeltive · Remote (Europe-based)

Operated remotely for a Europe-based team. Built the muscle for distribution-first thinking — running GTM from first principles without a full stack or a large budget. The constraint was the curriculum.

Aug 2025 — Aug 2026
Assistant Manager
Vedanta BALCO · Chhattisgarh, India · Onsite

A year on the ground at one of India's largest aluminum operations. Learned how systems actually function at scale — under pressure, with real consequences. The opposite of a startup. Which is exactly why it mattered.


/ contact

Let's build something that compounds.

Building in public. Looking for GTM Engineering, Growth Engineering, or RevOps roles at Seed–Series B SaaS. Global, remote-first.