Buyer guide · Updated August 2026

Football club CRM and fan data platforms

A practical framework for clubs trying to create a useful supporter view across ticketing, membership, retail, content and service.

For CRM, data, marketing and commercial leaders10 minute readNo vendor paid for inclusion

01 · Decision framing

Do not start by buying “a single customer view.”

A unified profile is only valuable when it changes a decision or workflow. Start with specific jobs: resolving a supporter enquiry, identifying likely non-renewals, valuing a partner audience or suppressing contacts without the right consent.

First question

Which five decisions should become faster, safer or more profitable when supporter data is connected?

02 · Architecture

CRM, CDP and service platforms solve different problems.

Operational CRMAct

Manages accounts, opportunities, cases, tasks and contact-centre workflows. It is often the system employees work in.

Customer data platformUnify

Collects events and profiles, resolves identities and builds audiences for activation across other systems.

Engagement platformCommunicate

Orchestrates email, mobile, web and other campaigns using audiences, behaviours and rules.

Analytics environmentMeasure

Combines operational and commercial data for reporting, modelling, experimentation and decision support.

03 · Evaluation framework

Six areas to settle before procurement.

01

Identity model

Decide how one supporter is resolved across ticketing, retail, membership, hospitality, apps and anonymous digital activity.

02

Source-system reality

Inventory the fields, identifiers, consent states, update frequency and ownership of every system before designing a target architecture.

03

Activation speed

Test how long it takes a normal user to build an audience, suppress ineligible contacts and launch a measurable campaign.

04

Service workflow

Separate marketing personalisation from supporter service. Some clubs need CRM cases and contact-centre history as urgently as campaign tooling.

05

Consent and governance

Model lawful basis, preference centres, retention, deletion, access controls and cross-border processing as product requirements.

06

Value measurement

Agree the decisions the platform should improve: renewal, attendance, conversion, partner value, service resolution or lifetime value.

04 · Observed deployments

What the ten-club research set shows.

The dataset contains different operating models rather than one universal stack: Salesforce-based CRM and service at Tottenham, Barcelona and Dortmund; Twilio Segment at Chelsea; SAS at Liverpool; Qloo cultural intelligence at Barcelona; KAGR's data programme at AC Milan; and Adobe-led experience systems at Bayern and Real Madrid.

These are deployment signals, not product endorsements. Scope, implementation quality, data governance and current contract status still need to be verified.

Customer dataMultiple models

Segment, SAS, Qloo and KAGR illustrate CDP, campaign, enrichment and strategy-led approaches.

Explore the evidence →

05 · Shortlist tool

A scorecard tied to operating value.

AreaSuggested weightEvidence to request
Identity and data quality25%

Live match-and-merge test using club records

Activation and service workflows20%

End-to-end user scenarios, not slides

Governance and security20%

Consent, retention, access and audit controls

Integration and portability15%

API, export and deletion tests

Measurement and analytics10%

Attribution and decision-use cases

Five-year cost and exit10%

Licences, profiles, events, service and migration

Score the operating model, implementation partner and internal readiness alongside the product. Technology cannot repair unclear ownership or unusable source data.