Research notes · checked July 2026Installer documentation
Revenue team reviewing prospect segments
USE CASES BY DECISION

Different teams need different evidence from the same market

The workflow should adapt to the decision being made, not force every buyer into one generic lead list. These use cases define the brief, expected output, and review responsibility for common B2B prospecting operators.

Choose the operator closest to your task

CRO / VP SALES

Pressure-test market coverage

Compare a strategic ICP against observable company attributes, discover where the addressable set becomes thin, and identify assumptions that need field validation. The output should support territory and resourcing discussions—not masquerade as a revenue forecast.

  • Brief: market boundary and sales motion
  • Review: segment logic and exclusions
  • Output: account set with evidence gaps
SDR / BDR MANAGER

Build a reviewable prospect queue

Translate a campaign thesis into a bounded list with role mapping, email status, and relevance notes. Managers can sample records before assignment and require message approval before a sequence receives any recipient.

  • Brief: campaign hypothesis and buyer role
  • Review: fit, verification, opt-out process
  • Output: approved research queue
REVOPS / GTM ENGINEER

Evaluate enrichment behavior

Test provider coverage on a representative record set, trace field provenance, expose conflicting values, and measure latency or cost in your environment. Waterfall enrichment should be a governed method rather than an invisible promise of completeness.

  • Brief: schema, providers, acceptance rules
  • Review: provenance and conflict policy
  • Output: measured evaluation ledger
FOUNDER

Research a narrow wedge

Turn a customer hypothesis into a small set of companies and people worth learning from. The first result is evidence for better discovery—not permission to blast a generic message across an untested market.

  • Brief: problem, segment, geography
  • Review: why each account belongs
  • Output: concise learning list
DEMAND GENERATION

Connect signals to account context

Combine firmographic and technographic observations with attribution events while recording time and source. Treat buying intent as a prioritization clue that needs corroboration, never as proof that a person wants contact.

  • Brief: signal definition and time window
  • Review: alternative explanations
  • Output: prioritized research candidates
OUTBOUND AGENCY

Standardize client research controls

Capture each client's exclusions, sending rules, approval owner, and data boundaries. A consistent evidence schema helps agencies explain how a record entered a campaign and keep one client's assumptions out of another's program.

  • Brief: client-specific policy
  • Review: segregation and authorization
  • Output: auditable client handoff

Selection checklist

Install, then begin with one use case and one review owner

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