Blueprints/Lead Enrichment, Scoring, Routing and Outreach
Make Scenario

Lead Enrichment, Scoring, Routing and Outreach

From form submission to first email in eight seconds

Most lead handling has the same gap: a form fires, a record lands in the CRM with an email address and not much else, and then it waits. This 15-module Make scenario closes that gap at submission time — enriching the contact, scoring their fit, routing to the right owner, and sending a personalised first email in roughly eight seconds.

15modules
8sper lead
MakeMakescenario
Download the scenario

Make scenario + readme. Free download.

What it does for you

Eight seconds per lead

From form submission to sent email while the lead is still on your site. No human steps in between.

Degrades, never drops

Both API calls have error handlers. Enrichment failures and generation errors produce fallbacks, not dropped leads.

Scoring you rewrite for your ICP

Five weighted criteria with letter grade thresholds. Change the keywords and weights without touching anything else in the scenario.

Provider-agnostic by design

Apollo is the default enrichment source. Swap recipes for Hunter, Clearbit, Pipedrive, Attio, Airtable, Instantly and Lemlist are documented in the readme.

How it works

Five stages. Runs in eight seconds.

01

Trigger and Normalise

A webhook receives the form payload from any tool that can POST. A second module cleans variable names and derives the company domain from the email address. Only the email field is required.

  • Works with Tally, Typeform, Webflow, Framer or any CRM workflow
  • Derives company domain from email when the form did not capture one
  • Every other field has a fallback — only email is required
02

Enrich

An HTTP call returns job title, seniority, company name, headcount, industry, country and LinkedIn URL. Results map into neutral variable names so everything downstream is provider-agnostic.

  • Apollo default, with Hunter and Clearbit documented as direct swaps
  • Neutral variable names mean switching provider rewrites one module, not six
  • Error handler resumes with empty data on rate limits or missing contacts
03

Score

Five weighted criteria produce a score out of 100 and a letter grade. Every threshold and keyword list is designed to be edited for your ICP.

  • Seniority 30pts, company size 25pts, industry 20pts, email type 15pts, intent 10pts
  • A: 70+, B: 45 to 69, C: 25 to 44, D: below 25
  • Scoring is split across two modules — Make cannot read variables a module set in itself
04

Route

A router splits three ways on grade. A and B leads get full processing. C leads go to the CRM as nurture. D leads are logged to a sheet and nothing else happens.

  • A and B: owner assigned, CRM record created, email generated and sent, Slack notification fired
  • C: written to CRM as nurture with no owner and no outreach
  • D: logged to Google Sheet — the feedback loop for tuning your scoring thresholds
05

Write and Send

An API call generates a first-touch email using enriched data, with a prompt that enforces brevity and bans cold email clichés. A plain fallback sends if generation fails.

  • Capped at 90 words, one clear question required at the end
  • A-grade leads get a call offer, B-grade get a lighter ask
  • Assigned owner is BCC’d on every send

Free download

Stop measuring lead response time in hours

Download the scenario, connect your four tools, and have it running before the end of the day. Nine placeholder values to replace, all documented module by module in the readme.

Download the scenario

Make scenario + readme. Free download.