Growth Loop Referral Architecture Framework

Document Type: Framework
Status: Active
Authority: Conversion Brain
Applies To: Affiliate Brain, Product Brain, AIBS Brain, Content Brain, Partnership Brain
Parent: Conversion Brain Canon
Version: v1.0
Last Reviewed: 2026-04-18


Purpose

The Growth Loop Referral Architecture Framework defines how MWMS structures referral-driven growth loops.

Referral loops can significantly reduce customer acquisition cost and create compounding growth effects.

However, referral behaviour does not occur automatically.

Referral loops must be intentionally designed, tested, and optimised.

This framework provides the structural model for designing repeatable referral systems.

It ensures referral growth is engineered rather than assumed.


Scope

This framework applies to:

Affiliate Brain referral traffic strategy
Product Brain product-led sharing mechanisms
Content Brain shareability design
Partnership Brain collaborative amplification loops
AIBS Brain SaaS referral architecture

This framework governs:

referral loop structure
referral trigger design
referral incentive design
referral conversion measurement
viral coefficient evaluation

This framework does not govern:

affiliate program commission structures
partnership agreement design
creative messaging design

These are governed by related frameworks.


Definition

A referral loop is a reinforcing growth mechanism where existing users introduce new users into the system.

Each new user creates the potential for additional referrals.

Referral loops may produce compounding growth effects when designed effectively.

Referral loops may be:

natural
incentivised
product-driven
affiliate-supported


Core Referral Loop Structure

MWMS uses a four-stage referral loop model.

Step 0 — Value Foundation
Step 1 — Trigger
Step 2 — Sharing Action
Step 3 — Conversion
Step 4 — Reinforcement

Each stage influences loop strength.


Step 0 — Value Foundation

Referral requires perceived value.

Users do not refer products or services lacking meaningful benefit.

Indicators of strong referral foundation:

high satisfaction
strong problem-solution fit
clear benefit communication
repeat usage behaviour
positive feedback indicators

Weak value reduces referral probability.

Referral architecture should not be prioritised before value validation.


Step 1 — Trigger

Referral behaviour often requires prompting.

Triggers create awareness of referral opportunity.

Trigger examples:

post-purchase prompts
milestone celebrations
achievement notifications
satisfaction confirmation
product success moments
community engagement prompts

Trigger timing influences referral participation rate.


Step 2 — Sharing Action

Sharing mechanisms must reduce friction.

Examples:

referral link generation
share buttons
email sharing tools
content embed options
product invite features
community discussion prompts

Ease of sharing increases referral likelihood.


Step 3 — Conversion

Referred users must successfully enter the system.

Conversion depends on:

clarity of value proposition
simplicity of onboarding
perceived trust transfer
relevance of referral context

Referral traffic often converts differently than cold traffic.

Referral conversion metrics should be measured separately where possible.


Step 4 — Reinforcement

Reinforcement encourages repeated referral behaviour.

Reinforcement mechanisms may include:

recognition
incentives
status progression
additional value access
loyalty rewards
community inclusion

Reinforcement strengthens loop sustainability.


Types of Referral Loops

Natural Referral

Occurs without incentives.

Driven by strong product satisfaction.

Example:

word-of-mouth recommendations


Incentivised Referral

Encourages sharing through structured rewards.

Examples:

discount incentives
bonus access
credit rewards
gift rewards

Two-sided incentives often increase participation.


Product-Led Referral

Referral mechanism embedded into product usage.

Example:

inviting collaborators
sharing project links
sharing content output
shared dashboards

Product-led loops often produce strongest compounding effects.


Affiliate-Supported Referral

Referral driven through structured partner incentives.

Examples:

affiliate programs
referral partnerships
creator revenue share models

Affiliate referral loops may complement organic referral loops.


Viral Coefficient Concept

Viral coefficient measures referral strength.

viral coefficient = number of new users generated per existing user

Example:

1 user generates 0.3 new users
viral coefficient = 0.3

Coefficient above 1 may produce exponential growth.

Most referral systems operate below 1 but still provide significant value.


Referral Loop Optimisation Variables

Referral rate

percentage of users referring others

Conversion rate of referred users

percentage of referred users becoming customers

Retention rate of referred users

likelihood referred users remain active

Improving any variable strengthens loop performance.


Referral Loop Measurement KPIs

referral participation rate
referral conversion rate
viral coefficient
share frequency
referral traffic volume
referred customer lifetime value
referred customer retention rate

Measurement supports optimisation prioritisation.


Referral Friction Reduction Principle

Referral behaviour decreases when friction increases.

Common friction sources:

unclear sharing method
complex sharing process
low perceived value
social risk concerns
poor communication clarity

Referral architecture should minimise friction.


Relationship to Growth Model Architecture

Referral loops contribute to:

acquisition efficiency
trust amplification
cost reduction
growth stability

Referral loops often interact with:

content loops
community loops
product loops
affiliate loops

Referral should be integrated within broader growth model structure.


Relationship to Growth Lever Framework

Referral performance constraints may become Growth Levers.

Example:

increase referral participation rate

increase referred conversion rate

increase viral coefficient

Referral optimisation should follow Growth Lever prioritisation logic.


Governance Rule

Referral systems must be intentionally designed.

Referral assumptions must be validated through measurable behaviour.

Referral loop performance should be periodically evaluated.


Version Control

v1.0
Initial definition of referral loop architecture structure for MWMS growth systems.