How podcast networks pay remote editors and producers: rates, rights and one weekly batch

Key takeaways

· A network running several weekly shows pays a distributed crew — an editor, a producer, a show-notes writer, sometimes a co-host — and the roles rarely share one pay structure.

· A flat per-episode fee suits editing and show notes, where the output is countable; a monthly retainer suits a producer's ongoing availability. Past four or five shows a week, most networks run both at once.

· The agreement needs a separate line for who owns the finished episode, the raw project files and the show notes once the invoice is paid. That's a different clause from the fee itself.

· Six weekly shows can generate more than a dozen small invoices across as many countries and currencies every week. The practical fix is one weekly payment run instead of a dozen separate transfers.

A network publishing six shows a week rarely has six in-house teams behind them. More often it has six editors scattered from Manila to Lisbon, two or three producers each running three shows apiece, and a show-notes writer turning a ninety-minute recording into a description, timestamps and a handful of pull quotes before the episode drops. None of them are on staff, none share an office, and most overlap with the host's own working hours for only a couple of hours a day. Each is paid for a deliverable — a mixed episode, a booked and briefed guest, a published show-notes page — on a schedule that has nothing to do with a payroll calendar.

Multiply that crew by six shows a week and the finance side of the operation is a dozen or more small invoices, in as many currencies, arriving on different days. Some networks handle that the way they'd handle any vendor bill: one transfer per invoice. Others put the whole roster under one contractor agreement and one weekly payment run, using a contractor platform such as 4dev.com instead of opening a new international transfer every time an editor submits one.

The remote podcast crew and who does what

Four roles show up on almost every distributed podcast operation, though not every show uses all four.

· Editor. Takes the raw recording, cuts dead air and mistakes, balances levels between hosts recorded on different microphones, and exports a broadcast-ready file. Paid per episode almost everywhere, because the deliverable is one file per episode and the time it takes tracks how clean the raw recording was.

· Producer. Books guests, sends pre-interview briefs, keeps a rundown so the host isn't improvising the whole episode, and often does a first pass of fact-checking on anything a guest claims on air. A producer is paid for ongoing availability — booking next month's guests while this week's episode is still in editing — so retainers are the more common structure for the role.

· Show-notes writer. Turns the finished episode into a page: a description, timestamps and the quotes worth pulling for social. Paid per episode, like the editor, because the unit of work is the same.

· Co-host or fill-in host. Some networks pay a second voice a flat fee per episode, which suits a rotating-panel format where not every host appears every week.

A network with two interview shows and a weekly news roundup might run one producer across all three on retainer, three different editors matched to each show's format on a per-episode fee, and a single show-notes writer handling all three at a per-episode rate, because the writing itself doesn't need format-specific judgment. Format drives the editor's rate more than anything else: a scripted narrative episode with sound design and multiple audio layers takes far longer to mix than a straight two-person interview recorded on a single clean feed, so networks running both formats usually set two different per-episode rates instead of one blended one.

Per-episode, retainer or per-show budget

Three ways to structure the pay, and most networks running more than a couple of shows end up using more than one.

· Per episode. A flat fee for one deliverable: one edited file, one show-notes page. Fits work where the output is countable and the time to produce it stays roughly consistent. Easiest to budget against a release schedule: ten episodes a month is ten invoices, whatever the calendar ends up looking like.

· Retainer. A fixed monthly fee for work that's ongoing. A producer's booking and briefing runs continuously, and per-episode pay misses the work happening between episodes. A retainer prices that ongoing availability directly.

· Per-show budget. A total monthly amount allocated to one show, split between its editor, producer and show-notes writer. This is the shape that scales: a network adding a seventh show sets one budget for the show and lets the three roles split it.

A rate that works at two shows a week can look wrong at six. A producer retainer priced for a three-show workload carries a heavier load once a fourth comparable show is added with no change to the fee, and it usually needs revisiting at that point, well before the next scheduled renewal. The same drift shows up on the editing side in reverse: a per-episode rate set for a weekly cadence quietly turns into a much bigger monthly commitment once a show adds a second weekly episode, even though nobody renegotiated a single number.

Agreements and who owns the audio

The pay structure is one clause. What happens to the work once it's paid for is a separate one, and it deserves its own explicit line in the agreement.

An editor's deliverable is usually the single exported file that gets published. The project file behind it — the timeline, the separated tracks, the settings used to clean up the audio — is a different asset. Unless the agreement says otherwise, an editor working independently may simply keep those project files. For a network that might re-edit an old episode, cut a highlight reel, or switch editors mid-season, that's worth specifying up front, before a new editor asks for source files the previous one no longer has on hand.

The same gap shows up around clips. A network that wants to cut a two-minute highlight for social media needs the right to reuse a segment of the episode outside its original feed, which is a separate permission from the right to publish the full episode itself. Where a show relies on short clips as its main promotion channel, that permission is worth writing into the agreement itself, since paying for the episode alone doesn't automatically cover it.

Show notes raise a smaller version of the same question: once paid for, does the network own the written page outright, including the right to reuse the pull quotes in a newsletter or on social. Most networks want yes, and most freelance show-notes writers will agree to it in writing. But a per-episode invoice with no accompanying agreement only establishes a fee. It doesn't transfer any rights on its own.

Some contractor platforms build this into the agreement itself: the client specifies what's being secured when a task is assigned, and the resulting paperwork reflects it. That turns a question that would otherwise go unsettled invoice by invoice into something decided once, up front.

Paying many small invoices every week

A network with six weekly shows and the crew above is paying twelve to eighteen invoices a week once every editor, producer and show-notes writer submits theirs, more if a show runs a second edit pass or a rotating co-host. Each invoice is small by wire-transfer standards: a single episode's edit fee, invoiced and paid on its own. The count alone adds cost. The average total cost of a cross-border business payment runs about 1.6% of the amount sent, and roughly seven-eighths of that is the exchange-rate margin — a cost buried inside the conversion rate, rarely shown as its own line item, and one that doesn't shrink much just because the invoice is small (Financial Stability Board, 2025 G20 cross-border payments progress report).

Paperwork compounds the count. A US-based network paying a foreign contractor who does all the work outside the US generally owes no 1099 and no withholding, provided it holds a valid W-8BEN on file before paying. The form has to be collected and kept on hand. It isn't filed with the IRS. Under IRS rules it's good through the end of the third calendar year after it's signed, then needs refreshing. A US citizen living abroad is a different case: still a US person for tax purposes, so a W-9 and a 1099, not a W-8BEN. Get the wrong form on file and the default shifts to withholding: 24% backup withholding domestically, 30% on a foreign payee.

The invoice itself isn't standardized either. A contractor abroad invoices under their own country's rules, and those rules vary: cross-border business services between the EU and a non-EU payer are usually handled under the reverse charge, which moves the value-added tax (VAT) liability onto the payer without making the paperwork disappear, and a contractor's invoice still has to meet their own country's formatting requirements — Brazil's nota fiscal, for one, has no direct English equivalent. None of this is specific to podcasts; it's the same paperwork any company owes on any foreign freelancer. What's specific to a six-show network is the volume. That paperwork, multiplied by twelve or eighteen invoices a week, is either a recurring manual check on every invoice or a check done once per contractor, covering every invoice that contractor sends afterward.

A weekly payout routine that scales to more shows

The operational fix for volume is batching: one weekly run that pays every contractor due that week, instead of a transfer initiated as each invoice arrives. Structurally, that takes fewer separate relationships to manage — one agreement covering the whole crew instead of a distinct contract per editor, per producer and per show-notes writer, so adding a seventh show doesn't mean drafting a seventh set of paperwork.

4dev.com is built around that structure. Contractors complete their own onboarding and document upload under the platform's guidance, one agreement covers all of a client's contractors regardless of which country they're in, and the platform generates documents automatically with each payment. Its published rate is a service fee of 3% or less per payout, with no subscription, and reach across 150+ countries covers most of where a distributed podcast crew is likely to be based. A network that wants to fold its whole payment run into its own finance systems can do that through 4dev.com's application programming interface (API), with a personal account manager handling access and documentation. It covers contractor engagements, not payroll for staff employees, which matches how most networks already pay an editing crew.

None of that removes the budgeting decisions covered above. What it changes is the shape of the operational load once those decisions are made: a dozen invoices a week become one payment run, reviewed once, with the currency conversion and paperwork check for every contractor handled inside that single pass.

FAQ

Should a podcast editor be paid per episode or by the hour? Per episode is the norm for editing and show notes, because the deliverable is countable and comparable episode to episode. Hourly pay only works if the network trusts its own time estimate and keeps renegotiating it as an editor gets faster. In practice, most don't bother, so the per-episode fee ends up as the default anyway.

Who owns the raw audio and edited files once the invoice is paid? Whatever the agreement says, and if it doesn't say, the safer assumption is that only the final exported episode changed hands, not the project file behind it. Put ownership of both the export and any source files the network might need later — a re-edit, a highlight reel — into the same agreement that sets the fee, before the question ever comes up.

Does a US network need to withhold tax on payments to a producer based abroad? Generally not, if the producer performs all the work outside the US and the network holds a valid W-8BEN on file before paying. Without that form on file, the default shifts to withholding, so it has to be collected before the first invoice is paid.