What is GTM Engineering?

GTM engineering treats revenue as a software problem. I design and ship the systems that move pipeline — AI agents that do outbound research, programmatic SEO that scales past 10k pages, lifecycle email that triggers on intent, and the orchestration glue between them. It's RevOps with a build-vs-buy bias toward build.

Fenil Parekh GTM Engineer SF Bay Area

I ship the AI agents that run go-to-market.

I build the inbound, outbound, paid, and email systems that revenue teams run on. The agents that operate them ship as code — failure modes named, architecture in the open.

Browse the library

Subscribe to the newsletter

function validateGptOutput(res) {
  let parsed;
  try { parsed = JSON.parse(res); }
  catch { return { status: "REJECTED", route: "manual_review" }; }

  const skills = parsed.extracted_skills.split(",").map(s => s.trim());
  const generic = ["communication", "teamwork", "leadership"];
  const real = skills.filter(s => !generic.includes(s.toLowerCase()));

  if (real.length < 2)
    return { status: "LOW_SIGNAL", route: "archive" };

  return { status: "APPROVED", data: parsed, route: "smartlead_sequence" };
}

Where this runs

ATS-signal outbound · working prototype

read the case study · architecture, failure modes, the full code

What is a GTM Engineer?

A GTM engineer builds go-to-market with code instead of headcount — the outbound, inbound, paid, and email systems a revenue team runs on, plus the AI agents that operate them.

I build two kinds. Internal agents work pipeline alongside the team. Go-to-market agents run a channel on their own.

They break in completely different ways. Figuring out where each one breaks is most of the job.

Plugs into the systems your revenue team already runs

Outreach

screen recording · unedited

Watch it run

An agent working a live pipeline — not a slide about one.

A short, unedited screen recording of one of the builds in the library doing its job.

View all

The work

The actual builds — code, diagrams, and what broke. Made solo, in public.

Browse the library

Now

Reframing my case studies and writing the first blog post.

In progress Updated May 2026

Identity

GTM engineer, CS background, based in the Bay Area. I'd rather ship a working agent than write another playbook about one — so everything here is built in the open, including the parts that broke.

LinkedIn X GitHub

The flywheel

It's one system, not four channels.

Outbound, inbound, paid, and email get run as four separate jobs. They're really one system. Go-to-market agents run a channel directly; internal agents work beside the team — and what they do becomes the signal that aims the next move.

concept-first · real numbers in case studies