verbator: See your own show answering

You don't have to know what to ask.

Verbator reads every episode you've ever made against every other one, continuously. Arguments that recur across years, positions that quietly reversed, predictions that have now resolved, the guest worth calling back — it finds them between episodes and puts them in front of you when you're planning, researching, recording or selling the show.

See your own show answering Currently onboarding a small number of shows.
Planning

The next three episodes, argued for out of material you already own.

Research

One page on your guest, twenty minutes before you record.

Studio

Openings in front of you while the conversation is still live.

Afterwards

Clips, teasers and threads — quoted and sourced — before the audio is mastered.

It keeps reading when you're not.

Verbator doesn't sit and wait to be queried. Every episode you publish is read against every episode you've already made, and against every one you make after it. Arguments that recur get linked. Positions get tracked to the moment they change. Predictions stay open until something resolves them. Names are matched across conversations that never mentioned each other.

None of it has to be asked for. By the time you sit down to plan, prepare or record, the work has already happened and is waiting — each piece of it carrying the passages it came from, so you can see what it rests on before you use it.

Threads

The same argument, made four years apart about two different subjects, connected without anyone suspecting it was there.

Positions

Who holds what, on this show, and the episode where they stopped holding it. Including the ones who never announced the change.

The ledger

Every claim about the future your guests have made, held open, and marked when the world settles it one way or the other.

Openings

Questions worth putting to someone, kept until the moment there's a reason to ask them.

A search box needs you to already suspect the connection. This doesn't.

The callback is the signature move.

“You said the opposite three years ago.”

“Last time you were here, you predicted this.”

“A guest in 2022 made exactly this argument — from the other side.”

It's what separates a host who feels like an institution from one working through a question list. And right now it runs entirely on one person's memory — which doesn't scale with the catalogue, doesn't transfer to a co-host, and quietly fails the moment your archive outgrows your recall.

Every great host already does this. Nobody does it completely.

The conversation goes further.

Twenty minutes in, your guest says something that rhymes with an argument from three years ago. A name comes up that a previous guest knew well. A claim lands that someone once took apart, carefully, on this same show.

Verbator Live follows along on a laptop or a shared screen in the studio, and puts those threads in front of you while they're still live.

The studio screen
verbator live 00:18:41
Listening
Asking the archive
Openings

The same session on the studio screen, on a laptop, or on a phone.
Illustrative session. The show, the guest and the passages are invented.

Openings, not instructions. Most you'll wave away. One of them takes the conversation somewhere neither of you planned to go — the tangent, the half-remembered detail, the objection worth chasing for ten minutes.

That's where the episodes people send each other come from.

It tells you when it doesn't know.

A callback that names the wrong person is worse than no callback at all — you'd be saying something false about your own show, on the record, to the person who supposedly said it.

So Verbator doesn't guess. Every line it gives you carries a named speaker, an exact timestamp and the source audio. When it can't establish who spoke, it says so and shows you what's missing, instead of filling the gap with something plausible.

That's the whole reason you can use it live.

And it answers when asked.

The standing read is what brings you things you'd never have gone looking for. The index underneath it is also there the moment you do have a question — about a subject, a person, or something you half remember saying.

Recall

“Has anyone on this show discussed conscription?”

“What has Ashkan said about attention?”

“Have we covered this before?”

Answers come back as passages — who said it, when, in which episode, with the audio ready to play. Not a summary of your show. Your show.

The guest is coming back

One page, twenty minutes before you record: everything they've said here, the positions they took, what they claimed last time, what they got right, and where you pushed back. New guest? Whatever the archive already holds about them from every other conversation they've been part of.

Connections you didn't make

Your archive has been having a conversation with itself for years. This is the first time you get to hear it.

The prediction ledger

Your guests make predictions. They're on the record, timestamped, attributed — and until now, unrecoverable. Verbator keeps score. Here is what was predicted on this show, by whom, and what actually happened. One episode a year writes itself.

Your whole catalogue, back in play.

Most of what your show has made is doing nothing. It earned its keep the week it published and has been sitting still ever since.

Indexed, it starts working again — and it gets better as you go, because every new episode gives every old one something to be compared against.

Clips become findable. Themes become traceable. The best-of, the newsletter, the book — none of it is blocked on nobody being able to find anything in the archive.

The next thing is already in there.

The same index that answers your questions also shows you what it is holding. An episode you already have the material for. A guest two of your previous guests have named. A piece assembled out of passages you recorded years apart.

Nothing is decided for you. Everything it puts up carries the passages it came from, so you can see what it is made of and then take it, change it or leave it. Nothing publishes itself.

Episode

The prediction audit

Claims your guests made on the record have since resolved. The tape is there to play back to them, timestamped and attributed, whenever that's an episode you feel like making.

built from ep. 96 · 147 · 168 · 211
Guest

Maria Lindqvist

Named by two previous guests, never on the show. Proposed theme: the reporting rebuild they both worked on and disagreed about — one of them on the record saying so.

named in ep. 147 · 01:14:22 and ep. 211 · 00:38:09
Writing

Right instrument, wrong unit

The same error, three subjects, four years apart. A newsletter piece or a chapter, drafted out of passages you already have, quoted and cited — no new reporting required.

built from ep. 96 · 203 · today's session
Back catalogue

Old episodes, back in circulation

When something in the news matches an argument in your archive, the clip that speaks to it is already located — the passage, the speaker, the timecode, and a caption that quotes it accurately.

matched against the full catalogue
Draft · teaser for today's recording audio not yet mastered
Suggested phrasing

“We assumed it was the money. It was never the money — we lose people in month seven, every single cohort.”

Recorded this morning. Full conversation Thursday.

today · 00:18:54 · verbatim Quote checked against the recording. Speaker confirmed.
Suggested imagery
pull-quote card
guest name, episode number,
the line above set large

Or the thirty-eight seconds of audio around the quote, ready to cut. Both are drafts. You approve, edit or throw them away.

We index your catalogue before we talk to you.

All of it. The first thing you'll see isn't a demo of our product — it's your own show, answering questions.

No setup fee, nothing to migrate, no minimum catalogue. If you decide it isn't for you, we delete it.

Studio: your show, your team, Live included.
Network: several shows on one archive, connected across all of them.
We index it before we get in touch. If you decide it isn't for you, we delete it.
verbator:

An audio corpus you can cite.

See your own show answering