Cut Demo Forms to Email Only and Fill the Rest with Clay

1. 1

   Cut the form to work email only, or work email plus one question enrichment cannot answer (for example "What do you want to solve?"), keep the hidden UTM and page URL fields, and record the current completion rate and field fill rates first so you can compare after launch

2. 2

   Send every submission to a Clay webhook table as it happens: a HubSpot workflow webhook action, a Salesforce flow, or a Zapier or Make step on your form tool that posts email, the question answer, UTMs, page URL, and submitted_at

3. 3

   Screen before spending credits: flag free email domains (gmail.com, outlook.com, yahoo.com) and junk entries, then look up the email and domain in the CRM so existing customers and open deals go straight to their owner without new enrichment

4. 4

   Run the enrichment waterfall on the email domain: company enrichment for employee count, industry, and HQ country; person enrichment for job title and seniority; a technographics source for the tools that matter to your routing; each provider runs only if the one before it returned nothing

5. 5

   Handle misses: if company size or role is still empty, either use the answer to one optional question on the thank-you page (company size) or put the lead in a manual review queue (a Clay view plus a Slack post to #inbound-review) with a time limit shorter than your routing SLA, so no lead waits on enrichment

6. 6

   Route on the filled fields with rules you can read: named accounts to the account owner, then employee count and industry bands to the right round robin (for example 200+ in target industries to enterprise, 20 to 199 to mid-market, under 20 to nurture), and post each routed lead to the owner in Slack with the fields that decided it

7. 7

   Write the fields back to the CRM with their source: company size, industry, HQ country, job title, seniority, detected tech, enrichment_source, enrichment_status (enriched, partial, missed), and routing_reason; only fill CRM values that are empty so rep edits are never overwritten

Clay credits are the main tool cost, and they depend on your providers and plan, so every number below is an assumption. Replace each one with your own figure; the formulas show how the result is built.

Inputs (all assumptions)

Replace each value with your own figure.

• FForm fills per week100AssumptionCount last month's submissions and divide by 4.33.
• HShare of fills where enrichment fills company size, industry, and role75%AssumptionMeasure it on your first 100 fills.
• MMinutes of manual research saved per enriched fill4AssumptionTime how long a rep or ops person spends looking up a lead today.
• CClay credits per fill across the waterfall steps that run8AssumptionRead the credit estimate on a 10-row test in Clay; waterfalls stop at the first result, so this varies by row.
• PDollar cost per Clay credit$0.05AssumptionYour Clay plan price divided by its monthly credits.
• RLoaded hourly cost of the person doing manual research$50AssumptionSalary plus benefits, divided by working hours.

Formulas

Time saved per weekF x H x M / 60

100 x 0.75 x 4 / 60 = 5 hours, the time-saved estimate on this page

Clay cost per weekF x C x P

100 x 8 x $0.05 = $40.00

Value of time saved per weekF x H x M / 60 x R

5 x $50 = $250.00

Break-even minutes saved per enriched fillC x P x 60 / (H x R)

8 x $0.05 x 60 / (0.75 x $50) = 0.64 minutes; enrichment covers its credit cost when each enriched fill saves more manual time than this

• The math counts research time only. A shorter form may change how many people complete it; measure completion before and after instead of assuming a change.
• Leads in the manual queue still cost reviewer time: add F x (1 - H) x your review minutes to compare.
• Screening free email domains and CRM matches first keeps C down, because those rows never reach the waterfall.

Template outline

The structure to recreate in your own workspace. Field names and thresholds are starting points.

Form (before > after):
- Before: name, email, company, company size, industry, role, phone, message
- After: work email (required), "What do you want to solve?" (optional)
- Hidden: utm_source, utm_medium, utm_campaign, page_url
- Thank-you page (optional): "How many people work at your company?" (1-19, 20-199, 200+)
- Baseline to save: completion rate, % of fills with each field, median minutes to first touch

Clay webhook table: Short-form inbound
Inputs: email, question_answer, utm_source, utm_medium, utm_campaign, page_url, submitted_at

1. domain = text after "@" in email
2. is_free_email = domain in (gmail.com, outlook.com, hotmail.com, yahoo.com, icloud.com)
   - true: no enrichment; enrichment_status = "missed", go to manual queue
3. CRM lookup (HubSpot "Look up object" / Salesforce "Lookup record") on email, then domain
   - Customer or open deal: route to the owner, skip enrichment
4. Company waterfall (only if not free email and not in CRM):
   provider A > provider B > provider C, stop at first result
   -> employee_count, industry, hq_country
5. Person waterfall: provider A > provider B, stop at first result
   -> job_title, seniority
6. Technographics: one source -> detected_tech (only the tools you route on)
7. enrichment_status:
   - enriched: employee_count, industry, and job_title all filled
   - partial: some filled
   - missed: none filled
8. Fallback (status partial or missed):
   - Use thank-you page answer for company size if present
   - Else manual queue view + Slack #inbound-review:
     "Unenriched demo request: {{email}} | {{question_answer}} | {{page_url}}
      Missing: {{missing_fields}} | Route by: {{deadline_time}}"

Routing rules (first match wins):
1. Named account (CRM owner exists) -> account owner
2. employee_count >= 200 AND industry in target list -> enterprise round robin
3. employee_count 20-199 -> mid-market round robin
4. employee_count < 20 -> nurture sequence
5. No match after fallback -> owner picked in manual review

Slack to the owner:
"New demo request: {{job_title}} at {{company_name}} ({{employee_count}} employees, {{industry}}).
 Asked: {{question_answer}}. Routed: {{routing_reason}}. Uses: {{detected_tech}}."

CRM fields written (only when the CRM value is empty):
- Company: employee_count, industry, hq_country, detected_tech
- Contact: job_title, seniority, enrichment_source, enrichment_status, routing_reason
- Contact: lead_source_detail = "Short form"

Measure after 4 weeks against the baseline:
- Completion rate, enrichment_status mix, manual queue volume, minutes to first touch