Campaign Chronicle Studio: Monetize Tabletop Scribe + TranscribeToText for TTRPG DMs & Actual‑Play Creators

Category: Monetization Guide

Excerpt:

Use Tabletop Scribe and TranscribeToText to build a “Campaign Chronicle Studio” for tabletop RPG groups and actual‑play channels. This guide leans on real session‑management pains and walks through a concrete 10‑day workflow to turn messy audio into clean recaps, wikis, transcripts, and highlight ideas—without promising fame or unrealistic income.

Last Updated: February 5, 2026 | Stack Focus: Tabletop Scribe (TTRPG session → wiki) + TranscribeToText.org (audio → text) | Monetization Angle: Campaign recap & archive service for DMs and actual‑play creators

Campaign Chronicle Studio Tabletop Scribe = session → recap + wiki TranscribeToText.org = full transcripts on tap

Your groups love playing. They hate paperwork. You turn raw audio into living campaign histories.

If you’ve ever DMed a long campaign, you know the feeling: someone asks “wait, who was that NPC from three months ago?”, everyone stares at half‑empty notebooks, and you silently scroll through Discord hoping past‑you wrote it down.

Actual‑play shows aren’t better. There’s the stream, the VOD, maybe a podcast cut… and then vague show notes and no transcripts. Lore is trapped in hours of video.

This guide is how you turn that mess into a small business. You’ll use Tabletop Scribe to auto‑build recaps and campaign wikis, and TranscribeToText.org to get clean transcripts when you need every word— then sell a simple, concrete service: “Campaign Chronicle Studio”.

The line you’re really selling: “Give me your session audio and I’ll come back with recaps, a wiki, and transcripts your table actually uses.”
What this page is really about

You’re building a small “Campaign Chronicle Studio”: not a massive agency, just a focused lane where you turn audio into recaps, transcripts, and wikis for a few tables and shows—enough to be worth real money, not hype.

On‑the‑table problems Your Chronicle offer Tool roles (keep it simple) 10‑day pilot project Packages & pricing Clients & outreach

“We’ve been playing for years. Nobody remembers what happened.”

Think about the average long‑running campaign you’ve played in:

  • Session 3 clue? Gone by session 12.
  • Player journals updated enthusiastically… for two weeks.
  • DM notes live in five different places, none in sync.

I’ve been that DM, promising “I’ll write a recap tomorrow” and then crawling into bed instead. I’ve been that player squinting at a character sheet, trying to remember which NPC we owed money to.

Actual‑play creators feel the same crunch but with more pressure: listeners ask “Which episode did X happen in?” and there’s no transcript, no searchable archive, just vibes.

Problems you can clearly solve
  • “Recaps eat prep time.” → No automated way to turn audio into a first draft.
  • “Our lore is scattered.” → No central, searchable wiki that updates as they play.
  • “New listeners get lost.” → No transcripts, no quick way to catch up on episodes.
  • “We forget our own story.” → No reliable “what happened last time?” before sessions.

Your Chronicle Studio doesn’t promise better dice rolls. It promises a clear memory: a recap, a wiki, and a transcript for every important session.

Offer: a 10‑Day “Campaign Chronicle Sprint” for one arc or season

Treat your work like a small project with a start and an end, not “editing forever”.

Working name: Campaign Chronicle Sprint (10 days)

Best for:

  • Home DMs who record sessions and want “grown‑up” recaps and lore.
  • Actual‑play podcasts / streams with a backlog but no transcripts or episode guides.
  • Clubs and stores running long campaigns that change players over time.

By the end of 10 days, you deliver:

  • Clean recaps for 4–8 sessions (or episodes) in plain language.
  • A browsable campaign wiki from Tabletop Scribe (NPCs, locations, arcs).
  • Full or partial transcripts from TranscribeToText.org for key sessions.
  • A simple “Next Time On…” snippet they can read at the table or at the start of an episode.
How you describe it without sounding like a tool tutorial

Instead of: “I’ll integrate AI transcription into your TTRPG workflows.”

Say something closer to:

“You record your sessions like you already do. I take the audio and come back with readable recaps, a wiki of your world, and transcripts for the key episodes. When someone asks ‘what happened last time?’, you’ll have a real answer in one link.”

You’re selling less mental load, not “AI wizardry”.

Keep the stack tiny: Scribe runs the world, TranscribeToText catches every word

Tabletop Scribe: the campaign brain

Tabletop Scribe is built for tabletop campaigns, not corporate meetings. You feed it session audio, it:

  • Transcribes and summarizes each session.
  • Detects characters, locations, items and events.
  • Builds a living “campaign wiki” your group can browse.
  • Can generate images and, eventually, even printed books from your story.

In your studio, Scribe is where you:

  • Get first‑draft recaps in the DM’s language.
  • Keep the cast of NPCs and locations straight across arcs.
  • Answer “when did we last go to X?” without scrubbing audio.
TranscribeToText.org: the raw text workhorse

TranscribeToText.org is a straightforward AI audio‑to‑text site:

  • Upload long audio or video files, get transcripts back quickly.
  • Supports common formats (MP3, WAV, MP4, and more).
  • Exports as plain text or subtitle‑friendly formats.

You’ll use it when you:

  • Need full transcripts for actual‑play episodes (for captions or blogs).
  • Want detailed text to search for quotes, rules calls, or lore drops.
  • Have non‑game audio (DM prep, Q&As) you still want in text form.

A 10‑day “Campaign Chronicle” pilot: from messy audio to usable lore

Don’t start by selling this to strangers. Run this once on your own game or for a friend’s table. Then you’ll know how long everything really takes.

Days 1–2 · Pick your test campaign and gather raw audio
  1. Choose one of:
    • Your own weekly home game (best, you already know the story).
    • A friend’s campaign that’s been running for a while.
    • A small actual‑play show with 4–8 episodes in a season.
  2. Make sure you have 4–8 recorded sessions (audio or video). If they only have video, you can still use it—both tools can work from that.
  3. Put the files in a clean folder:
    /ChroniclePilot
  /Audio
    session01.mp3
    session02.mp3
    ...
  /Outputs (empty for now)
Days 3–4 · Run a first pass through Tabletop Scribe

You’re not trying to get perfect text from Scribe. You’re getting a solid starting point.

  1. Install / open Tabletop Scribe on your phone. Create a campaign for this test game.
  2. Upload session 1’s audio. Let Scribe:
    • Transcribe and summarize the session.
    • Create or update NPC, location, and event entries.
  3. Read the recap like a player. Ask:
    • Does it capture the big beats?
    • Are NPC names roughly right?
    • Are there obvious mistakes you’d always fix (rules terms, setting names)?

Repeat for 3–4 sessions. Don’t edit deeply yet; just see what the raw output looks like so you know how much human cleanup you’ll have to charge for later.

Day 5 · Use TranscribeToText.org for full transcripts on a key episode

Pick one especially lore‑heavy or emotional session and put it through TranscribeToText.org.

  1. Go to TranscribeToText.org, upload the chosen audio/video file, and wait for the transcript.
  2. Once it’s done, skim the text:
    • Highlight important lines (“we swear to protect…”, “we owe 500 gold…”).
    • Mark recurring locations and NPC names.
  3. Paste a cleaned‑up excerpt into Scribe’s notes or wiki if you want that particular speech or rules ruling preserved word‑for‑word.

Full transcripts are overkill for every session, but gold for key episodes and for public shows that care about accessibility and SEO.

Days 6–7 · Turn AI drafts into human‑readable recaps & a clean wiki view

This is where you actually earn your fee. The tools make drafts; you make them usable.

  1. For each session, take Scribe’s recap and:
    • Fix names, in‑jokes, and rules terms.
    • Shorten long paragraphs into 6–12 punchy bullet points.
    • Add a 2–3 sentence “Previously on…” summary at the top.
  2. Check the wiki it built:
    • Merge duplicate NPC entries (Thorn vs Thorne, etc.).
    • Add 1–2 lines of DM context where needed (“Secretly working for X”).
    • Tag locations by region or arc so they’re easier to scan.
  3. Export or screenshot the wiki in a way the group can use: link to Scribe if they’re happy using the app, or copy key data into a shared doc if they prefer that.

Don’t over‑polish. Aim for “DM can prep in 15 minutes because this exists”, not “award‑winning prose”.

Days 8–9 · Package everything into something players & viewers will actually touch

Groups don’t want “another tool”. They want a link or file they can open without thinking.

  1. For a home campaign, create:
    • A single “Campaign Home” doc (Notion, Google Doc, whatever they use) with:
      • Links to each recap.
      • A short cast list (PCs + major NPCs).
      • Links to Scribe’s wiki if they’re comfortable with the app.
  2. For an actual‑play show, create:
    • Episode blurbs adapted from your recaps.
    • Links to transcripts (even partial) from TranscribeToText.org.
    • A simple “Start here if you’re new” page highlighting key episodes.
  3. Make sure everything lives in one shared folder the client controls. Your job is to organize, not to lock them in.
Day 10 · Check your own workload and codify the offer

Before you ever talk about money, be honest with yourself:

  1. How many hours did this 4–8 session arc actually take you?
  2. What parts took the most time (audio upload, name fixing, wiki cleanup, packaging)?
  3. Which bits did the DM or creator care about the most when you showed them?

That’s your real data. Use it to shape your paid packages instead of guessing from thin air.

Pricing: realistic, not “quit your job from D&D” numbers

This is side‑income or one pillar of a freelance mix, not instant full‑time work. Across a few tables and shows, it can add up to a few hundred to maybe a couple of thousand dollars a month if you’re consistent.

OfferWhat’s included (concrete)Best forExample range (USD)
Arc Chronicle (4–5 sessions) Recaps + wiki cleanup for 4–5 sessions of one arc using Tabletop Scribe, plus a short “Previously on…” summary and a simple campaign home doc. No full transcripts, just Scribe‑level detail + your edits. Home DMs who want to get a messy arc “back under control”. Around $80–$200 one‑time, depending on your region and time spent
Season Chronicle (6–10 episodes) + transcripts Everything in Arc Chronicle, plus full or partial transcripts from TranscribeToText.org for 3–6 key episodes (for captions, blogs, and search), and a “Start Here” guide for new listeners or viewers. Small actual‑play podcasts / streams with one or two seasons already out. Roughly $200–$600 per season, depending on length and transcript depth
Monthly Campaign Scribe (ongoing) A fixed bundle each month, for example: recaps + wiki maintenance for 2–4 sessions, plus one key‑episode transcript and a monthly “story so far” summary. Clear cap on number of hours / sessions covered. Long‑running campaigns or shows that want a stable archivist without hiring staff. Around $150–$450 per month to start; more if you handle bigger shows

These are rough ranges, not promises. Your actual rates depend on your speed, your niche, and your clients’ budgets. The important part is to charge for clean arcs and saved time, not for “X hours of AI tool usage”.

In every proposal, say it plainly: you are not promising sponsorships, partner deals, or view spikes. You’re promising a campaign memory that doesn’t fall apart—recaps, wikis, and transcripts built on real tools.

Who will actually pay for this (and how they sound)

The right people don’t talk about “AI tooling”. They say things like:

  • “I wish someone kept track of this campaign for me.”
  • “We keep saying we’ll do recaps and never do them.”
  • “Our actual‑play has fans now, but no transcripts or summaries.”
  • “I’d pay to not feel lost when we miss a few weeks.”

Places they tend to hang out:

  • Discord servers for D&D, Pathfinder, and indie TTRPGs.
  • Subreddits and forums where people share session recaps or AP episodes.
  • Twitter / Bluesky / Mastodon circles for small actual‑play shows.
  • Local game store communities, Facebook groups for campaigns and clubs.
A DM / email you can send without sounding like a bot
Subject: Making your campaign easier to remember

Hey [Name],

I’ve been following your [home game / actual-play] and it looks like
you’ve got a really fun story going.

Something I see a lot:
- everyone loves playing,
- nobody has time to write recaps,
- and after a few months, half the table forgets what happened.

I run small “Campaign Chronicle” sprints where I:
- take your session audio,
- use tools like Tabletop Scribe to build recaps + a campaign wiki,
- and add transcripts for key episodes via TranscribeToText.

End result: you get:
- a clear summary of each session,
- a searchable list of NPCs/locations,
- and text you can use for show notes or blogs.

If you’d like, send me:
1) a link to your channel (or a couple of session files),
2) and 1–2 sentences about your campaign.

I can reply with a quick outline of what a 10-day sprint
would look like for you, so you can see if it actually
sounds helpful.

No pressure either way,
[Your name]
Set clear boundaries so “AI” doesn’t become “guaranteed success”
Just to be transparent:

Using Tabletop Scribe + TranscribeToText
won't magically make your game famous or fix bad audio.

What I can do is:
- make sure what you play doesn't get forgotten,
- give you recaps your group can actually skim,
- and provide transcripts for the episodes that matter.

You still run the game and grow your audience.
I just look after the story once the dice stop rolling.
A 7‑day plan before you call yourself a “studio”
  1. Day 1: Run 3–4 of your own sessions through Tabletop Scribe. Edit the recaps until you’d happily share them with your group.
  2. Day 2: Put one lore‑heavy session through TranscribeToText.org. Highlight the sort of details clients will care about.
  3. Day 3: Build a simple “Campaign Home” page for your own game as if you were your own client.
  4. Day 4: Share screenshots (with player permission) in a TTRPG community, talking honestly about how it helped your table.
  5. Day 5: DM or email 5–10 DMs or small AP creators you know, offering one discounted Arc Chronicle.
  6. Day 6: Deliver that first paid (or heavily discounted) project carefully. Track your hours.
  7. Day 7: Adjust your scope and pricing based on reality, not theory. Then talk about it a bit more publicly.

A couple of well‑run chronicle projects will do more for your reputation than any landing page can.

You’re not chasing virality. You’re becoming the person who remembers.

If you’ve ever sat down at a session and thought “I have no idea what happened last time”, you already understand why this service matters. You’re taking that frustration and turning it into a job: the person who makes sure stories don’t dissolve between sessions.

Tabletop Scribe does the heavy lifting on TTRPG‑specific structure. TranscribeToText.org gives you full text when you need it. The real value isn’t those tools—it’s you noticing what matters, fixing rough edges, and delivering something your clients actually lean on every week.

Start with one campaign. Chronicle one arc. Charge once. Adjust. By the time you’ve done that a few times, you won’t just “play with AI tools”—you’ll run a small Campaign Chronicle Studio that quietly makes tabletop stories easier to remember and easier to share.

Tags： , , , , , ,
FacebookXWhatsAppEmail