Practical guide

Who should pay for an agency-managed podcast?

Last materially reviewed 2026-09-19

Quick answerDecide who owns the continuing relationship before deciding whose card pays the hosting bill.
What to know

Separate service from ownership

An agency can produce a programme without owning the client’s hosting account. Alternatively, it may manage several shows centrally under an agreed service arrangement. These are different models with different handoff responsibilities. Do not allow the easiest initial payment method to decide the long-term ownership structure by accident. Discuss the intended end state while the relationship is straightforward, not during a rushed departure.

What to know

Write the responsibilities plainly

Record who approves spending, receives billing notices, controls directory accounts and authorizes a transfer. Keep credentials out of the document. Make sure the person paying knows whether the charge covers hosting alone or a bundle of production services. This guide is an operational worksheet, not a contract template or legal advice; material commercial terms should be reviewed through the appropriate process.

What to know

Plan for a missed payment

Ask how the show continues if a client invoice is late or an agency payment method fails. Avoid promising a technical grace period that has not been verified. Decide who receives the first alert and what information they need to resolve it. A public feed can remain a client asset even when the agency’s service relationship is ending, so payment and transfer discussions should not be conflated carelessly.

What to know

Make the exit unsurprising

Define the supported transfer path and who will establish the receiving account when needed. Preserve source media, directory references and a dated list of current responsibilities. If central billing delivers real administrative value, explain that value openly rather than using inaccessible ownership as a retention tactic. A good arrangement is one both parties can understand while working together and one they can unwind without reconstructing the show’s history from scattered messages.

Continue when useful

Next: Podcast RSS ownership: know what you control

The audio file, hosting account, feed address and directory listing are separate pieces of control.

Open Podcast RSS ownership: know what you control →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Transistor for agencies: account responsibility — Merchant documentation · transistor.fm · Merchant-controlled · checked 2026-09-19
  2. Transistor show-level ownership transfer — Merchant documentation · support.transistor.fm · Merchant-controlled · checked 2026-09-19