Enrich the submission with company size, industry, and role at the moment the form lands, so routing and personalization work on the enriched record rather than on what the prospect typed
The standard B2B form asks the prospect for first name, last name, work email, and company, on the reasonable principle that asking for less converts more. The team then needs company size, industry, and role to route and personalize the response, and the standard solution is a nightly enrichment batch that adds the fields the next morning. By morning the prospect has already received a generic welcome email, the lead has already been routed to the wrong segment, the sales workflow has already chosen a treatment, and the enriched data lands too late to inform any of them. The batch enrichment is correct and useless; the work has already happened against the unenriched record.
The real-time variant fires the enrichment at the moment the form lands, so the routing, the personalization, and the initial sales workflow all consume the enriched record from the first moment. The prospect's first touch reflects who they are rather than the minimal set of fields the form asked for. The recipe is medium-low readiness because the patterns are well-established (the vendor calls, the API integration) and the work is mostly engineering: the harder part is the fallback discipline for the share of submissions where the enrichment returns no match or low confidence, because routing that stalls on a missing field is worse than routing on partial data.
This recipe builds the enrichment as a real-time call at submission, with the fallback path that keeps the lead moving when the enrichment cannot reach it.
A form submission that arrives at the routing layer with firmographic enrichment already applied, with the coverage and the confidence to drive the downstream decisions the team makes within the first hour. The metric is enrichment coverage at submit: the percentage of form submissions arriving at the routing layer with company size, industry, and role populated above the confidence threshold, measured against the historical baseline where those fields were nightly. The value shows up in the routing accuracy (the lead reaches the right segment from the first touch), in the personalization quality (the welcome treatment reflects the prospect's segment), and in the sales workflow (the BDR sees the firmographic context immediately rather than the next day).
The second outcome is the provenance trail: each enriched field carries the source it came from and the confidence the vendor returned, so a routing decision made on enrichment data is traceable to the vendor and the confidence, and downstream consumers know whether to weight the enrichment heavily or to hedge.
A real-time enrichment service that fires the vendor call at form-submit, with the latency budget the routing can tolerate (usually under five hundred milliseconds for the routing to remain real-time). Composable stacks suit this because the form submission, the enrichment, and the routing all live in the activation layer with the warehouse as the persistence point. The capability that decides whether the recipe holds together is the latency-and-fallback discipline: a vendor that takes two seconds to respond cannot be the synchronous path, and the design needs the fallback (route on what is known now, enrich the record asynchronously, re-route if the enrichment changes the segment) for the latency-tail cases.
Compare the tools on Martech Stack Builder
Marketing ops owns the vendor choice, the routing rules that consume the enriched fields, and the SLA the enrichment has to meet for routing to be real-time. Data engineering owns the real-time enrichment call, the fallback path, the provenance recording, and the asynchronous enrichment for the tail of cases where real-time did not reach. Sales ops owns the downstream routing the enrichment feeds, including the qualification rules that say which segments get which treatment, because the recipe ships the enriched record into a routing system that is owned outside marketing. The recipe ships in weeks where a vendor relationship and a CRM integration already exist; longer where the vendor selection is open or where the CRM cannot consume the enriched fields without integration work. The slip is rarely the enrichment vendor; it is the downstream consumer expecting the fields to land in a specific shape and the integration that maps them.
Work in this order. Fire the enrichment, attach provenance, route on the enriched record, fall back deterministically.
Enrichment on event covers steps 1, 2 and 6, third-party data overlay with provenance tracking steps 4 and 5, and real-time decisioning with deterministic fallback steps 3, 7 and 8.
The first failure is the silent vendor latency. An enrichment that times out three percent of the time, with the timeout treated as a no-match, looks fine until the routing tail starts to compound and the leads in the bottom three percent are routed worse than the leads where the vendor failed loudly. A latency monitor on the enrichment call, surfaced as a metric, is what catches the silent degradation, and the fallback has to be the same whether the enrichment timed out or returned no match, because the routing's job is to keep the lead moving.
The second is the over-trust of vendor confidence. A high-confidence match from the vendor is still a third-party assertion about the prospect's company, and edge cases (acquired company, name collision, mislabelled industry) produce confidently wrong enrichment. The routing should treat high-confidence enrichment as actionable but recoverable: the welcome email and the initial routing run on the enrichment, and a check at the BDR's first conversation surfaces the wrongness if it is wrong, with a feedback loop that updates the record and the vendor's correction.
The third is the enrichment that lands but is not used. A team that fires the vendor call, records the result, and continues to route on the fields the prospect typed defeats the purpose of the real-time enrichment, and the cost of the vendor relationship is producing data the routing does not consume. The integration with the routing is the last mile, and a recipe that ships the enrichment without the routing change is the recipe that produces a dashboard improvement and no operational change.
The Workshop works out with your team which of these matter for your stack right now, and what to do first: a 90-minute session with the people who own the decision.
The vendor call at the submission, the latency budget that keeps the routing synchronous, the provenance trail that makes the data auditable, and the fallback that keeps the lead moving when the enrichment cannot reach: those are the decisions that turn nightly enrichment into routing the prospect's first touch reflects who they are.
Did this recipe match your situation?Anonymous response. Sign up to leave a longer note tied to your account.
Activate the target account list with one identity resolution and one exclusion list across paid display, paid social, direct mail, and BDR outreach, so the same account stops getting contradictory treatment
Aggregate the signals from every contact in the account into one account score, because the buying committee is buying together and scoring leads in isolation misses the picture that matters
Lower acquisition cost by feeding the bidding algorithms better conversions, deduplicated, consent-valid, and weighted by value, rather than just more of them