Start with the task
Ask what the person is trying to improve and request an example of the current process. Someone requesting software may also need clearer responsibilities. Record the problem in their language before mapping it to your service. Avoid turning the first exchange into a checklist that leaves no room for their actual question.
Explore practical constraints
Ask who uses the process, which tools are involved, and whether timing matters. Budget and decision-making questions are more useful when connected to the work under discussion. Do not assume the person who sent the enquiry has purchase authority, or that an unknown budget means there is no relevant need.
Offer a proportional next step
A simple question may need a written answer rather than a meeting. A complex workflow may justify a demonstration. For example: “Would a short walkthrough of the import flow help, or would you prefer the checklist?” Give a choice that advances the open question instead of automatically pushing every enquiry into the same process.
Document what is known
Separate confirmed requirements from unanswered questions and your own interpretation. Add the agreed action to the lead record. Review your qualification questions when the team notices repeated confusion. Their purpose is to improve understanding and next steps, not to make a score appear more certain than the conversation supports.
Continue reading
Guide / Research
How to write a lead research brief
Define a useful lead before anyone starts collecting names and contact details.
Read the guide →Guide / Research
A source-checking checklist for lead research
Separate published facts from assumptions before adding researched contacts to your workflow.
Read the guide →Guide / Research
Lead intelligence vs contact data: what your team needs
Contact details tell you how to reach someone. Context helps you decide what to do next.
Read the guide → Browse all guides →