Skip to main content
Outcomes are one of the strongest truth sources in Introd. They convert theory into operating data. Opportunity flow in Introd

Where outcomes flow

  • intro request status changes
  • intro request event records
  • graph sync for outcome ingestion
  • connector execution insight invalidation
  • relationship intelligence recalculation
  • intro outcome and marketplace dashboards

What outcomes should influence

  • connector ranking
  • introducer likelihood
  • target responsiveness
  • company memory and route health
  • recommendations for similar future targets
  • follow-up sequencing

Outcome quality bar

The system should distinguish between:
  • sent
  • accepted
  • declined
  • replied
  • meeting booked
  • converted
  • ghosted or ignored
Those are not equivalent signals.

Why this matters to ranking

Connector score, target score, and introducer likelihood already use weighted outcome history in code. That means a connector with fast replies and completed intros should outrank a connector with only generic adjacency.

Product expectation

The product should surface outcome learning back into: