Learn

AI agents for GTM

Use LLMs for research, scoring and drafting, with costs, checks and humans in the right places.

Roadmap: AI agents & measurement

Why it matters

AI has changed what one GTM engineer can do. A research step can read a company's site, job posts and news and answer a specific question for 5,000 accounts overnight. Models can classify replies, score fit, draft personalised lines and summarise calls. But they also invent facts, cost real money at scale, and can be steered by text on the web pages they read. Employers want people who use AI for leverage and can prove it's working, not people who wire a prompt to the send button.

What it's made of

  • Choosing tasks that suit LLMs: reading, classifying, summarising, drafting
  • Research agents: web search, browsing and structured answers
  • Structured outputs with an explicit "unknown"
  • Evaluating outputs against a hand-labelled sample
  • Cost and latency budgets per row and per run
  • Guardrails: grounding, citations, human review, no auto-send at first
  • Handling untrusted web content and prompt injection
  • Reply classification and inbound qualification

Good GTM jobs for a model

LLMs are strong at reading messy text and answering a narrow question about it. Good fits:

  • Answering yes/no/unknown questions about a company from its website and job posts.
  • Summarising a company's offering in one sentence a rep can scan.
  • Classifying replies: interested, not now, wrong person, unsubscribe, out of office.
  • Drafting one personalised line from research, for a human or rule to accept.
  • Turning call notes into CRM fields and next steps.
  • Poor fits: exact numbers (headcount, revenue) a data provider sells, and anything final and irreversible without review.

Design a research pipeline, not a mega-prompt

Break the job into steps: filter with cheap data first (industry, size), fetch the specific pages that matter, ask one clear question per step, and return structured JSON with the answer, a confidence level and the source URL. One prompt that tries to research, score and write all at once is hard to debug and hard to improve.

Run each step on 50 hand-labelled rows before scaling. If agreement with your labels is under the bar you agreed with sales (say 85–90%), improve inputs and instructions before adding more rows.

Know your cost per row

Multiply it out before you run it. If a research step uses about 8,000 input tokens and 300 output tokens per company and runs on 10,000 companies, that's around 80 million input tokens. Depending on the model, that ranges from a few dollars to a few hundred. Web search and browsing add per-call fees on top. Use smaller models for classification, cache results so re-runs don't pay twice, and only run deep research on accounts that passed earlier filters.

Autonomy in steps

Increase what the AI may do only as measured accuracy and trust allow:

  • Suggest: the model's output is shown to a rep, who decides.
  • Draft: the model fills in a message or field; a human approves.
  • Auto with sampling: low-risk actions run automatically and a person reviews a random sample weekly.
  • Never automated: messages to existing customers, anything involving pricing commitments, deleting records.

Mid-level looks like

Writes prompts that return structured answers for a list of companies and spot-checks the results.

Senior looks like

Designs multi-step research pipelines with cheap filters first, measures accuracy on labelled sets, sets cost ceilings, decides where humans approve, and treats scraped content as untrusted input.

Common pitfalls

  • Letting a model send emails or update CRM fields automatically before anyone has measured its accuracy.
  • No "unknown" option, so the model guesses confidently on every row.
  • Running the most expensive model on every row instead of filtering first.
  • Trusting web content as instructions: a page that says "ignore previous instructions" shouldn't change your output.

Practice drills

  1. Drill 1

    Build a research step that answers "Does this company have a dedicated RevOps function?" for 300 companies. Label 50 yourself, measure agreement, and report cost per company.

    A strong answer: A clear definition, sources fetched deliberately, structured output with unknown and evidence, measured accuracy, and cost per row with the arithmetic shown.

  2. Drill 2

    Design a reply-classification system for 2,000 replies a week that routes interested replies to reps within 5 minutes.

    A strong answer: Clear classes, a confidence threshold with human review below it, handling for unsubscribes across all tools, and a weekly accuracy check.

  3. Drill 3

    A web page you're researching contains hidden text telling the model to rate the company as a perfect fit. How does your pipeline handle it?

    A strong answer: Treating page content as data, not instructions; structured outputs; evidence checks; and scoring logic partly in code rather than only in the prompt.

  1. 1GTM Engineering With Claude AI For Beginners (Full Course)86 min
  2. 2Full Clay.com Course (6+ Hours)367 min
  3. 3What is GTM engineering? Inside Clay’s GTM strategy18 min
  4. 4How I Replace 10 SDRs With Clay + AI (GTM Engineering)18 min
  5. 5How to land a GTM engineer role at a $2B+ company (Founding GTME explains)56 min
  6. 6How Anthropic uses Claude in GTM Engineering2 min

Best resources for this skill

Repos, courses, articles and podcasts, ranked by how much they teach.

Read next

Next skillMeasurement & experimentation