Most disputes between marketing and sales about pipeline are disputes about a definition that was never written down. Marketing counts a lead when a form is filled in, sales counts one when a buyer agrees to talk, and each month the two teams argue about the gap between those numbers instead of the accounts behind them. A qualified lead has to be defined in facts that either side can check, before the work starts, or the argument restarts every month.
We use five facts, and each one closes a specific argument. The lead is a named person in the buying group, which closes the argument that an anonymous visitor or a student downloading a white paper was ever a lead. They work at a target account the client agreed to in writing, which closes the argument that a company could never have bought. They stated a need or a timing in their own words, recorded as they said it, which closes the argument that a page visit was interest. There is a lawful basis for contacting them in their country, which closes the argument that sales can't follow up without legal risk. And the account is not already an open opportunity in the CRM on the day the lead is delivered, which closes the argument that marketing claimed credit for a deal sales was already working.
In the vocabulary most teams already use, the first two facts are what a marketing qualified lead tries to capture, fit with the account list, and the third is what a sales qualified lead tries to capture, interest confirmed by the buyer. BANT, the budget, authority, need and timing test in most sales guides, asks for two things that are rarely known at first contact when a dozen people share the decision, budget and authority, so we keep need and timing in the buyer's own words and replace the other two with facts anyone can check: a lawful basis for contact and no open opportunity in the CRM.
The definition only holds if rejection is bounded too. A client gets five business days to reject a lead, with a reason picked from a fixed list, and after that the lead counts. The fixed list matters as much as the window: when either side can reject for any reason at any time, the definition reopens every month under a different name, and the five facts stop meaning anything.
A qualified lead is still not a deal. The definition says a conversation is justified and the evidence for it is recorded, while the technical evaluation, the relationship and the close stay with the client's own team, and many qualified leads will not become customers. With a list of a few hundred accounts, one month can also produce too few leads to judge a channel, and a report that pretends otherwise is guessing.
For a revenue leader, the consequence is practical. If your team bought leads, or reported them, without these facts written down, or on a price per lead set before anyone measured the list, the number on your dashboard measures activity rather than demand, and the budget decisions built on it inherit that error.
The same test works on any lead source, whether it's an agency, an event or your own website, and the Torke Service page shows how each fact is recorded. Take last month's leads and check each one against the five facts, then count how many survive: that count is your real lead number, and the gap between it and the reported figure tells you how much of your pipeline reporting is definition rather than demand.