Disclosed partners
Independent of every vendor. Here is every vendor.
Independence is a claim that only means something if it can be checked. This page lists what the practice and its platform run with, what each relationship is, and the rules that govern all of them. It is the only page on this site where vendors are named.
The rules
No referral fees
I am not paid by any vendor for a recommendation, an introduction or a sale, and I do not co-sell.
Disclosed advisory
Where I advise a vendor on its product, it is disclosed in writing to that vendor and to any client. I never advise a property on a choice where that vendor is in the running.
The platform is a product, and it says so
Where my own platform could be an answer to a client's question, it is never on a shortlist in a selection I am paid to run. The client is told that in writing before the selection starts.
Named when real
A partner appears on this page when something is connected, signed or in writing. Conversations in progress are described, not named.
Connected or in use
Current facts, kept current-
Hightouch
Activation
Connected in the Studio demonstration
Reads the released audience views from the Studio database through a read-only login and carries them to its destinations on a schedule. It sees released views only and writes nothing back. The pattern a property's own activation tool follows.
-
Google Ads and Meta
Destinations
Formats supported
Released audiences are produced as hashed identifiers in the formats these platforms accept for customer matching. Delivery to either runs through the property's activation tool or the sponsor's own account, never direct from the Studio.
-
Supabase (Postgres)
The demonstration backend
In use
The Studio runs on a Postgres database with row-level tenancy, the consent ledger, the rights matrix and the release functions. A real deployment runs the same SQL on the property's own database or cloud account.
-
Anthropic (Claude)
Build tooling
In use
The Studio and the practice site are built with AI coding agents. The release checks and the evaluation checks are tested the same way, against the live deployment.
In conversation
Described, not named, until agreed- A ticketing and membership platform used by clubs and leagues below the top tier, as a supply partner: it holds the record, the kit enforces consent and rights at release and proves cross-club and sponsor audiences.
- A brand-side activation platform, to agree lanes: the rights-holder side is mine, the brand side is theirs, and a sponsor's audience lands in their instance without raw fan data moving.
- An identity partner for the sponsor-side match, where the sponsor already runs its own clean room.
- Clean-room compute on the property's existing cloud account, so the federated match runs where the data already lives.
For vendors