Automating Lead Routing in HubSpot for a 14-Person SaaS: 9 Zaps, One Workato Recipe, One Painful Slack Notification

The Client and the Setup

A 14-person B2B SaaS selling a developer-focused observability product, with three account executives, two SDRs, a marketing lead, and the rest in engineering. HubSpot Starter CRM, HubSpot Marketing Hub Professional, and a single Workato seat used for one Salesforce-to-NetSuite handoff that we left alone.

Inbound lead volume: ~110 leads/week, mostly from product-led trials, gated content, and demo requests. The existing routing was three Zaps written 18 months earlier, and the team complained that "good leads disappear" — meaning the SDRs were not picking them up fast enough, and AEs were getting late hand-offs.

We had three weeks of automation work and two weeks of measurement window before the next monthly QBR.

What We Built

The final stack was nine Zaps in Zapier Professional, a single Workato recipe, three HubSpot workflows, and one Slack notification. The split mattered: Zaps for cross-system glue, HubSpot workflows for in-CRM lead-stage logic, Workato for the audited handoff to billing once a deal closes.

The nine Zaps:

1. Demo-request form → enrich via Clearbit (kept their existing seat) → create or update HubSpot contact.
2. Pricing-page exit-intent form → HubSpot lead with mql_source = pricing_page.
3. Inbound trial signup → match to existing contact or create → assign to SDR via round-robin.
4. Round-robin engine → maintains a small Airtable table of SDR availability and current load.
5. SLA timer → if SDR has not actioned the lead in 30 minutes, escalate to a backup.
6. New MQL → Slack notification to #pipeline-inbound (the painful one — see below).
7. SQL handoff → SDR-to-AE assignment with HubSpot owner change.
8. Lost-lead retargeting → if disqualified, push to Customer.io for nurture.
9. Closed-won → trigger the Workato recipe for billing handoff.

The MQL-to-SQL Number

Pre-rebuild, MQL-to-SQL conversion measured over the prior 90 days was 14%. Eight weeks after the rebuild, the same measurement was 22%. The biggest contributor was Zap #5, the SLA timer. Before the rebuild, leads regularly sat for hours; after, the median time-to-first-touch was under 18 minutes during business hours. Faster touch correlated with higher conversion in the pre-data, and the post-data confirmed it.

Editor's Note: We rebuilt inbound lead routing for a 14-person B2B SaaS using HubSpot, Zapier Professional, one Workato recipe, and one Slack notification. MQL-to-SQL went from 14% to 22% over eight weeks (110 leads/week, ~$2,300 ACV). The honest caveat: this is correlation; the SDRs were also retrained mid-project and the marketing lead changed the demo-request form copy. We can't cleanly isolate the automation's contribution from those changes.

The Slack Notification That Took Three Days

Zap #6 is one Slack message: "New MQL: , , , , HubSpot>." It was the single hardest piece of the project.

The problem was deduplication. The trigger fired on HubSpot lifecycle stage change to MQL. Some leads bounced between MQL and SQL within minutes (a known HubSpot quirk when multiple workflows touch the same record). Each bounce produced a Slack notification. The pipeline channel got 30+ duplicate messages on a Monday morning, the SDRs muted the channel, and good leads went unnoticed for the rest of the day. The whole point of the rebuild was lost on day three.

The fix was three layers:

1. Add a 5-minute debounce in Zapier (a Schedule + Storage Zap pattern: write to Zapier Storage with the contact id and timestamp, suppress sends within the window).
2. Add a HubSpot workflow filter that only fires the cross-Zap webhook if the contact has been an MQL for at least 60 seconds.
3. Add a last_notified_at property on the contact to belt-and-suspenders the deduplication.

Three days. For one Slack message. We have shipped five identical lead-routing rebuilds since this one and the deduplication is still the most underestimated part of every project.

Editor's Note: We have built lead-routing automations like this for at least eight different B2B SaaS clients (4-30 person teams) since 2024. The Slack-notification-debounce problem has hit all eight, every single time. It is the most reliably underestimated part of inbound automation. If you remember nothing else from this case study, debounce your notifications.

What We Would Do Differently

• Build the round-robin in HubSpot, not Airtable + Zapier. HubSpot rolled out improved meeting-link round-robin in 2025 that is now sufficient for teams under ~30 reps. We could have removed two Zaps.
• Add a lead-routing audit dashboard from day one. We added it in week 6. It should have been week 1.
• Pre-write the Slack notification debounce. Saved templates would have cut the three days to half a day.

Caveats

• The 14% to 22% number is sensitive to ACV and segment. The same automations would not move the number for a $50/month self-service product.
• HubSpot's native lead-rotation features have improved enough that very small teams may not need a Zapier round-robin engine at all.
• The Workato recipe stayed because the audit trail mattered for the close-to-billing handoff. For teams without that audit constraint, a single Zap would do the same job at a fraction of the cost.