“It happened mid-workflow — the knowledge worker is writing a strategy memo about pricing models.. readwise handled something they'd been doing manually, and it just worked. That was the moment it stopped being a tool they were evaluating and became one they relied on.”
When I'm the knowledge worker is writing a strategy memo about pricing models, I want to capture highlights from every reading source (Kindle, web, podcasts, PDFs) in one place, so I can resurface forgotten highlights through daily review to reinforce key insights.
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.
To reach the point where capture highlights from every reading source (Kindle, web, podcasts, PDFs) in one place happens through readwise as a matter of routine — not heroic effort. Their deeper aim: resurface forgotten highlights through daily review to reinforce key insights.
readwise becomes invisible infrastructure. Capture highlights from every reading source (Kindle, web, podcasts, PDFs) in one place works without intervention. The old problem — the daily review emails can feel like a chore if the highlights aren't curated — quantity dilutes quality — is a memory, not a daily fight. Smarter daily review that prioritizes high-signal highlights based on tags, recency, and topic relevance.
The knowledge worker is writing a strategy memo about pricing models. They search their Readwise library for "pricing" and find 23 highlights across 8 different books and articles they've read over the past two years. Three highlights are directly relevant — one from a SaaS pricing book, one from a newsletter about value-based pricing, and one from a psychology article about anchoring. They pull these into their memo with citations. The memo is stronger because it's grounded in research they've already done. Their colleague asks "how do you always have the perfect reference?" The answer: they highlighted it once, Readwise kept it, and search found it.
Reads 20–40 books per year and 50–100 articles per month. Has 5,000–30,000 highlights in Readwise. Uses Readwise Reader as their primary reading app for articles and newsletters. Exports to Obsidian or Notion weekly. Reviews the daily highlight email 4–5 days per week. Has tagged 30–50% of their highlights with topics. Uses the search function monthly when writing or researching. Pays for Readwise + Reader. Has a reading workflow: discover → save to Reader → read and highlight → auto-sync to Readwise → periodic export to PKM.
The proof is behavioral: capture highlights from every reading source (Kindle, web, podcasts, PDFs) in one place happens without reminders. They've customized readwise beyond the defaults — templates, views, integrations — and their usage is deepening, not plateauing. When new team members join, they hand them their setup as the starting point.
The daily review emails can feel like a chore if the highlights aren't curated — quantity dilutes quality keeps recurring despite updates and workarounds. They start tracking how much time they spend fighting readwise versus using it. The switching cost was the only thing keeping them — and it's starting to look like an investment in the alternative.
Pairs with readwise-primary-user for the standard reading tool perspective. Use with obsidian-plugin-developer for the PKM destination of highlights. Contrast with notion-ai-writer for the AI-assisted knowledge query approach.