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

The VS Code Full-Stack Developer

A full-stack developer with 2–10 years of experience for whom VS Code is the primary tool of their craft — the place they spend most of their working day. They have a VS Code configuration that took months to arrive at and that they bring to every new machine. They know their extensions. They know their keybindings. They have an opinion about whether Prettier should run on save. Their editor is not the default installation — it's a reflection of how they think about working.

“A teammate asked how they managed stay in flow state — the editor should get out of the way and let them write.”

The Mixpanel Product Analyst

A product analyst or data analyst embedded in a product team who uses Mixpanel as their primary tool for understanding user behavior. They build funnels, analyze retention, and create the dashboards that PMs reference in every planning meeting. They know SQL but prefer Mixpanel's UI for speed. They've named every event in the tracking plan and written documentation for each one. They are the person the PM turns to and asks "are users actually using this feature?" — and they always have the answer.

“A teammate asked how they managed build funnels that accurately capture user journeys from signup to activation to retention.”

The Amplitude Growth Analyst

A data analyst, growth analyst, or analytics engineer at a Series B–D company who owns Amplitude as the source of truth for product behavior. They are technical enough to write SQL but prefer not to for exploratory analysis. They've mastered the Amplitude chart types. They build dashboards that PMs and executives use but don't fully understand. They're the person in the room who says "let's look at the data" and then actually pulls it up.

“The head of product wants to know which activation milestone most predicts 30-day retention.”

The Mixpanel Product Manager

A product manager or growth lead at a B2C or B2B SaaS company for whom Mixpanel is the primary lens on user behavior. They are not a developer. They understand events and properties well enough to answer most of their questions self-service. They have a set of saved reports they look at every Monday. They also have questions that require a data analyst to answer — and they're slowly working to reduce that list.

“A teammate asked how they managed understand where users drop out of key flows and why.”

The Raycast Power User

A developer, designer, or technical knowledge worker on Mac who replaced Spotlight with Raycast and then spent three weekends making it the center of their computing workflow. They open Raycast more than any other application. They open it for things they didn't know a launcher could do. They've written or installed extensions for their most repetitive tasks. They mention Raycast in the same breath as mechanical keyboards and monitor setups — tools that are invisible when they work and felt intensely when they don't.

“It's 9am.”

The Raycast Workflow Automator

A developer or technical power user on macOS who has made Raycast the nerve center of their computing workflow. They don't just launch apps — they manage clipboard history, control Spotify, search GitHub issues, translate text, convert currencies, and run custom scripts — all from a single keyboard shortcut. They've installed 15–30 extensions and written a few of their own. They are the person whose colleagues watch them work and ask "what is that tool and how do I get it." They measure productivity in keystrokes saved.

“It happened mid-workflow — the developer starts their day.”

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

The Sentry Error Wrangler

A developer — usually mid-level to senior — who has become the de facto owner of error tracking on their team. They set up Sentry, configured the alerts, and now they're the person who triages the error feed every morning. They know the difference between a real bug and a noisy exception. They've learned to read stack traces the way a doctor reads X-rays — quickly, looking for the thing that's actually wrong. They carry the mental burden of knowing exactly how many errors are happening in production at any given moment.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about grouping algorithms that split one bug into multiple issues or merge different bugs into one in two weeks.”

The Ramp Finance Controller

A finance controller, VP of Finance, or head of accounting at a 50–500 person company who chose Ramp because they were tired of chasing receipts, manually categorizing expenses, and closing the books a week after month-end. They manage corporate cards, set spend policies, and review transactions. They appreciate Ramp's automation but know that "automated" still means they're the one who catches the exceptions. They are the financial guardrail of the company.

“It happened mid-workflow — month-end arrives.”

The Cal.com Scheduling Power User

A consultant, agency owner, or team lead who uses Cal.com because Calendly was too simple for their scheduling needs. They manage round-robin scheduling for a team, paid consultation bookings, multi-timezone availability, and custom booking forms that collect information before the meeting. They chose Cal.com because it's open-source, self-hostable, and extensible in ways Calendly's paid tiers can't match. They are the scheduling architect for their team.

“It happened mid-workflow — a consulting agency needs different scheduling for three scenarios: free 15-minute discovery calls (routed to available consultant), paid 60-minute strategy sessions (It happened mid-workflow — a consulting agency needs different scheduling for three scenarios: free 15-minute discovery calls (routed to available consultant), paid 60-minute strategy sessions (The aha moment happened the first time they used Cal.”

The PostHog Growth Engineer

A growth engineer, product engineer, or technical PM who uses PostHog as their all-in-one growth stack — analytics, feature flags, A/B tests, session replay. They chose PostHog because they didn't want to stitch together Amplitude, LaunchDarkly, and Hotjar. They think in funnels, retention curves, and statistical significance. They are technical enough to self-serve but product-minded enough to care about the "so what" behind the data.

“It happened mid-workflow — the growth engineer is running an A/B test on the onboarding flow.”

The Runway AI Video Producer

A video producer, creative director, or content creator who has integrated Runway into their production workflow. They use it for practical production tasks: generating b-roll from text prompts, extending clips that are a few seconds too short, removing backgrounds without green screens, and creating concept videos for client approval before shooting. They are not experimenting with AI video for fun — they are using it to solve production problems that were previously solved by money, time, or compromise.

“A marketing team needs a 30-second concept video for a product launch.”

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 PagerDuty On-Call Engineer

A software engineer or site reliability engineer who is on a rotating on-call schedule and whose relationship with PagerDuty is defined by the moments it wakes them up. They've been paged at 3am. They've resolved incidents from their phone in bed. They've also been paged for something that wasn't an incident — a flaky alert, a threshold set too low, a monitoring rule that was never updated after the system changed. Every false positive erodes their trust in the alert and their willingness to respond with full urgency next time. They manage this tension carefully.

“The shift was quiet.”

The Runway AI Video Editor

A video editor, creative director, or content producer who has integrated Runway into their professional workflow — not as a novelty, but as a production tool that changes what's achievable in a given timeline and budget. They use Runway for AI video generation, background removal, inpainting, motion tracking, and generative effects that would require a VFX team or days of Premiere work otherwise. They have a traditional video editing background. They understand the craft. They are not using Runway to replace craft — they're using it to expand what they can produce without expanding the team or the deadline.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about consistency across generated clips — maintaining visual coherence between in two weeks.”

The HubSpot Marketing Manager

A marketing manager at a company with 20–150 employees who is responsible for the entire marketing function — content, email, social, paid, and now increasingly the CRM data that sales keeps asking about. They chose HubSpot or inherited it. They use more of it than anyone else at the company. They still feel like they're not using it right, even after two years.

“It's Monday morning.”

The Beehiiv Newsletter Operator

A newsletter founder, media operator, or content entrepreneur who runs a publication with 5,000–100,000 subscribers and treats it as a business with its own P&L, not a side project. They chose Beehiiv because it was built for operators — it has ad network access, referral programs, segmentation, and analytics that treat the newsletter as a product. They think in CAC, LTV, open rate, and click-to-open rate. They have a growth number they're working toward. They may or may not write the newsletter themselves.

“They're in the monthly business review.”

The Google Analytics Marketing Analyst

A digital marketer, marketing analyst, or growth lead who uses Google Analytics as their primary source of truth for website performance. They lived in Universal Analytics for years — they knew where every report was, how sessions worked, and what their bounce rate meant. Then GA4 happened. The interface changed, the data model changed, sessions became events, and reports they relied on disappeared or moved. They're learning GA4 because they have to, not because they wanted to. They are adapting their expertise to a tool that feels like it was rebuilt for data engineers, not marketers.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about the GA4 interface is unintuitive — reports that took one click in UA now require custom explorations in two weeks.”

The Hotjar UX Researcher

A UX researcher, product designer, or growth PM who uses Hotjar as their window into real user behavior. They watch session recordings to understand confusion, analyze heatmaps to validate layout decisions, and run micro-surveys to capture user sentiment in context. They are the person on the team who says "let me check what users are actually doing" before anyone makes a design decision based on assumptions. They think in user journeys, not funnels.

“The shift was quiet.”