Acquisition growth loops need a declared entry event

A growth loop is not a circle on a strategy slide. This article uses the term for an acquisition or referral loop: a sequence of events with a declared entry rule and a visible next-entry condition.

A measurable acquisition growth loop runs from an eligible entry unit through participant action, transfer, received value, next-entry eligibility, reward or cost, and an outcome window. In this article, the next eligible unit is a distinct recipient or other unit outside the declared starting population. If the arrow returns to the beginning but no new eligible unit is recorded, the diagram describes an aspiration rather than an auditable acquisition mechanism.

This distinction protects the useful idea in the loop. It also prevents a referral, a reward, or a second purchase from being counted as proof of compounding growth.

What is a growth loop?

A growth loop is a declared mechanism in which an outcome from one participant can create or expose an eligible entry for the next iteration. This article intentionally uses the narrower acquisition and referral class: the next entry is a distinct user, account, buyer, invited contact, partner, or content recipient outside the starting population. The entry event might be activation, a referral invitation, a shared asset, a purchase, or another observable event. Retention, usage, and expansion loops can reuse the same user or account and need a different identity and state rule; they are outside this article’s scope.

The loop needs at least six boundaries:

• the eligible entry population and unit identity;
• the participant action;
• the transfer event;
• the received or accepted value;
• the event that makes the distinct next unit eligible; and
• the cost and outcome window.

The growth-accounting article owns the bridge between new, retained, expanded, and lost revenue. This page owns the acquisition event sequence that might generate a new eligible unit before the revenue bridge is evaluated.

Why is a funnel not enough?

A funnel counts units at states. An acquisition loop claims a transfer from one iteration to the next. The funnel can show that 100 users are active and 20 referrals were recorded. It cannot tell you whether those 20 referrals reached a new person, whether that person became eligible, or whether the same unit was counted again.

The loop therefore requires an identity and time rule. A referral event is not automatically a new eligible unit. A share is not automatically a received impression. An activated user is not automatically a paying customer. The record must state which event crosses the boundary.

What does research say about referrals and relationship conditions?

Biyalogorsky et al. (2001)¹ model customer referral management through reward programs. Their result is conditional on the economic and behavioural assumptions of the model. Rewards can be profitable under some conditions, but the analysis leaves room for free riding and reward misallocation. It is not a universal referral rate or viral coefficient.

Morgan and Hunt (1994)⁴ identify commitment and trust as key mediating variables in their relationship-marketing model. Their model was tested cross-sectionally with automobile tire retailers, so the setting and single-point design limit transfer to another market or time horizon. That gives a useful mechanism boundary: a relationship condition can make cooperation or referral more plausible, but it does not prove that every customer will refer or that a proposed loop will compound.

Kumar et al. (2010)³ distinguish customer engagement value beyond transactions through customer lifetime, referral, influencer, and knowledge components. A transaction-only view can therefore undervalue or overvalue a customer when those non-transactional contributions matter. The framework is a valuation lens, not a universal loop multiplier.

Villanueva et al. (2008)⁵ compare marketing-induced and word-of-mouth acquisition across speed, cost, and customer-equity paths in a bounded setting. Their web-hosting evidence reports different short-term and long-term value paths for the two acquisition sources. The setting and horizon stay attached to the result; it is not a universal paid-versus-word-of-mouth ratio.

Which fields belong in an acquisition growth-loop ledger?

The table is an acquisition and referral example. A retention, usage, or expansion loop would need a different identity and state contract rather than silently reusing this new-recipient ledger.

Loop element	Evidence field	Synthetic example	Next-entry rule	Failure mode
Entry event	Eligible unit, entry date, and inclusion rule	100 active paying users at period start	Active means paid and used under the declared period	Trial and paid units are mixed
Participant action	Named action and actor	32 users send a direct invitation	Invitation is recorded once per recipient	Button clicks are treated as transfers
Transfer	Recipient identity and delivery event	20 invitations reach new recipients	Recipient is outside the starting population	Existing users are counted as new units
Received value	Acceptance or first-value event	12 recipients accept the invitation	Acceptance rule is timestamped	Delivered message is called value
Next eligibility	Event that admits the next distinct unit	8 recipients pay and activate	Recipient is deduplicated and qualifies within 30 days	Eligibility has no time boundary
Reward or cost	Incentive, channel, and cost	EUR 160 in rewards and delivery cost	Cost is assigned to the loop period	Reward is called free
Outcome	Contribution, retention, or later value	30-day outcome remains unresolved	Outcome window closes before interpretation	Loop conversion is called payback

The example is deliberately unresolved at the outcome row. Eight recipients became eligible within the illustrative window, but that does not tell us whether they stayed, generated contribution, or would have arrived without the loop. That is the difference between recording a mechanism and proving its economics.

When does a referral become a new loop entry?

A referral becomes a new loop entry only when the recipient crosses the declared eligibility rule. For example, a team might define eligibility as a new account that receives an invitation, accepts a declared value event, and starts a paid plan within 30 days. Another team might use a qualified opportunity or a verified partner introduction. Both can be valid. They are not the same numerator.

The ledger should therefore keep these events apart:

• invitation or referral created;
• delivery or receipt confirmed;
• first value or acceptance observed;
• payment, qualification, or activation recorded;
• exclusion, duplicate, or pre-existing relationship identified; and
• downstream outcome observed at the declared horizon.

For this acquisition loop, a referral becomes a next entry only when the recipient is a distinct, deduplicated unit outside the starting population and crosses the declared rule. A retention or usage loop would instead need a different identity relation and is not measured by this article’s formula. This is why a referral rate is not a loop-conversion rate. The former may count actions per participant. The latter counts eligible entrants that reach the next defined acquisition-loop state under a named window.

How should reward and value be treated?

A reward is an incentive and a cost. The cost may include the reward itself, delivery, sales support, fraud review, service effort, or another declared resource. If the record only says “rewarded,” the economic boundary is incomplete.

The same applies to value. Paid acquisition, referral, influencer, knowledge, retention, and customer lifetime contributions can all matter to customer economics. They should remain separate until the decision names why aggregation is appropriate.

The partner-led growth article owns partner-motion selection, and the customer-selection article owns the allocation of scarce commercial capacity. A growth loop can generate an input to either decision. It does not decide the allocation on its own.

What is the growth-loop formula, and how should it be calculated?

Declare the denominator first. A bounded descriptive convention is:

loop conversion = entrants with at least one qualifying next entry within the window / eligible loop entrants

Each eligible entrant is counted at most once in this numerator, so the conversion is bounded from 0 to 100 percent. The next entry must be a distinct, deduplicated unit under the same unit, period, and exclusion rules. When one entrant can create multiple qualifying units, report a separate output-yield metric:

next-entry yield = deduplicated qualifying next-entry units / eligible loop entrants

Yield can exceed 100 percent because it counts output units rather than entrants with at least one output. A team may also report transfer rate, acceptance rate, time to next entry, reward cost per eligible entry, and later contribution. These are different metrics.

In the synthetic ledger, suppose eight of 100 starting users each produce at least one qualifying next entry and eight distinct recipients qualify. The illustrative loop conversion is 8%, and the yield is also 8%, or 0.08 qualifying units per entrant, because this example has one output per converting entrant. If those same eight entrants produce 20 distinct recipients, conversion remains 8% while yield becomes 20%, or 0.20 units per entrant. Neither value is a benchmark or proof that the next iteration will reproduce the output, because the next population, cost, and outcome have not been observed.

What data do growth loops require?

The formula is reproducible only when the records keep the same unit, population, period, and exclusion rules from entry to outcome. A useful minimum dictionary is:

Data object	Minimum record	Why it matters
Loop and unit identity	Loop version, entrant ID, unit type, recipient ID, and starting population	Prevents accounts, users, contacts, and recipients from being mixed.
Entry	Entry event, timestamp, eligibility rule, source, and cohort	Fixes the denominator and the starting period.
Action and transfer	Actor, action, channel, recipient, delivery, and acceptance event	Separates an attempted action from a received output.
Next-entry eligibility	Qualifying event, deduplication key, exclusion reason, and window close	Makes the numerator auditable and prevents existing units being counted as new.
Reward and cost	Incentive, channel, service effort, payer, amount, currency, and cost date	Keeps an output or reward from being mistaken for free growth.
Outcome	Outcome event, comparison, contribution or margin field, and outcome horizon	Keeps later value separate from the entry event and from causal interpretation.
Governance	Schema version, permission status, owner, reviewer, and review date	Makes changes and unresolved fields visible over time.

At minimum, the formula needs three reconciled counts: eligible loop entrants, entrants with at least one qualifying next entry, and deduplicated qualifying next-entry units. Store those counts under the same boundary, while retaining the event records that let another reviewer reconstruct them. A dashboard containing only referrals, clicks, or conversions is not a complete growth-loop dataset until identity, eligibility, exclusions, costs, and the outcome window are also present.

How should a team interpret a growth loop?

Read a loop as a chain of declared states. The diagram is useful only when each arrow names the event, unit, receiver, boundary, and next-entry rule that it represents.

Observed signal	Reading allowed	Next inspection	Interpretation not allowed
Participant action	A named participant performed a recorded action.	Identity, eligibility, and time.	That the action created demand.
Transfer	A recipient or channel received the output.	Acceptance, duplication, and ownership.	That the recipient converted.
Next-entry eligibility	A distinct unit meets the declared entry rule.	Population boundary and exclusion rule.	That the loop compounds automatically.
Reward or cost	A declared incentive or channel cost was incurred.	Payer, timing, and cost grain.	That reward caused referral or profit.
Outcome	A later state was observed in the declared window.	Comparison, margin, and horizon.	That the loop caused the outcome.

The source set supports bounded readings of referral rewards, commitment and trust, engagement value, and word-of-mouth acquisition. It does not turn those constructs into one universal growth-loop score.

Why do growth loops fail?

A loop can fail at the entry, transfer, eligibility, value, cost, or outcome boundary. Failure diagnosis should name the missing state instead of treating a lower output as evidence that the entire mechanism is wrong.

Failure pattern	Boundary to inspect	Evidence to retain	Safe disposition
Action recorded, no recipient	Transfer	Participant, event, channel, and timestamp	Keep as participant activity.
Recipient reached, no acceptance	Value or acceptance	Delivery, receiver, response, and reason	Hold the next entry.
Many outputs from one source	Eligibility and identity	Source unit, recipient identity, and deduplication key	Separate yield from unique entry.
Reward paid, no later state	Cost and outcome	Reward, cost, outcome window, and comparison	Report spend without claiming lift.
New entries arrive outside the rule	Population boundary	Entry definition, exclusions, and source	Reclassify or reject the entry.
Outcome changes after a campaign	Comparison and horizon	Exposure, comparison, timing, and alternatives	Preserve association only.

Biyalogorsky, Gerstner, and Libai model referral rewards under their stated assumptions. Morgan and Hunt⁴ connect commitment and trust to relationship marketing. Kumar and colleagues³ separate components of customer engagement value, while Villanueva and colleagues⁵ compare acquisition sources in a bounded customer-equity setting. These sources help locate failure boundaries, not diagnose a universal loop coefficient or causal effect.

How can a team improve a growth loop?

Improve one transition at a time and keep the loop’s identity stable while the change is reviewed.

1. Freeze the entry unit, event, population, and time window.
2. Find the first missing or ambiguous state in the ledger.
3. Change one transfer, eligibility, value, reward, or follow-up rule.
4. Record owner, version, cost, and expected next state.
5. Compare the declared path with a valid comparison before discussing effect.
6. Retire the change when disconfirming evidence breaks the stated mechanism.

This is an author operating sequence. It improves inspectability, but it does not assert that any one intervention improves referrals, conversion, margin, or compounding.

How should a growth loop be read by cohort and customer segment?

A cohort fixes when and how an entry began. A segment fixes a declared characteristic of the unit or context. Keeping the two views separate prevents a mix of populations from appearing to be a mechanism.

View	Fixed boundary	Useful question	Required caution
Entry cohort	First qualifying entry and date	Do later transfers or outcomes differ by starting cohort?	Later cohorts may have different exposure or rules.
Source cohort	Referrer, channel, or originating unit	Which source produces eligible recipients?	Yield is not unique acquisition.
Account segment	Named account or customer characteristic	Does acceptance or cost differ by segment?	Segment labels do not prove fit or profit.
Recipient cohort	Recipient type and first-entry date	Which recipients become eligible participants?	The recipient may remain outside the next-entry rule.

The slice is an analysis boundary. It is not a universal taxonomy of growth loops and cannot replace an outcome comparison.

What remains human when AI enters a growth loop?

AI can cluster referral events, flag a possible duplicate, suggest a recipient segment, or summarize a loop ledger. Jarrahi (2018)² describes human-AI work as complementary: analytical processing can sit beside human context, judgment, and responsibility. An AI suggestion therefore remains a candidate record until a person confirms the unit, eligibility rule, value, and permitted action.

Candidate AI contribution	Human responsibility	Minimum record
Cluster actions or sources	Confirm meaning, unit, and source boundary.	Event, version, cohort, and reviewer.
Flag a possible next entry	Check identity, exclusions, and timing.	Eligibility rule, evidence, and disposition.
Suggest a reward or message	Check relationship context, cost, and permission.	Recommendation, override, cost, and rationale.
Detect a break in the loop	Validate transfer, acceptance, and value context.	Break type, source record, and next state.
Summarize outcomes	Check denominator, comparison, and uncertainty.	Source records, summary version, and sign-off.

Jarrahi supports complementarity and responsibility, not an AI performance result or a claim that AI improves growth loops.

How should finance connect growth loops to the P&L?

Finance should receive a bridge from loop exposure to declared costs and outcomes. A referral or new entry is not revenue merely because it appears after a participant action.

Bridge object	Commercial question	Financial field	Boundary failure
Exposure	Which units saw or received the loop action?	Eligible population and delivery cost.	Exposure is treated as value.
Transfer	Which output was delivered and accepted?	Channel, reward, service, and support cost.	Delivery is treated as revenue.
New entry	Which distinct unit met the entry rule?	Acquisition cost and timing.	Entry is treated as incremental revenue.
Outcome	What changed under which comparison?	Revenue, margin, retention, or cash line.	Association is called causal lift.
Timing	When should the outcome be recognized?	Recognition, collection, and review dates.	A later outcome is assigned to the loop without a horizon.

This is an author finance framework. It does not report a universal return, payback period, or causal growth result.

How should growth-loop governance work?

Governance should version the entry rule and the evidence boundary before the loop becomes a target.

Governance object	Local control	Accountable owner	Escalation trigger
Entry rule	Unit, population, event, and window are versioned.	Growth or analytics owner.	Eligibility changes mid-period.
Transfer	Receiver, acceptance, and permission are recorded.	Channel or commercial owner.	Output has no receiving owner.
Reward and cost	Payer, amount, timing, and cost grain are recorded.	Finance or program owner.	Reward is counted without cost.
Outcome	Comparison, result, margin, and horizon are named.	Evidence owner.	Post-action movement is called causal.
Review	Disconfirmation, decision, and retirement date are logged.	Governance owner.	A failed assumption remains active.

These are local controls, not industry standards. A declared rule should trigger review within its own scope and never become a universal referral benchmark.

What counts as evidence for a growth-loop decision?

Evidence must match the decision. A ledger can show that an event happened. A comparison can show that two paths differ. A causal claim needs a design that addresses selection, timing, and alternative explanations.

Evidence type	It can support	It cannot support alone	Minimum fields
Descriptive	An action, transfer, cost, or state was observed.	Demand, profit, or causality.	Unit, event, period, and source.
Comparative	Two declared paths differ.	That the loop caused the difference.	Eligibility, comparison, timing, and uncertainty.
Causal	A specified effect under a defensible design.	A universal loop coefficient or growth result.	Exposure, comparison, outcome, horizon, and assumptions.
Delivery	The promised referral or transfer path was delivered.	That delivery created revenue.	Promise, recipient, workflow, reviewer, and date.

The evidence taxonomy is an author framework. It keeps source, population, loop boundary, outcome, and decision together without turning a diagram into validated causal evidence.

What should a growth-loop checklist preserve?

Before a team names a loop result, the checklist should preserve:

• the entry unit, event, eligible population, exclusions, and window;
• participant action, transfer, receiver, acceptance, and next-entry rule;
• recipient identity, deduplication key, cohort, and segment;
• reward, channel, service cost, payer, and timing;
• source, comparison, outcome, margin, horizon, and uncertainty; and
• owner, version, disconfirmation, decision, and review date.

What does a growth-loop diagram not prove?

A diagram does not prove causal growth, profitability, payback, retention, or self-sustaining demand. The referral model may depend on assumptions that do not hold in the new setting. Trust may be absent. The recipient may already be exposed through another channel. The reward may attract low-value or duplicate units. The apparent next entry may be a measurement artifact.

To claim causal growth, specify the intervention, eligible population, counterfactual or comparison, outcome, attribution rule, and horizon. To claim payback, add contribution, cost, cash timing, and a recovery rule. A loop is a hypothesis about a mechanism until those tests are done.

How should a team run a loop test?

Choose one loop and one period. Version the entry rule before the test. Then record:

1. who was eligible at entry;
2. what action was taken and by whom;
3. what transfer event was observed;
4. which distinct recipient crossed the next-entry rule;
5. what reward and channel cost were incurred;
6. what exclusions or duplicates were removed; and
7. which contribution, retention, or customer-value outcome remains open.

Review the ledger after the outcome window closes. If the loop cannot identify the next distinct eligible unit, keep it as a campaign or referral activity, not as a measured growth loop. If it can identify the unit but not the outcome, keep the mechanism and mark the economics unresolved.

The defensible conclusion is narrow: a growth loop is a declared event sequence, not a circular arrow. Its credibility comes from a visible entry population, transfer event, next-entry rule, cost, and outcome horizon. Measure the mechanism first, then test whether it creates value relative to a credible comparison.

References

1. Biyalogorsky, E., Gerstner, E., & Libai, B. (2001). Customer referral management: Optimal reward programs. Marketing Science, 20(1), 82–95. https://doi.org/10.1287/mksc.20.1.82.10195
2. Jarrahi, M. H. (2018). Artificial intelligence and the future of work: Human-AI symbiosis in organizational decision making. Business Horizons, 61(4), 577-586. https://doi.org/10.1016/j.bushor.2018.03.007
3. Kumar, V., Aksoy, L., Donkers, B., Venkatesan, R., Wiesel, T., & Tillmanns, S. (2010). Undervalued or overvalued customers: Capturing total customer engagement value. Journal of Service Research, 13(3), 297–310. https://doi.org/10.1177/1094670510375602
4. Morgan, R. M., & Hunt, S. D. (1994). The commitment-trust theory of relationship marketing. Journal of Marketing, 58(3), 20–38. https://doi.org/10.2307/1252308
5. Villanueva, J., Yoo, S., & Hanssens, D. M. (2008). The impact of marketing-induced versus word-of-mouth customer acquisition on customer equity. Journal of Marketing Research, 45(1), 48–69. https://doi.org/10.1509/jmkr.45.1.48