Skip to main content
← B2B Lead Intelligence service

B2B Lead Intelligence · Sample deliverable

See exactly what a qualified B2B lead report should contain.

Not just a company name, a generic email and a spreadsheet row. Explore a complete research dossier: whom the account fits, what the evidence actually says, who owns the purchasing decision, which contact gates must pass and what Sales can do next.

D2 · DATA CONTRACT

46

Illustrative fields across six research groups

Client ICP & research contract06
Account identity & verifiable fit08
Buyer map & direct-contact gate08
Signal ledger, source dates & timing08
Solution fit, counter-evidence & sales action07
Quality gate, disposition & CRM handoff09

EXAMPLE ONLY · FICTIONAL ACCOUNT · NO REAL CONTACT INFORMATION

Direct answer

What information is included in one complete B2B lead from D2?

A completed B2B Lead Intelligence record identifies a company that fits the client's agreed ICP, documents why it qualifies with attributable sources and freshness context, maps a relevant named buyer, includes that person's verified DIRECT professional email with VALID contact status, checks exclusions and duplicates, and gives Sales a clear next action. L2/L3 research may add dated observed signals, opportunity hypotheses and counter-evidence; those layers are not proof of a purchase. Incomplete buyer/contact records remain research output and are not counted as completed leads.

RESEARCH ANATOMY

One record. Six connected layers of research.

These are the blocks Sales and RevOps should be able to inspect before accepting a lead. The demo does not assert that its example data is real.

01

ICP & selection

Who the client wants to reach and why this company qualifies.

02

Account facts

Identified company, activity, location, sources and freshness.

03

Buyer & contact

Relevant purchasing function, named buyer and independent direct-email QA.

04

Signals & timing

What was observed, when, where, and which claims remain unknown.

05

Opportunity reasoning

Offer-to-problem fit, hypothesis, counter-evidence and limitations.

06

Acceptance & CRM

Status, exclusions, freshness rules and the next sales action.

L1 / L2 / L3

Choose research depth without confusing evidence and intent

L1, L2 and L3 are research depth choices, not three different promises of meetings. Completed-lead acceptance still requires a named buyer and verified direct professional email.

L1

Verified Fit

ICP, source-backed company qualification, relevant named buyer and verified DIRECT contact.

No buying signal required

  • Company matches must-have ICP and exclusion rules
  • Account facts linked to appropriate evidence
  • Current named buyer and DIRECT professional email VALID
  • Duplicate check and CRM-ready acceptance

L2

Opportunity Intelligence

All L1 gates plus time-bound searches for observable trigger signals and relevance.

NO_VERIFIED_SIGNAL is a valid result

  • Hiring, expansion, tender, stack or operational change
  • Source identity, publish/observed and verification dates
  • Signal-to-offer relevance, confidence and limitations
  • No fabricated "buying now" statement

L3

Proof of Opportunity

L2 evidence and a testable commercial opportunity thesis with counter-evidence.

Hypothesis—not a guaranteed deal

  • Who might own the problem and why timing matters
  • Hypothesis versus confirmed fact clearly labeled
  • Alternatives, conflicts, stage and counter-evidence
  • A specific next question for the client's sales team

Field-level data contract

What one full research dossier actually contains

A research handoff is useful only when each field explains the sales decision it supports. Source references and statuses in this demo are non-operational placeholders.

Illustrative lead dossierDEMO_ONLY · NOT SALES_READY

Example Factory Account 001

Illustrative electronics manufacturer · Đồng Nai, Vietnam

The client's fictional ICP

Supplier of industrial electrical switchgear looking for manufacturing plants with on-site electrical distribution and suitable engineering/procurement buying roles in Southern Vietnam.

Names and facts below are invented solely to demonstrate fields. A real QA_PASS requires independently verified business sources, a current named buyer and a verified DIRECT work email.

01Client ICP & research contract6 FIELDSWithout a commercial brief, an impressive-looking account can still be wrong for the offer.
CLIENT_OFFER
Industrial electrical switchgear (illustrative supplier)
Anchors qualification to the product, not a sector label.
TARGET_COUNTRY
Vietnam (Supported research market)
Prevents unsupported country claims and scope drift.
ICP_INDUSTRY
Manufacturing / electronics assembly
Defines target segment and use-case relevance.
MUST_HAVE
On-site industrial electrical distribution (example criterion)
Explicit acceptance rule; not inferred from a registration code.
EXCLUSIONS
Resellers, inactive sites, existing customers, duplicate accounts
Removes wasted outreach and overcounting.
RESEARCH_DEPTH
L1 required; L2 signal scan optional; L3 thesis by scope
Separates base qualification from signal/opportunity layers.
02Account identity & verifiable fit8 FIELDSShow what is known about the operating company and what remains unconfirmed.
ACCOUNT_NAME
Example Factory Account 001 (fictional)
Identity field; verified legal/trading name is required in production.
WEBSITE_DOMAIN
[No live domain in this demo]
Avoids fabricated company URLs; production records keep sourced domain.
PRIMARY_LOCATION
Đồng Nai, Vietnam (illustrative)
Territory and actual site relevance must be checked.
BUSINESS_ACTIVITY
Electronics assembly plant (illustrative)
Actual operating use case rather than a broad classification.
WHY_SELECTED
Hypothetical factory power infrastructure could fit the offer
Sales can review the fit rationale; must be independently sourced in production.
EVIDENCE_SOURCE
DEMO-SRC-001 — fictional identifier; no URL
Real records cite retrievable evidence, not unverified IDs.
LAST_VERIFIED_AT
NOT_VERIFIED — example only
Distinguishes a live source check from a fabricated timestamp.
ICP_STATUS
DEMO_ONLY — would require separate FIT / NOT_FIT decision
Prevents any sample value from being treated as qualified.
03Buyer map & direct-contact gate8 FIELDSA correct company is not a completed lead without the relevant named buyer and a validated direct work email.
BUYING_FUNCTION
Plant Engineering / Technical Procurement (example roles)
Directs Sales to the party that specifies or buys the offered item.
TECHNICAL_EVALUATOR
Plant Electrical Engineer / Engineering Director (role example)
Identifies technical specification owner versus approver.
PURCHASING_OWNER
Head of Technical Procurement (role example)
Separates operational demand from contracting authority.
NAMED_BUYER
[PRIVATE — NO PERSON USED IN DEMO]
Real full names appear only with corroborating current-role sources.
BUYER_ROLE_SOURCE
DEMO-ROLE-001 — not a verifiable source
Real handoff checks role, employer, identity and freshness.
DIRECT_WORK_EMAIL
[REDACTED — NOT A VERIFIED ADDRESS]
A completed lead requires this buyer's actual verified DIRECT work email.
CONTACT_METHOD
DIRECT business email required (scope gate)
Generic inboxes, guessed patterns and personal emails do not pass.
CONTACT_STATUS
DEMO_NOT_VALIDATED (real accepted records: VALID)
Unverified or masked demo contact must never count as SALES_READY.
04Signal ledger, source dates & timing8 FIELDSThe researcher must distinguish observation, commercial relevance and unknowns.
SIGNAL_01_TYPE
Illustrative production-hall / electrical upgrade announcement
Shows which type of external change could be researched.
SIGNAL_01_FACT
FICTIONAL — no real event or source has been observed
Avoids presenting demo storytelling as an actual buying signal.
SIGNAL_01_SOURCE
DEMO-SIGNAL-001 (placeholder, non-clickable)
A real sourced signal needs a retrievable location and evidence extract.
PUBLISHED_DATE
UNKNOWN / N/A for fiction
A published date cannot be fabricated to make a signal look recent.
OBSERVED_DATE
NOT_OBSERVED
Observation date is independent of source publication date.
SIGNAL_01_RELEVANCE
May relate to switchgear planning if technical scope confirms
Commercial interpretation must not be confused with observed fact.
SIGNAL_STATUS
DEMO_ONLY; real L2 can return NO_VERIFIED_SIGNAL
A clean empty signal scan is better than manufactured intent.
BUYING_WINDOW
UNKNOWN — not a confirmed project or budget
Prevents a guessed timeline from becoming a sales promise.
05Solution fit, counter-evidence & sales action7 FIELDSWhen L3 is requested, explain why the opportunity might exist and what would falsify it.
SOLUTION_FIT
Industrial switchgear could apply to site distribution (hypothesis)
Connects the offered product to a real operating problem when verified.
OPPORTUNITY_THESIS
Example: site expansion may trigger power-system review (hypothesis)
Keep inference clearly distinct from an approved procurement plan.
COUNTER_EVIDENCE
Equipment may already be procured / facility may be leased
Shows why signals alone cannot guarantee a buying window.
CONFIDENCE_LEVEL
UNASSESSABLE — fictional input
Real scoring depends on verified evidence, not polished prose.
BUDGET_STATUS
UNKNOWN
No claim of budget without a substantiating source.
DECISION_STAGE
UNKNOWN
Published activity alone does not prove tendering or vendor selection.
SALES_OPENING
Ask whether electrical-system plans are already specified
A consultative next question, not a fabricated personalized pitch.
06Quality gate, disposition & CRM handoff9 FIELDSIncomplete research needs a transparent hold status and explicit next action, not a fake accepted lead.
DUPLICATE_CHECK
REQUIRED — no actual CRM run on demo
Production handoff excludes repeated accounts and suppressed contacts.
ICP_QA
NOT_RUN — demo
A real acceptance includes the agreed must-have and exclusion checks.
EVIDENCE_QA
NOT_RUN — demo
Material company and signal claims need independently retrievable sources.
BUYER_QA
NOT_RUN — demo
Current named-person and role are mandatory for a completed record.
CONTACT_QA
NOT_RUN — demo
Verified DIRECT professional email with VALID status is mandatory.
RESEARCH_STATE
DEMO_ONLY; would be CONTACT_GAP without a verified direct email
Shows the actual consequence of a missing contact field.
SALES_READY
NO — illustrative record must not enter production counts
Prevents generated samples from inflating accepted-lead metrics.
RECOMMENDED_NEXT_STEP
Research legitimate company source, buyer identity and direct contact
Specifies the next bounded research action before Sales outreach.
CRM_HANDOFF_FIELDS
Account ID, fit, sources, buyer, contact gate, signals, QA, next action
Structured import contract for Sales/CRM, not just a flat email list.

The dossier below is 100% illustrative. Its company, events, names, dates, source IDs and contact fields are placeholders—not researched companies, verified signals or deliverable-ready contacts. Real client records and direct emails stay private.

SOURCE → FACT → INFERENCE → SALES

Source-to-decision trail

Multi-signal means reconciled evidence, not merely attaching many links. A researcher records what the source supports and what it does not.

  1. 01 / SOURCE

    Company-owned operating information

    Identifies company, location and business model; the demo intentionally has no live URL.

  2. 02 / OBSERVATION

    Illustrative facility/electrical-system announcement

    Could justify checking equipment relevance; the demo does not confirm any real expansion.

  3. 03 / INTERPRETATION

    Industrial switchgear may be relevant

    A commercial hypothesis pending engineering discovery, not a confirmed budget.

  4. 04 / BUYER

    Engineering and technical procurement functions

    Find current named people and verify direct business emails separately.

  5. 05 / HANDOFF

    ICP + buyer/contact gates + QA state

    Only accepted, verified records enter the counted completed-lead set.

RAW LIST VS RESEARCH

What Sales gains versus a raw B2B data list

CriteriaOrdinary data listD2 research handoff
Account qualificationCompany category or filter matchICP decision, exclusions, operating evidence, WHY_SELECTED
Who to contactGeneric inbox or guessed titleNamed relevant buyer and verified DIRECT work email
Why nowGeneric "high intent" labelObserved dated facts and distinct NO_VERIFIED_SIGNAL option
Sources and freshnessUnclear source and crawl dateSource IDs, observed/verified dates and missing-evidence flags
Opportunity notesAutomatically written sales pitchSolution fit, counter-evidence, UNKNOWNs and question to verify
AcceptanceRows counted as leadsPASS, CONTACT_GAP, BUYER_GAP, NOT_FIT or REVIEW with QA trace

QUALITY GATES

The non-negotiable acceptance gate

A company may be relevant and have strong signals, yet still be held. Account fit cannot compensate for missing named-buyer and direct-email validation.

01 · ICP and exclusion match

The account satisfies all must-have filters; competitors, duplicates and excluded segments are checked.

02 · Evidence and freshness

Material company/qualifying facts have suitable provenance; stale or ambiguous data is flagged.

03 · Named buyer

A current, relevant named person is confirmed for an accepted buying function.

04 · DIRECT professional email

The named person's direct work email is verifiable; a guessed address or generic inbox is not enough.

05 · Final disposition

QA_PASS / SALES_READY only when required gates pass; otherwise CONTACT_GAP, BUYER_GAP, REVIEW or NOT_FIT.

ANONYMIZED PRODUCTION EVIDENCE

What real QA looks like when private client data is excluded

A separate anonymized Vietnam technology-solutions pilot in October 2026 demonstrates why research and completed leads must be counted separately. These real cohort totals do not validate the fictional dossier above.

55

Accounts researched

24

Accounts eligible under ICP

15

Accepted for handoff

9

Eligible but held for direct-contact gaps

This is one pilot's QA denominator, not a market average, booked meetings, replies or revenue. Individual real client account names, buyer identities, direct emails and private source trails are not public.

Read the real anonymized pilot evidence

FAQ

Questions buyers ask before ordering research

Is this a real B2B lead or a real company?

No. It is a deliberately fictional example that documents the structure, field descriptions and QA rules only. Public evidence about actual completed research is linked separately without disclosing client-private contacts.

Do D2 leads always include phone numbers and multiple signals?

Phone is included when explicitly agreed and supportably verified. L1 needs ICP fit and validated buyer/direct email; L2/L3 add deeper signal and opportunity research as the scope requires. A valid outcome may be NO_VERIFIED_SIGNAL.

Does an L2/L3 buying signal mean the company will buy?

No. Signals are sourced observations. A project announcement, tender or job opening can inform timing but not guarantee budget, purchase approval, a reply or a signed contract.

Why are DIRECT emails hidden in this public sample?

Real named-person business contact details and customer project context belong to a private, access-controlled handoff. This demonstration neither publishes them nor pretends placeholders are verified.

When is a researched account counted as a completed lead?

Only after agreed ICP and exclusions pass, current named buyer is validated and that person's DIRECT professional email has VALID status. CONTACT_GAP/BUYER_GAP records remain separately visible and uncounted.

Can my sales team receive the same fields in a spreadsheet or CRM?

The delivery structure, required evidence fields and CRM mapping are scoped with the client. Export format and optional fields depend on the accepted research brief and delivery workflow.

D2 B2B LEAD INTELLIGENCE

See your own ICP reflected in a research-ready sample.

Share what you sell, the target market, ICP and exclusions, buyer functions, required evidence and contact gates. D2 can assess a bounded 15-lead test and an acceptance contract before production.

Discuss a 15-lead research test

Vietnam is the currently Supported target market. Other destinations require documented research/contact feasibility. Managed outreach and appointment setting are not included in the standard intelligence service.