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

The Height Engineering Team Lead

An engineering team lead or technical PM at a company of 20–150 people who evaluated Linear and wanted more — more project hierarchy, more cross-functional visibility, more flexibility for non-engineering teams to work alongside engineering in the same tool. They chose Height. They're building their system in it. They like that it feels like a tool built by people who understand engineering workflows, not a project management tool that engineering is expected to tolerate. They're still learning the edges of it.

“It happened mid-workflow — sprint planning is Monday.”

The Height Autonomous Project Tracker

A product team lead or engineering manager at a startup who chose Height because it promised what every PM secretly wants: a project tracker that maintains itself. They use Height's AI features to auto-triage bug reports, suggest task labels, and identify duplicate issues. They still do the strategic work — prioritization, sprint planning, roadmap decisions — but the administrative overhead of keeping the tracker clean is lower than with Jira or Linear. They are cautiously optimistic about AI in project management — it works 75% of the time, and the 25% it doesn't requires less effort to fix than doing it all manually.

“A teammate asked how they managed reduce the time spent on task triage, labeling, and organization by 50% with AI assistance.”

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 Tally Non-Technical Form Builder

A startup founder, indie maker, or operations person who creates forms for surveys, lead capture, applications, and feedback — and who bounced off Typeform's pricing, Google Forms' aesthetic, and Airtable Forms' rigidity. They found Tally and built their first form in 4 minutes. They converted immediately. They use Tally for things that other tools make too complicated or too expensive for what's essentially a box to collect information.

“A teammate asked how they managed create a well-designed form fast without a mental model of how the tool works.”

The Whimsical Fast Diagrammer

A product manager, designer, or engineer who uses Whimsical for the work that happens before the work — user flows, information architecture diagrams, quick wireframes, system diagrams. They chose Whimsical over Figma for this because Figma requires too much setup for a sketch. They chose it over Miro because they need structure, not freeform. They chose it over Lucidchart because Lucidchart is too heavy for what they're doing. Whimsical is the tool for the thinking phase. It is rarely the final deliverable. It is always the thinking that produces the final deliverable.

“A teammate asked how they managed get a flow or wireframe out of their head and onto a shareable canvas in under 15 minutes.”

The Segment Data Engineer

A data engineer or analytics engineer at a tech company for whom Segment is the central nervous system of the data stack. Every tool the company uses for analytics, marketing, and customer success gets its data through Segment. They did not design the original tracking plan. They inherited it. They've been cleaning it up for eight months. It will take eight more. They are the person who gets paged when an event stops flowing.

“A teammate asked how they managed maintain a clean, consistent event schema that all downstream tools can rely on.”

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 GitHub Open Source Maintainer

A developer who maintains one or more open source projects with 500–50,000 stars. They started the project to solve their own problem and now thousands of people depend on it. They review PRs from strangers, answer issues that are really support questions, and write release notes at midnight. They are simultaneously proud of what they've built and exhausted by the weight of other people's expectations. They do this in their spare time, or they're one of the lucky few who gets paid for it.

“A teammate asked how they managed triage issues efficiently — separate bugs from feature requests from support questions.”

The Substack Independent Writer

A journalist, essayist, researcher, or domain expert who chose to publish directly to an audience rather than through a publication that owns the relationship. They've been on Substack for 1–4 years. They have a free list and a paid tier. They take the writing seriously. They also think about the business of the writing — open rates, growth, conversion from free to paid — more than they expected to when they started. They are doing something that didn't exist at scale five years ago and they feel the weight and freedom of that simultaneously.

“It happened mid-workflow — they've been on Substack for 18 months.”

The Drata Compliance Manager

A security manager, compliance lead, or IT director at a SaaS company of 50–500 people who is responsible for achieving and maintaining SOC 2 Type II certification. Before Drata, this was a spreadsheet, a shared drive, and a six-month audit season that consumed 30% of their capacity. Drata made it something they can manage in the background with periodic attention spikes. They're not relaxed about compliance — that would be naive — but they're less reactive. That's the win.

“A teammate asked how they managed maintain continuous compliance evidence without a manual collection sprint before every audit.”

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 Dropbox Cross-Functional File Sharer

A project manager, creative director, or department lead at a company that produces large files — design assets, video, documents, presentations — that need to move between internal teams and external partners. They use Dropbox because it works for people who aren't on their company's Google or Microsoft stack. It's the lowest-friction way to get a 2GB folder to a client or vendor who uses a PC, a Mac, or a Linux box, and doesn't have access to their internal SharePoint.

“A client has requested all source files from a project completed eight months ago.”

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