A Large Lead List Can Still Cover Very Few Target Accounts
Assess lead volume by counting distinct people, distinct target accounts, and relevant roles separately. A growing contact list can deepen coverage inside companies you already know without increasing the number of companies represented. Neither result is inherently wrong, but they support different claims about your prospecting supply.
Start with a permitted list and a defined account universe. Resolve duplicate people and ambiguous account associations, then group the remaining contacts by account. Report unresolved records separately. The worksheet below is a proposed review method, not an observed benchmark or a recommended contacts-per-account ratio.
What does the contact count actually measure?
A row count measures records in a file. It does not necessarily measure distinct people, because imports can include duplicate identities or multiple addresses. A distinct-person count measures individuals after your identity rules have been applied. It still says nothing by itself about how many companies those people represent.
Account coverage asks a different question: which target companies have at least one qualifying person in the list? Role coverage asks whether those people represent responsibilities relevant to your offer. Keep these counts alongside each other instead of treating them as interchangeable versions of “leads.”
Unify's company and audience filtering documentation distinguishes company records from people associated with them. That distinction is the basis for this review; a people audience is not an account count.
How many distinct target accounts does the list represent?
Define the account unit before grouping contacts. Use the stable CRM account identifier where available, with a reviewed mapping for records that do not yet have one. Treat a domain as evidence for matching, not a universal definition of a buying organization.
If a corporate group contains separate operating companies, document whether the report counts the group or individual accounts. The parent and subsidiary targeting guide addresses that identity question. Apply the same rule across the comparison period so a change in grouping does not masquerade as account growth.
Likewise, multiple product lines do not automatically create multiple accounts. Record the relevant operation when prospecting companies with several business lines, while keeping the account-counting rule explicit.
Count the distinct resolved accounts that meet the target definition. If you also report a coverage percentage, its denominator must be a separately defined target-account universe. Without that universe, describe accounts represented in the list; do not claim a share of the addressable market.
Account coverage (%) = represented qualifying target accounts ÷ accounts in the defined target universe × 100. Use the same account grouping rule and snapshot for both counts. If the target universe is undefined or empty, the percentage is undefined: report represented accounts as a count instead.
How much of the list is concentrated in a few accounts?
Group distinct people by resolved account and sort by contact count. Inspect the distribution rather than relying only on the average. An average can hide both heavily populated accounts and accounts with little usable coverage.
Choose any concentration grouping before comparing periods and disclose it in the report. The numerator and denominator must use the same population: for example, distinct qualifying people mapped to resolved target accounts. Keep unmapped people visible outside that calculation rather than silently treating each as a new account.
This is a proposed descriptive analysis, not a threshold for deleting records. Concentration may reflect a deliberate account plan, a narrow source list, duplicate identities, or easier access to data at certain companies. Inspect the evidence before deciding which explanation applies.
Top-k concentration (%) = qualifying people assigned to the k largest accounts ÷ qualifying people assigned across all resolved target accounts × 100. Choose k in advance, rank accounts by that person count, and assign each qualifying person to one documented reporting account. If a person legitimately counts toward several accounts, use person–account relationships consistently in both counts and label the measure accordingly. An empty population has no defined concentration percentage. Report unresolved associations separately.
Do the contacts cover relevant responsibilities?
Review role coverage within each account after establishing account identity. A list of different people can still repeat the same function while missing the responsibility relevant to your offer. Use documented scope, not seniority alone, as explained in finding the owner of the problem.
Mark a role as supported, plausible but unconfirmed, or absent from the available evidence. These are proposed review categories. They should not imply that a person has purchasing authority merely because their title resembles your persona.
For an account that needs deeper engagement, buying committee mapping can guide the next research step. Keep that strategic decision separate from the descriptive count: another relevant stakeholder adds role depth even when the number of accounts remains unchanged.
Check complicated associations individually. A consultant may legitimately relate to several companies, but each connection needs evidence. The fractional executive account-matching workflow helps avoid counting every company in a biography as a current buying account.
Which concentrated accounts need review?
Review accounts where the contact count is high but the purpose is unclear. Ask whether the people are distinct, current, relevant, and assigned to a documented motion. Keep useful depth when it serves an account objective; flag redundant or unsupported records for correction.
Do not automatically delete contacts to make the distribution look balanced. That can remove legitimate operational or technical stakeholders. Equally, do not keep adding familiar titles solely to meet a weekly sourcing target. Decide whether the next research task should deepen a particular account or add a currently uncovered target account.
Separate list composition from campaign eligibility. Unify's audience discrepancy guidance explains that record type and exclusions can produce different list and Play counts. A lower eligible audience is not, by itself, evidence that accounts disappeared from the underlying list.
What should an account-coverage worksheet contain?
Create an account-level worksheet from the resolved list. Leave unknown values explicit and retain the list version or snapshot used for the review. The blank structure below supports a repeatable review without inventing account observations.
| Field | Record for each account | Review question |
|---|---|---|
| Account identity | [Stable ID, name, grouping rule] | Is this the account unit used throughout the report? |
| Distinct qualifying people | [Observed count and person IDs] | Were duplicate identities and irrelevant records separated? |
| Relevant responsibilities | [Supported roles and evidence] | Does the list cover the function the offer concerns? |
| Unresolved records | [Unmatched people or uncertain roles] | Which unknowns could change the interpretation? |
| Reason for depth | [Account objective or review needed] | Is concentration intentional and useful? |
| Next research action | [Owner, action, review condition] | Should research add account breadth or role depth? |
Keep a separate summary containing the list scope, snapshot, raw records, distinct people, represented target accounts, and unresolved records. For each count, name the inclusion rule. Do not subtract every excluded contact from account coverage if another qualifying person still represents that account.
What does the calculation look like?
This hypothetical example holds the target universe, account grouping, and qualification rules constant. It illustrates the arithmetic; the numbers are not observed results or a recommended list size.
| Metric | Snapshot A | Snapshot B |
|---|---|---|
| Accounts in the defined target universe | 100 | 100 |
| Distinct qualifying people, each assigned to one resolved target account | 500 | 650 |
| Represented qualifying target accounts | 20 | 20 |
| Account coverage | 20 ÷ 100 × 100 = 20% | 20 ÷ 100 × 100 = 20% |
| Qualifying people in the five largest accounts | 200 | 325 |
| Top-5 concentration | 200 ÷ 500 × 100 = 40% | 325 ÷ 650 × 100 = 50% |
The people count rises by 30%, while account coverage remains 20%. Top-5 concentration rises from 40% to 50%, a change of 10 percentage points. These counts alone do not prove improved role coverage: inspect the responsibilities of the people added. There are no unresolved associations in this illustration; in a real review, report their count separately rather than assigning them invented accounts.
How can a manager report repeatable prospect supply?
Compare consistent snapshots using the same target and identity rules. Report newly represented accounts separately from additional contacts at previously represented accounts. Also identify accounts that lost their last qualifying contact. A rising people count can coexist with unchanged or shrinking account coverage.
Use Unify's audience concepts to distinguish the current qualifying population from a saved review snapshot. A live audience and last week's export answer different time-based questions, so label them accordingly.
For research gaps, Unify's company and contact data provides the product context for finding accounts and people. Unify Agents supports research and qualification. Ask for evidence about account fit or role scope, then review the output before changing the worksheet. Neither capability establishes that a list is evenly distributed or covers your whole market.
A useful management statement names the movement: account breadth increased, role depth improved, or unresolved identity work remains. Keep those outcomes separate from sending volume and replies. That makes the next sourcing decision clear without using contact growth as a substitute for account reach.
Frequently asked questions
Does a larger contact list mean broader market coverage?
No. Additional people can belong to accounts already represented. Count distinct qualifying accounts separately, and only describe a coverage rate when you have a defined target-account universe for the denominator.
Is there an ideal number of contacts per account?
There is no universal ratio established by this worksheet. The useful depth depends on the offer, relevant responsibilities, and account objective. Review concentration in context rather than treating a single ratio as a quality standard.
Should concentrated accounts be removed?
Not automatically. Verify identity, role relevance, and the reason for deeper coverage. Correct duplicates and unsupported associations while retaining useful stakeholders for a documented account motion.
How should unmatched contacts affect the account count?
Keep them in an unresolved category until their account association is established. Do not count each unmatched person as a unique company or assume that all unmatched people belong to one account.
Can a new stakeholder improve a list without adding an account?
Yes. A verified stakeholder can fill a relevant role gap within an existing account. Report that as improved role depth rather than new account coverage, so the contribution remains visible and accurately labeled.
Glossary
- Account breadth: The distinct target accounts represented under a stated account rule.
- Role depth: The relevant responsibilities represented within an account.
- Contact concentration: How the people in a list are distributed across its accounts.
- Review snapshot: A fixed version of the population used for a comparison.
Published by Unify Team. The company profile provides organizational background; this worksheet is an editorial method, not an independently validated study.
