Inbound enrichment playbook for SentinelOne, a concept by Mike Santos

What I saw on your site

As of October 22, 2026:

The main demo form (Marketo form 13216) has 10 required fields.
It doesn't ask for job title or current endpoint vendor. Title is only on the Sales contact form.
Company size comes from a self-reported dropdown with 5 bands, 0-49 up to 25K+.
The form name includes "TEST B", so an A/B test is already set up.

What I'd aim for is having that context on every lead before scoring and routing run.

I haven't used Clay hands-on. My background is 10 years in HubSpot and Marketo, 8 in Salesforce, and automation in Zapier and n8n. This is how I'd apply Clay's waterfall model to that stack.

1Enrich form fills before routing

A Marketo smart campaign sends each new form fill to a Clay table by webhook. Each column tries providers in order and stops at the first good answer. Results go back to Salesforce, so MQL_Priority_Level__c and routing work from a full record.

Marketo form fillDemo 13216, contact, or PathFactory gate 2692
Webhook to ClaySends email, company, and UTMs
Clay waterfallPerson, company, tech stack, account match. Provider A, then B, then C
Write backEnriched_* fields in Salesforce and Marketo, plus Enrichment_Status
Score and routeWaits for the status flag, with a timeout

Inbound · Demo requests Sample data Click a row to run it

	formEmail	formCompany	enrich: companyDomain	enrich: personTitle	formulaSeniority	enrich: companyEmployee count	enrich: companyIndustry	formula + enrichPublic sector	tech stackCurrent EDR vendor	lookupDemandbase account	waterfallProvider used	formulaFill status

Sample data. Companies, people, and emails are made up (.example domains). Provider A/B/C are placeholders. I'd set the real order by measured fill rate and cost per field.

Waterfall log

// Click a row to see each lookup.

Guardrails

Enriched values go to separate fields. What the buyer typed is never overwritten.
If enrichment runs past the timeout, scoring runs on form data and enrichment backfills later.
Skip contacts enriched recently. Run tech stack and people search only after a business-email check.
Check for a Demandbase account ID or existing Salesforce account before paying for firmographics.

Metrics, baseline first, then weekly

Metric	What it measures
Field fill rate	% of leads with each key field filled, by field and provider. Sample table: run rows to see
Routing accuracy	% of routed leads a reviewer agrees went to the right segment and owner (see section 3).
Time to first touch	Form submit to first rep or Piper touch. Median and 90th percentile, before and after.
Latency and cost	Enrichment time (p50/p95), timeout rate, and credits per enriched lead. Alert when they drift.

2Test a 3-field demo form

Run a variant with email, company, and interest against form 13216, and let enrichment fill in the rest. The existing A/B setup can handle the split. The variant has to win on SQLs, so extra junk fills won't help it.

Fields from the public form 13216, October 22, 2026

Current · 10 required fields plus consent

First name *

Last name *

Business email *

Company *

Employees *

Select▾

Phone *

Country *

Select▾

State *

If US/CA

Postal code *

Conditional

Interested in learning about *

Select▾

Consent / privacy

Request a demo

Test plan

Hypothesis: Fewer required fields raise demo-form conversion, and enrichment keeps routing quality where it is.
Split: 50/50 on the demo page in Marketo's A/B setup. Same traffic sources and thank-you step.
Primary metric: Form CVR × MQL→SQL rate, which is SQLs per 1,000 demo-page visitors.
Secondary: Meetings booked, time to first touch, fill rate on the backfilled fields.
Duration: Sample size set from the baseline before launch. No early stopping.

Guardrails

Phone: If sales needs it, make it optional or have Piper or the meeting step ask. Agree with sales before launch.
Consent: Same language in both versions. Without a country field, show consent to everyone or use geo-IP. Legal signs off.
Quality floor: Stop the test if the variant's SQL rate or sales acceptance drops below an agreed % of control.
Junk email: Check junk and personal-email share daily. reCAPTCHA stays on.
Low fill: A lead enrichment can't fill falls back to today's routing.

Judging the test Illustrative defaults

Put in your own numbers. This isn't a forecast. It shows how a variant can get more form fills and still produce fewer SQLs.

Current form CVR (%) Current MQL→SQL (%) Variant form CVR (%) Variant MQL→SQL (%)

SQLs per 1,000 visitors, current	12.0
SQLs per 1,000 visitors, variant	13.5
Change in SQLs	+12.7%

3Score and route on enriched data

Enriched fields feed the existing MQL_Priority_Level__c and routing rules. Each lead gets a segment, a competitive-displacement tag when the current vendor is known, a Slack alert to its owner, and context for Qualified Piper.

Pick a sample lead:

Segment	Rule	Goes to
Enterprise	2,500+ employees or a Demandbase target account	Named AE or enterprise BDR
Commercial	Under 2,500 employees, business domain	Commercial pod, round-robin
MSSP / Partner	MSP/MSSP industry, partner-form answers, or managed-services signals	Channel team
Public Sector	Gov, SLED, or edu domain, or public-sector flag	Public sector team

Slack alert to the owner Mock

Context sent to Piper Mock

Piper already chats and follows up. This gives its first message better facts. Customer-facing text stays within approved messaging.

Weekly review Sample data

Each week a reviewer checks about 50 routed leads (extra MSSP and Public Sector) for segment, owner, and displacement tag. That becomes the routing accuracy number and the test set for rule changes.

Lead	System	Reviewer	Match
Northwind Health	Enterprise, CrowdStrike	Enterprise, CrowdStrike	Yes
City of Maple Creek	Public Sector	Public Sector	Yes
Brightline Managed Svcs	MSSP / Partner	MSSP / Partner	Yes
Fernwood Logistics	Commercial	Commercial (vendor unknown)	Yes
Harbor & Pine Univ.	Commercial	Public Sector (state univ.)	No, rule gap

Each miss becomes a rule fix and a regression case. I'd re-run past samples before shipping the change.

Rollback

Switch: A Use_Enriched_Routing flag (Marketo token or custom setting). Turning it off sends every lead back to today's logic.
No restore: Enrichment only writes new fields, so rolling back means ignoring them.
Triggers: Routing accuracy below the agreed threshold, a spike in timeouts, or an owner-assignment error. Flip the flag and page the owner.
Logging: Each write records provider, timestamp, and previous value.
Staging: Shadow mode first (compute the segment, don't act on it), then one segment, then all.

30/60/90 plan

Days 1-30: baseline and shadow mode

Map current forms, scoring, and routing. Record baselines for fill rate, time to first touch, and routing accuracy.
Agree with Steven on providers and waterfall order. Test fill rate on a historical sample.
Build webhook → Clay → Salesforce in shadow mode: enrich and log, no routing changes.
Start the weekly review on today's routing to get an accuracy baseline.

Days 31-60: go live in stages

Turn on enriched routing for one segment, probably Public Sector or MSSP, where the form gives the least signal.
Add the displacement tag, Slack alerts, and Piper context.
Write the brief for the 3-field form test. Get sign-off from sales, legal, and web.
Document the build as a template other teams can copy.

Days 61-90: test and expand

Run the form test to the planned sample size, then judge it on SQLs per visitor.
If accuracy holds, expand to all segments and to contact and PathFactory forms.
Weekly dashboard for fill rate, accuracy, speed, and cost. Run at least one rollback drill.
Train marketing ops and demand gen to change the rules themselves.

Questions I'd want answered first

I built this from the public site only. These answers would change the design.

Does Demandbase already enrich form fills (form autofill or firmographic append)? Are other enrichment or intent tools still running?
How is MQL_Priority_Level__c set today, and where does routing live: Marketo, Salesforce assignment rules, or a routing tool?
Is Qualified Piper live on the demo flow? Who books the meeting after a form fill?
What did the current demo-form A/B test ("TEST B") compare, and what did you learn?
How are Public Sector and MSSP leads identified and routed today?
Is Clay phase 1 batch enrichment of Salesforce contacts and accounts, real-time inbound, or both? Does the Inbound team own the inbound tables?
What's the speed-to-lead baseline from form submit to first touch, by segment?