
Three minutes. That's the delay we put between asking ZoomInfo to enrich a new contact and letting HubSpot decide who owns it.
It looks wrong on the workflow canvas. Everyone has read the speed-to-lead advice, and here we are adding wait steps on purpose. I'd still build it this way every time. A second project in the same week ran into the same rule from the other direction.
Routing reads fields that aren't there yet
A software client came back from an event with a list of 50 attendees. The follow-up workflow we built does five things. It excludes customers, anyone with an open deal or lead, and anyone already in another sequence. It triggers ZoomInfo enrichment on the contact and the company. It routes the contact to an owner, creates a lead, and enrolls that lead in a follow-up sequence.
The assignment rules run on values like company size and location. Those values come from the enrichment. With no pause, assignment runs the moment the contact enters the workflow, the fields are still empty, and the contact lands with whoever catches the blanks.
So the order is: enrich, wait three minutes, run the assignment workflow, wait two minutes so the owner is set, create the lead, wait one more minute, enroll in the sequence. Contacts that already have an owner skip the routing and go to that owner.
That's six minutes of waiting in total. For event follow-up going out the next morning, nobody notices.
The speed-to-lead advice is right about demo requests
For someone who just asked for a demo, six minutes matters, and I won't pretend it doesn't. If that's your process, shorten the waits and test them.
I'd still keep one. A fast reply from the wrong rep, followed by a handover, is slower for the buyer than a reply a few minutes later from the right one. That's my opinion, and I hold it firmly.
The fair criticism is that a fixed delay is a guess. Three minutes is the number we chose. Nothing in the workflow confirms the enrichment finished. So check your own portal: pull the leads assigned in the last month and count how many still have an empty company size. If the count is high, your routing has been running on blanks.
During a migration, turn instant enrichment off
The other project is a company moving from Salesforce to HubSpot. We connected ZoomInfo, set the field mappings for contacts and companies, and switched Instant Enrich off before the data load.
With it on, every imported record is a new record to enrich, and a large migration can use up the credit balance on records nobody has reviewed yet. Scheduled Enrich stays on, so the team can enrich the segments they choose once the data is in.
One more setting from that build. We created a separate ZoomInfo Technologies field for tech-stack data, so enrichment adds to the record without overwriting fields the team already maintains.
Decide when enrichment runs, process by process
Both builds answer the same two questions: when does enrichment fire, and what reads its output? For new inbound records, enrich first, wait, then route. For a bulk load, keep automatic enrichment off and enrich by segment afterwards.
What delay do you use before routing, and how did you pick it? I'd like to compare numbers.
This came out of a client project. The story behind it, and what to check in your own portal, goes to subscribers on Thursdays. Get Thursday's note.
by Perry Nalevka on November 18, 2026
CEO of Penguin Strategies



