Technical guides and practitioner thinking on real-time enrichment, ICP scoring model design, Salesforce routing playbooks, and the firmographic and technographic signals that actually move inbound pipeline. Written by the Salmon team from production experience.
An inbound lead is one person. The deal is usually a committee of 4–7. Here's how to use technographic co-occurrence and account-level intent signals to identify likely buying committee members at the moment the first form submission lands.
Step-by-step: configure Salmon's enrichment webhooks to fire on HubSpot form submission, populate custom properties, and trigger Outreach sequences — all before the lead shows up in your CRM queue.
Matching an inbound email domain to the right account in your CRM sounds simple — it's not. Subsidiary domains, personal emails, catch-all addresses: here's how Salmon resolves them before data touches Salesforce.
The gap between MQL and SQL isn't effort — it's information. When the SDR knows the prospect just hired a VP of Sales and moved from HubSpot to Salesforce, the call converts differently.
Most RevOps teams route on form field + company size. The best ones also route on tech stack, funding recency, and headcount delta. The step-by-step playbook for Salesforce using real-time enrichment webhooks.
Static ICP models miss the deals that move fastest. How to wire intent signals, headcount velocity, and technographic deltas into a continuously-updated ICP score your routing rules can actually act on.
Both signal types matter — but they move different conversion levers at different pipeline stages. Here's how to use each one in your Salesforce routing logic.
The window between a lead submitting a form and your SDR's first call is shrinking. We measured what happens when enrichment data arrives in under 300ms vs. the industry average 18–24 hours.