Part of Lead generation
Use operational definitions
| State | Useful definition | Evidence to retain |
|---|---|---|
| Lead | Potential customer interest worth evaluating | Source and need |
| MQL | Meets agreed marketing evaluation criteria | Relevant interaction and fit hypothesis |
| SQL | Passes agreed sales qualification criteria | Need, fit, constraints and next decision |
| Opportunity | A viable commercial decision is being pursued | Scope, participants and next action |
These definitions must reflect your process. There is no universal score that makes an MQL or SQL valid across companies. A small service business may not need both labels.
A handoff that preserves context
Provide the original interaction, stated problem, known fit, unanswered questions and any commitment already made. Sales should not have to reconstruct why the person was included.
Avoid handing over a contact based only on repeated content consumption. Ask whether the interaction supports a conversation and whether the proposed channel is appropriate. Distinguish interest in learning from interest in hiring.
When sales rejects a lead
Return the reason to marketing: irrelevant scope, closed project, unsupported audience, no current need or incomplete context. A rejected handoff can reveal a weak definition rather than poor sales effort.
Review patterns together. If the definition changes, document the date so reporting does not compare incompatible cohorts. Keep qualification criteria stable while evaluating a channel experiment.
When the labels are unnecessary
For a freelancer with a small number of requests, a simple evaluated → qualified → opportunity process may be clearer. Add states only when they help ownership and decisions.
The goal is a useful handoff, not a complex funnel diagram. A clearly documented problem and next step are more valuable than an impressive set of abbreviations.