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

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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 Kajabi Course Creator

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

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

The Logseq Academic Researcher

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

“The shift was quiet.”

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