The situation
A six-person B2B SaaS reseller based in Newcastle was generating around 80 web form leads a month from its website and paid channels. Those leads landed in a spreadsheet that the sales administrator reviewed twice a week. On a good week, a rep received their assignment within a day or two of the lead submitting. On a bad week, a lead that came in on a Thursday might not reach a rep until the following Tuesday.
The three-day average lead-to-rep handoff was compressing an already tight sales window. The data the business had on its own conversion rates showed that leads contacted within an hour converted at roughly three times the rate of leads contacted after 24 hours. The delay was not a deliberate choice; it was just how the process worked when a human had to sit in the middle of it.
The flow we built
Every web form submission now fires a Zap immediately. The lead's email domain is sent to Apollo for enrichment: company name, size, industry, technology stack, and estimated revenue come back within a few seconds. A scoring function in Zapier's built-in code step assigns an ICP fit score based on the enriched data against the firm's ideal customer profile criteria.
Leads scoring above 70 points are assigned to a senior account executive via round-robin within that pool; leads below that threshold go to the SDR pool on the same rotation. HubSpot creates the deal and assigns the owner automatically. The assigned rep receives a Slack alert in their personal channel with the enriched lead profile, the ICP score, and a pre-written first-reply template they can edit and send directly from the message.
The platforms
Zapier connects the web form, Apollo, HubSpot, and Slack. Apollo provides the enrichment data. HubSpot manages deals, owners, and the CRM record. All platforms were already in use; the automation connected them in a sequence that previously required manual steps. The setup runs on a Bot Care Professional tier, with monitoring on the Apollo API quota and the HubSpot connection, both of which have historically caused silent failures when unmonitored.
The results
Average lead-to-rep handoff dropped from three days to under 60 seconds. Reply rate within the first hour of a lead submitting roughly tripled compared with the previous batch-assignment process. The sales administrator's twice-weekly spreadsheet review was retired within the first week.
The enrichment step delivered a secondary benefit that was not part of the original brief. Because reps now receive an enriched profile at assignment, they arrive at the first call with context about the prospect's company, stack, and likely pain points. Average first-call duration dropped as reps spent less time gathering basic information that Apollo had already provided.
What this could look like for your sales team
If leads sit in a queue for hours or days before a rep knows they exist, the revenue impact of that delay is almost certainly measurable. A lead routing pipeline like this can typically be built in a week and pays for itself in the first month. We build these with Zapier, Make.com, or n8n depending on your existing stack and volume.