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

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 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 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 Notion AI Knowledge Worker

A product manager, writer, or operations lead who already uses Notion as their primary workspace and added Notion AI to make their existing workflows faster. They were already in Notion 4–6 hours a day. Notion AI is not a new tool to them — it's a capability inside the tool they already trust. They use it to summarize meeting notes, draft first versions of documents, and ask questions of their existing workspace. The context is already there. The AI can work with it. This is the part that makes Notion AI different from a separate AI tool to them.

“It happened mid-workflow — they've just finished a 90-minute discovery call.”

The Pika Video Creator

A social media manager, content creator, or marketer who uses Pika to generate short video clips for social media, ads, and content marketing. They're not a video editor — they're a marketer who needs video content faster than traditional production allows. They type descriptions and get video clips. They use image-to-video for product animations. They create motion graphics from static designs. They've learned that "good enough for social" is a valid quality bar, and Pika hits it in minutes instead of hours.

“It happened mid-workflow — the social media manager needs 5 short clips for the week's content calendar.”

The GitBook Developer Documentation Lead

A developer advocate, technical writer, or senior engineer at a developer-facing company who owns the documentation. They chose or inherited GitBook because it lowers the friction for engineers to contribute alongside the technical writers. They care about documentation quality in a way most of their colleagues don't — because they're the one who gets the support tickets when the docs are wrong. They know the gap between documentation that exists and documentation that works. They're trying to close it.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about documentation that drifts from reality because nobody owns the update process in two weeks.”

The Mintlify Developer Advocate

A developer advocate, DX engineer, or technical founder at a developer-facing company who chose Mintlify because they believed documentation was a product, not a document. They write docs in MDX. Their docs live in a git repository alongside their code. They ship documentation the same way they ship features: PR, review, merge, deploy. They care about the visual quality of their docs because they know developers judge a product by how it feels to learn it — and bad docs signal a bad API. They've recommended Mintlify to three other devrel teams. All three use it now.

“The shift was quiet.”

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.”