Lead Qualification: Screen Inbound Leads With Your ICP
Learn how to qualify inbound leads using your ideal customer profile (ICP) to prioritize high-fit prospects and improve sales conversions.
A demo request lands in the marketing queue. The form says little about the company’s industry, size, or the requester’s role. Sending it to sales would make the rep do the research. Rejecting it would be a guess. Lead qualification gives the team a third option: check each condition in its ideal customer profile (ICP) and hold uncertain parts for review.
For a single inbound lead, the process has four parts:
| Question | Record |
| What counts as a fit? | A test that can be checked |
| What do we know? | Evidence and the date checked |
| What is missing? | Unknown fields, kept separate from failures |
| Where does the lead go? | A decision with a named reviewer |
Build Lead Qualification Tests From Your ICP
An ICP such as “midmarket companies in our target industries” sounds clear until two people apply it to the same form. Marketing and sales should agree on each condition before assigning leads. For a hypothetical demo request, tests might cover industry, company size, service region, and contact function.
Write each test for another person to repeat. “Target industry” needs an approved list and a rule for companies serving several markets. “Company size” needs an agreed range and source. “Service region” refers to where the buyer needs service, which may differ from headquarters. A job title hints at function but may not show buying authority. Mark any condition that controls sales assignment as mandatory before reviewing the queue.
Research can start with the form, company website, and existing CRM records. An AI lead qualification agent is another way to prepare the check: its page describes a fit or no-fit result for each lead, supporting fields, and separately flagged missing data. Treat that output as a draft. Check sources and dates; let a person resolve conflicting records. A spreadsheet and manual checks also work.
A blank size field is unknown, not proof that the company sits outside the agreed range. A location outside a mandatory service region, backed by a dated source, is a no-match result. Keep those outcomes apart.
Record the Evidence, Not Only a Score
Here is a hypothetical demo request. Assume the team has defined its target industries, size range, regions, and contact functions. This is not a real customer or measured result.
| ICP test | Match / no match / unknown | Evidence and date | Missing data | Next step |
| Industry on approved list | Match | Company site describes a category on the team’s list; check date recorded in the working record | None for this test | Keep the page URL with the lead |
| Company size within agreed range | Unknown | Form gives no size; company site does not state it; check date recorded | A reliable size field | Check an approved company source |
| Buyer needs service in a supported region | Unknown | Demo form names a supported operating region; submission date recorded, but does not state where service is needed | Buyer’s required service region | Confirm the service location before deciding fit |
| Contact function is relevant | Unknown | Form contains a role label that could cover several functions; submission date recorded | Actual responsibility for the problem | Ask a human reviewer to interpret or confirm |
When someone performs the check, record its date. “Current website” tells a later reviewer nothing about when the page was checked. Store the source URL or CRM field, observed value, and check date together. If the form and company site disagree, retain both observations. Do not choose the version that makes the lead look better.
For B2B lead research, decide which sources are acceptable for each field before opening the form. A company’s own site may describe its market, while an internal account record may hold the service region previously confirmed by a rep. If neither source answers a mandatory test, name the gap and who will check it.
Lead scoring helps sort a queue, but a total hides its inputs. A high score from content interactions cannot fill an unknown mandatory ICP field, so an otherwise strong company stays “unknown” until that field is checked. Keep field-level evidence beside any score so the reviewer sees whether the number reflects fit, activity, or an assumption.
A company description supports an industry judgment. The requester’s role in a buying decision still needs separate evidence. Leave that question open.
Illustrative workflow: one matched ICP field and three unknown fields keep the hypothetical inbound lead in human review.
Separate an ICP Match From Sales Readiness
The hypothetical company fits the approved industry. Its required service region, size, and contact function remain unclear. If those are mandatory fields, put the lead in a review queue. Raising its score would only hide the gaps.
SpringBrand describes itself as a shared layer of APIs and plugins for existing AI agents. That explains how a team might run research from its current assistant. The lead qualification page describes output for a person to review, then paste or import into a CRM or other tools. It does not route leads, so assignment and contact stay with the team’s approved process.
Fit and interest answer different questions. Salesforce Trailhead describes a model that considers both, with sales and marketing agreeing on criteria. A demo request proves an action; it does not establish company fit, budget, authority, or purchase timing. The team may choose prompt follow-up while labeling those unknowns. Make that an explicit routing rule, not a claim about intent.
For this lead, a person checks the required service region and size, clarifies the contact’s function, then applies the agreed conditions. If evidence remains unavailable, assign a review owner. “Unknown” is a work item, not a softer spelling of “no.”
Route the Lead With a Reviewable Reason
A handoff note should let a rep understand the decision without repeating the research. Include the request, each ICP result, its source and date, open questions, and next owner. For a private CRM field, identify the field and access context rather than copying sensitive content into an uncontrolled note.
The note also needs a time boundary. A form timestamp shows when the prospect asked for contact; an old account record may describe a different business. If the decision relies on that older record, the reviewer should refresh it or explain why it remains usable.
Apply routing rules agreed before this lead arrived. Send it to sales when mandatory conditions and the readiness rule are met. Send it for review when a mandatory field is unknown or sources conflict. Hold or decline it when reliable evidence shows a mandatory failure, and record the reason. An optional criterion may affect priority but should not override that failure. Keep the path visible beside any score.
This lead belongs in review until the required service region, size, and contact function are checked. A researcher or agent may draft the evidence and note; a person should approve judgments where evidence is thin. CRM updates, assignment, and outreach follow the organization’s existing controls.
Each week, examine why sales returned leads marketing had marked qualified. If one ICP field repeatedly causes disagreement, give its test a clearer source or threshold, then apply the new rule to future leads.
