The form problem is old and unresolved. Ask for four fields and conversion holds, but you do not know enough to route or prioritise. Ask for nine and you know a great deal about the people who did not leave.
Every team lands somewhere unsatisfying in the middle, then adds a company-size dropdown that half the respondents guess at.
Ask for four fields and you learn nothing. Ask for nine and you learn about the people who stayed.
The email domain already contains most of the answers
A work email address carries a domain, and the domain identifies the company. From that, most of what those extra fields were asking for is retrievable without asking anyone: size, sector, location, technology in use, whether the company is already in your CRM, whether the account has an owner.
None of it needs to be a question on the form. It needs to happen between the form being submitted and the lead being handed to a person.
- Nine fields, and conversion drops
- Company size is a dropdown people guess at
- Job title is whatever they felt like typing
- Still nothing about their stack or their CRM history
- Four fields, and you still know the company
- Data comes from sources, not from self-reporting
- Runs before routing, so the score exists when it is needed
- Existing customers and open opportunities get caught
The order that matters
The distinction worth being precise about is not before or after submit, it is before or after routing.
Most stacks submit a form, write a record, assign it by rule, and then run enrichment on a schedule that catches up hours or days later. By the time the useful fields arrive, the lead is already in someone's queue and the decision has been made without them.
Putting enrichment and qualification between submission and assignment changes what the routing rule can see. The ICP score exists. The CRM has been checked. Ownership is known. The rule is choosing with the facts rather than ahead of them.
Two practical constraints. Personal email domains resolve to very little, so the fallback has to be graceful rather than an error, and for a consumer-heavy funnel, enrichment will not carry the qualification on its own. And the work has to run inside the workflow rather than as a nightly job, or you are back to routing blind.
What it lets the confirmation do
Once the qualification is finished before assignment, the next step can be specific rather than generic. A lead who obviously qualifies can be shown a calendar instead of being promised a reply. An account with an existing owner can be pointed at that person rather than a round-robin queue. A poor fit can be sent somewhere sensible without occupying a rep.
From the visitor's side, the visible version is that a short form produced the right next step. That is the whole trick, and it costs them four fields rather than nine.
The bit people get wrong
Do not show the enrichment back to the visitor. Confirming their company name on the thank-you page is a small delight the first time and unsettling the second, and it invites the question of what else you know about them.
Use it to decide what happens next, not to demonstrate that you did it. Same rule as every other signal: it should shape the response, not become the subject of it.
