The deployment kit
Everything a deployment contains, and everything it does not.
A deployment is working code on the property's own records, not a slide about it. Each part below is running today in the Studio on a synthetic club, with the same rules a real deployment uses. Open any of them and try to break it.
What is in the kit
Each part links to its live module01
The identity spine
Keys from ticketing, the app, the shop, the gate, streaming and email resolved to one person, with the rule for each key written down and the duplication number reported, not hidden.
Identity graph02
Consent by purpose
A ledger, not a tick box. Marketing email, push, partner offers, audience extension and profiling are separate purposes with separate states, and the latest state wins at the moment of use.
Consent gate03
The rights matrix
Who may ask which question of whose records: a league of its clubs, a club of its sponsors, a sponsor of the club. A rival asking is refused by the rules, and every refusal is logged.
The match refusing a rival04
Release checks
Every export runs the rights check, the consent check and the minimum group size before a hashed identifier leaves, and writes a run record that says who was excluded and why.
Export by purpose05
Activation through what you have
Released audiences appear in a read-only schema that the property's activation tool reads and carries to its destinations. The tool sees the released views and nothing else, and writes nothing back.
Activate06
Sponsor proof
The two-party match with k-anonymity: fans reached, matched to outcomes, with small groups withheld and no records pooled between the parties. The output is a report both boards can read.
Lift measurement07
The board scoreboard
Records per real person, known-fan share, marketable consent, over-communication stopped, time to audience and partner-attributed spend, each with a direction and a target.
Scoreboard08
Evaluation checks
A standing set of checks that run against the live deployment: a rival is refused, a withdrawn consent drops out of the next release, no raw key reaches a partner view, small groups stay withheld. Results are published, not promised.
Evaluation resultsWhat you provide
Nothing complexExports, not access
A periodic export from ticketing, membership, the shop and the app. No system is replaced and no fan record leaves your environment unhashed.
One owner
A commercial or data lead who can decide, and a legal contact for the data terms. Half a day a week for the first weeks, less after.
One sponsor
A renewal to build the proof around. The sponsor needs to bring its own outcome data or agree to a matched measure; either works.
Your activation tool
Whatever already carries audiences to email, push or the ad platforms. If there is none, a free tier of a warehouse-native tool is enough for season one.
How a season runs
Assess, build, run- Weeks one and two Assess. Exports in, keys mapped, duplication measured, consent states classified, the sponsor renewal chosen.
- Weeks three to six Build. Identity rules, the consent ledger, the rights matrix and the release checks stood up on the property's own records. First release to the activation tool.
- The rest of the season Run. Releases on a schedule, the scoreboard in the board pack, the match run for the chosen sponsor, the proof report delivered before the renewal meeting.
Weeks, not quarters, because the hard part is already built and the property's part is an export and a decision. A property with a clean ticketing export and one willing sponsor has seen its first release inside the first month.
Deliberately not included
- A new CRM, email tool or app. The kit sits on what you have.
- A mobile app, a content platform or a ticketing system.
- Direct integrations to ad networks. Those run through your activation tool or the sponsor's own seat.
- A proprietary identity graph. Your keys, your rules, written down and yours to take away.
The two rules
Consent is enforced at the moment of use, not at collection. Every release checks purpose and lawful basis when it runs. It is the first question a data protection officer asks, and almost nobody builds it this way.
Your records never leave your environment unhashed. The kit runs on the property's own database or cloud account. Partners read released views; nobody receives a copy of the fan table.
The tools and partners it runs withStart here