What Clay got right about GTM Engineering

Clay did the industry a favor when it named the job.

In GTM Engineering: What It Is, How It Works, and How to Hire, Clay argues that most GTM teams are not under-staffed. They are under-engineered. The fix is not ten more reps. It is someone who builds automated revenue systems with AI, data enrichment, and workflow automation, then measures the work in meetings booked and hours saved.

That definition is right. It is also incomplete once the stack includes agents that keep working after the laptop closes.

Figtech is a fractional GTM Engineer practice aimed at Grok Bot for GTM. Clay is often the enrichment and orchestration layer in the same motion. This post is about how those pieces fit without pretending Clay and a bot roster are the same product.

What Clay got right

Clay’s framing is sharp in three places.

First, the unit of work is a system, not a ticket. A traditional ops hire researches one account. A GTM Engineer builds the workflow that researches every account in the slice, scores it, and hands a seller something they can trust.

Second, the work climbs three rungs: data foundation, data modeling, data activation. Skip the first rung and the fancy plays rot. Clay’s guide is explicit about that, and every messy CRM you have ever inherited agrees.

Third, GTM Engineering is commercial and technical at once. Hybrids win. People who ask whether the workflow closes a deal, not whether the spreadsheet is pretty.

Clay also showed what an internal function looks like when you treat it like product engineering. In How We Built Clay’s GTM Engineering Function, Everett Berry describes two-week sprints, version control on tables and workflows, release notes, and a team that sits close enough to leadership to make architectural calls. That is the opposite of an ops queue that never ships infrastructure.

If you are standing up GTM Engineering for the first time, read those two posts. They are the best public map of the discipline Clay coined in 2023.

Where the job continues after the table

Clay is infrastructure for sourcing, enrichment, scoring, and many of the plays that turn signals into outreach. That layer still needs an operator who owns the full motion around it.

A GTM Engineer in Figtech’s sense owns four things we keep repeating because they are the whole job:

1. Roster. Named seats with named outcomes. Prospecting that stops at a review list. Forecast notes in the format Monday’s call already uses.
2. Tooling. Sessions that persist. Instantly or Origami for sequences. CRM, mail, Slack, Gong. Clay for the enrichment and research spine when that is the right tool. The computer stays on.
3. Approval gates. Bots draft. People send. Enrolls and CRM writes sit behind a human.
4. Cadence. Nightly research. Morning reviews. A weekly pass that kills dead routines.

Clay’s blog is strongest on building and shipping the systems. The roster is how those systems land in a seller’s day without becoming another sidebar that answers “help with outbound.”

You can have a beautiful Clay table and still fail GTM Engineering if nothing owns the weekly loop, the gate, and the seat that wakes up with a short list.

A practical split

Here is a clean division that teams actually run.

Clay (and the data layer) owns coverage, waterfalls, ICP scores, signal columns, and the research that would have eaten Sunday. It is where GTM alpha starts: unique data and plays that are hard to copy with a generic sequence.

The outbound engine (Instantly, Origami, or your sequencer of choice) owns volume, deliverability, and the send path the seller already trusts.

The Grok Bot roster owns overnight jobs that are messy, multi-source, and approval-bound: account research packs, review lists, forecast notes, post-call drafts, SEO briefs. Named bots. Named stops.

The GTM Engineer designs the jobs across all three, wires them, and stays on the cadence. Fractional works when you need architecture and taste more than a full-time seat on day one.

Clay’s own internal story even nods at human-in-the-loop workflows and Slack as the day-to-day interface. The gate is not a Figtech invention. It is what keeps automation from becoming a customer-facing accident.

What “done” looks like with Clay in the stack

GTM Engineering with Clay is working when:

• The golden list (Clay’s phrase for the accounts you would be thrilled to meet tomorrow) is clean, reasoned, and not a CSV graveyard.
• Enrichment and scoring run without a hero in the spreadsheet.
• A prospecting seat returns a short, evidenced review list, not a thousand-row dump.
• Outreach drafts respect suppression, multi-channel sense, and a human send.
• RevOps still owns the system of record. GTM Engineering writes into it. You do not grow a second CRM in Slack.

If you only buy Clay and skip the engineer, you bought a powerful workbench. If you only stand bots and skip the data foundation Clay describes, you bought a chat window with confidence.

You need both the systems Clay named and the roster that runs them on a clock.

How Figtech uses that premise

Figtech does not replace Clay. We sit next to the stack you already bought.

Map the motion. Decide which jobs live in Clay tables and workflows, which live in the sequencer, and which belong on a Grok Bot desk with a hard stop. Rehearse one real workflow until a seller will put their name on it. Save the skill. Put it on a cadence. Keep the gate.

That is GTM Engineering in practice: Clay’s definition of building revenue systems, plus the seats and approvals that make those systems safe overnight.

If you want the role definition without the Clay angle, start with What is a GTM Engineer?. If you want the fractional seat, read What a fractional GTM Engineer actually owns. If you want the gate, read why approval gates are the product.

Start here

1. Read Clay’s GTM Engineering guide and how they built the function.
2. Write three jobs with outcomes, sources, format, and a hard stop.
3. Put enrichment and scoring where Clay is strongest.
4. Put overnight research and drafts on a roster that cannot send.
5. Stay on the weekly loop until the system gets sharper.

Clay named the discipline. A GTM Engineer makes it run.