Data coverage

Know what an account record can—and cannot—support

Demandbase-oriented research is useful when identity, observation, inference, and action remain separate. This compact reference defines the fields an evaluator should inspect before an account enters a revenue workflow.

Company facts, presented with their limits

Account identity

Begin with domain, legal entity, operating brand, parent, subsidiary, headquarters, and sales region. A shared domain, redirect, acquired brand, or franchise relationship can produce competing matches. The workflow should retain those conflicts instead of silently selecting one company.

Acceptance check
Test known parent-child structures and record why a particular entity was accepted.
Unknown state
Keep unresolved identity explicit; do not convert it into a confident account match.

Firmographic fit

Industry, employee range, geography, ownership, and business model can help evaluate an ICP, but each field may differ by source and observation date. A category label is evidence for review, not proof that the organization has the budget or problem your offer addresses.

Acceptance check
Compare representative good-fit, poor-fit, and ambiguous accounts.
Unknown state
Preserve missing or conflicting attributes rather than filling them by assumption.

Observed signals

Website activity, hiring, technology change, campaign engagement, and topic research need provenance and time context. None independently proves active purchase intent. Reviewers should ask whether the event is recent, attributable to the correct entity, relevant to the offered problem, and unusual against its baseline.

Acceptance check
Require source, observed date, topic, identity confidence, and a plausible alternative explanation.
Unknown state
Mark recency or attribution as unavailable when the connected source does not disclose it.

Buying committee context

Titles can suggest responsibility but do not establish it. Research should distinguish economic buyer, technical evaluator, operator, champion, and blocker, while retaining the reason each role was proposed. Contact verification and lawful outreach assessment remain separate gates.

Acceptance check
Review role relevance, current employment, suppression status, and regional requirements.
Unknown state
Do not invent a champion or claim access to a verified decision maker.

Verification checklist

  • Provenance: material claims retain a retrievable source reference.
  • Recency: events and mutable fields display an observation date when available.
  • Conflict handling: competing values remain visible until a reviewer resolves them.
  • Credential scope: connected API keys use the minimum permissions required for the task.
  • Retention: local files, agent logs, exports, and deletion behavior are inspected in the runtime.
  • Human gate: a person approves relevance, personalization, suppression, and any outreach action.

No coverage quantity, refresh interval, match rate, certification, or customer outcome is asserted here because the supplied brand materials do not substantiate those claims. Evaluate those changing facts against current official documentation and your own test cohort.

Test the evidence boundary yourself

Run a cohort containing known accounts, subsidiaries, ambiguous domains, stale events, and deliberate exclusions. Record acceptance, unknowns, correction work, and review time.

npx -y @okki-global/okki-go-taroball