A lead quality audit answers a question most dashboards avoid: of the leads we reported last month, how many would still count if someone checked them against a written definition? It needs no new tool, a month of leads can be checked in a few hours, and the result is a number the next budget conversation can be built on.
We call that number the Definition Gap. You take the leads reported for a period, check each one against the five facts, and divide the number that fail by the total that was reported. If 60 of 100 reported leads fail, the gap is 60 percent, which means six of the ten leads on the dashboard were counted only because nobody had written the definition down.
The gap exists because every team that reports leads has a reason to count generously, and nothing in the reporting tool stops it. A form fill from a student, a webinar registration from a competitor, a contact at a company far outside the ideal customer profile and a call with an account that was already an open opportunity all arrive in the CRM looking like leads. Each one is easy to count and hard to remove later, because removing it lowers a number someone has already presented.
Running the audit is mechanical once the facts are written. Export last month's leads with the account, the person's role, the source and the date. For each lead, mark whether the person is named and belongs to the buying group, whether the account is on the account list agreed in writing, whether the person stated a need or a timing in their own words with a record of what they said, whether a lawful basis for contact exists for their country, and whether the account was already an open opportunity on the day the lead arrived. A lead that fails any one fact fails the audit, and the reason it failed is worth recording, because the reasons tell you which source to fix.
Take a month with 120 reported leads. Suppose 30 have no named person behind them, 25 are at companies outside the account list, 20 have no recorded statement of need and 5 were already open opportunities, with no lead failing twice. That leaves 40 leads that meet all five facts, a Definition Gap of two thirds, and a real cost per lead three times higher than the one in the report. The figures are an example, and your own figures can be worked out from records you already hold.
The audit has two limits. It can only check what was recorded, so a team that never wrote down what the buyer said will see a large gap that partly measures missing notes rather than missing demand, and the first fix may be the record rather than the source. And a gap of zero is not the goal in every program, since some early programs deliberately collect contacts that are not yet leads, which is fine as long as they are reported under their own name instead of being added to the lead count.
For a revenue leader, the gap is the correction factor for every number built on reported leads. Cost per lead, conversion rates, channel comparisons and the case for next quarter's budget all inherit it, so a channel that looks cheapest may simply be the one with the loosest definition. Reporting the audited figure next to the reported one every month removes the incentive to count generously, because the gap itself becomes the number people discuss, and the activity that never produced a lead shows up for what it is, free spin.
A lead count is only as good as the definition behind it, and the Definition Gap is the cheapest way to find out what yours is worth. The same audit works on any number built from a definition, from opportunities to trial sign-ups, wherever a team reports a figure it also benefits from. Pull last month's leads this week, check each one against the five facts and write the surviving count next to the reported one, because that pair of numbers is where every honest conversation about what lead generation should cost starts.