Why qualification belongs before the pitch
Belfort includes prospecting and qualifying among the official resources for Way of the Wolf. For a founder, the practical issue is allocation: which opportunities deserve a proposal, which need more information and which should end? The checklist here is our own small-business application.
Time spent on an unsuitable proposal is not free. The owner loses time for delivery, hiring or better-fit opportunities. More seriously, a persuasive pitch may turn that unsuitable opportunity into a disappointed customer. Qualification should be allowed to change the answer from yes to no.
Define fit in operational terms
Start with the problem you can solve, the conditions required to solve it and the limits of your capacity. Avoid defining the perfect customer only by company size or job title. Those attributes may help you search, but they do not explain whether the work is viable.
For example, a fictional implementation agency can migrate a supported platform when the customer has an internal owner and access to the required data. A large company without either condition may be a worse fit than a small company that is ready. A clear qualification process makes this visible without judging the prospect’s importance.
Ask questions that affect the recommendation
- What has made this worth considering now?
- What would need to work differently after the project?
- Which systems, people or constraints must the solution fit?
- How will the decision be made, and who needs information?
- What resources can the customer realistically commit?
Explain why a sensitive question matters. If you ask about budget, describe which decisions it helps you narrow. A customer may reasonably prefer to see an outline first. You can proceed with a stated assumption and make clear that it needs checking.
A three-outcome decision note
After discovery, write one of three outcomes: propose, investigate or decline. For a proposal, state the evidence that the work fits. For investigation, name the unanswered question and who can answer it. For a decline, explain the mismatch plainly.
Imagine a prospect asks the agency to finish a migration in two weeks. The technical work could take two weeks, but access approval has not started. The right next step is checking that dependency, not promising the full delivery date. The opportunity remains open without turning an assumption into a commitment.
Use a short note the delivery team can read. A CRM score with no explanation is less useful than two sentences describing the customer’s goal and the dependency that could prevent it.
Do not turn the checklist into a barrier
A checklist can become an excuse for refusing to think. New customers may not understand your terminology or know every stakeholder yet. Help them understand the decision without demanding that they arrive already qualified.
Review declined opportunities periodically. Were the criteria too narrow, or did they correctly identify work you could not serve? Review accepted projects too: where did delivery reveal a missing question? This feedback connects sales activity to the actual customer experience rather than just to pipeline size.
Put the idea to work.
Choose one offer and define three necessary conditions for successful delivery. Write a question for each condition and a useful next step when the answer is unknown. Review one won and one lost opportunity against the checklist, using anonymised notes.
