B2B Lead Intelligence · Production QA evidence

A strong Lead Intelligence process proves why records are held back — not only how many are accepted.

This guide turns an anonymized Vietnam production cohort into a reusable QA method. It publishes the denominator, observation period, acceptance gates and state distribution while keeping client, prospect, buyer, contact and account-level source identities private.

Read the direct answer B2B Lead Intelligence

Direct answer

How does D2 QA B2B Lead Intelligence before handoff?

D2 applies account/ICP, evidence, buyer, direct-contact, freshness and final QA gates before a record reaches SALES_READY. In one anonymized Vietnam production cohort of 100 account records researched or revalidated on 10–11 October 2026, 43 reached SALES_READY, while 24 remained CONTACT_GAP, 16 BUYER_GAP, 7 REVIEW, 9 NOT_FIT and 1 NURTURE. This is cohort-specific research evidence, not a market benchmark or sales-conversion claim.

Observed cohort

Publish the denominator and period before publishing a percentage.

The denominator is 100 account records that were researched or revalidated during 10–11 October 2026 under one private Vietnam software/security Lead Intelligence brief. The cohort includes revalidation work, so it is not described as 100 newly discovered prospects.

The public case is aggregate. Account identities, buyer/contact details and account-level source URLs remain private, while the production system retains record-level traceability internally.

QA state	Records	Share of 100	Meaning
SALES_READY	43	43%	Passed the agreed research and handoff-readiness gates
CONTACT_GAP	24	24%	Direct validated contact requirement not satisfied
BUYER_GAP	16	16%	Accepted current buyer could not yet be verified
REVIEW	7	7%	Material ambiguity required further human/research review
NOT_FIT	9	9%	Failed the agreed ICP/evidence boundary
NURTURE	1	1%	Potentially relevant but outside the current ready set
INVALID	0	0%	No record ended in INVALID in this observation cohort

Acceptance contract

SALES_READY is a hard-gated research state, not a positive-sounding label.

For the active production cycle represented in this snapshot, all 43 SALES_READY records had a verified DIRECT business email for the selected buyer and contact status VALID. Generic or fallback company email did not satisfy the acceptance rule.

The same records also had to satisfy the account, buyer, evidence/signal and final QA contract. A plausible company was intentionally held back when a hard gate was unresolved.

Source & freshness

Evidence age and contact verification must be visible enough to refresh stale records.

Signal/evidence dates and contact verification dates are preserved when they are material to the brief. All 43 SALES_READY records in the active production cycle had contact verification dates on 10 or 11 October 2026.

Freshness is field-specific. A current buyer/contact route can age faster than a stable company fact, so a production process needs dates and refresh states rather than one vague batch-level claim that all data is fresh.

Buyer & contact

A company can fit the ICP and still fail the handoff gate.

CONTACT_GAP and BUYER_GAP are valid research outcomes. They show that the account may remain commercially plausible even though the required buyer or direct validated route has not been verified to the brief's standard.

Keeping those states visible prevents a research team from pattern-generating emails, guessing ownership or downgrading the acceptance rule just to hit a row quota.

Claim boundary

This cohort proves research discipline, not downstream sales performance.

The snapshot did not contain handoff_date values, so SALES_READY is presented as handoff-readiness rather than proof that every accepted record had already been delivered to the client.

The cohort contains no public downstream response, meeting, pipeline, purchase-intent, closed-revenue or ROI measurement. Those outcomes require separate source records, periods and attribution rules.

Benchmark discipline

One 100-record cohort is not a Vietnam market benchmark.

The 43% SALES_READY share is an observation under one private brief, one acceptance contract and one period. Different products, ICPs, buyer roles, required contact fields, source availability and freshness rules can materially change the distribution.

D2 therefore publishes this as production QA evidence and methodology support, not as an industry-average lead acceptance rate.

Decision checklist

QA checklist before a B2B record enters the handoff-ready set

01State the observation period and denominator before reporting rates.

02Resolve company/domain identity and duplicate or suppression rules.

03Apply the agreed ICP and exclusion hard gates.

04Preserve evidence/source/date where the brief requires factual or timing support.

05Keep observed facts separate from need or purchase-intent inference.

06Verify a current buyer in an accepted function or record BUYER_GAP/REVIEW.

07Meet the required contactability standard without guessing direct emails or phones.

08Expose the contact/evidence verification date needed for freshness decisions.

09Record the gap/rejection reason instead of silently repairing a failed record.

10Keep research readiness separate from delivery, reply, meeting, pipeline and revenue claims.

Related decisions

Continue through the buyer journey.

Production QA case

See the same cohort presented inside D2's B2B Work evidence hub with explicit claim boundaries.

Read next

B2B lead quality criteria

Define the acceptance contract before production begins.

Read next

Vietnam B2B Lead Intelligence

See the supported Vietnam research scope and how evidence, freshness and contactability are handled.

Read next

B2B Lead Intelligence service

Review the current public service boundary, deliverables and acceptance logic.

Read next

FAQ

Common buyer questions.

Is the 43% SALES_READY share a Vietnam benchmark?

No. It is the observed state distribution of one anonymized 100-record production cohort under one specific private brief and acceptance contract.

Were the 43 SALES_READY records already handed to the client?

This public snapshot does not claim that. The records met the research/handoff-readiness gate, but handoff_date was not recorded in the snapshot used for the case.

Why are the source URLs and account names not published?

They are private client/prospect research data. The public asset publishes aggregate method, denominator, period and QA distribution while preserving account-level traceability inside the private production layer.

Does SALES_READY guarantee a reply or sale?

No. It means the agreed research and handoff gates were satisfied. Outreach, replies, meetings, proposals, negotiation, revenue and ROI are downstream client-side outcomes.

B2B Lead Intelligence

Make the failed states measurable before scaling the accepted set.

Share the target market, offer, ICP, buyer functions, evidence requirements, freshness rule and mandatory contact fields. D2 can validate a bounded cohort before recurring production.

Discuss a QA-defined pilot