Your Inbound Leads Die in the Gap Between Systems

You don’t have a “lead gen” problem. You have a lead-routing fog machine that turns high-intent inbound into a Slack argument, a stale spreadsheet, and a missed window where the buyer was actually ready to talk. It’s not marketing. It’s operations.

This playbook builds a working intake-to-first-touch system that forces clarity: where leads come from, how they get scored, who owns the next action, and what context follows them. No heroics. Just plumbing.

Tools (and why they belong together)
Webflow: the capture point you control, with forms that don’t depend on a plugin circus.
n8n: the orchestration layer that can branch, retry, and log without turning into a Zapier bill.
HubSpot CRM: the system of record for pipeline ownership, SLA, and follow-up accountability.
Perplexity: the research engine that enriches a company fast enough to matter, before the first reply.

Workflow Analysis: the actual system
1) Webflow form submits. n8n receives a webhook event immediately, not “every 15 minutes.”
Fast is a feature.

2) n8n normalizes fields, dedupes by email/domain, and checks HubSpot for existing contacts/companies.
Duplicates aren’t noise; they’re signals you keep ignoring.

3) n8n calls Perplexity with the domain and a tight prompt: what they do, ICP fit cues, recent funding/news, and likely team size. It returns a short enrichment payload.
No 30-minute tab binge.

4) n8n writes the contact/company to HubSpot, sets lifecycle stage, assigns owner based on territory/segment, and creates a task with a hard SLA (e.g., 15 minutes) plus the Perplexity brief in the notes.
Context travels with the work.

5) If the SLA misses, n8n escalates: reassign, notify, and tag the record with “breached” for weekly ops review.
You can’t fix what you won’t measure.

Outcome: faster first-touch, fewer routing debates, and a pipeline that behaves like a system instead of a dare.

Tuesday, 9:07 a.m. The SDR manager is already in Slack triage. Someone pasted a screenshot of a form submission. Again. “Who owns fintech in the UK?” “Is this enterprise or mid-market?” Meanwhile the buyer is on your pricing page refreshing like they’re waiting for the site to blink.

At 9:09 a.m., a Webflow form comes in: name, work email, company domain, “Need SOC2 by end of quarter.” n8n catches the webhook instantly. No polling delay. It normalizes “Acme Inc.” to “Acme” and strips free-email edge cases. Then it hits HubSpot: contact exists from a webinar six months ago, marked as “Unqualified.” That’s not a dead lead. That’s context.

Here’s where it got messy the first time. Someone set dedupe rules on email only. The same person filled the form with a different alias, and now you had two contacts, two companies, two owners. Double tasks. SDRs arguing which record is real. Fix was boring: dedupe by domain plus a fuzzy company name match, and if conflict, attach as an additional email property instead of creating a new record.

At 9:10 a.m., n8n calls Perplexity with the domain. It returns: B2B payments platform, 220 employees, SOC2 mention in a job post, recently raised a Series B, likely buying committee includes security and compliance. The brief gets written into the HubSpot task notes. Not a novel. A weapon.

At 9:11 a.m., owner assignment fires. Territory rules. Segment rules. Round-robin only if no match. Task created with a 15-minute SLA. Slack DM to the owner with the task link and the Perplexity bullets.

At 9:28 a.m., nobody touched it. Calendar got in the way. The SLA timer trips. n8n tags the record “breached,” reassigns to the backup SDR, and pings the manager. Awkward. Necessary.

Does this feel strict? Sure. But what’s the alternative. Hope and vibes and a spreadsheet nobody trusts?

Here’s the part most teams skip: making this survivable inside an actual company with actual politics. The workflow is easy. The behavior change isn’t.

If we tried to drop this into a org tomorrow, the first failure wouldn’t be n8n or HubSpot. It’d be ownership. Sales ops thinks they own routing. RevOps thinks they own automation. SDR leadership thinks they own speed-to-lead. Marketing thinks they own the form. Security thinks Perplexity is “sending data to an LLM.” Everyone is right, which is why nothing ships.

So implement it like a product rollout, not a “quick automation.” Start with one path: one Webflow form, one segment, one region. Pick the lane with the highest intent and lowest stakeholder count (usually demo requests for a single geo). Define the SLA as a contract with teeth: what counts as first touch, what pauses the clock (meeting booked vs. email sent), and what happens on breach. If you can’t write that in five lines, you don’t have an SLA; you have a wish.

Next, treat dedupe and enrichment as governed data, not magic. Create a short “data constitution”: which properties are authoritative, what gets overwritten, how aliases are stored, and what happens when company domain is blank or weird. Then add observability from day one: a simple log table (even in HubSpot custom objects or a lightweight DB) with event ID, timestamps, assigned owner, SLA status, and error messages. When something breaks, you want an audit trail, not a ghost story.

The Perplexity piece is where legal and security will push back. Fine. You can still get 80% of the value by only sending the domain and asking for public signals. Or swap it for a vetted enrichment provider until procurement calms down.

And don’t underestimate the Slack DM. It’s not a notification; it’s enforcement. Put the task link, the brief, and the SLA clock in the same place. If reps have to hunt, you’ll be back to screenshots by next Tuesday.