For clubs below the top tier
The same fan data problem as the biggest clubs, with none of the suppliers.
Ticketing, the app, the shop, the gate and the inbox each hold a version of the same supporter. The commercial team sells sponsors a reach number because that is the only number it has. The firms that fix this at the top of the pyramid price for a board that wants risk transfer, and they do not come down the table.
If this sounds familiar
- A record count on the slide that nobody in the room believes is a fan count.
- Consent captured as one tick box, so the legal answer to any new use is no.
- A sponsor asking at renewal which fans the activation reached, and a reach figure in reply.
- An email tool, a ticketing export and a spreadsheet standing in for a fan data platform.
Season one
Prove, release, measure01 · Prove
One supporter across every system you already run, with records per real person as the first number in the board paper. Consent recorded by purpose, so a new use is a check rather than a legal project.
02 · Release
Audiences leave only after the consent, rights and group-size checks run, and they leave through the activation tools you already pay for. Nothing is copied into a new platform.
03 · Measure
One sponsor renewal with a proof report: who was reached, what they did, small groups withheld. The report is the sponsor's board paper as much as yours.
The first move
Pick the one sponsor whose renewal is furthest away and most valuable. Season one is built around that renewal, and everything else follows from it.
Offers that fit
How it is priced- First-Party Readiness DiagnosticThree weeks · Starts here
A budget decision on the fan data estate in the next two quarters.
- Clean Room & Partner MeasurementProject
A sponsor renewal that needs proof of return, not a reach number.
- AI Builder SprintSix weeks · Two-person team
A marketing or fan data workflow everyone complains about and nobody owns.
Built, not described
- The identity graph on a synthetic club
- A release checked at the moment it leaves
- The Club Data Blueprint
The Studio runs on a real backend with a synthetic club, labelled as such. Named properties appear here when they agree to be named.
The usual objection
“We already have a CRM.”
Good. It stays. The platform sits on your own records and uses your CRM and email tools as destinations. The work is identity, consent and proof, and no CRM does those three across a league and a sponsor.
Start here