Lead Qualification
Decide quickly whether a new lead is worth pursuing so your team spends time on real opportunities.
#Business goal
Focus sales effort on leads that fit and can buy.
#When to use this
When a new lead enters the pipeline.
#At a glance
| Detail | Value |
|---|---|
| People involved | Sales owner, SDR |
| Departments used | Sales |
| Modules used | CRM |
| AI used | Sales Agent drafts outreach and proposals; you review and send |
| Recommended timeline | Per lead, 10–15 min |
| Prerequisites | CRM access; Leads in the pipeline |
#Step-by-step process
1
Capture the lead
Ensure the lead is in CRM with source and contact details.
2
Score fit
Assess budget, need, timeline, and decision-making against your ideal profile.
3
Qualify or disqualify
Mark strong leads to pursue; set weak ones aside with a reason.
4
Assign an owner
Give qualified leads a clear owner and next action.
#Decision points
Decisions to make along the way
- Does the lead match your ideal client profile?
- Is there budget and a real timeline?
#Approval points
No formal approval gate
This routine has no separate sign-off step, but review your work before it affects clients or finances.
#Success metrics
- Higher win rate on pursued leads
- Less time spent on poor-fit leads
#Best practices
- Use a consistent qualification standard.
- Record why a lead was disqualified.
#Common mistakes
- Chasing every lead regardless of fit.
- Leaving leads unassigned.
#Realistic example
In practice
A referral comes in. The owner checks budget and timeline, sees a strong fit, marks it qualified, and schedules discovery — while a tyre-kicker with no budget is set aside with a note.
#Related documentation
Discovery Process
Next step.
Capture a lead
How-to.
Business Workflows
Underlying step-by-step flows.
Contact Support
Reach the DevSphere OS team.
Still need help?
Can’t find what you’re looking for? The DevSphere OS team is happy to help.
Was this page helpful?