The playbook
Referral Programs: Metrics and Measurement
Measure referral programs by defining qualified referred opportunities precisely enough that two people can reproduce the result from the same records. Keep the reporting unit, date basis, and scope visible. Without those definitions, a change in the report may reflect a changed calculation rather than a changed customer outcome.
Put the task in context
Explain what makes a relevant introduction and how the referred person will be contacted. Keep incentive terms clear. Track introductions through acceptance and qualification so the program rewards useful relationships rather than indiscriminate contact submissions.
Create a metric definition
| Definition field | What it must explain |
|---|---|
| Measure | qualified referred opportunities |
| Unit | What one customer or opportunity record or completed outcome represents |
| Included records | The scope identified by referrer and introduction |
| Date basis | The event date or period used to include a record |
| Exclusions | Tests, duplicates, or other records outside the agreed definition |
| Source owner | sales manager |
Separate delivery checks from outcome measures
A delivery check asks whether the team completed a specific task, such as define who is a suitable referral and how introductions work. An outcome measure asks what happened for the user or business afterward. Keep both visible. Completing the task is useful evidence of execution, but it does not by itself prove that the broader outcome improved.
Worked arithmetic example
Suppose an illustrative review includes 80 eligible records, and 60 satisfy the explicitly defined completion condition. The completion share is 60 ÷ 80 × 100 = 75%. This is hypothetical arithmetic, not an industry benchmark or a predicted improvement. It describes only the population and condition you defined.
For referral programs, explain the condition before applying that calculation. If the question is whether the team can track referrals through qualification and follow-up, a record counts only when the evidence demonstrates that condition. Do not replace missing outcomes with successful ones just to complete a report.
Compare like with like
Keep the scope, date basis, and exclusions consistent between observations. If introduction changes meaning between periods, note the change and rebuild a comparable view where possible. A rate can also move because the composition of the underlying group changed, even when individual performance did not.
Investigate an unexpected result
- Check whether the underlying referrer records are complete.
- Look for this known failure: rewarding raw contact submissions without regard to relevance.
- Verify that the process still includes: explain any incentives and eligibility clearly.
- Reconcile a sample with the original record before changing the operating plan.
Use the report to choose an action
If the evidence supports a correction, measure accepted introductions and disclose program terms. Record when the change occurred and what should be checked next. Keep uncertainty visible when the sample is small or the observation period is incomplete. The purpose of measurement is a better decision about qualified referred opportunities, not a favorable-looking number.
Review a small sample of underlying records before trusting a summary. Duplicates, stale close dates, and missing outcomes can make a dashboard misleading even when the calculation is correct. Correct the record-level cause.
Skip the manual steps. Let AgentixCRM run this for every client.
Start now