# Ring for Analysis: Liverpool's Multi-Club Confusion Page: https://stenobird.com/podcast/tifo-football-podcast-539882/ring-for-analysis-liverpool-s-multi-club-confusion Text version: https://stenobird.com/podcast/tifo-football-podcast-539882/ring-for-analysis-liverpool-s-multi-club-confusion.md Podcast: [Tifo Football Podcast](https://stenobird.com/podcast/tifo-football-podcast-539882) Published: 2026-03-27T05:00:00+00:00 Episode link: https://shows.acast.com/tifo-football-podcast/episodes/ring-for-analysis-liverpools-multi-club-confusion Audio file: https://sphinx.acast.com/p/open/s/681cccd63e6644d7a3b3065c/e/69c5bb08786da3955dae583e/media.mp3 Processing state: not_requested JSON: https://stenobird.com/v1/public/podcasts/tifo-football-podcast-539882/episodes/ring-for-analysis-liverpool-s-multi-club-confusion Duration seconds: 3587 ## Resource Two years ago, when Michael Edwards re-joined Liverpool to become CEO of Football for FSG, he did so with the recommendation that the American ownership group seek to expand their football portfolio and explore a multi-club model. But today, it seems unlikely that FSG will follow through on this expectation. On today's episode, Joe & Jon perform Ring for Analysis, while reading through James Pearce's story on this topic, discussing what this means for Liverpool, FSG and Michael Edwards' future. https://www.nytimes.com/athletic/7125072/2026/03/20/liverpool-fsg-michael-edwards-future/ Join the discord! https://discord.gg/CGVn8crYYa Hosted on Acast. See acast.com/privacy for more information. ## Actions - request_transcript: `POST https://stenobird.com/v1/public/podcasts/tifo-football-podcast-539882/episodes/ring-for-analysis-liverpool-s-multi-club-confusion/transcription-requests` — Idempotently request low-priority transcript generation for this episode. - read_markdown: `GET https://stenobird.com/podcast/tifo-football-podcast-539882/ring-for-analysis-liverpool-s-multi-club-confusion.md` — Read the agent-friendly Markdown representation of this episode resource. A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed. ## Transcript Full transcripts are not published on public pages unless there is a clear rights basis.