Framework
Leads vs Prospects — Canonical Definition
Define the operational difference between a lead and a prospect in outbound contexts, using observable criteria only.
This framework defines the operational difference between a Lead and a Prospect in outbound — using observable criteria only.
It is intentionally rules-based, observable, and non-opinionated.
Core Comparison Table
| Dimension | Lead | Prospect |
|---|---|---|
| Definition | A contact record | A business selected for outreach |
| Selection basis | Availability of contact info | Observable business signals |
| How identified | Scraped lists, databases, directories | Filtered based on criteria |
| Intent evidence | None | Implied via signals |
| Timing relevance | Unknown | Contextual |
| Outreach trigger | “We sell X” | “We noticed Y” |
| Personalization input | Name, company only | Reason for outreach |
| Message structure | Generic template | Context-specific opener |
| Response predictability | Low | Higher |
| Volume strategy | Maximize count | Minimize noise |
| Primary failure mode | Irrelevance | Misread signal |
| Skill dependency | Copywriting-heavy | Targeting-heavy |
| Scaling constraint | Reply quality | Signal accuracy |
Signal Definition + Categories
A Prospect is identified only if ≥1 observable signal is present.
Signals must be public, verifiable, time-bounded where applicable, non-interpretive.
Valid Signal Categories
1. Website Signals
- Website exists
- PageSpeed / performance issues
- Missing or thin service pages
- Outdated or unclear conversion paths
2. SEO Signals
- Low indexed page count
- No service-location pages
- Poor mobile experience
- No structured content for core services
3. Paid Ads Signals
- Active ads (Meta, Google)
- Ads driving to weak landing pages
- Mismatch between ad intent and page structure
4. Conversion Signals
- No clear CTA
- Broken forms
- No trust elements
- Poor mobile UX
5. Hiring / Expansion Signals
- Recent job postings
- Marketing, growth, or ops roles
- Signals ≤90 days old
Explicit Non-Signals
These do not qualify a business as a Prospect on their own:
- Industry
- Company size guesses
- Revenue estimates
- Visual opinions (“site looks bad”)
- Generic labels (“needs SEO”)
- Gut feeling
If no signal exists → it is a Lead, not a Prospect.
Operational Implications
Outreach to Leads
- Requires heavy personalization to compensate for lack of context
- Reply rates depend on copy quality
- Scales poorly without large volume
Outreach to Prospects
- Personalization anchored to signal
- Copy can be simpler
- Reply rates depend on signal accuracy
One-Sentence Definitions
Lead: A contact you can email.
Prospect: A business you should email, based on evidence.
Constraints / Rules
Do not use “lead” to describe a prospect
- Do not use “lead” to describe a prospect
- Do not imply guarantees or outcomes
- Do not frame prospects as “better leads”
- Treat this as a classification model, not marketing copy
Zendory is built using these principles, not presented as a perfect implementation of them.