Part of Lead generation
The worksheet
| Check | Evidence to record | Decision if unknown |
|---|---|---|
| Need | Buyer’s stated problem or request | Ask what outcome is wanted |
| Fit | Service, platform, audience and constraints | Compare with offer exclusions |
| Current status | Date and resolution context | Confirm whether the request is open |
| Feasibility | Scope, dependencies and timeline | Offer limited scoping if worthwhile |
| Decision path | Role and other participants | Ask who evaluates the solution |
| Economics | Engagement expectations | Clarify the commercial model |
| Contact context | Channel rules and stated preference | Do not assume permission |
Use supported, unknown or unsuitable for each check. A total score should never override a decisive failure such as an infeasible scope or an unwanted contact path.
A filled hypothetical example
A business requests a checkout specialist before a launch. Need is supported by the request. Platform fit is supported if you work on that platform. Deadline feasibility is unknown until you see the integration scope. Budget and decision role remain unknown.
The next step is a concise feasibility question in a permitted channel. The lead is not yet a confirmed opportunity. If the buyer says the request has been filled, close it rather than continuing because the original signal looked strong.
Use the checklist in a handoff
Include the original source, reviewer date, known constraints and next question. The receiving person should be able to understand the decision without reading a vague label such as “hot.”
Agree on which checks must be supported before escalation. Small projects may need a lighter process than complex procurement. The checklist should scale to the decision rather than become a ritual.
Review rejected leads
Record one primary rejection reason and any important secondary constraints. Review a meaningful batch to see whether discovery is finding the wrong audience, scope or timing.
Do not remove rejection records simply to improve a dashboard rate. They explain labor cost and help improve the query brief. Collect only the operational context needed and manage the records appropriately.