How much does an audio version of an article really cost?
Studio recording, a DIY text-to-speech stack or a managed service: what each option really costs a news publisher, and how to compare them fairly.
The question sounds simple and the honest answer is: it depends entirely on how you produce it. There are three ways to give your articles a voice, and their price tags are not even in the same currency. One is billed per article, one is mostly paid in engineering time, and one is a flat subscription.
That makes naive comparisons misleading. A speech API that costs a fraction of a cent per character looks unbeatable next to a monthly subscription, until you count the developer who has to turn that API into a working product. A voice actor's day rate looks reasonable, until you multiply it by your daily output. The only comparison that holds up is cost per published article at your real volume, including your team's time.
Option 1: human studio recording
This is the quality ceiling: a professional voice, direction, editing. It is also the option whose economics collapse fastest for news. Every article carries its own cost: the talent's time, the recording and editing, the back-and-forth to get names and corrections right. Whatever that per-article figure is for your market, multiplying it by twenty or fifty articles a day gives a monthly bill no regional publisher signs.
The delay is the other problem. A recording pipeline takes hours at best, often days, and an article corrected at 11am needs its audio corrected too. Human recording remains the right tool for what it was made for: a flagship long read, a narrated series, a branded podcast. It is not a way to voice your daily output.
Option 2: building your own stack on speech APIs
Modern speech synthesis APIs are genuinely good and genuinely cheap per character. The raw synthesis, however, is maybe a fifth of the product. To ship audio on a news site you also need to: extract clean article text from your CMS (minus captions, embeds and related-links blocks), regenerate audio when an article is updated or corrected, handle the pronunciation of local names your region cares about, build and embed a player, host and deliver the files, and measure whether anyone listens.
That is weeks of development up front, then permanent maintenance: APIs change, voices are deprecated, your CMS gets redesigned. The per-character fee is the visible cost; the real cost is the loaded salary of the developers building and maintaining the pipeline. If you have a product team with spare capacity and audio is strategic enough to own the code, this route is legitimate. Most regional publishers have neither the spare capacity nor the appetite.
Option 3: a managed service
The third option is a subscription that covers the whole chain: generation, corrections and updates, player, hosting, delivery, statistics. At WeDispatch, plans run from 69 to 419 EUR excluding VAT per month depending on your article volume, with everything included; the details are on the pricing page. No per-article metering, no code to maintain, and audio appears on new articles without anyone in the newsroom lifting a finger.
The trade-off is the mirror image of option 2: you give up owning the pipeline in exchange for a predictable line in the budget and a launch measured in days rather than quarters. There is also a free tier, so you can test it on your own articles and hear the result on your actual content, including the tricky local names, before any commitment.
How to run the comparison for your site
Take your real monthly article count and work out three numbers. For studio recording: per-article cost times volume, plus coordination time, which for daily news usually ends several multiples above the other two options. For the DIY stack: the API fees, which will be small, plus the honest number of developer days to build and then to keep it running each month. For a managed service: the subscription tier your volume lands in.
Then add the dimension spreadsheets forget: time to live. Audio that ships this month starts building listening habits, ad inventory and subscription arguments this month. A pipeline delivered in two quarters starts from zero in two quarters. For most regional newsrooms, that calculation, more than any per-article figure, is what decides the question.
Give your articles a voice with WeDispatch
All plans, from 69 to 419 EUR excluding VAT per month, are detailed on the pricing page, and you can try it free on your own articles today.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo