Skip to main content
FanSignal OS
Demo
Solution Guide

CRM & Lifecycle

Fan journeys that close the revenue loop

Platform Walkthrough →← All Solution Guides

Primary Business Challenges

  • 01Journeys built on calendar logic send the same message to lapsed fans and engaged fans
  • 02Win-back campaigns launch after the fan has already left, not while there's still time to act
  • 03CRM enrollment is based on lists, not lifecycle stage transitions
  • 04Revenue attribution from CRM is a guess at the end of the season, not a design constraint
  • 05There is no closed loop between journey performance and segmentation: the list doesn't update when a fan's behavior changes

Typical Executive Questions

  • Q1How do you decide when to trigger a win-back journey versus suppressing a fan who's truly gone?
  • Q2How do you structure attribution when one fan touches five journeys before converting?
  • Q3Walk me through the data model behind your most successful retention campaign.
  • Q4How do you handle journey conflicts: what happens when a fan is eligible for three journeys simultaneously?
  • Q5Describe how you'd measure the impact of a CRM program on renewal rate.

Discovery Questions

  • 01What's currently driving journey enrollment: a list export, a behavioral trigger, or a manual decision?
  • 02How do you handle suppress logic today, is there a suppression model, or does every eligible fan get enrolled?
  • 03Where does revenue attribution live, and how confident is the team in those numbers?
  • 04What's the relationship between your CRM team and your data/analytics team, are journeys informed by behavioral data?
  • 05How does content get aligned to lifecycle stage, or does that connection not exist yet?

Suggested Demonstration Flow

  1. 01Fan Lifecycle: show stage model and walk through how a stage transition triggers journey enrollment
  2. 02Personas: walk one persona's LTV arc and explain what CRM investment thesis it generates
  3. 03CRM Automation: show journey architecture, enrollment logic, and revenue attribution summary
  4. 04Fan Bot: show how intent classification from a bot conversation becomes a CRM trigger
  5. 05Content Pipeline: show how a content brief maps to a lifecycle stage and tracks back to revenue

Key Takeaways

  • “Lifecycle stage drives every campaign decision. Sending the same renewal offer to a lapsed fan and an engaged fan is how you train fans to ignore your emails.”
  • “Attribution is a design constraint, not a reporting layer. If you don't trace revenue from the journey structure, you can't attribute it at the end of the season.”
  • “The CRM isn't the system of record in this platform: the lifecycle model is. The CRM executes what lifecycle intelligence recommends. That's the inversion that matters.”
  • “Win-back campaigns only work when you know why the fan lapsed. This platform tracks the signal that triggered the lapse, not just that they lapsed.”

Relevant Architecture Decisions

  • →Stage transition as the enrollment event, not a calendar trigger or a manual list refresh
  • →Signal-driven suppression logic built into the journey model alongside enrollment logic
  • →Attribution tracing from journey enrollment through conversion with named source signals
  • →Persona-differentiated journey tracks: the same journey name has different content and cadence per segment
  • →Bot intent classification as a structured CRM input, not a freeform conversation log

Recommended Follow-Up Demo

Open CRM Automation and walk through the win-back journey from trigger signal to enrolled fan count to attributed revenue. Then switch to Fan Lifecycle and show the churn risk flag that would have enrolled that fan. End on Personas to show how the investment thesis changes by segment, and therefore how the journey content should too.

Platform Walkthrough →← All Solution Guides

Coming Soon: data pipeline in progress · FanSignal OS