Key points
- Define the acceptance rules and measurement units before delivery.
- Measure coverage, field quality and accepted output on comparable cohorts.
- Report the sample, review date and unresolved limitations with each result.
Benchmark an agency lead list against a defined audience, a documented review method and a comparable prior cohort. Separate the quality of the delivered records from the client's sending setup, message and follow-up.
A useful report explains what was checked, what remains unknown and which action follows. Unsupported industry-wide accuracy, phone-match or meeting-rate ranges do not become reliable simply because they are labelled benchmarks.
Agree on the accepted record before measuring it
Record the client's account and role criteria, required fields, exclusions and intended channel. Define whether delivery counts contacts, unique people or unique accounts, and how multiple stakeholders at one company are treated.
Specify the review method and how uncertain outcomes are reported. A field being populated, an identity being matched and an address passing a particular validation check are separate findings.
The client ICP validation workflow helps turn the brief into testable criteria.
Give each metric a definition and denominator
| Metric | Define it from | Limit |
|---|---|---|
| Reviewed account and role fit | Records meeting the stated criteria among the records reviewed | A sample needs its method, size and unresolved cases disclosed |
| Known-input match rate | Matched records among eligible supplied inputs under the declared rule | A match is not a verified email or a current-job guarantee |
| Required-field completeness | Populated required fields or complete records under an explicit definition | Presence does not establish correctness |
| Validation outcomes | Results among the addresses or numbers actually checked | Report method, time and uncertain outcomes; do not call the rate overall accuracy |
| Duplicate findings | Duplicate or unresolved records under declared person/account identity rules | Shared names, domains or inboxes do not automatically establish the same person |
| Campaign delivery outcomes | The sending system's classified results with its stated denominator | Failures can involve configuration or policy as well as contact data |
Keep attempted messages, delivered records, unique contacts and unique accounts distinct. A campaign can send several messages to one contact, so a message-level rate is not automatically a record-level rate.
Build an internal baseline from comparable cohorts
- Freeze the definitions. Keep eligibility, identity rules, required fields and review method consistent.
- Record the cohort. Capture source, audience, geography, role mix and delivery period.
- Inspect a declared review set. Explain how records were selected and what was checked.
- Report outcomes and uncertainty. Keep failures, unresolved cases and missing observations visible.
- Compare like with like. Identify changes in audience, source, method or sending conditions before interpreting a trend.
- Choose a corrective action. Assign an owner and a check that will show whether the problem was resolved.
If a source or method changes, label the break in the series. Do not treat it as proof that one market has become inherently easier or harder to reach.
A small cohort may still be commercially useful, but its rates can be unstable. Report the underlying counts and uncertainty rather than presenting a narrow sample as an industry norm.
Keep delivery quality and business outcomes connected but separate
A correct account and role can still produce no response. A failed campaign can involve audience fit, contact quality, authentication, messaging, timing or follow-up. Investigate the observed failure instead of assigning blame from one metric.
- Wrong accounts: review the brief, query interpretation and exclusions.
- Missing fields: review coverage and whether the requirement is essential.
- Invalid-recipient failures: investigate the source and relevant contact evidence.
- Authentication or policy rejections: review the sending setup and actual provider response.
- Weak qualified outcomes: inspect role fit, message relevance, expectations and follow-up.
The data quality checklist helps assess the source evidence. The deliverability guide develops the sender-side distinction.
Do not label pipeline multiplication as ROI
Qualified leads multiplied by an average deal value describe a hypothetical pipeline calculation, not realised profit. An open opportunity has not necessarily become revenue, and attributed revenue is not automatically incremental return.
Xero's ROI explanation uses net profit relative to investment cost. A simplified campaign calculation can compare incremental gross profit before campaign costs with the relevant campaign investment:
Campaign ROI = (incremental gross profit before campaign costs − campaign costs) ÷ campaign costs × 100
Define the time period, cost scope and evidence supporting incrementality, avoiding double-counted costs. If that evidence is unavailable, report observed pipeline, revenue and cost under those names rather than claiming a profit multiple from unclosed leads.
Give the client a report that supports a decision
Use a compact report with the cohort definition, output counts, review method, metric denominators, unresolved findings and next actions. Include campaign outcomes only when their source and scope are clear.
- State what was delivered and which acceptance criteria were checked.
- Show counts alongside percentages and label missing observations.
- Separate contact retrieval from independent validation evidence.
- Explain changes that affect comparability.
- Assign ownership for corrections and the next review.
Use the agency production workflow to apply those findings to the next delivery rather than merely redesigning the report.
Describe the underlying source honestly
Dievio contact search can supply candidate records for the client's audience. Free previews count matching contact records; they do not certify quality, unique company totals or email reachability.
Available contact fields are not proof of a fresh verification or guaranteed campaign result. Keep the agency's actual checks, source limitations and delivery obligations explicit.



