How to qualify LinkedIn leads before contacting them

Before first contact, you are asking whether there is a credible business reason to speak with this person. Before a sales meeting, you may also need to understand the current problem, who is involved and what a conversation could resolve. An opportunity stage should have its own criteria. These decisions require different amounts of evidence.

LinkedIn's lead-generation guide describes BANT: budget, authority, need and timing. Those categories can help organize discovery, but a public profile rarely answers all four. A form submission or an actual exchange may provide information that a job title cannot. Treat a missing answer as unknown until you have a reliable basis for updating it.

Suppose your team sees a finance director at a suitable company. The title may make the person worth investigating. It does not establish an allocated budget for your project. Requiring a guessed budget before any contact encourages invented data; assuming budget is available creates the opposite error. Write the question down instead.

Use the account criteria you already defined for your offer. A CRM cleanup service for multi-person sales teams might require an existing CRM, a process its consultants support and a delivery arrangement the client can accommodate. A company can be successful and still have no use for that service.

Check the company's own website and current public information before relying on a directory label. Confirm the business model and the work it actually performs. If geography, language, system compatibility or implementation access is a real delivery constraint, write that constraint specifically. Do not turn a convenient search filter into a hard requirement without a business reason.

Check your existing records too. An active customer, an account already being handled by a teammate, a prior refusal or a known conflict needs different treatment from a new prospect. Finding the same person through another post does not erase that history. Resolve the ownership or contact restriction before considering a campaign.

A useful checklist tells a reviewer where an answer came from. It also shows where the source stops. A current role description can support responsibility for a process; it cannot prove the person wants to change it. A job advertisement can describe planned work without establishing an outside-services budget.

Record the source and review date close to the conclusion. When sources disagree, retain the conflict and choose a verification step. Do not silently select the version that makes the prospect look more attractive.

If a prospect posts about reporting problems, read the post. Is it their current team's situation, an old case study, a general industry observation or someone else's story? The distinction determines whether your opening can refer to an actual problem or should ask whether the subject is relevant at all.

A new job, hiring announcement or strong sales quarter can suggest a useful research question. None proves that an outside project is a priority. Likewise, a quiet profile is not evidence that the person has stopped working, does not make decisions or never reads LinkedIn. Avoid disqualifying a suitable account solely because its relevant contact does not post frequently.

The We-Connect qualification guide lists profile sections and activity worth inspecting. Its claim that title and seniority directly identify budget or authority goes beyond what those fields establish. Use the inspection list to gather context, then verify the buying process through an appropriate conversation.

Keep the business purpose narrow. You do not need a dossier of personal interests to explain why a CRM process might matter to a sales-operations lead. Professional evidence relevant to the offer is easier to review, correct and use respectfully.

You can start with four review decisions: an appropriate first question, more research, revisit for a named reason, or do not contact. These are proposed working labels, not built-in OutreachGenie statuses or a universal sales framework. Each label should come with an explanation another teammate can check.

Use more research when a material fact is unresolved, such as whether the person still works at the company. Use revisit when you have a specific reason to wait, such as the prospect's stated request to reconnect after a named event. Without that reason, a revisit list can become a queue of indefinite follow-ups.

A hard fit failure or refusal is not something engagement points should outweigh. If you later introduce scoring, define each input, keep missing data visible and compare the decisions with actual reviewed outcomes. A mathematically correct total can still be based on unsupported assumptions.

Consider a CRM cleanup consultancy reviewing the following fictional records. These companies, people and observations are invented to demonstrate the method. They are not OutreachGenie customers or campaign results.

The first record has no engagement signal, but it has a plausible business fit and a relevant responsibility. The second is enthusiastic but outside the service's requirements. The third needs a basic employment check. The fourth must not be contacted, regardless of how attractive its company looks.

Notice what the review does not do: it does not guess budget from company size, turn interest into urgency or count a refusal as an objection to overcome. The outcome is a defensible next action for each record, not a ranked list of people assumed ready to buy.

For the fictional Cedar record, a first message could say: 'Hi Sam, your current role mentions CRM reporting. I work with sales teams on CRM cleanup and reporting processes. Does reviewing that work sit with you?' It states the commercial context and asks about a relevant uncertainty without asserting that the company has a problem.

If Sam replies that a reporting review is under way, the next question should follow that answer. You might ask what prompted the review or which part of the process is causing difficulty. You do not need to send budget, authority, need and timeline as four demands in one message.

A request for a resource can be answered as a resource request. It need not be converted into a meeting condition. When a call becomes useful, explain what it would help decide and let the other person choose. If the reply is a refusal, stop; a switch of channel is not a qualification step.

This pre-contact checklist cannot answer every discovery question. Its purpose is to remove avoidable mismatches and make the first exchange relevant. A useful answer from the prospect should update the record, including any correction to your original hypothesis.

Use OutreachGenie's prospect company, title and profile URL fields for the basic record. Custom fields and notes can hold your team's manual review decision, supporting source, date checked, unresolved question and owner. Name research lists so they are not confused with lists cleared for outreach.

In the same fictional example, the consultancy's reviewer could write: 'Company website and Sam's current profile checked September 10. Company/use case fit supported; role covers reporting. No active project confirmed. Decision: appropriate first question. Research owner: Nina on our team. Next action: ask whether reporting review sits with Sam.' The owner is your teammate responsible for the next step, not the prospect. Replace outdated statements when better evidence arrives and retain the reason for material corrections.

Review selected records before adding them to a campaign. A label in a note is not an automatic enforcement mechanism, and this article does not claim the product implements the four review decisions for you. Check the actual list, prior contact and restrictions. LinkedIn's limits on third-party scraping and automated activity also apply independently of how carefully a list was qualified.

Review a sample with a teammate and see whether you reach the same decision from the recorded evidence. Disagreement can reveal an unclear fit rule, stale information or a missing source. Resolve the rule rather than changing a score until the total looks convincing.

For a simple record-quality check, count records containing all five required review fields: source, review date, decision, owner and next action. In an illustrative batch of 12 records, nine complete records produce a completeness rate of 9 divided by 12, or 75%. This is a fictional calculation, not a campaign benchmark or an estimate that 75% will buy. A record can be complete while correctly marking budget unknown.

After outreach, review substantive corrections, wrong-person replies and reasons the offer was unsuitable. Feed those observations back into your criteria. Keep those measures separate from acceptance or total replies: a polite response can reveal a mismatch, and discovering that mismatch is still useful research.