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

The 1Password Security-Conscious Admin

An IT manager, security engineer, or technically-minded operations lead at a company of 20–500 people who adopted 1Password for Teams and now manages credential hygiene across an organization. They have strong feelings about credential sharing via Slack. They have seen what happens when a shared account has no owner and the person who knew the password leaves. They've spent time cleaning up credential sprawl left by a company that grew faster than its security practices. They run 1Password now. It is imperfect but it is dramatically better than what came before.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about vaults that grow without structure until nobody knows what's in them or who owns it in two weeks.”

The Airtable Ops Manager

An operations manager, program manager, or department lead at a 20–200 person company who discovered that spreadsheets couldn't hold what they needed to track anymore. They built something in Airtable that their team actually uses. They are not a developer, but they've learned to think like one — tables, relations, fields. They are simultaneously proud of what they've built and anxious about what happens when it breaks.

“A teammate asked how they managed maintain operational data that's accurate enough to make real decisions from.”

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 Apollo SDR

A sales development rep or account executive at a B2B company of 20–300 people who runs outbound prospecting as a core job function. Apollo is their prospecting database, their sequencing engine, and their activity tracker. They use it every day. They've built sequences that work and sequences that don't, and they've learned the difference by watching reply rates. They're not sentimental about approaches that aren't working. They test, they iterate, they move on.

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

The Apollo Sales Development Rep

A sales development representative or outbound sales rep at a B2B company who uses Apollo as their prospecting command center. They build prospect lists from Apollo's database, enroll them in email sequences, track opens and replies, and try to book meetings. They send 50–200 outreach emails per day and know that personalization is the difference between a reply and the spam folder. They are a relationship builder working at volume, and they've developed an intuition for which prospects will respond and which won't.

“The shift was quiet.”

The Arc Browser Power User

A developer, designer, or technical knowledge worker who switched to Arc and reorganized their browser-based work around Spaces and Folders instead of horizontal tab strips. They had 40 tabs open in Chrome on a normal day. They were managing them by scrolling and guilt. Arc replaced the tab strip with something structural. They have opinions about it that they've refined over 8 months of use. The opinion is: it's better. The caveat is: it requires learning a new mental model that takes 3 weeks to stop fighting.

“The shift was quiet.”

The Asana Agency Project Manager

A project manager at a digital or creative agency juggling 6–12 active client projects at various stages simultaneously. Asana is their external brain — it holds everything they can't hold in their head, which is most of it. They've been through the Asana certification. They've built the templates. They've trained the team. They're still fighting the battle of getting everyone to actually update their tasks.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about team members who don't update their tasks, making the board a fiction in two weeks.”

The Asana Project Coordinator

A project coordinator, program manager, or PMO lead who uses Asana to keep cross-functional projects on track. They don't do the work — they make sure the work gets done. They manage timelines, dependencies, and status updates across teams that each have their own Asana projects, their own workflows, and their own definitions of "on track." They are the person in every meeting who asks "what's the status?" and "who owns this?" — and they need Asana to give them those answers without asking.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about portfolios that show project status but not the why — "at risk" doesn't explain the blocker in two weeks.”

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 Attio Revenue Operations Lead

A revenue operations lead or head of sales operations at a Series A–C startup who chose Attio because legacy CRMs either cost too much (Salesforce) or think too rigidly (HubSpot). They build custom objects, design pipeline views, and create automations that match how their team actually sells — not how a CRM template assumes they sell. They think in data models, not contact records. They've realized that a CRM is only as good as the data in it, and their primary job is making sure the data stays clean and the team actually uses the tool.

“It happened mid-workflow — the company is expanding from SMB to mid-market sales.”

The Basecamp Small Agency Owner

A small agency owner, studio founder, or remote team lead with 3–20 people who chose Basecamp because they were tired of configuring project management tools. Basecamp's opinionated structure — message boards, to-dos, schedules, docs, campfire — is not a limitation to them. It's the point. They didn't want to design a system. They wanted to use one. They've been on Basecamp for 2–6 years. They've recommended it to other agency owners who are drowning in Notion setups and Jira configurations. Some of them listened.

“A client project kicks off Monday.”

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 Cal.com Developer Scheduler

A developer, indie maker, or privacy-conscious professional who uses Cal.com because they either self-host it or value that they can. They were on Calendly and either hit a pricing ceiling, wanted customization Calendly doesn't allow, or made a deliberate decision about data ownership. Cal.com is open source. They can read the code. They can modify it if they need to. The fact that this is possible — even if they never do it — matters to them in a way that influences their tooling choices.

“It happened mid-workflow — they're building a product that includes embedded scheduling — customers can book time with their su.”

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 Calendly High-Volume Scheduler

A consultant, account executive, advisor, or service professional for whom scheduling external meetings is a daily operational task. They use Calendly because they calculated — consciously or not — that 20 minutes per meeting of back-and-forth email was adding up to hours per week. They now send a link. They feel slightly awkward about it the first time with each new contact. The other person always thanks them for it.

“The shift was quiet.”

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 Canva Non-Designer

A marketing coordinator, social media manager, small business owner, or teacher who is responsible for creating visual content and has no design training. They discovered Canva and it changed what was possible for them. They can now make things that look professional without calling a designer or spending three hours in PowerPoint. They are faster than they were. They are not as good as an actual designer. They know this and they've made peace with it.

“A teammate asked how they managed create content that looks polished enough to publish without a professional review.”

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 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 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 ClickUp Everything-App Operator

An operations manager, department head, or systems-minded project lead who chose ClickUp because they wanted one tool that could replace three. They were right that ClickUp could do this. They underestimated how long configuration would take. They have built a system that works well for them and is difficult to explain to new team members. They are aware that ClickUp's reputation for complexity is earned. They are also aware that the people who complain about it most haven't learned the difference between what's in the tool and what they actually need to turn on.

“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 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 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 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 ConvertKit Creator Monetizer

An online creator — YouTuber, course seller, coach, author, or educator — who has built an email list and uses ConvertKit to turn that audience into revenue. They chose ConvertKit because it was built for creators: the tagging system makes sense for how creators think about audience segments, the Creator Pro features align with their actual business model, and the community of ConvertKit users is full of people doing exactly what they're doing. They are building a creator business, not just an email list. They see their subscribers as an audience, not a database.

“They've just launched a new course.”

The Craft Personal Document Creator

A professional in the Apple ecosystem — Mac, iPad, iPhone — who uses Craft for everything from meeting notes to project proposals to personal journals. They chose Craft because it feels native to macOS and iOS in a way that Notion and Google Docs don't. They value beautiful typography, smooth block-based editing, and the ability to work offline on an airplane and sync when they land. They are a writer who cares about the writing environment, not just the output.

“The shift was quiet.”

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 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 Cursor AI-Native Developer

A software developer with 2–10 years of experience who switched to Cursor after a trial period and didn't go back. They've restructured how they code around the assumption that AI is in the loop. They write less boilerplate. They spend more time reviewing and directing than typing. They're faster on unfamiliar codebases than they've ever been. They're also developing opinions about when AI help hurts — about the kinds of errors that look right until they don't.

“The shift was quiet.”

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 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 Deel Global HR Manager

An HR manager, people ops lead, or COO at a company of 20–200 people that has hired internationally — contractors in one country, full-time employees in another. Before Deel, this involved a law firm, a local accountant, a foreign entity, and a spreadsheet of exchange rates. Deel collapsed that. They can now hire in a new country in days instead of months. They are not naive about the complexity they're offloading — they understand that Deel is doing what they used to do badly.

“They've found the right candidate for a senior engineering role.”

The Deel Global Team Manager

An operations lead, HR manager, or founder at a remote-first company who has team members across 5–20 countries. They use Deel because hiring internationally is legally complex and paying people across borders is operationally painful. They manage contracts, process payments, and handle compliance for contractors and full-time employees in countries they've never visited. They've learned that "hiring remotely" really means "learning employment law for every country you hire in." Deel handles the parts they can't.

“The shift was quiet.”

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 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 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 DocuSign Contracts Sender

A sales rep, account executive, or operations manager who sends 5–30 contracts per month for electronic signature. DocuSign is not their job — it's the thing they do at the end of their job. They want contracts signed as fast as possible because a signed contract is a closed deal or a cleared obligation. They did not design the templates they use. They sometimes modify them in ways that create problems they don't discover until someone calls.

“The shift was quiet.”

The Dovetail UX Researcher

A UX researcher or research ops manager at a company with a growing research practice. They've conducted enough studies that the insights are now a problem: they exist in documents, recordings, sticky notes, and people's memories. Dovetail is where they're consolidating that. They tag, they theme, they surface insights in a way that teams can find without having to ask a researcher. They believe the research repository is the infrastructure of a research-driven company. They're building it while also running new studies. It is a lot.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about research that gets done, presented, and forgotten — the insight graveyard problem 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 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 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 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 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 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 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 FigJam Product Team Facilitator

A product manager, design lead, or team facilitator at a product company who uses FigJam for team whiteboarding because their team already lives in Figma. They chose FigJam over Miro because the context switch is lower — design references, wireframes, and working files can be linked or embedded directly from Figma. They run planning sessions, retrospectives, decision workshops, and design crits on FigJam. Their team knows how to use it. This matters more than they expected it to.

“The shift was quiet.”

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 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 Figma Product Designer

A mid-to-senior product designer at a tech company with 3–8 years of experience. Figma is where they spend most of their working day — from rough explorations to polished specs. They work across a shared team library and collaborate with PMs in comments and engineers in dev mode. They are fast, opinionated about component architecture, and quietly frustrated by how the tools around Figma still slow everything down.

“A teammate asked how they managed move from concept to spec without losing fidelity at each stage.”

The Fly.io Edge Deployer

A backend developer or DevOps engineer who deploys applications on Fly.io because they need their app running close to users globally — not just served from a CDN, but actually computing at the edge. They've outgrown Heroku's simplicity, don't want AWS's complexity, and find Vercel too opinionated for non-Next.js workloads. Fly.io hits the sweet spot: Docker containers deployed globally with a CLI that feels developer-first. They're comfortable with infrastructure but don't want it to be their full-time job.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about stateful workloads at the edge (databases, volumes) have limitations that aren't always clear until production in two weeks.”

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

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 FullStory Behavioral Analytics PM

A senior product manager, digital experience lead, or data-savvy UX researcher at a company of 200–5,000 people where FullStory was purchased as a platform — not a point tool. They use it to answer questions that neither analytics dashboards nor individual session recordings can answer alone: what does the full behavioral pattern look like for users who churn? Where in the enterprise checkout flow do users consistently struggle? Which UI elements are generating frustration signals at scale? They work with data. They also watch sessions. Both inform the decision.

“The shift was quiet.”

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 Ghost Independent Publisher

An independent journalist, researcher, media entrepreneur, or content organization that chose Ghost because platform ownership matters to them. They're running a publication with a membership model — free and paid tiers, regular editorial content, and a direct relationship with readers they're not willing to cede to Substack's network effects or Beehiiv's operator framing. They are technically capable enough to run Ghost on managed hosting or self-host it. This was a deliberate choice. The people who choose Ghost have thought about the alternatives more carefully than most tool decisions require.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about theme customization that requires Handlebars knowledge most writers don't have in two weeks.”

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 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 GitHub Software Engineer

A software engineer with 3–10 years of experience who uses GitHub as the center of their development workflow. They push code, open PRs, review others' PRs, and track issues daily. They've developed strong opinions about what a good PR looks like and suffer quietly through colleagues who don't share them. They know GitHub deeply in some areas — git blame, actions, advanced search — and use the UI for everything else because the CLI is faster until it isn't.

“A teammate asked how they managed ship code with confidence that it's been reviewed and won't break things.”

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 GitLab DevOps Engineer

A DevOps engineer, platform engineer, or senior developer at a company that chose GitLab — often for self-hosting, compliance, or all-in-one platform reasons. They maintain the GitLab instance or the pipeline configurations that all other engineers depend on. They think in pipelines, stages, and artifacts. They've written `.gitlab-ci.yml` files that are 300 lines long and know every YAML key by memory. They've debugged a pipeline failure on a Friday evening. They have strong opinions about GitHub Actions versus GitLab CI that they will share if asked.

“The shift was quiet.”

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 Google Analytics Marketing Manager

A marketing manager or digital marketer at a company of 10–200 people who is responsible for understanding how the website is performing and why. They are not a data person. They've been through the GA4 migration and have not recovered emotionally. They know enough to navigate the interface but not enough to build custom reports without three tabs of documentation open. They check analytics several times a week and leave most sessions with more questions than answers.

“The VP of Marketing wants to know if the new landing page is performing better than the old one.”

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 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 Greenhouse In-House Recruiter

An in-house recruiter at a company of 100–1,000 people managing 5–15 open roles at any given time. Greenhouse is their operating system for hiring. They know it well. They also know all the ways their company uses it wrong — job stages that don't reflect reality, interviewers who don't submit scorecards, hiring managers who give verbal feedback in Slack instead of structured feedback in the system. They are the connective tissue of a hiring process held together by their own follow-up.

“The shift was quiet.”

The Greenhouse Recruiting Coordinator

A recruiting coordinator or in-house recruiter at a growing company who manages 15–40 open roles simultaneously. Greenhouse is their command center — every candidate, every interview, every offer lives there. They are the logistics engine of hiring: scheduling interviews across time zones, nudging hiring managers for feedback, and keeping candidates warm through what feels like an increasingly long process. They measure their success not in hires made but in process efficiency — time-to-fill, interview-to-offer ratio, candidate experience scores.

“A teammate asked how they managed keep candidate response times under 24 hours across all active roles.”

The Gusto Payroll Administrator

An office manager, operations person, or small business owner at a 5–50 person company who runs payroll through Gusto. They're not an HR professional — they're the person who ended up doing payroll because someone had to. They learned Gusto's interface, set up direct deposit, configured PTO policies, and now they run payroll every two weeks with the quiet anxiety of someone who knows that a payroll mistake means an employee doesn't pay their rent on time. They appreciate Gusto's simplicity but still double-check every run.

“A teammate asked how they managed run payroll accurately every cycle with minimal manual input.”

The Gusto Small Company HR Manager

An HR manager, office manager, or operations lead at a company of 10–75 people for whom payroll and benefits are one of many responsibilities, not the whole job. They run payroll twice a month. They onboard new hires. They manage benefits open enrollment once a year and feel mild panic every time. They chose Gusto because it was less terrifying than what came before it. They trust it, mostly, but payroll is the one area of their job where a mistake has immediate and personal consequences for real people.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about state tax registration requirements that surface after they've already hired in a new state in two weeks.”

The Harvest Freelance Time Tracker

A freelance designer, developer, consultant, or small agency owner who bills by the hour and uses Harvest to track every minute. They know that untracked time is unpaid time, and unpaid time is a silent business killer. They start timers when they begin work, stop them when they break, and review their timesheets weekly to make sure nothing slipped. They've built a system that balances accurate tracking with not letting the tool interrupt their flow. They are both the worker and the business.

“A freelance developer juggles three active clients.”

The Harvest Freelancer and Agency Owner

A freelancer, consultant, or small agency owner (2–15 people) for whom time is the product. They track hours against client projects and invoice from those hours. Harvest is where the financial reality of their business lives. They've learned that unbilled hours are lost revenue, that clients will dispute invoices without time entries to back them up, and that the difference between a profitable month and a break-even month is often the accuracy of their time tracking. They are disciplined about logging time — or they are trying to become disciplined about it.

“A teammate asked how they managed track time accurately enough that invoices are defensible and projects are profitable.”

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 Hex Collaborative Data Analyst

A data analyst or analytics engineer who uses Hex because it combines everything they used to do across 3–4 separate tools into one collaborative environment. They write SQL to pull data, Python to transform it, and build visualizations and dashboards — all in the same notebook. They share their work as interactive apps that stakeholders can explore without learning SQL. They've replaced Jupyter notebooks, Mode, and Google Sheets with Hex. They are the data person who makes data accessible to people who aren't data people.

“The marketing team asks: "Which campaigns drove the most pipeline last quarter?" The data analyst opens Hex, writes a SQL query to pull campaign data, joins it with pipeline data, and adds a Python cell to calculate attribution.”

The Hex Data Analyst

A data analyst or analytics engineer at a company with a modern data stack — dbt, Snowflake or BigQuery, and a growing demand from business stakeholders for self-service data access. They use Hex because Jupyter notebooks are hard to share and dashboards aren't flexible enough. Hex sits in the middle: code-first enough for real analysis, shareable enough that a PM can click through an interactive version without needing to run code. They build notebooks in Hex. Business people use the published apps. This is the workflow they've been trying to build for years.

“A teammate asked how they managed build analyses that colleagues can interact with without running code themselves.”

The Hotjar Session Watcher

A product manager, growth marketer, or UX designer at a company of 20–500 people who uses Hotjar to answer questions that quantitative analytics can't. They know their funnel. They know where users drop off. What they don't know is why. Session recordings are how they find out. They've watched hundreds of sessions. They've seen users rage-click on things that aren't buttons, scroll past CTAs without seeing them, and get confused by flows the team thought were obvious. Each one of these is a design decision waiting to happen.

“The checkout conversion rate dropped 2.”

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

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 HubSpot Sales Rep

A B2B sales rep or account executive who opens HubSpot 30+ times a day. They manage a pipeline of 20–80 active deals and are measured on close rate and revenue. They didn't pick HubSpot — their sales leader did — but they've gotten good at working within it. They know which shortcuts save time and which required fields are slowing them down. They log activities because they have to, not because they want to. They care about closing deals, not about CRM hygiene.

“The shift was quiet.”

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 Intercom Support Lead

A customer support lead or manager who runs their team's entire operation through Intercom. They built the macro library, set up the routing rules, and configured the chatbot — all while also jumping into the inbox during peak hours. They measure first response time, resolution time, and CSAT obsessively. They believe in automation but hate when it makes customers feel like nobody's listening. They are the bridge between what the product team ships and what customers actually experience.

“A teammate asked how they managed keep first response time under 5 minutes during business hours.”

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 Jira-Burdened PM

A product manager or engineering team lead at a software company who runs sprints in Jira. They did not set up the Jira instance they work in — it was configured by someone who left 18 months ago, and the workflow has accumulated technical debt as surely as the codebase has. They know what they need Jira to do. Getting it to do that is a separate problem.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about ticket statuses that don't map to how engineering actually works in two weeks.”

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 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 Linear Startup Engineer

A software engineer at a startup of 10–100 people who has used Jira and has Opinions. They switched to Linear — or advocated for switching — because it's fast, opinionated, and built for people who care about the work rather than the process around it. They use Linear every day to track their own work, manage issues, and follow the work of their small team. The keyboard shortcuts aren't optional to them — they're the point.

“They're back from a two-day sprint on a difficult bug.”

The Linear Product Manager

A product manager at a 20–200 person startup who moved to Linear because Jira was too heavy and Notion boards weren't structured enough. They work at the initiative and project level while their engineers work at the issue level. They need to see the forest while the team sees the trees. They love Linear's speed and keyboard shortcuts but struggle to get the strategic views they need without building custom views for every stakeholder meeting.

“It happened mid-workflow — the CEO asks "are we on track for the Q2 launch?" The PM opens Linear, checks 4 projects across 2 teams, counts completed vs.”

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 Liveblocks Collaboration Developer

A frontend or full-stack developer at a SaaS company whose product needs real-time collaboration — multiple users working in the same document, canvas, or interface simultaneously. They've looked at building it themselves. The WebSocket infrastructure, the conflict resolution, the presence system, the storage — it's 3–6 months of work that isn't their product. They chose Liveblocks to compress that into a week. They are now the person at their company who knows how Liveblocks works. This is a niche form of expertise they didn't expect to develop.

“The shift was quiet.”

The Liveblocks Real-Time Developer

A frontend developer who needs to add real-time collaboration to an existing app — live cursors, presence indicators, shared document editing, or collaborative whiteboards. They chose Liveblocks because building WebSocket infrastructure from scratch is a project in itself, and they need to ship the feature, not the infrastructure. They understand React, they understand state management, and Liveblocks extends those mental models to multiplayer. They are building the "Google Docs" experience for their product.

“It happened mid-workflow — the developer is adding collaborative editing to a project management tool.”

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 Logseq Local-First Knowledge Builder

A researcher, developer, writer, or privacy-conscious knowledge worker who chose Logseq because their notes are plain `.md` files in a folder they control — not in a proprietary database, not in someone else's cloud. They care about data ownership in a specific way: not paranoia, but principle. They've watched tools sunset, pricing change, and export options degrade. Their Logseq graph syncs to iCloud or a private git repository. It will exist regardless of Logseq's future. They've also genuinely internalized the outliner-first paradigm. They think in bullets that can be linked and referenced anywhere else in the graph.

“They're synthesizing research for a paper.”

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 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 Mailchimp Small Business Owner

A small business owner, solopreneur, or creator who sends a regular email to their list — weekly newsletter, promotional email, customer announcement. They are not a marketer by training. They set up Mailchimp because it was recommended and free. They've been using it for 1–4 years. They care about their list and think of it as their most direct connection to their customers. They are not fully sure what open rates mean in a post-Apple-MPP world but they still check them because it's the only signal they have.

“A teammate asked how they managed send emails their list looks forward to, not emails that get unsubscribed from.”

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 Make Power Automator

An operations lead, automation specialist, or technical non-developer who moved to Make (formerly Integromat) after hitting the ceiling on Zapier. They know what they wanted to build and Zapier's linear trigger-action model couldn't do it: conditional branches, iterators, error handlers, multi-route flows. Make could. They learned Make. They have built things in Make that non-technical people would describe as software and technical people would describe as creative. They exist in the middle of the developer-to-non-developer spectrum and they've built a practice there.

“A client needs a system: when a new deal is created in HubSpot above a certain value, create a proje.”

The Maze Unmoderated Research Lead

A UX researcher or product designer at a company where research is valued but researcher time is scarce. They use Maze to run tests they can't run fast enough with moderated sessions. They design the test, connect the Figma prototype, send the link, and come back to results in 24–72 hours. They know unmoderated testing misses the nuance of moderated sessions. They also know that running 8 moderated sessions takes 2 weeks of scheduling and 2 days of synthesis. Maze takes 2 hours to set up and 1 hour to analyze. They're using the right tool for the question.

“A teammate asked how they managed get directional usability signal fast enough to influence a design decision.”

The Maze UX Research Automator

A UX researcher or product designer who uses Maze to test prototypes before they go to development. They run unmoderated usability tests where participants interact with Figma prototypes while Maze captures click paths, task success rates, and misclick patterns. They chose Maze because moderated testing doesn't scale — they can't schedule 50 individual sessions for every design decision. They need data, not opinions, and they need it in days, not weeks.

“A teammate asked how they managed test prototypes with 20–100 participants without scheduling individual sessions.”

The Midjourney Visual Creator

A creative professional — designer, art director, marketer, or content creator — who has integrated Midjourney into their production workflow. They don't generate random images for fun; they craft prompts with precision to produce specific visual outcomes: hero images for landing pages, mood boards for brand development, concept art for product pitches, and social media visuals. They've developed a prompt vocabulary that gets consistent results. They understand that AI art isn't "pushing a button" — it's iterating, refining, and curating from dozens of generations.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about consistent brand characters and specific product representations are still unreliable in two weeks.”

The Midjourney Creative Director

A creative director, art director, or senior designer who adopted Midjourney after realizing it was changing their concept phase. They use it to generate reference material, explore visual directions, and produce images that would previously have required a stock license, a photographer, or a two-week illustration commission. They have strong prompt craft. They know what they're doing. They also know the tool's failure modes and work around them. They do not use it to replace their judgment — they use it to accelerate the point at which judgment can be applied.

“It happened mid-workflow — a campaign needs 12 concept images for a client presentation in two days.”

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 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 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 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 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 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 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 Monday.com Team Lead

A team lead or department manager at a 30–200 person company who chose Monday.com because it looked simple enough that their team would actually use it. They set up the boards, configured the automations, and built the views. Now they spend 20 minutes every morning making sure the board reflects reality. They are the bridge between the team's actual work and the executive's need for status updates. They don't love project management tools, but they love knowing where things stand.

“It happened mid-workflow — the team lead sets up a sprint board with automations: when a task moves to "In Review," it notifies the reviewer and updates the deadline.”

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 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 Calendar Unified Planner

A founder, PM, or knowledge worker who lives in Notion and has always felt the calendar app sitting separately as a second system that doesn't talk to the first. They adopted Notion Calendar because the promise — their calendar and their Notion workspace, unified — is the thing they've wanted for years. They're still calibrating how much of that promise is real. The answer is: more than Google Calendar, not yet everything they imagined.

“The shift was quiet.”

The Notion Second-Brain Builder

A solo founder, PM, or highly organized individual contributor who has made Notion the center of their work life. They have a workspace that would take three hours to explain to someone new. They've built custom dashboards, linked databases, and templates they're genuinely proud of. They've also started from scratch twice after a system got too complex to maintain. They believe the perfect Notion setup is always two weekends away.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about performance on large databases — the lag is a betrayal in two weeks.”

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 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 Obsidian PKM Builder

A researcher, writer, software developer, or knowledge worker who has built their second brain in Obsidian and means it. They write in Markdown. They link notes intentionally. They have a vault structure they've iterated on at least twice. They use the graph view occasionally, for the pleasure of seeing their thinking made visible, not because it's the most useful view. They've installed 8–20 plugins. They have strong opinions about the right way to take notes, opinions that evolved over two years of using the wrong way.

“A teammate asked how they managed capture ideas in a format that connects them to related ideas automatically.”

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 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 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 Perplexity AI-Native Searcher

A researcher, analyst, consultant, or curious professional who started using Perplexity for quick lookups and gradually shifted most of their search behavior to it. They value citations. They appreciate the synthesized answer more than a list of links they have to open and read. They trust it for most things. They verify independently for decisions where being wrong has consequences. They've tried to explain why they prefer it to people who use Google and have not fully succeeded because the difference is in the feel of the first answer, which doesn't translate to a verbal description.

“It happened mid-workflow — they're researching a niche regulatory question for a client: the current status of SEC rules around.”

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

The Photoshop Production Designer

A graphic designer — in-house or agency — who uses Photoshop as their primary production tool for image work. They've been in Photoshop for 5–15 years and work with the efficiency of someone who knows exactly where everything is and what everything does. They don't explore menus. They use shortcuts. Their workspace is a system they've tuned. Photoshop is slow sometimes and they've learned to work around it the way you work around a colleague's habits — with patience and workarounds they've stopped noticing.

“The shift was quiet.”

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 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 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 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 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 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 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 QuickBooks Small Business Owner

A small business owner — a contractor, consultant, retailer, or service business — doing their own bookkeeping in QuickBooks because they can't yet justify what an accountant costs. They are not a numbers person by nature. They are running QuickBooks because they were told they had to, not because they wanted to. They feel mild anxiety every time they open it and have not reconciled their accounts in two months.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about transactions that categorize wrong and silently corrupt their books 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 Ramp Finance Manager

A finance manager, controller, or CFO at a company of 20–300 people who adopted Ramp to eliminate the expense report process that everyone hated and nobody trusted. They issue cards. They set limits. They receive receipts automatically from employees who forward a text message or take a photo. They close the books faster. They've calculated how many hours per month expense reports used to consume and they don't miss a single one of them. They are the person at the company who is most enthusiastic about Ramp.

“A teammate asked how they managed close the books faster by eliminating the expense report chase.”

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 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 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 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 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 Replit Non-Traditional Builder

A student, career changer, or self-taught developer who is building real things before they've mastered the full developer toolchain. They use Replit because it removes the setup. There's no local environment to configure, no PATH to fix, no version conflicts. They open a browser, pick a language, and the environment exists. They have learned more by shipping things than by completing tutorials. They have strong momentum. They have significant gaps. This is not a problem — it's a developmental stage.

“It happened mid-workflow — they're building a personal finance tracker.”

The Resend Transactional Email Developer

A full-stack or backend developer who needs to send transactional emails — password resets, welcome emails, order confirmations, notifications — from their application. They chose Resend because the developer experience felt like it was designed for someone who writes code, not someone who uses a drag-and-drop email builder. They write their email templates in React. The API is simple enough that they memorized it. They are not thinking about email infrastructure. They are thinking about their product.

“The shift was quiet.”

The Retool Internal Tools Developer

A full-stack developer or engineering lead tasked with building internal tools — admin dashboards, customer support panels, operations consoles. They chose Retool because writing React apps for internal use felt wasteful, but they still need to write SQL, connect APIs, and handle auth. They are a developer using a low-code tool, which means they appreciate the speed but feel the constraints more acutely than a no-code user would.

“The support team needs a tool to look up customer accounts, view their subscription history, and issue refunds.”

The Retool Internal Tools Developer

A full-stack or backend developer at a startup or scale-up who has been asked — once too many times — to pull data from the database for a non-technical teammate. They discovered Retool as a way to give those teammates self-service access without giving them direct database access. They've built 3–8 internal tools: an admin panel, an operations dashboard, a customer lookup tool, and at least one thing they built in a weekend that the whole company now depends on.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about retool queries that are fast in development and slow in production on real data volumes in two weeks.”

The Rippling HR Administrator

An HR administrator, people ops manager, or office manager at a 50–500 person company who manages Rippling as their all-in-one HR platform. They handle onboarding (IT provisioning, payroll setup, benefits enrollment), offboarding (access revocation, final paycheck, COBRA), and everything in between. They chose Rippling because the alternative was stitching together 5 separate tools. They appreciate the unified system but have learned that "all-in-one" means "all the complexity in one place." They are the person who makes sure new hires have a laptop, a paycheck, and health insurance on day one.

“It happened mid-workflow — a new engineer starts Monday.”

The Rippling HR/IT Admin

An HR manager or IT admin — sometimes the same person — at a company large enough that onboarding a new employee involves both an HR workflow and an IT workflow, and small enough that the same person owns both. They chose Rippling because it promised to unify those two workflows into one. When it works — when a new hire's laptop ships, their apps provision, and their payroll is set up in a single flow — it delivers on that promise in a way nothing else does. When it doesn't work, it's complicated in proportion to how much it was supposed to simplify.

“An employee is leaving in two weeks.”

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

A designer or creative developer who builds animations that respond to state, not just ones that play and loop. They discovered Rive when they realized that Lottie was great for playing animations but couldn't handle the "and then when the user clicks, it does this" requirement. Rive's state machine changed their practice. They now build animations that are interactive first — hover states, press states, loading-to-success transitions, character rigs that respond to game input. They are comfortable in both the design and the runtime.

“It happened mid-workflow — they're building a loading animation for a fintech app.”

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 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 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 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 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 Salesforce Admin

A business analyst, operations manager, or former power user who became the Salesforce admin because they were the person who understood the data best. They don't write code — they build Flows, create reports, manage permissions, and configure the org to match how the business actually works. They have 3–5 Trailhead certifications and a bookmark folder of Salesforce Help articles they reference weekly. They are simultaneously the most important and most under-appreciated person in the revenue organization.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about flow Builder that's powerful but crashes on complex flows and has limited debugging in two weeks.”

The Reluctant Salesforce User

An enterprise sales rep at a company with 200+ employees who did not choose Salesforce. It was there when they arrived. They've been trained on it twice. They use about 20% of its features and have found workarounds for everything else. They log activity because their manager checks. They update opportunities because forecasting requires it. They do not believe Salesforce makes them better at sales. They believe it makes their manager better at measuring sales.

“The shift was quiet.”

The Sanity Content Architect

A developer or content architect who uses Sanity because they think about content as structured data, not pages. They design content models that serve web, mobile, email, and API consumers from a single source. They've built custom studios, created real-time collaborative editing environments, and used GROQ to query content in ways traditional CMS query languages can't express. They are the architect of the content layer, and they treat content modeling with the same rigor as database schema design.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about customizing the Studio deeply requires significant React knowledge, raising the bar for non-senior developers in two weeks.”

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 Segment Data Architect

A data engineer or analytics engineer who manages Segment as the central event routing layer. Every product event — page views, clicks, purchases, signups — flows through their Segment workspace before reaching the data warehouse, analytics tools, and marketing platforms. They are the plumber of the data stack. Nobody thanks them when data flows correctly, but everyone notices when it doesn't. They think in events, properties, and destinations. They've learned that the hardest part of data infrastructure isn't moving data — it's keeping it clean.

“The shift was quiet.”

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 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 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 Shopify App Developer

A developer or small agency building Shopify apps — either custom apps for specific merchants or public apps for the Shopify App Store. They know Liquid well enough to customize themes and the Admin API well enough to build features merchants ask for. They spend equal time writing code and reading Shopify's changelog to see what broke or changed. They've been through at least one major API version migration and still have scars.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about aPI versioning deadlines that force migration work on their timeline, not the developer's in two weeks.”

The Shopify DTC Brand Owner

A founder or owner of a direct-to-consumer brand doing $10K–$500K in annual revenue on Shopify. They launched the store themselves, chose the theme themselves, and manage it themselves — occasionally with help from a contractor they can barely afford. They know their products, their customers, and their margins. They do not know why their abandoned cart rate is what it is or how to fix it, but they know it matters.

“It's November 8th.”

The Slack-Drowning Knowledge Worker

A full-time knowledge worker — marketer, PM, ops, customer success — at a company large enough that Slack has become the ambient noise of their workday. They didn't design the channel structure they live in. They inherited it. They have 12 unread DMs, are mentioned in 3 channels they rarely check, and have muted so many channels that important things occasionally slip through the cracks. They're not bad at their job. They're bad at Slack because Slack has become its own job.

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

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

A web designer or creative developer who uses Spline to add 3D to their web projects without the learning curve of Blender or Cinema 4D. They create 3D hero sections, interactive product visualizations, animated icons, and immersive landing pages. They are a designer who crossed into the third dimension. They appreciate that Spline runs in the browser, exports to the web natively, and feels like a design tool rather than a 3D modeling application. They are the person making websites feel like they have depth.

“A SaaS company wants a landing page that stands out.”

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 Squarespace Small Business Owner

A photographer, therapist, consultant, restaurant owner, or small retailer who built their own website on Squarespace because it was the best option they could manage independently. They are not a developer. They do not want to be. They want a website that looks professional, is easy to update, and doesn't require a support ticket to change the menu. They've succeeded at this mostly. There are two things on their site that have been wrong for three months because fixing them would require understanding something they don't want to learn.

“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 Storybook Frontend Developer

A frontend developer or design systems engineer at a company with a shared component library. Storybook is where they develop components in isolation, document their props and variants, and give designers a place to review and interact with components without pulling a branch. They've set up Storybook, they've configured it, they've written stories for 40–150 components. They're the person who knows where Storybook falls short and stays anyway because the alternative is worse.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about storybook configuration that fights the build tooling when the team's setup is non-standard in two weeks.”

The Stripe Platform Builder

A technical founder or senior developer building a platform where money flows between multiple parties — a marketplace, a SaaS with payouts, or a platform that onboards sellers. They chose Stripe because the API is good, but they've discovered that Stripe Connect is a different animal entirely. They understand payment intents but still get confused by the relationship between accounts, charges, and transfers. They are building financial infrastructure and it keeps them up at night.

“The first time a seller on their platform got paid automatically — money flowed from buyer to platform to seller with the correct fee split, no manual step, no CSV export.”

The Stripe Integration Developer

A full-stack or backend developer at a startup or mid-size company who built and maintains the Stripe integration for their product. They integrated Stripe once — it took a week in dev, two days in staging, and then went live and mostly just worked. Now they're the person who gets the Slack message when a payment fails. They know the Stripe docs well enough to find what they need. They have a complicated relationship with webhooks.

“A teammate asked how they managed understand what happened when a payment fails before the customer reaches support.”

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 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 Supabase Indie Hacker

A solo developer or indie hacker building a SaaS product where Supabase is the entire backend. They chose Supabase because it gives them Postgres, auth, storage, and real-time out of the box — and they can ship their MVP in a weekend instead of a month. They write SQL directly, use Row Level Security because they have to, and treat the Supabase dashboard as their admin panel. They are building a business alone and Supabase is the co-founder that handles the backend.

“The shift was quiet.”

The Supabase Full-Stack Developer

A full-stack developer or indie hacker who uses Supabase as their backend and thinks of it as their database, their auth layer, their file storage, and their API layer at once. They came from Firebase and wanted Postgres. Or they came from setting up their own Postgres and wanted the tooling. Either way they arrived at Supabase and found a backend they could move on from thinking about. They write SQL fluently. They use Row Level Security. They are deeply comfortable in the Supabase dashboard. They have strong feelings about their Supabase tables.

“The shift was quiet.”

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 Superhuman Executive

A founder, executive, investor, or senior individual contributor for whom email is a primary work surface and inbox zero is not aspirational — it is the operating condition required to function. They use Superhuman because they did the math: the time saved per email multiplied by 200 emails per day is real money. They have strong keyboard habits. They were already fast at email. Superhuman made them faster. They will tell you about it if you ask, and sometimes if you don't.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about mobile experience that can't fully replicate the keyboard-driven speed of desktop in two weeks.”

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 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 Todoist Productivity System Builder

A knowledge worker — often a freelancer, consultant, or senior IC — who has turned Todoist into a personal operating system. They don't just track tasks; they've built a system. GTD-inspired projects, context-based labels, custom filters for different energy levels and time blocks. They have recurring tasks for weekly reviews, monthly planning, and annual goal-setting. They've tried every productivity app and keep coming back to Todoist because it's fast, reliable, and doesn't try to be more than a task manager.

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

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 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 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 Typeform Research and Marketing User

A UX researcher, marketer, or operations person who uses Typeform because they've seen what happens to completion rates when you use Google Forms. They care about the quality of the responses they collect — which means they care about the experience of filling in the form. They design forms deliberately: question order, logic branches, conversational tone. They know their completion rate. They have an opinion about it.

“The shift was quiet.”

The Typeform Survey Designer

A UX researcher, product manager, or marketer who chooses Typeform over Google Forms because the survey experience matters. They've learned that completion rate is the most important metric for a survey, and completion rate is a design problem. They craft surveys that feel like conversations: one question at a time, conditional logic, thoughtful copy. They spend as much time on the question experience as they do on the question content. They are the person who says "we can't just send a Google Form — that sends a message about how much we value their feedback."

“The shift was quiet.”

The Vercel Agency Deployer

A developer at a web agency or a freelancer who deploys and manages 20–100 client projects on Vercel. They chose Vercel because the developer experience is excellent and Next.js deploys are zero-config. But managing 50 projects across 15 clients has turned deployment into project management. They spend as much time in the Vercel dashboard organizing teams and domains as they do writing code. They know every deployment preview URL is a demo link, and they've sent the wrong preview to the wrong client exactly once.

“A client emails asking why their site is showing an old version.”

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 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 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 Webflow No-Code Designer

A designer — visual, brand, or marketing — who uses Webflow to design and build production websites without relying on a developer. They came from Figma or Sketch and discovered that the gap between design and the live site was where everything good went to die. Webflow closed that gap. They have strong opinions about how websites should look and work, and Webflow lets them act on those opinions directly. They are faster in Webflow than any developer who doesn't know the design would be.

“It's launch week for a new product campaign.”

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 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 Wix First-Time Website Owner

A small business owner, freelancer, event organizer, or individual who needed a website and chose Wix because they wanted to design it themselves. They are not technical. They have no interest in becoming technical. They evaluated Squarespace and liked Wix's drag-and-drop freedom more — the ability to place anything anywhere without template constraints. They've built a website they're proud of. It has some inconsistencies that they can't see but a designer would notice immediately. This is fine. The website does what they need it to do.

“The shift was quiet.”

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 Zapier Power Automator

A RevOps lead, marketing ops specialist, or operations manager who has become their company's automation architect without the title. They've connected 15–30 apps through Zapier and built workflows that the entire company depends on but nobody else understands. They started with simple two-step Zaps and now build multi-step workflows with filters, paths, formatters, and webhooks. They are the person who gets called when "something stopped working" — which means a Zap failed and nobody noticed until the damage was done.

“A teammate asked how they managed build multi-step automations that handle edge cases without breaking.”

The Zapier Non-Technical Automator

An operations coordinator, marketing manager, or executive assistant who discovered Zapier and spent an afternoon automating a task that had been eating 45 minutes of their week. That experience was formative. They now have 12 Zaps running, three of which they fully understand, one of which they're afraid to touch, and one that they know has been broken for two weeks but the fix intimidates them. They are not a developer. They are the closest thing to one in their department.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about error messages that tell them a Zap failed but not what to do about it in two weeks.”

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