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

The Cursor AI-Native Developer

A developer who has made Cursor their primary IDE and restructured their workflow around AI-assisted coding. They don't use AI as autocomplete — they use it as a pair programmer, architect, and refactoring partner. They've learned which prompts work, which context windows matter, and when to trust the AI vs. when to verify manually. They are faster than they were in VS Code, but they've also developed new anxieties about code they didn't fully write.

“The shift was quiet.”

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 Riverside Remote Podcast Host

A podcast host, interview show creator, or video podcast producer who records remote guests and has been burned enough times by Zoom audio artifacts that they moved their entire recording setup to Riverside. They care about sound quality in a way that most people around them don't understand. They've explained "local track recording" to three different guests and still have guests who join from a coffee shop with AirPods. They've made peace with this.

“It happened mid-workflow — a major guest has agreed to record.”

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 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 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 Pika AI Video Creator

A content creator, marketing director, or creative professional who has integrated AI video generation into their content workflow. They use Pika to turn static concepts, images, and text prompts into short video clips for social media, ads, and marketing presentations. They are not video producers. They don't have a camera setup, a motion designer on staff, or the budget for a production house for every asset. They have prompts and a process. They're producing things that didn't exist two years ago from a budget that hasn't changed.

“A teammate asked how they managed produce motion content for social and marketing without a video production budget.”

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 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 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 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 Descript Podcast Producer

A podcast producer, video content creator, or marketing team member who discovered Descript and now finds traditional timeline editing alienating. They edit by editing the transcript. They remove filler words in bulk. They record pickups without re-recording the whole segment. They've explained Descript to other editors and watched the same expression — skepticism that becomes revelation — every time. They are not a professional audio engineer. They produce content that sounds professional. That gap is Descript.

“It happened mid-workflow — a 52-minute interview recording has just finished uploading.”

The Clerk Authentication Developer

A full-stack developer at a startup who chose Clerk because building authentication from scratch — login, signup, email verification, OAuth, MFA, session management — is 2 months of work that adds zero product differentiation. They integrate Clerk's pre-built components, customize the flows, and manage users through the dashboard. They appreciate that auth "just works" but they've also hit moments where Clerk's opinionated approach conflicts with their product's specific needs. They are a developer who decided that auth is infrastructure, not a feature worth building themselves.

“The developer is building a new SaaS product.”

The Clerk Authentication Developer

A full-stack developer or indie hacker building a SaaS product who has decided that authentication is not a competitive advantage and has no interest in building it. They chose Clerk because it ships the full auth experience — sign in, sign up, user profile, MFA, social providers, and organization management — as components they can drop in and style to match their product. They were building on NextJS and Clerk was the obvious answer. It took them four hours to integrate. They've never looked back and have never thought about auth again unless a customer asked for a feature.

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

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 Replit Coding Educator

A coding instructor, bootcamp teacher, or CS professor who uses Replit because it eliminates the "but it works on my machine" problem. Every student gets the same environment, in the browser, with no setup. They can see student code in real time, run it, and give feedback without cloning repos or debugging local environments. They've taught programming long enough to know that environment setup kills motivation faster than any algorithm does. They chose Replit to remove the barrier between "wanting to code" and "coding."

“A teammate asked how they managed eliminate setup and environment issues so students can focus on learning to code, not configuring tools.”

The Zoom-Fatigued Remote Manager

A manager or team lead at a remote-first or hybrid company for whom Zoom is the primary way they experience their job. They run standups, 1:1s, team meetings, cross-functional syncs, and the occasional all-hands. They are good at running meetings. They are exhausted by running meetings. They've read the articles about camera fatigue and still feel obligated to be on camera. Their background is a shelf they specifically arranged.

“A teammate asked how they managed run meetings that actually need to be meetings — and end on time.”

The Pendo Product Manager

A product manager at a B2B SaaS company who owns feature adoption and in-app user education. They have engineering bandwidth for product, not for tooltips. Pendo lets them publish in-app guides without a ticket. They've also realized that Pendo's analytics tell them something different from their product analytics tool — not better, different. Pendo tells them where users are, not just what they do.

“A major new feature shipped three weeks ago.”

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 Mintlify Developer Relations Lead

A developer relations lead, technical writer, or engineering manager responsible for their API's documentation. They chose Mintlify because the docs should look as good as the product. They write guides, maintain API references, and obsess over the developer experience from first visit to first API call. They measure success not by page views but by time-to-first-successful-API-call. They've learned that bad documentation is the most expensive support channel a company has.

“The company ships a new API endpoint.”

The Fly.io Container Developer

A backend or full-stack developer who needs to run server-side applications — not just static sites and serverless functions — and wants them deployed globally without managing Kubernetes or paying for managed Kubernetes overhead. They found Fly.io and found a platform that takes a Dockerfile and runs it near users. They `fly deploy`. It works. They have opinions about Fly.io that include real affection and specific frustrations, which is the relationship one has with a platform they actually depend on.

“It happened mid-workflow — they're deploying a Phoenix application — Elixir, with WebSockets and a persistent database connecti.”

The Pitch Deck Builder

A startup founder, sales director, or brand marketer who builds presentation decks that matter — investor pitches, sales proposals, quarterly business reviews. They chose Pitch because PowerPoint felt like 2005 and Google Slides felt like giving up on design. Pitch gives them templates that look professional and a collaborative workflow that doesn't require sending a file over email. They spend more time on decks than they'd like to admit. They care more about how those decks look than they'd admit in a meeting.

“An investor meeting is in 48 hours.”

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 Whimsical Product Thinker

A product manager, designer, or architect who uses Whimsical when they need to think visually but don't need pixel-perfect precision. They create flowcharts to map user journeys, wireframes to sketch interfaces, and mind maps to explore problem spaces — all in the time it would take to set up an artboard in Figma. They value speed over fidelity. They are the person who brings a Whimsical link to a meeting and says "here's what I'm thinking" before anyone else has a concrete proposal.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about there's a ceiling — when wireframes need more detail, the transition to Figma requires starting over in two weeks.”

The Roam Research Networked Thinker

A researcher, academic, writer, or knowledge-intensive professional who uses Roam because it is the only tool that treats the connection between ideas as a first-class object. They write in Daily Notes. They [[bracket]] everything. They have a graph with 3,000–15,000 nodes that they've been building for 2–4 years. They know their graph is their most valuable intellectual asset. They also know that Roam's development has slowed, that the tool has rough edges, and that they've considered migrating to Obsidian or Logseq at least twice. They haven't migrated. The switching cost is partly the data — mostly the habit.

“They're writing an essay about institutional memory.”

The Datadog SRE

A site reliability engineer or DevOps engineer responsible for the uptime and performance of production systems. They chose Datadog because it combines metrics, traces, logs, and alerts in one place — but now they're paying for all of it and the bill is terrifying. They've built dashboards that are beautiful, alerts that are precise, and runbooks that nobody reads. They are the person who gets paged at 3 AM and needs to determine in 90 seconds whether this is a real incident or a flapping alert.

“The shift was quiet.”

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 Drata Compliance Automation Lead

A security engineer, compliance lead, or CTO at a startup who needs SOC 2, ISO 27001, or HIPAA compliance to close enterprise deals. They chose Drata because the alternative was spreadsheets, manual evidence collection, and $50K in consultant fees. They've connected their cloud infrastructure, HR tools, and code repositories to Drata for automated evidence collection. They understand that compliance is a business requirement, not a security one — the real security work is separate. They are simultaneously grateful for automation and frustrated by how much manual work remains.

“A teammate asked how they managed automate evidence collection across cloud infrastructure, identity providers, and HR systems.”

The Kajabi Course Creator

A consultant, coach, or subject-matter expert who has turned their expertise into an online course business on Kajabi. They teach everything from business strategy to photography to fitness. They chose Kajabi because they didn't want to connect Teachable + ConvertKit + Stripe + WordPress + Zapier just to sell a course. They build landing pages, host video lessons, manage email sequences, process payments, and track student progress — all in one platform. They are a teacher who became a business owner, and the business runs on Kajabi.

“A teammate asked how they managed create and deliver online courses with video, text, quizzes, and downloadable resources.”

The Miro Remote Facilitator

A UX designer, product strategist, design researcher, or Agile coach who uses Miro as their workshop room. They've run retrospectives, journey mapping sessions, design sprints, and ideation workshops — all on Miro, all remote. They are good at facilitation. They have strong opinions about how a Miro board should be structured. They've also learned that a beautifully structured board means nothing if participants don't know how to use sticky notes.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about new participants who spend the first 10 minutes learning Miro instead of the topic in two weeks.”

The Framer Interactive Designer

A product designer or creative developer who uses Framer for either high-fidelity interactive prototypes or production marketing sites — often both. They came from Figma and knew it wasn't built for interaction. They came from Webflow and wanted more design control. Framer sits between those two worlds and they've made it home. They are comfortable with the code escape hatch. They don't use it unless they have to. When they have to, they can.

“The shift was quiet.”

The Attio Revenue Operator

A revenue ops manager, head of sales, or technical founder at a startup of 10–100 people who evaluated the legacy CRMs and decided not to inherit their constraints. They chose Attio because it's data-model-first — they can define what a record means in their business rather than forcing their process into Salesforce's assumptions. They are building their CRM from scratch. This is a significant investment. They are aware of that and have decided it's worth it.

“A teammate asked how they managed build a CRM that reflects their actual sales process rather than a generic framework.”

The Contentful Content Manager

A content manager, digital editor, or marketing manager at a company with a developer-built Contentful implementation. They publish product pages, blog posts, campaign content, and documentation through Contentful's web interface. They did not design the content model — a developer did. They live inside that model every day and have a detailed understanding of which fields do what and which ones are a mystery. They are not a developer but they've learned to think in content types.

“A teammate asked how they managed publish and update content quickly without waiting on a developer for every change.”

The Excel Financial Analyst

A financial analyst at a corporation, investment firm, or consultancy for whom Excel is not software — it is the medium of thought. They spend 5–7 hours a day inside spreadsheets. They build models that other people are afraid to open. They have keyboard shortcuts memorized that the rest of the company doesn't know exist. They've rescued a broken model the night before a board presentation. They have opinions about Excel that they share without being asked.

“It happened mid-workflow — they're building a 3-year P&L model for a new product line.”

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 Notion AI Content Strategist

A content strategist, knowledge manager, or team lead who uses Notion AI as part of their daily workflow inside Notion. They don't use it to write blog posts from scratch — they use it to summarize 45-minute meeting transcripts into action items, turn rough notes into structured documents, answer questions about information buried in the team's wiki, and draft from templates. They've found the sweet spot: AI handles the structure, they handle the thinking.

“The shift was quiet.”

The Notion Workspace Admin

A team lead, chief of staff, or ops person who became the unofficial Notion admin because they were the first person to organize anything in the workspace. They've built the team wiki, the project tracker template, and the onboarding guide. They spend more time maintaining the structure of Notion than using it for their actual job. They live in fear of someone moving a page to the wrong section and breaking every linked database.

“A new team member joins and asks where to find the product roadmap.”

The Coda Doc Builder

A team lead, ops manager, or product manager who uses Coda to build interactive documents that are half-doc, half-app. They've built meeting note trackers with automated action items, sprint planning boards with voting buttons, and OKR trackers with progress rollups — all inside Coda docs. They chose Coda because Notion didn't have formulas and Airtable didn't have documents. They love that everything lives in one place. They worry that they've built something only they understand.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about formula complexity escalates quickly — what starts as a simple lookup becomes a nested formula chain in two weeks.”

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 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 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 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 Vercel Frontend Developer

A frontend or full-stack developer with 2–8 years of experience who discovered Vercel and decided that deploy-on-push preview URLs should be table stakes for every project. They've tried to describe the Vercel experience to developers still using other deployment pipelines and can't fully convey it. They use Vercel for personal projects, client work, and have advocated for it at their company — sometimes successfully. Their bar for deployment infrastructure is now set by Vercel, which makes everything else feel like a step backward.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about build times that climb as the project grows — especially Next.”

The Clay GTM Engineer

A GTM engineer, growth operations lead, or RevOps professional who uses Clay as their data enrichment and workflow engine. They build spreadsheet-like tables that pull from 50+ data providers — enriching companies with technographic data, finding decision-makers' emails, scoring leads based on signals, and triggering personalized outreach. They think in data transformations and API calls. They've replaced hours of manual prospect research with Clay workflows that run in minutes. They are the engineer of the sales pipeline's data layer.

“The shift was quiet.”

The Coda Ops and Strategy Builder

An operations manager, strategy lead, or chief of staff who discovered that the documents they needed didn't fit neatly into either a Google Doc or a spreadsheet. They found Coda and spent two weeks building something they couldn't have built elsewhere — a doc with a database inside it, buttons that trigger actions, and views that update automatically. They are evangelical about it in proportion to how many people they've tried to explain it to. It's hard to explain until you see it.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about the learning curve that separates people who "get" Coda from people who bounce off it in two weeks.”

The Make Integration Architect

An automation specialist, operations engineer, or technical ops manager who builds complex workflows in Make because Zapier wasn't enough. They connect 10–30 tools with branching logic, iterators, aggregators, error handlers, and data transformations. They build automations that look like flowcharts, not if-then rules. They've learned Make's visual interface deeply — routers, filters, webhooks, custom HTTP modules. They are the person who automates what everyone else does manually, and they take quiet pride in systems that run for months without intervention.

“A teammate asked how they managed build multi-step automations with branching logic that handles different cases (approval/rejection, success/failure).”

The Monday.com Team Lead

A team lead or department head at a company of 50–300 people who uses Monday.com as the primary place their team tracks work. They may not have chosen Monday — it was often adopted company-wide because the CEO liked the demo. They've made it work. Their board is actually used. They've built automations their team quietly depends on. They spend 30–60 minutes a day in Monday and would describe it as "pretty good once you know what you're doing," which is a backhanded compliment they mean sincerely.

“Their team has just absorbed a new function.”

The FullStory Digital Experience Analyst

A product analyst or UX researcher at a digital product company who uses FullStory as their lens into the user experience. They don't just look at funnels and conversion rates — they watch sessions, identify frustration signals (rage clicks, dead clicks, error clicks), and correlate behavioral patterns with business outcomes. They've learned to find the story in the data: why conversions dropped, where users get confused, what makes the checkout feel broken. They are the translator between raw user behavior and product decisions.

“The product team sees a 15% drop in checkout completion after a recent redesign.”

The Dropbox Creative Team Manager

A creative director, design lead, or production manager who manages files for a creative team — designers, photographers, video editors, copywriters. They chose Dropbox because it handles large files (PSD, AI, video) better than Google Drive and because the desktop sync means creatives can work in their native apps without learning a new tool. They are the person who designs the folder structure, enforces naming conventions, and answers the question "where is the latest version of the logo?" at least three times a week.

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

The Prisma TypeScript Developer

A backend or full-stack developer working primarily in TypeScript who uses Prisma as their database interface and considers the Prisma schema file to be the authoritative source of truth for their data model. They came from raw SQL, or from another ORM, and found that Prisma's type generation changed how they think about database access — not as a string-query problem but as a typed function call where the compiler tells them when something is wrong before it runs. They have strong feelings about the Prisma schema. Those feelings are mostly fond.

“The shift was quiet.”

The Sentry Error Monitor

A backend, frontend, or full-stack developer at a product company for whom Sentry is the first place they look when something goes wrong in production. They didn't set Sentry up — it was already there when they joined — but they've learned to read its output. They've been paged because of a Sentry alert. They've traced a production incident back to a specific line using Sentry's stack traces. They've also spent 40 minutes investigating a Sentry error that turned out to be a bot making malformed requests. They've learned to filter.

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

The Canva Marketing Manager

A marketing manager or content lead at a 10–100 person company who produces 20–50 pieces of visual content per week. They're not a designer and they know it — but Canva makes them good enough. They've built a template library that keeps everything on-brand, and they resize for every platform in one click. They're proud of the speed but occasionally embarrassed when a real designer sees their work. They are the reason the brand looks consistent, even if the brand guidelines live in a Google Doc nobody reads.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about brand Kit limitations — fonts upload fine but brand colors sometimes don't apply consistently in two weeks.”

The Toggl Self-Tracker

A freelancer, consultant, or productivity-conscious knowledge worker who tracks time for one of two reasons: they bill by the hour and accuracy is revenue, or they've realized they have no idea where their hours go and they want to find out. Both types start Toggl for practical reasons and discover something unexpected — tracked time is honest in a way that memory and intention are not. They've had the experience of thinking they spent 4 hours on a project and the timer saying 2.2. They've also had the reverse. Both were useful information.

“It happened mid-workflow — they're a UX consultant.”

The Superhuman Inbox Zero Executive

A startup CEO, VP, or senior director who receives 150–300 emails per day and treats email like a production system. They chose Superhuman because Gmail was too slow and too noisy. They've memorized the keyboard shortcuts, configured their split inbox, and use the AI triage to surface what matters. They process email like a speed reader processes text — scanning, deciding, acting — in bursts of 15–20 minutes, 3–4 times per day. They are allergic to unread counts and consider inbox zero a professional discipline, not a personality quirk.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about the AI triage sometimes miscategorizes important messages from new contacts in two weeks.”

The Kajabi Course Creator

A course creator, coach, consultant, or subject matter expert who chose Kajabi because they wanted one platform instead of five. They have a course, probably a coaching program, possibly a membership community, and they wanted all of it to live together with one checkout, one email system, one analytics dashboard. They pay more for this than they would if they stitched together cheaper tools. They've decided that simplicity and integration are worth the difference. The Kajabi community is genuinely part of their decision — knowing that tens of thousands of other creators are building on the same infrastructure.

“A teammate asked how they managed run a profitable online education business without managing multiple platforms.”

The Logseq Academic Researcher

An academic researcher, PhD student, or independent scholar who uses Logseq as their research knowledge base. They take notes on papers, link concepts across disciplines, and use the graph view to see how ideas connect in ways linear note-taking never revealed. They chose Logseq because it's local-first (their research data stays on their machine), uses an outliner format that matches how they think, and builds a knowledge graph without forcing a predetermined structure. They are building a second brain for their research, and they expect it to outlast their current institution.

“The shift was quiet.”

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 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 Spline Web 3D Designer

A product designer, visual designer, or creative developer who started using Spline because they wanted 3D on their website or product and Blender was too much. They have a 2D design background — Figma is their native language. Spline felt like Figma with a Z-axis. They've built at least one thing they're proud of: a 3D hero section, an interactive product visualization, a floating element that reacts to cursor position. They use it for client work and personal projects. They consider themselves an early adopter of the idea that 3D should be accessible to product designers, not just motion designers.

“They're redesigning a SaaS product's marketing homepage.”

The Squarespace Small Business Owner

A small business owner — a bakery, a yoga studio, a photography business, a consulting firm — who built their website on Squarespace because they needed something that looked professional without hiring a designer or developer. They chose a template, swapped in their photos, wrote their copy, and launched. They're not technical, but they figured out the editor. They update the site monthly — new photos, seasonal hours, blog posts when they have time. The website is their digital storefront, and they treat it with the same pride they treat their physical one.

“A potential customer finds the small business owner's Squarespace site through Google.”

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 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 PostHog Product Engineer

A product engineer or full-stack developer at a startup of 5–50 people who chose PostHog — or advocated for it — because they wanted product analytics that behave like engineering tools. They self-host or use PostHog Cloud. They instrument events themselves. They use feature flags as part of their development workflow. They are not a data analyst but they want to be able to answer product questions without filing a request to one.

“It happened mid-workflow — they've shipped a new onboarding flow behind a feature flag to 10% of users.”

The Todoist GTD Practitioner

A knowledge worker — often a project manager, consultant, writer, or developer — who has read productivity books and tried multiple task managers before settling on Todoist. They've built a system. It works when they use it. The failure mode is not the tool — it's consistency. They believe in GTD or a GTD-adjacent framework. They have projects, labels, and filters set up in a way that feels logical to them and would confuse anyone else. They've rebuilt the system twice.

“It's Sunday evening.”

The Datadog SRE

A site reliability engineer or platform engineer at a company with a production system that people depend on. Datadog is their window into that system. They've built dashboards that tell the story of what's happening in production. They've written monitors that page them when something goes wrong. They've been paged at 2am by monitors they wrote themselves and have opinions about that experience. They are better at Datadog than most people at their company and still feel like they're using 30% of what it can do.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about alert fatigue from monitors that fire on normal variance — the cry-wolf problem in two weeks.”

The Figma-to-Code Developer

A frontend or full-stack developer who didn't choose Figma but lives in it three hours a week. They open Figma to inspect designs, grab spacing values, export assets, and try to understand what the designer intended for edge cases that weren't mocked up. They've learned enough about auto-layout to know when a design will be painful to implement. They have opinions about design tokens that the design team doesn't want to hear yet.

“A teammate asked how they managed extract exact spacing, color, and typography values without guessing.”

The Obsidian Plugin Developer

A developer who uses Obsidian for their own notes and started building plugins to scratch their own itch. They now maintain 1–5 plugins with thousands of downloads and a Discord channel full of feature requests. They know the Obsidian API intimately but wish it was better documented. They build in TypeScript, ship through the community plugin store, and handle support in their spare time. They love the Obsidian community but sometimes feel buried by the expectations that come with a popular free plugin.

“Obsidian ships a new version and the developer's most popular plugin breaks.”

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 Clay Growth Operator

A growth lead, revenue ops manager, or technical sales operator who found Clay and spent two weeks rebuilding their entire outbound motion around it. They were already combining data from LinkedIn, Apollo, Clearbit, and spreadsheets manually — a process that was slow, inconsistent, and unscalable. Clay collapsed that into one workflow. They now build outbound lists in hours that previously took weeks. They are evangelical about it. They're also aware that most people at their company don't understand what they've built.

“The head of sales wants a list of 500 Series B SaaS companies that have posted a VP of Sales job in .”

The Sanity Developer-Content Team

A developer who chose Sanity for a project that needed a content infrastructure serious enough to model complex relationships and flexible enough to be customized for a non-developer content team. They built the schema. They configured the Studio. They wrote the GROQ queries. The content team uses what they built every day. The developer's relationship with Sanity is: maintenance, evolution, and occasional deep satisfaction when the content model they designed months ago handles a new requirement gracefully.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about schema changes that require migration scripts for existing content — the cost in two weeks.”

The Figma Dev Mode Engineer

A frontend engineer at a product company who implements UI from Figma designs. Dev Mode is their interface to the design file — the layer of Figma that was built for them rather than around them. They use it to extract measurements, inspect component properties, copy CSS values, and verify that what they've built matches what was designed. They have strong feelings about when Dev Mode helps and when it's still faster to ask the designer. Those feelings are specific.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about cSS output that assumes a different architecture than the codebase they're working in in two weeks.”

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 Webflow Design-to-Production Designer

A web designer or design agency owner who ships production websites directly from Webflow — no developer handoff, no code translation step. They think in layout, typography, and spacing, but they've also learned Webflow's class system, CMS collections, and interaction triggers. They are a designer who became a builder. They're proud that they can ship a client site in a week, but they're aware that their Webflow projects are sometimes held together with class naming conventions only they understand.

“A teammate asked how they managed build responsive, pixel-perfect websites that match the design vision exactly.”

The Jira Engineering Manager

An engineering manager leading a team of 5–15 developers. They use Jira because the company chose it years ago and migration would be worse than staying. They plan sprints, groom backlogs, and build the reports their VP needs for quarterly reviews. They know Jira's power but resent its complexity. They've customized their board exactly once and now they're afraid to touch it. They protect their team from Jira overhead by doing most of the admin work themselves.

“The shift was quiet.”

The Excel Financial Modeler

A financial analyst, FP&A professional, or investment banker who builds financial models in Excel the way architects build buildings — with structure, precision, and the knowledge that if one formula is wrong, everything above it falls. They've been using Excel for 5–15 years. They think in cell references, not coordinates. They know keyboard shortcuts that most people don't know exist. They've built models that a CEO used to make a $50M decision, and they've spent weekends debugging a circular reference that shouldn't have been circular.

“The CFO asks for a scenario analysis by tomorrow morning: what happens to cash flow if revenue grows 10% slower than projected and two enterprise deals slip to next quarter.”

The Prisma ORM Developer

A TypeScript or Node.js backend developer who uses Prisma as their ORM. They chose it because the type safety and auto-generated client make database interactions feel like writing TypeScript, not SQL. They've come to depend on the schema-first workflow — define the schema, generate the client, write queries with full autocomplete. But they've also hit the wall where the ORM can't express what they need, and they have to drop down to raw SQL with a guilty feeling, like they're breaking the abstraction.

“The developer is building a leaderboard feature that requires ranking users by score within time windows, with pagination.”

The Wix Small Business Builder

A small business owner — a personal trainer, a photographer, a bakery, an accountant — who built their website on Wix because they could drag and drop their way to something that looked professional enough. They aren't designers. They aren't developers. They are business owners who need an online presence. They picked a template, moved things around until it looked right, added their text and photos, and hit publish. They update it when they remember to. It's not perfect, but it exists, and it brings in customers.

“A potential client searches "photographer near me" and finds the business owner's Wix site on the second page of Google.”

The DocuSign Legal Operations Manager

A legal operations manager, contracts administrator, or legal team member responsible for the organization's DocuSign implementation. They manage templates, set up signing workflows, and make sure contracts go through the right approval chains. They're the person who built the NDA template, the SOW template, and the vendor agreement template. They field requests like "I need this signed by Friday" and translate them into proper DocuSign envelopes with the right fields, routing, and compliance settings. They are the API between the legal team and everyone else who needs something signed.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about template management becomes unwieldy as the library grows — versioning and deprecation are manual processes in two weeks.”

The Dovetail Research Operations Manager

A UX research lead or research operations manager at a product company who uses Dovetail to turn the chaos of qualitative research — interview transcripts, survey responses, usability test recordings — into a structured, searchable insights repository. They tag, code, and synthesize findings so that when a PM asks "what do we know about onboarding friction?" the answer is a link, not a 3-week research project. They are the librarian of user insights, and they've learned that research nobody can find is research that didn't happen.

“A teammate asked how they managed tag and code qualitative data (transcripts, notes, videos) with consistent taxonomy.”

The Substack Independent Publisher

A writer, journalist, or subject-matter expert who has turned their expertise into a Substack newsletter with paying subscribers. They are not a blogger — they are running a media business. They write 2–4 times per week, manage a growing list of free and paid subscribers, and check their subscriber metrics more often than they'd admit. They chose Substack because it was the simplest path from "I should write" to "people are paying me to write." They appreciate the simplicity but worry about what happens if the platform changes its terms.

“The shift was quiet.”

The Storybook Design System Maintainer

A frontend developer or design technologist who maintains the company's Storybook instance. They write stories for every component, document props with controls, set up visual regression testing, and serve as the bridge between designers and developers. They are the keeper of the design system's technical truth. When a designer asks "does this component exist?" the answer lives in their Storybook. When a developer asks "how do I use this prop?" the answer lives in their Storybook. They are the librarian of the component library.

“The shift was quiet.”

The Contentful Headless CMS Developer

A frontend or full-stack developer who integrates Contentful as the content backend for a website, app, or digital experience. They set up the content models, build the delivery layer, and create the bridge between what content editors want to publish and what the frontend can render. They appreciate the API-first approach but have learned that "headless" means they're responsible for everything the CMS traditionally handled — routing, preview, caching, image optimization. They build the head.

“A marketing team wants to launch a new campaign page type.”

The GitLab DevOps Engineer

A DevOps engineer or platform engineer who chose GitLab because the promise of "one tool for the entire DevOps lifecycle" was too compelling to ignore. They manage the CI/CD pipelines, configure the runners, set up the security scanning, and maintain the deployment workflows. They appreciate that everything lives in one place — no integrating GitHub with CircleCI with Snyk with ArgoCD. But they've also learned that "one tool that does everything" sometimes means "one tool that does everything at 80%."

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about cI pipeline configuration in YAML becomes deeply nested and hard to maintain as complexity grows in two weeks.”

The Miro Workshop Facilitator

A product designer, agile coach, or team lead who facilitates remote workshops in Miro. They don't just draw on a whiteboard — they design participatory experiences: timed exercises, voting rounds, structured templates, and breakout activities. They've learned that the tool is 30% of a good workshop; the other 70% is facilitation design. They are the person who spends 2 hours preparing a Miro board so that a 1-hour workshop runs smoothly for 20 people.

“The facilitator is running a design sprint kickoff with 15 people.”

The Framer Motion Designer

A product designer or motion designer who gravitates toward Framer because it treats animation and interaction as first-class design elements. They don't just design screens — they design how screens transition, how elements respond to hover, how content enters and exits. They've used Figma for static design but find it limiting when the design's value is in how it moves. They are the person who insists that the ease curve matters and that a 200ms delay feels different from a 300ms delay.

“A teammate asked how they managed design and prototype complex animations and transitions that developers would struggle to implement from specs.”