Defining lead qualification
How to define a qualified lead for your business
By ByTomorrow · Published
A CRM label such as "qualified" is useful only when your team agrees what it means. If one person uses it for anyone who answered the phone and another reserves it for a ready buyer, the pipeline cannot guide work reliably.
Define the decision before asking automation to apply it. The worksheet below is for ordinary business-service inquiries. It supplies a process template, not a universal sales rule or regulated eligibility standard.
What needs attention
Where the process can go wrong
Interest is confused with service fit
Someone can be interested in a service you do not provide. Conversely, a good-fit inquiry may need time before scheduling. Keep those questions separate.
Missing information becomes a rejection
A person who has not supplied a location or scope is not necessarily unsuitable. Use an incomplete category and a specific next question.
The score has no evidence behind it
A number from a model or a checklist is not a fact about the customer. Store the supporting answer and the rule used for the decision.
Practical worksheet
Use this with your own business details
Service-fit row
Write the requirement in observable terms: the requested work is within an owner-approved service category. Record the source answer, yes/no/unknown result and reviewer. A request that does not fit any current category goes to review rather than an invented category.
Location or delivery-fit row
Where relevant, compare the provided location or delivery requirement with the actual service rules. Leave the result unknown if the address is incomplete or near an unresolved boundary. Do not infer fit from a phone area code.
Readiness row
Record whether the person wants information, an estimate, a conversation or an available next step. Store a requested timeline as a request, not confirmed availability. Readiness can guide follow-up without changing the underlying service fit.
Missing-information row
List the exact unanswered question and who will ask it. Example: "Requested installation, but the required installation type is unknown; intake owner will clarify." That is incomplete, not declined.
Decision and evidence row
Use a small set of outcomes: ready for the defined next step; fit but later; incomplete; outside current scope; human review. For each, write the evidence and permitted action. Ask the owner to approve the definitions before automation uses them.
Fictional worked example
A caller requests a supported service in a confirmed area but has not chosen a date. Service fit is yes; readiness is information gathering; next action is an owned conversation. Do not mark the inquiry lost merely because no appointment was booked.
Put it to work
Check the complete process
Select one service
Start with the actual requirements for a single offered service instead of a company-wide score.
Define the next step
Write the action qualification permits, such as arranging an estimate discussion. Qualification should not silently authorize an unrelated commitment.
Label representative fictional cases
Include clear fit, clear mismatch and incomplete information. Have different staff apply the same worksheet.
Resolve disagreement
Change vague criteria until the team can explain why each case receives its outcome.
Review automated suggestions
Compare suggestions with the agreed cases and preserve overrides. Investigate systematic mistakes before letting a score route work.
Questions
Straight answers.
No. HighLevel documents contacts, opportunities and stages as organizational structures. Your business supplies the meaning and evidence required for a stage.
Only if the business can explain how it changes this decision. Avoid collecting information simply because a generic sales template contains the field.
Yes, under a definition that separates fit from readiness. The label should tell the team the permitted next step and what remains unresolved.
Sources and further reading
- HighLevel pipelines and opportunities
HighLevel distinguishes contacts, opportunities and pipeline stages. These structures do not define a business-specific qualification standard.
Checked .
Define the next action
Bring one service and examples of inquiries your team handles differently. Turn that judgment into an explicit worksheet before connecting it to automation.
Talk through your workflow