How Clay built a $5 billion company with go-to-market engineers

Executive overview

Most B2B sales teams separate data work from customer work. Clay collapsed that divide by creating the go-to-market engineer — a role that builds automated systems to find, qualify, and reach customers, then deploys those same people directly to enterprise accounts.

Clay runs two GTM engineering teams: one internal team that generates and qualifies pipeline, and one forward-deployed team that sells by building live workflows for prospects. The loop feeds itself.

The core insight: when the people selling your product have the same skills as the people buying it, the sales motion becomes a product demo.

What a go-to-market engineer actually does

• Pulls and structures messy prospect data from across the internet
• Tracks buying signals (e.g. website visits, product usage) to score intent
• Builds automated systems for outreach, follow-up, and CRM enrichment
• Creates proof-of-concept workflows tailored to each prospect's data stack
• Replaces manual list-building and sequencing with repeatable, automated pipelines

How Clay grew from zero to $100M

• Spent five years with near-zero revenue before finding product-market fit in early 2022
• Early breakout users were technical operators using Clay to build outbound systems
• AI integration in late 2022 enabled personalised outreach generation inside the tool
• First major enterprise customer (Rippling) pushed Clay past $1M ARR in March 2023
• Struggled to land large companies — enterprise buyers wanted proof, not pitches
• Shifted from traditional sales to GTM engineers who build live demos for each prospect
• Closed Figma and OpenAI by end of 2023; crossed $100M ARR by 2025

The two-team GTM engineering structure

• Internal GTM engineers build pipeline infrastructure: automated lead generation, scoring, and enrichment
• Forward-deployed GTM engineers take qualified enterprise leads and build custom Clay workflows pre-sale
• Both teams share the same core skill set; personality determines which track fits
• Internal team feeds the deployed team; deployed team's learnings feed back into internal systems
• The flywheel: help customers with Clay → learn how they use it → improve Clay's own GTM

What makes the forward-deployed model work

• GTM engineers understand the customer's pain points because they have the same job
• They enter each deal as consultants, diagnosing the root cause of a prospect's go-to-market problems
• Builds are completely custom — small-scale proofs using the prospect's actual data
• Common entry point: replace a fragmented, expensive data vendor stack with a single Clay workflow
• Once a use case lands, expand to outbound, inbound, CRM enrichment, and event targeting