Understand qualification results
Read the score, match reason, evidence, and hard requirements behind a delivered prospect.
When to use this
Use this article when reviewing why a record was delivered or deciding what to change for the next run.
Requirements and availability
- Qualification uses the saved profile and evidence available during the run.
- Selected Extra requirements are pass-or-fail.
- Human review remains necessary because public and inferred information can be incomplete or outdated.
How to do it
- Open Prospects.
- Open a prospect.
- Review Qualification score, Why they match, and company and contact facts.
- Compare the evidence with the saved profile and its Extra requirements.
- Open the company website or public profile before outreach.
Fields and controls
| Control | What it does |
|---|---|
| Qualification score | A 0–100 fit score when one is available; filters support 50+, 60+, 70+, 80+, and 90+. |
| Why they match | The reason the record aligns with the profile. |
| Suggested first angle | A draft direction that still requires human review. |
| Targeting profile | The saved profile responsible for the decision. |
What happens next
A reviewer can trace the record to its profile, inspect fit, and decide whether the contact and context are appropriate. Leama may check market, company type, size, buyer role, buying signals, and exclusions where data and the saved profile permit. These are review dimensions, not a promise that every record passes six identical checks; selected Extra requirements are hard gates.
States you may see
| State | Meaning |
|---|---|
| Score shown | A numerical score is available. |
| No score | No numerical score exists; use the other evidence. |
| Delivered | Configured delivery completed. |
| Staged | The qualified record is stored but delivery is incomplete. |
Credits and usage
Reviewing does not use credits. Credit use belongs to the research run and its options.
Common problems
| Problem | What to check |
|---|---|
| The match reason is not convincing | Verify the source, then refine one profile field before comparing a later run. |
| A required field is missing | Confirm the requirement was enabled when the run started and review the event log. |