Lead generation system
Sales Engine
One Notion page turns a city and a job title into 50 booked calls a month.
A Notion-native lead generation system. Apify and Google Maps and Apollo feed Clay for enrichment, n8n orchestrates, Lemlist and Smartlead and Expandi run the sequences, HubSpot and Notion share the CRM layer, Cal.com books the call. The dashboard is one Notion page your head of sales opens every Monday.
Totals across every stage of this system. Manual numbers reflect what a real team does by hand today. Automated numbers reflect the same work running through this Notion build.
Every stage opens its own tools and Notion artifact. Nothing is auto-expanded. Tap what you want to read.
Scrape the right rooms
Apify scrapers pull job titles, city, and industry. Google Maps scraper grabs local businesses. Apollo filters on funding and headcount. Everything writes to Notion Leads DB with the source stamped on the row.
Find the email, verify, score
Clay waterfalls emails through Apollo, Hunter, Dropcontact, and BetterContact until one verifies. Claude scores fit against ICP criteria. Rows that hit score 7 or higher get flagged ready-to-sequence.
The engine that moves data
n8n is the primary engine for the hot path because you control the tenant and the rate limits. Zapier and Make act as bridges to SaaS that n8n does not speak natively.
Send the sequence that books calls
Each enriched lead drops into the right sequencer by channel. Lemlist for email, Expandi for LinkedIn, Smartlead for cold email at scale. Copy gets personalized by Claude using the enrichment payload.
Lead handler + CRM handover
Replied leads route to the right AE in HubSpot. Slack DMs the AE with a 3-sentence context brief (source, pain signal, the reply). Notion mirrors the HubSpot deal so ops sees pipeline in one place.
What worked and why
Notion dashboard shows reply rate by source, cost per booked call by sequence, and ICP-fit vs close rate. Claude writes a Monday-morning digest in plain English and drops it in Slack.
lead-handler
Lead Handler
Routing rules, SLA timers, Slack digests, round-robin. The 10-minute gap between a reply and an AE response is where deals die. This sub-system closes it.
crm-handover
Internal Handovers + CRM
The Notion to HubSpot mirror. Every deal has an ops handover log, an activity timeline, and a 3-sentence context brief an AE can read in one breath.
pipeline-reporting
Pipeline Reporting
One Notion page with 5 charts. Claude writes a Monday-morning digest in plain English. Leadership stops asking "how is the pipeline".
Time saved
~44 hours/week of manual BDR work (scrape, enrich, sequence, handover, report) collapses to ~3.75 hours/week of review. For a 3-person BDR team at $75/hr blended cost, that is ~$12,000/month back.
ROI
Swaps a $12,000/mo BDR line for a ~$820/mo tooling stack plus a 0.5 FTE ops review loop. Payback typically lands inside month 1 on a single booked call from an outbound source that was not running before.
Who actually runs this
Industries where this automation earns its keep.
We build to industry, not to headcount. If your world looks like any of these, this one works as-is.
Want this wired up for your team?