Lead
A lead is an identified person or organization that may be relevant to a business, but has not necessarily passed qualification or accepted a sales conversation.
A lead is an identified person or organization that may be relevant to a business and can be evaluated for a defined next step. A lead record is not evidence of fit, intent, permission, qualification, opportunity or purchase.
- Meaning: a potential relationship recorded for evaluation.
- Why it matters: it creates a traceable starting point without overstating readiness.
- Used by: marketing, sales, partnerships, events, service and revenue operations.
- Commonly confused with: prospect, qualified lead, contact, opportunity and customer.
What a lead means and what its record needs
Salesforce describes sales leads as people or businesses that could become customers. This is a vendor category explanation, not a universal lifecycle contract. Review the source.
Every business should define the identity unit, accepted sources, minimum fields, permitted purpose, duplicate rule, owner, next evaluation and expiry. Labels such as inbound, outbound, event, referral and product-led describe source or motion; warm/cold describe an assessment that needs evidence; MQL and SQL are later business-defined states.
lead record = identity evidence + source/event + permitted purpose + observed signal + owner + next evaluation + expiry
Do not fill unknown budget, need, role or intent from weak proxies. Preserve what was observed separately from what a person or model inferred.
Example: completed lead record
| Field | Fictional entry |
|---|---|
| Identity unit | One company contact, work email verified; company match not yet confirmed |
| Source/event | Submitted webinar question on 12 August |
| Permitted purpose | Send requested answer and one event follow-up under reviewed rules |
| Observed signal | Asked how to route enquiries between two service teams |
| Unknowns | Company fit, authority, timing and active project |
| Owner/next step | Event team sends answer; sales evaluates only after explicit reply |
| Expiry | Re-evaluate or close after 30 days with no new evidence |
The record remains a lead. It is not qualified because the next sales transition lacks current evidence and acceptance.
How a lead differs—and how to use it safely
| Concept | Meaning | Use when | Do not confuse with |
|---|---|---|---|
| Contact | Identified person record | Identity/relationship management | Sales relevance |
| Lead | Potential relationship awaiting evaluation | Early capture and routing | Readiness |
| Qualified lead | Explicit criteria support a next action | Prioritization and accepted handoff | Guaranteed purchase |
| Opportunity | Defined potential deal in a sales process | Deal-level work is justified | Every interested lead |
In practice, lead definitions control routing, response, suppression, deduplication, reporting and denominator integrity. If teams count a download, a person, a company and a conversation as the same unit, lead metrics cannot be interpreted.
Common mistakes include buying records without provenance, treating contact details as consent, assigning several owners, never expiring stale records, overwriting the original source and letting an AI-generated score become fact. Measure duplicate rate, reachable/valid identity, owner acceptance, corrections, expiry and transition quality—not raw lead volume alone.