When a growth model double-counts referrals
Referred customers appear both in the referral loop and in the ordinary acquisition total. Diagnose the cause, choose a bounded correction and verify unique acquired customers reconciled across modeled channels.
On this page 8 sections
- Confirm the problem in the actual workflow
- Separate the visible symptom from the cause
- A situation to work through
- Choose the smallest useful correction
- Preserve the important limitation
- Verification worksheet
- Decide whether to keep, revise or stop the change
- Related methods and next steps
- Frequently asked questions
The short answer
Referred customers appear both in the referral loop and in the ordinary acquisition total. Start with this check: Trace the model's stock and flow definitions and identify overlapping cohorts. The corrective action is to assign each new customer to the intended counting rule and show contribution views separately.
Key points before you start
Referred customers appear both in the referral loop and in the ordinary acquisition total. The useful response is a diagnosis that changes a decision, not another report describing the symptom. Use this play with the experiment owner and the analyst responsible for design integrity. The working evidence should include hypothesis, assignment rules, metric definition and decision record, with private or sensitive details removed from any shared example.
Confirm the problem in the actual workflow
Trace the model’s stock and flow definitions and identify overlapping cohorts. Start with one representative case and follow it from the original action to the reported outcome. Identify where the observed behavior first differs from the intended process. A screenshot of a final dashboard can be useful, but it may hide the source record, a delayed update or a decision made elsewhere.
Keep the unit of analysis explicit: the prespecified eligible user or account cohort. The same label can conceal different populations or stages. Before comparing two results, check that they describe the same kind of work and have had a comparable chance to complete it.
Separate the visible symptom from the cause
Check the design before interpreting a result. Assignment, exclusions, outcome timing and stopping rules can change the meaning of an apparently precise statistic. Separate practical effect from statistical evidence and keep guardrails beside the primary outcome.
The symptom in this case is specific: referred customers appear both in the referral loop and in the ordinary acquisition total. Ask which piece of evidence would distinguish an operating failure from a measurement failure or a mismatch in the original plan. If the evidence is unavailable, record the missing source and its owner instead of treating the preferred explanation as established fact.
A situation to work through
A customer who clicks a referral link and later a search ad should not become two new customers in the forecast.
This is an illustrative situation, not a reported client case. Record the equivalent evidence and assumptions for your own workflow.
Choose the smallest useful correction
Assign each new customer to the intended counting rule and show contribution views separately. Keep the change narrow enough that the responsible people can implement and inspect it. If a correction changes several things at once, describe it as a combined operating change; do not later claim that one small element caused the whole result.
Assign the correction to the experiment owner and the analyst responsible for design integrity. Agree which artifact will show that the work is complete. An owner without an observable acceptance condition can close a task while leaving the original problem unresolved. A detailed checklist without an owner creates the opposite problem: the evidence requirement exists, but nobody is accountable for producing it.
Preserve the important limitation
A referral invitation is not a referred customer until the defined conversion occurs. This condition belongs beside the recommendation because it can change the decision. It should not disappear when the plan becomes a short presentation or a status update.
A higher signup rate is not automatically a better activation path if the removed step helped users reach a useful workflow. Review the complete sequence and the relevant customer outcome. A bundled product change can be evaluated as a bundle without claiming to isolate every component.
Verification worksheet
| Review item | What to record for this issue | Owner | Evidence |
|---|---|---|---|
| Observed symptom | Referred customers appear both in the referral loop and in the ordinary acquisition total. | ||
| Diagnostic test | Trace the model’s stock and flow definitions and identify overlapping cohorts. | ||
| Proposed correction | Assign each new customer to the intended counting rule and show contribution views separately. | ||
| Guardrail | A referral invitation is not a referred customer until the defined conversion occurs. | ||
| Review measure | Unique acquired customers reconciled across modeled channels |
Download a working copy and follow the worksheet instructions. Keep unknown facts visible rather than filling gaps with guesses.
Decide whether to keep, revise or stop the change
Review unique acquired customers reconciled across modeled channels after the agreed observation period. Keep the correction when the intended behavior is verified and the guardrail remains acceptable. Revise it when the diagnosis was useful but the intervention did not resolve the cause. Stop and reassess when new evidence shows that the original problem was framed incorrectly.
Record what changed in hypothesis, assignment rules, metric definition and decision record. This gives the next review a stable starting point and prevents a definition change from being mistaken for a performance improvement.
Related methods and next steps
- B2B SaaS Growth: The Levers That Move the Model
- SaaS Growth Model: Build the Equation Before Tactics
- Scale SaaS growth after repeatable customer value
- SaaS growth model worksheet
Return to the saas growth topic guide, browse its complete resource collection, or use the working resource library. The primary reference provides relevant platform or methodological context; the diagnosis and example here are original editorial guidance.
Page-specific CSV worksheet
Put this plan to work
Get the worksheet from this page. Add your evidence, owner, status and next decision to each working item.
Frequently asked questions
What is the first diagnostic check?
Trace the model's stock and flow definitions and identify overlapping cohorts. Inspect the actual working record or customer path rather than relying only on a summary report.
What should change after the diagnosis?
Assign each new customer to the intended counting rule and show contribution views separately. Record the owner and the evidence needed to verify the correction.
What limit should the team keep visible?
A referral invitation is not a referred customer until the defined conversion occurs. A local improvement does not establish a universal benchmark or guarantee a commercial result.
How should the correction be evaluated?
Review unique acquired customers reconciled across modeled channels using a consistent unit and observation window. Keep the original evidence and record any measurement changes.
The saas-marketing.net editorial team Research and editorial
We research, write and maintain every page on this site. The library explains marketing decisions through practical frameworks, explicit assumptions and references. Corrections can be requested through the contact page.
Published September 17, 2026. Last updated .