Skip to main content
D2 GROUP

Insight / B2B Sale Research

How to review a batch of B2B account dossiers without hiding quality gaps

Review each dossier's facts and missing fields, record reasons for ACCEPT, GAP or REJECT, and use sales feedback to improve the next research cycle.

Content owner: D2 GROUP. The batch, records and acceptance decisions below are fictional training examples; no production delivery metrics, verified client results or guaranteed volume are claimed.

Direct answer

Batch acceptance summarizes dossier QA, not a fixed quota

A B2B account research batch review checks the agreed ICP version, company identity, source provenance, buyer/contact verification, exceptions and the client's acceptance decision for each submitted dossier. Record ACCEPT only when all mandatory fields meet the shared QA standard; use GAP for work that needs a stated recheck and REJECT for confirmed ineligible entities. Group decisions by reasons and next owners, not just total rows. D2's Core, Growth and Scale plans purchase research hours at the same quality standard, not a fixed number of accepted accounts.

Was the same ICP version used?

Record the market, offer, hard exclusions and approval date for the batch. If a client revises fit criteria midway, identify affected dossiers rather than silently comparing incompatible versions.

Are the evidence fields reproducible?

Sample material claims at the original source, publication/event date where available, checked-at date and current operating entity. A compelling headline cannot replace company-fit facts.

Are mandatory contacts checked?

Check named buyer, relevant role, present employer and direct work email against the agreed policy. Separate dossier ACCEPT from company-fit PASS when contact QA remains GAP.

Does someone own each exception?

Give unclear records a specific owner, reason, source to recheck and decision deadline if agreed. A GAP left in an unassigned column is not a finished deliverable.

Practical workflow

Five-stage batch review with a feedback loop

Use a review record the next researcher and sales owner can reconstruct.

  1. 01

    Confirm the batch contract

    Record the approved ICP and exclusion policy version, mandatory dossier fields, reviewer, any market-specific differences and the current research-hours scope. Do not invent a throughput commitment from the package name.

  2. 02

    Check entity and duplicate integrity

    Inspect sample legal operating entities, aliases, parent/subsidiary relationships, repeated records and exclusion matches. Escalate ambiguous merges instead of counting two spellings as two independent accounts.

  3. 03

    Review evidence and contact gates

    Check the reason selected, signal evidence if present, source dates, person-role-employer fit and direct work-email QA. Do not turn an inferred buyer timeline into a fact or hide contact gaps under a general green company-fit score.

  4. 04

    Decide status for every dossier

    Record ACCEPT, GAP or REJECT with reason codes, reviewer, checked-at date and the next action. The batch report should distinguish candidate count, company-fit qualified count and finally accepted dossiers without treating them as equivalent units.

  5. 05

    Review corrections before new discovery

    Return a compact list of recurring identity, ICP, source, contact and exclusion issues to the research team. Agree who updates rules and what rechecks are necessary; preserve old decisions and any approval instead of overwriting history.

Review checklist

Six acceptance gates for the batch owner

Use this list before announcing that a review cycle is complete.

  • Batch scope, approved ICP version and reviewer are recorded.
  • Every account has a unique identity and a documented exclusion decision.
  • Material company and timing claims show source and checking dates.
  • Buyer name, current employer/role and direct work-email fields meet the agreed final QA.
  • ACCEPT, GAP and REJECT labels have explicit reason codes and accountable next actions.
  • Any totals describe their actual unit and do not imply replies, meetings or revenue.

Illustrative examples

Three fictional batch review outcomes

This is an invented three-record teaching exercise, not a D2 customer batch, case study, historical throughput or productivity benchmark.

Record A — ACCEPT after complete QA

Fictional Alder Manufacturing matches the approved operating-site ICP, has an attributable source trail, is not excluded and has a current relevant named buyer with a direct work email that meets the contracted QA checks. The reviewer records ACCEPT, the verified fields, check dates and the sales-owned next step. It is still not a confirmed opportunity.

Record B — GAP on buyer contact

Fictional Briar Logistics fits the company requirements and its warehouse announcement has a clear historical source, but the named purchasing owner and direct work email are unresolved. Record company-fit PASS, dossier GAP, missing-field reason and follow-up owner. Do not include it in the accepted-dossier count.

Record C — REJECT on a hard exclusion

Fictional Cedar Components matches the industry but resolves to an existing customer that the client explicitly excluded from new prospecting. Record REJECT against the approved rule ID and entity match, retain a minimal audit trail and avoid treating it as a new target.

Interpretation limits

Three misleading batch-level measures

A reliable progress report does not conceal the work required to verify one entity.

Rows discovered equals accounts accepted

Discovery candidates are inputs, not the final accepted dossiers. Report the funnel by stage and reasons for unresolved records.

An average score substitutes for mandatory gates

A high company-fit score cannot override a missing current buyer or direct work-email requirement when the acceptance standard says those fields are mandatory.

Research hours are not a fixed dossier quota

Core, Growth and Scale allocate research capacity with the same QA. The number of accepted dossiers depends on ICP difficulty, source availability and verification work, not a published fixed quota.

Use insights without assuming a sale

Turn a research question into a checkable account brief.

The evidence can inform your approach but does not establish customer demand. Inspect the dossier standard, compare research hours or discuss a relevant ICP.

For this topic: Bring the observable event, your target market, the company-fit rule and what your team needs to verify next. An enquiry is voluntary, not a marketing subscription; the current website prepares an email for you to send yourself.

FAQ

Questions sales teams ask

How many dossiers should a research batch contain?+

The volume is scoped to the available research hours, ICP difficulty, source and buyer-verification work. The three D2 packages do not guarantee a fixed accepted-dossier count.

Can a company-fit PASS be counted as a delivered ACCEPT?+

Not when final mandatory fields remain GAP. Keep discovery, qualified company and QA-accepted dossier totals separate.

Should missing signals cause automatic rejection?+

No, unless a confirmed timely event is explicitly an approved mandatory criterion. Record NO_VERIFIED_SIGNAL and keep company fit separate.

What should a sales owner send back after review?+

Record decisions per dossier, field-level discrepancy reasons, ownership of corrections, agreed ICP changes and the next checks. Avoid unsupported claims about revenue or meeting performance.

Discuss the account research your team needs

Share your ICP, target geography and current sales research challenge. D2 can explain the evidence and acceptance criteria for a suitable scope.

Discuss your research brief