Case studies · Newsrooms in production · 2026

Different newsrooms.
Different fights.
One operating layer.

Each newsroom brings a different problem — retention, scale, revenue, voice quality, time-to-launch. The plays they ran are below. The control layer underneath is the same.

The case studies

Pick the play that's closest to yours.

  1. taz Berlin · since 1979 Retention

    Print, retired.
    Voices, cloned.
    Subscribers, kept.

    When Germany's taz ended its weekday print edition, custom voice clones of its own journalists became one of the strongest reasons subscribers stayed.

    • 90% subscribers retained
    • +10% above best-case
    • 2 custom journalist voices
    • ~1-month build
    Read the taz case study
  2. Tamedia Bern · Lausanne · Zürich Scale

    24 titles.
    Two languages.
    Three weeks.

    Tamedia put editorial-grade audio behind the paywall across its German and French Swiss portfolio — without rebuilding a single CMS.

    • 24 titles live
    • ~40% past two minutes
    • ~6% player click-through
    • POC → prod in 3 weeks
    Read the Tamedia case study
  3. heute.at Vienna · OE24 network Accessibility

    Austrian voice.
    Accessibility deadline.
    Live by late 2025.

    heute.at had to ship editorial audio for accessibility compliance — and to an Austrian audience that would not accept a German-accented voice. BotTalk delivered both.

    • Live since late 2025
    • Austrian voice · plug-and-play
    • Predictable pricing
    • OE24 network
    Read the heute.at case study
  4. Hamburger Morgenpost Hamburg · since 1949 Revenue

    278K readers.
    75% accept the ad.
    One line of code.

    Mopo embedded BotTalk's audio-advertising platform into its CMS — and turned a declining print-ad line into a growing audio one.

    • 10% reader → listener
    • 75% in-audio ad accept
    • $6–30 CPM
    • Single-line CMS embed
    Read the Mopo case study

30+ publishers running BotTalk in production

Run a play in your newsroom

Talk to Andrey.

No deck. No pitch. Your CMS, your audience, your editorial voice. Thirty minutes. One call.