Insight / B2B Sale Research
Research acceptance criteria: define what complete means
A dossier can look detailed and still miss a mandatory buyer check. Acceptance criteria should specify verifiable fields and honest exception states before work begins.
Content owner: D2 GROUP. Educational guidance on the disclosed research QA standard, not a substitute for an approved SOW. Examples are fictional, not D2 client cases.
Direct answer
An accepted dossier meets documented requirements, not a row quota
Research acceptance criteria are a written agreement about which company, evidence, buyer and direct work-email checks must pass for a completed account dossier. Under the current D2 B2B Sale Research definition, Core, Growth and Scale share one QA standard. Missing mandatory information must remain GAP or research in progress; a confirmed hard exclusion is REJECT. Acceptance is not a guarantee of reply, meeting, active buying need or revenue.
Which company counts?
Specify the correct legal or operating entity, geographic eligibility, required ICP characteristics and existing-customer exclusions.
Which claims need sources?
Define how WHY_SELECTED, publicly observed signals and person-role matches are attributed, dated and tested.
Practical workflow
Five steps to write useful acceptance criteria
Agree on the policy during scoping, not after the first difficult contact check.
- 01
Define final deliverable fields
List company identity, ICP rationale, dated material evidence, buyer and work-email verification, known limits and next action.
- 02
Separate stage gates
Allow early candidate discovery and company qualification to have lighter checks without calling those records completed ACCEPT dossiers.
- 03
Document exception states
Define each decision as a documented contract rule. ACCEPT requires all mandatory dossier checks; GAP keeps unresolved required evidence with reviewer/next action; REJECT records a verified hard-fit or exclusion failure. NO_VERIFIED_SIGNAL is permissible when the approved brief does not mandate a signal.
- 04
Select reviewer and feedback path
Name who inspects dossiers, records acceptance or defect reasons and determines whether more research is needed.
- 05
Review disputed examples
Use hypothetical cases to test the standard, especially absent signals, old events, group entities and unverified direct emails.
Review checklist
Acceptance policy review checklist
Each answer should be specific enough for both client and researcher to apply.
- Are mandatory ICP fit and account exclusions versioned and explicit?
- Is the correct operating entity required rather than only a brand name?
- Must significant statements have attributable sources and check dates?
- Does the standard distinguish signals from inferred buying intent?
- Are named buyer and direct work-email checks required for final ACCEPT?
- Are review ownership, GAP/REJECT handling and correction scope clear?
Illustrative examples
Apply the ACCEPT, GAP and REJECT contract to three sample records
A fictional QA policy requires the correct operating entity, hard ICP fit, attributable material evidence, a current named buyer and verified direct work email. A public buying signal is not mandatory. All three decisions are hypothetical.
GAP — company fit passes, contact remains unresolved
An eligible fictional manufacturer matches the approved ICP, passes exclusions and has source-backed operations. Its suggested engineering contact is not verified at the current employer and no direct work email has passed checking. Company qualification can be retained, but the final dossier must remain GAP with owner and next verification step recorded.
ACCEPT — no mandatory buying signal
A fictional operator has verified legal entity and ICP fit, documented WHY_SELECTED and source dates, a current relevant named buyer and a direct work email passing the agreed method. There is NO_VERIFIED_SIGNAL and the contract does not require one. The record can be ACCEPT for dossier quality; it is not a confirmed opportunity or a meeting.
REJECT — explicit customer exclusion
A fictional firm has a suitable production process and a recent public expansion, but its verified legal entity matches the client's existing-customer exclusion list. The hard exclusion overrides other positives. Record the matched entity, rule and review date; do not reclassify it as ACCEPT to inflate delivery count.
Interpretation limits
Common mistakes in setting acceptance rules
Do not confuse quality assurance with business outcomes.
Different quality by package
A higher research-hour package does not justify different mandatory acceptance requirements under D2's current one-standard definition.
Volume substituted for evidence
A fixed number of company rows can reward weak qualification and does not establish how many completed dossiers meet the standard.
Unknown treated as certainty
Blank sources, guessed emails or unspecified buying authority cannot be turned into PASS by a preferred conclusion.
Specialist research decisions
Make the acceptance calculation reproducible
A rate is meaningful only when the team defines the counted records and time window. The quantities here are definitions, not measured D2 delivery performance.
Count unique reviewed dossiers, not source rows
Define a fictional review cohort with one row per distinct company legal entity and dossier ID, a documented period and a frozen ICP version. Keep discovered candidates, submitted dossiers and final QA decisions separate. Do not call a contacted company ACCEPT when the named buyer, current employer or direct work-email check failed.
Use ACCEPT / GAP / REJECT with auditable reasons
Accepted-dossier rate equals ACCEPT dossiers divided by the eligible dossiers actually reviewed in the specified cohort. Report GAP and REJECT as separate counts and define the handling of rework, duplicates and exclusions; do not use REVIEW or NOT_FIT as ambiguous substitutes for the final three statuses. A rate without its denominator, period and exceptions is not a verified supplier-quality benchmark.
Keep signal absence and sales results out of the numerator
NO_VERIFIED_SIGNAL does not automatically fail a dossier when the agreed ICP brief does not require a time-based event. Buyer contact verification is part of the current core research acceptance standard; Outreach and Appointment Setting are separately contracted. QA ACCEPT cannot be equated with sales replies, appointments, consent to contact, pipeline value or revenue.
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
Can a qualified company be GAP?+
Yes. Company-level fit can be established while an agreed mandatory buyer, email or evidence check remains incomplete.
Must every accepted account have a buying signal?+
Only if explicitly required by the approved scope and supported by evidence. Otherwise NO_VERIFIED_SIGNAL is an honest, usable outcome.
Does ACCEPT confirm the company will buy?+
No. It indicates a quality-checked research deliverable, not an active opportunity or guaranteed conversion.
Do the plan prices define an accepted dossier quota?+
No. Current D2 pricing uses research-hour capacities; the number of dossiers that pass QA varies with ICP complexity and evidence availability.
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
