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

The Slack Workspace Architect

An IT admin, department head, or operations lead responsible for how their company uses Slack. They set up the workspace when it was 20 people and now it's 200. They created the channel naming conventions that nobody follows. They are the person people DM when they can't find something, when a channel needs to be archived, or when someone needs to be added to a private channel they shouldn't have access to.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about channel sprawl — 400 channels, half are dead, nobody wants to archive them in two weeks.”

The Loom Async Communicator

A product manager, engineering lead, or designer working on a remote or distributed team who realized that most meetings could be a Loom. They record 5–15 looms per week — product updates, code walkthroughs, design feedback, project kickoffs. They've developed a recording style: concise, screen-shared, with their face in the corner. They are an async communication evangelist who believes the 30-minute meeting is a relic of co-located work.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about video organization becomes a mess — finding a specific loom from three months ago requires remembering the exact title in two weeks.”

The Loom Async Communicator

An individual contributor or people manager at a remote-first company who uses Loom as their primary format for communicating complex information asynchronously. They record walkthroughs, give feedback, share context, and replace 80% of the meetings they used to have. They are comfortable on camera — not because they love being on camera, but because they've made peace with the fact that async video is the clearest way to communicate nuance without a meeting. They have a good mic. They have a ring light. They did not buy these for fun.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about videos that never get watched — the async promise only works if the other person opens it in two weeks.”

The Grammarly Professional Writer

A professional writer, business analyst, marketer, or non-native English speaker for whom written communication is central to their professional credibility. They use Grammarly not because they can't write — they can — but because they write quickly and under pressure, and the gap between their intent and their output sometimes closes imperfectly. Grammarly is the layer that catches what their brain skips. For non-native speakers especially, it's the difference between writing with confidence and writing with anxiety.

“It happened mid-workflow — they're writing a proposal to a new enterprise client.”

The Grammarly Professional Writer

A content writer, communications manager, or marketing professional who writes 3,000–10,000 words per week — blog posts, emails, reports, social copy. They don't need Grammarly to tell them "their vs. there." They use it for the subtle stuff: passive voice creep, sentences that technically make sense but are hard to read, tone shifts that happen when they're tired, and the comma they always second-guess. They've learned to accept some Grammarly suggestions automatically and reject others consistently. They have a relationship with the tool.

“It happened mid-workflow — the writer is finishing a 2,500-word blog post.”

The Zoom Event Producer

An event coordinator, marketing ops person, or executive assistant who runs 5–20 Zoom events per month for audiences of 50–2,000 people. They're not a video producer by training but they've become one by necessity. They know how to spotlight a speaker, manage breakout rooms, and recover from someone sharing the wrong screen — all while monitoring chat for questions. They have a pre-event checklist that's 30 items long because they learned the hard way.

“It happened mid-workflow — it's 5 minutes before a 500-person webinar.”

The Twilio Communications Developer

A backend or full-stack developer at a startup or mid-size company who built the Twilio integration that handles customer-facing communications — appointment reminders, verification codes, order updates, or two-way SMS. They did the integration once. It worked. Now they're the person who gets paged when a customer says they didn't receive their verification code, and they have to determine whether that's a Twilio problem, a code problem, or a carrier problem — in that order.

“It happened mid-workflow — three customers have filed support tickets saying they didn't receive their OTP.”

The Twilio Communications Builder

A backend developer or full-stack engineer who integrates Twilio for transactional SMS, voice calls, or WhatsApp messaging. They're not building a call center — they're adding "send a verification code" or "notify the driver" to an existing product. They understand the API well enough to send messages, but the telecom layer underneath — carrier filtering, number provisioning, regulatory compliance — feels like a different industry entirely. They write code that talks to phones, and they've learned that phones are unreliable in ways servers are not.

“The developer ships a phone verification flow.”

The Intercom Customer Success Manager

A customer success manager or support lead at a B2B SaaS company who uses Intercom as their primary customer communication layer. They handle inbound support conversations, run proactive outreach campaigns to at-risk accounts, and manage the onboarding message sequences that new users see. They know which customers are about to churn before anyone else does because they read the conversation history. They are the person who knows more about the product's real failure points than anyone in engineering.

“The shift was quiet.”

The Pendo Product Manager

A product manager at a B2B SaaS company who uses Pendo as both their analytics platform and their in-app communication tool. They track feature adoption, build onboarding guides, run NPS surveys, and analyze user paths — all without filing engineering tickets. They appreciate that Pendo lets them own the user communication layer. They've become the person who says "let's add a guide for that" whenever a feature has low adoption, and they're starting to wonder if they've created guide fatigue.

“It happened mid-workflow — the PM launches a new dashboard feature.”

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 Pitch Startup Storyteller

A startup founder, head of product, or strategy lead who creates presentations that need to look beautiful and tell a compelling story — investor decks, product roadmaps, board updates, customer pitches. They chose Pitch because it produces better-looking slides with less effort than PowerPoint or Google Slides. They value design defaults that make everything look good automatically. They collaborate in real time with co-founders and design team members. They are visual communicators who believe that how a story is presented is as important as the story itself.

“It happened mid-workflow — the founder is preparing for a Series A fundraising round.”

The Linear Engineering Manager

An engineering manager or head of engineering at a startup of 20–150 engineers who uses Linear at the issue level to track work and at the Projects level to communicate progress. The ICs live in issues and cycles. The EM lives in projects and the roadmap view. They're the translation layer between "what the team is building" and "what the company thinks we're building" — and Linear Projects is the interface they use to close that gap.

“It happened mid-workflow — it's Thursday.”

The Craft Docs Intentional Writer

A product manager, writer, consultant, or knowledge worker who uses Craft as their primary document and note environment because it is the only tool that takes both writing and structure seriously at the same time. They're on Apple devices — Mac and iPhone, usually iPad. They've tried Notion (too database-y), Bear (too simple), Obsidian (too much tinkering), and Apple Notes (not embarrassed about this, just limited). Craft is what they settled on. The fact that it looks good is not superficial to them — environment affects their thinking.

“It happened mid-workflow — they're preparing a strategy document for a quarterly review.”

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 Rive Interactive Animation Designer

A motion designer or creative developer who uses Rive to create animations that aren't just decorative — they're interactive. They build loading indicators that respond to progress, toggle switches that morph between states, onboarding illustrations that react to user input, and game-like UI elements. They think in state machines: idle, hover, active, success, error. They chose Rive because After Effects exports video, Lottie exports playback, but Rive exports interactive, state-driven animations that respond to runtime input.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about the state machine editor has a learning curve, especially for designers coming from timeline-based tools in two weeks.”

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 Perplexity Research Analyst

A research analyst, journalist, consultant, or knowledge worker who has replaced their Google-and-10-tabs workflow with Perplexity. They don't search for links — they ask questions and expect synthesized answers with citations. They use it for competitive analysis, market research, fact-checking, and deep dives into topics where they need to learn fast. They've learned which types of questions Perplexity handles well (factual synthesis) and which it doesn't (opinion-based, very recent events). They trust it more than ChatGPT because of the citations, but they still verify.

“A teammate asked how they managed get comprehensive, cited answers to complex research questions in minutes instead of hours.”