Measure network contribution by recording what happened at each step: a possible path, an introduction request, an accepted introduction, a meeting, an opportunity and an eventual outcome. Keep those stages separate. A connection is not a meeting, and a meeting is not revenue.
A small, consistent ledger is more useful than an impressive dashboard built on unclear definitions.
Start with a relationship-to-outcome ledger
| Field | What to record |
|---|---|
| Target | The person or account you wanted to reach |
| Connector | The person who offered relevant context or an introduction |
| Path state | Identified, requested, declined, accepted or introduced |
| Meeting | Whether a meeting was scheduled and actually held |
| Opportunity | Whether your team qualified a real opportunity |
| Outcome | Progressed, paused, closed or still open |
| Evidence and dates | The source and timing of each real event |
Use the same definitions across the team. An introduction should be marked made only when it actually happened, not when someone appeared on a network map.
Distinguish sourced from influenced
Network-sourced pipeline can describe a new opportunity that entered your defined pipeline because of a qualifying relationship or introduction. Network-influenced pipeline can describe an existing opportunity where a relationship later helped the team reach another stakeholder or answer an important question.
Choose your team's attribution rules before reporting totals. Decide how to handle multiple connectors, pre-existing opportunities and opportunities that never qualify. Do not add sourced and influenced totals together if the same opportunity appears in both.
Look for useful questions, not vanity numbers
- Which introduction requests resulted in a welcomed conversation?
- Where did a possible path need better context?
- Which connectors received a thank-you and an outcome update?
- Which qualified opportunities had a clear next step?
- Where did a direct approach work better than waiting for a path?
These questions can improve the process without claiming that a relationship caused a sale.
A worked example of clean attribution
Imagine ten possible paths identified, six requests made, three introductions made and two meetings held. These are separate stages in a fictional example, not results Finta has measured. If one meeting becomes a qualified opportunity, record that event under your team's definition rather than counting all ten paths as pipeline.
Try it with Aurora, Claude or Codex
Share only information you are authorized to use, and review the result before acting.
Help me design a network contribution ledger.
Our stages, data sources and attribution rules: [details].
Define each event, its denominator, how to avoid double counting and the questions we can answer with the data we actually have.
Connect the work
Finta Networks helps you review available relationship context, and Finta's CRM can keep conversations and next actions together. Your team still needs to define attribution and verify which events your reporting captures. See how to track warm intro requests for the operational side.