Turning a community into a growth engine.
Referral, velocity, repeat
Split out from paid and organic
No more one-and-done guessing
The problem.
Everyone agreed the community was the engine, but the reporting could not prove it. Referral and UGC-driven sales were blended into "organic," so the team could not tell whether a viral moment actually converted, which heroes the community pulled hardest, or whether new buyers came back. Paid got the credit because paid was the only thing measured cleanly.
The approach.
I separated community-driven revenue from paid and organic, then built three views around it: a community engine that tracks referral and UGC revenue against blended CAC, a product-velocity view that ranks heroes by real demand pull, and a repeat-behavior view with a proper cohort curve. One definition per metric, refreshed on a single screen.
The outcome.
Community stopped being a vibe and became a number the team can grow on purpose. Leadership can see how much revenue referrals and UGC actually drive, which heroes to lean into, and how well new buyers retain, so budget shifts toward the channel that was quietly doing the heavy lifting.
Explore the dashboard.
INTERACTIVE SAMPLE · Illustrative data, not client figures. Switch tabs for the community engine, product velocity, and repeat behavior.
If referrals and word of mouth are your real engine but never show up in a report, I will make them measurable on one screen. One slot open for Q3 2026.