Who actually uses these products,
and what made them stay.

The Descript Podcast Producer

A podcast producer, video content creator, or marketing team member who discovered Descript and now finds traditional timeline editing alienating. They edit by editing the transcript. They remove filler words in bulk. They record pickups without re-recording the whole segment. They've explained Descript to other editors and watched the same expression — skepticism that becomes revelation — every time. They are not a professional audio engineer. They produce content that sounds professional. That gap is Descript.

“It happened mid-workflow — a 52-minute interview recording has just finished uploading.”

The Riverside Remote Podcast Host

A podcast host, interview show creator, or video podcast producer who records remote guests and has been burned enough times by Zoom audio artifacts that they moved their entire recording setup to Riverside. They care about sound quality in a way that most people around them don't understand. They've explained "local track recording" to three different guests and still have guests who join from a coffee shop with AirPods. They've made peace with this.

“It happened mid-workflow — a major guest has agreed to record.”

The Descript Content Creator

A content creator, podcaster, or YouTuber who discovered that editing video by editing text is the workflow they always wanted. They are not a professional video editor — they are a creator who needs to edit video. They record long-form content and use Descript to clean it up: remove filler words, cut dead air, generate highlights, and export polished clips. They've tried Premiere and DaVinci Resolve but found the timeline-based editing paradigm unnecessary for talking-head and interview content.

“A teammate asked how they managed edit video and audio by editing the transcript — cut a sentence, cut the video.”

The Readwise Knowledge Synthesizer

A voracious reader — books, articles, newsletters, podcasts, Twitter threads — who realized that reading without capturing is forgetting. They use Readwise to collect highlights from Kindle, Instapaper, podcasts, and the web, then Readwise Reader for their daily reading queue. They've built a workflow where everything they consume flows through one system, highlights are tagged and resurfaced, and insights compound over time. They are the person who can always find "that article I read about X" because they highlighted the key passage six months ago.

“It happened mid-workflow — the knowledge worker is writing a strategy memo about pricing models.”

The Readwise Highlight Librarian

A voracious reader — typically a knowledge worker, researcher, writer, or lifelong learner — who realized that reading without retention is expensive entertainment. They started using Readwise because they kept forgetting what they'd read. They now have 8,000–30,000 highlights across Kindle books, web articles, PDFs, and podcasts. They do the daily review. Not every day — most days. The review takes 5 minutes and resurfaces things they've completely forgotten. Occasionally a highlight resurfaces at exactly the right moment for what they're working on. This is not magic. This is why they pay for Readwise.

“It happened mid-workflow — tuesday morning.”

The Roam Research Networked Thinker

A writer, researcher, or knowledge worker who uses Roam Research as an extension of their thinking. They don't organize notes into folders — they write, link, and let the graph reveal connections. They use daily notes as their entry point, double-bracket references to build a web of ideas, and block references to connect thoughts across pages. They've read about Zettelkasten, spaced repetition, and evergreen notes. They've adopted some of these ideas and adapted others. They are building a thinking system, not a filing system.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about performance degrades with large graphs — search and page loads slow down over time in two weeks.”