2026 SPEED TO LEAD REPORT

Speed to lead

The 2026 Speed to LeadBenchmark

6,346

Forms tested with agents

The first GTM Engineering Benchmark from Clay. We sent AI agents to test what happens after a buyer fills out a B2B form—and how every company stacks up.

Get the benchmark and compare your speed

Enter your company email to see how you compare to your peers.

How speed to lead is measured

Create custom research agents by describing your task, connecting tools, and deploying to any table.

1. Prospect

Request a demo
Form submitted

A prospect fills out the form

The submission timestamp starts the clock.

2. Company

The company replies by email

The first observed response stops the clock.

3. Measurement

00:37:00Time to first responseIllustrative example

The timer shows speed to lead

Every response can now be compared with the benchmark.

Benchmarks to improve your GTM systems

AI has changed what's possible in GTM. The introduction of AI SDRs, enrichment waterfalls, and autonomous research agents has moved the goalposts for everyone at the same time. We're all learning in real-time how to fold automation into the way we sell.

This raises a question: how do you know if you're actually good at it?

That's what our GTM Engineering Benchmark series is for. Each report picks one metric that matters, measures it across the real internet, and shows you how to benchmark your level of execution against the data—and then how to move the number. We'll explain what the metric is, why it matters, what the data shows, how to benchmark yourself, how to improve, and the exact build behind it.

We're starting with speed to lead: how fast you respond when a prospect fills out a form. Few metrics tie more directly to pipeline, but our results show most companies miss the mark.

  1. 1. What it is
  2. 2. Why it matters
  3. 3. What data shows
  4. 4. Benchmark yourself
  5. 5. How to improve
  6. 6. Exact build
Methodology

Clay orchestrated 4 agents to automate form fills

Filling out thousands of forms by hand would be time-consuming and expensive for a study. Instead, we built AI agents—orchestrated by Clay—to do the work.

Each agent went to a company's website, found the demo or contact form, and submitted it. When a company replied by email or called, the response was timestamped automatically. In total, the agents filled out 6,346 real demo and contact forms.

To do this, an agent needs the same primitives a human uses to interact with the world: a way to reason and navigate a form, an email address, and a phone number. We partnered with three startups that are providing those primitives today:

How Clay orchestrated the agent system to test response times

One Clay table orchestrated the entire run. The agents pulled their assignments from it, the inboxes and phone numbers reported back to it, and the analysis ran inside it. The same sequence repeated 6,346 times, and no one on our team touched a single form. Here's how:

1. Input

Target account list uploaded

The study starts with Clay's Tier 1 and Tier 2 accounts. Each row gives the agent a company and domain to investigate, while Clay keeps the full test set structured and auditable.

AccountDomain
NNorthstarnorth.co
MMeridianmeridian.io
AAtlas Labsatlas.ai
SSignalWorkssignal.co
2. Claygent research

Agent finds web form

Claygent visits each domain and locates the exact contact or demo-request URL. This avoids testing generic homepages and gives the browser agent a precise destination.

3. Browser execution

Subconscious Agent fills out the form autonomously

The browser-control agent submits one consistent synthetic identity. AgentMail and Saperly provide the monitored email address and phone number used to observe every response.

Request a demo

company.com/request-demo

Subconscious

Name

Jack O'Brien

Title

Founder & CEO

Company

Subconscious

Work email

AgentMail email address

Mobile

Saperly mobile number

Form submitted
4. Observation window

Wait for company to respond

The system pauses after submission. No follow-up is sent. The clock keeps running until an email or phone response arrives—or the observation window closes with no reply.

Observation windowClock running

00:37:00

Form submitted

00:00:00

First response

00:37:00

5. Response capture

Monitor both inbox and phone

AgentMail catches email replies with their timestamps. Saperly listens for calls to the submitted mobile number. Together they cover the two response channels in the benchmark.

Response monitorListening
AgentMailinbox
New reply

Re: Your demo request

Saperly phone line

Incoming call

Email reply captured+ 03:42:18
Inbound call captured+ 00:37:00
6. Webhooks

Return events to Clay

Each provider posts its response payload into a listening Clay table. Formula columns compare the original form-fill time with the observed response time to produce speed to lead.

Response eventClay destination
AgentMail email event+ 03:42:18
via MCP
Clay
Saperly phone event+ 00:37:00
via MCP
Clay
7. Analysis

Claygent classifies speed + personalization level

Claygent compares timestamps, identifies human versus automated senders, and scores the level of personalization. Those structured outputs become the benchmark distributions in this report.

Speed

3h 42m

Sender

Human

Personalization

Full

If you're building agents for GTM, the ceiling on what they can do is set by which primitives they can reach. Give an agent an inbox and a phone number, and it stops being a chatbot and starts being something that can act in the real-world. GTM agents will need these primitives as the future of GTM goes from agents to orchestrated agents to self-optimizing systems from learning loops.

Structured benchmark data, ready to analyze

How to read this benchmark (and where it has limits)

Like any study of this size, ours has limits. These are three worth knowing before we dive into the data:

  • A Non-response doesn't equate to ghosting. A share of the 68% who didn't reply may have disqualified our agent rather than dropped the ball. We can't see the difference from the outside. That said, disqualification isn't a reason to stay silent—more on that below.
  • Our "buyer" was an agent. The identity on each form was consistent but synthetic. If it read as off-ICP to a given company, that could suppress responses.
  • Agent email domains can get flagged. AgentMail addresses may trip spam or bot filters at some companies, which would understate true response rates.
  • Human vs. automated classification is itself AI-judged. Claygent classified replies, and a well-written automated email can pass for human (and vice versa). Some error rate is baked into the split.

Synthetic buyer identity

Same identity on every form

Name
Jack O'Brien
Title
Founder & CEO
Company
Subconscious
Work email
AgentMail email address
Mobile
Saperly mobile number
MetricResultMethodology
Form complexityNumber of fieldsClaygent analysis
ResponseYes or noWhether or not we received an email or call
Speed of email follow upTime in minutes, hours, or daysCompared the submission timestamp with when a follow-up email reached our AgentMail inbox
Speed of phone call follow upTime in minutes, hours, or daysCompared the submission timestamp with when our Saperly phone number was called
Personalization levelTemplate, light, or fullClaygent categorization
Who sent itHuman vs. automationClaygent AI estimate based on timing and personalization
Correct qualificationYes, no, or unsureClaygent analysis of the website ICP compared with the identity we submitted

What we couldn’t determine

  • The company’s qualification definition
  • Whether the company has automated qualification
  • How strong its enrichment is and whether it can power qualification
  • How long the qualification process takes
  • Whether companies that did not respond had correctly qualified us out, which would be a positive outcome

The data set

The benchmark spans 6,346 companies across 100 countries and 255 industries

Industries

6,346 companies
Software & IT
1,62726%
Professional Services
1,08417%
Other
75312%
Manufacturing & Industrial
63910%
Financial Services
63410%
Retail & Consumer
4768%
Healthcare
4257%
Media & Marketing
2814%
Real Estate & Construction
2264%
Education & Government
1693%
Transportation & Logistics
321%

Firmographics

100 countries6,346 companies
Company size
1–5048
51–2001,319
201–5001,711
501–1K1,177
1K–5K1,584
5K+504
Unknown3
Regional mix
  • NAMER45.4%
  • EMEA42.7%
  • APAC11.7%
  • Unknown0.2%
Ownership type
  • Privately held71.2%
  • Public company21.8%
  • Partnership2.5%
  • Nonprofit2.4%
  • Government agency1.2%
  • Self-owned0.9%
6,291 companies with ownership data

Get the benchmark and compare your speed

Open your personalized benchmark and see where your company stands.

Company email address

*

2026 Speed to Lead Benchmark — one metric that matters, measured across the real internet.

© 2026 Clay Labs, Inc.

Terms · Privacy · Security