Persona Library
Community-sourced UX research

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

Deep persona profiles for the tools that run modern work. Community-validated. Exportable. Open for contribution.

72
loomAPP-140
3 comments

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.

Aha

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

loomAPP-046
3 comments

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.

Aha

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

zoomAPP-120
2 comments

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.

Aha

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

zoomAPP-092
3 comments

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.

Aha

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

calcomAPP-008
6 comments

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.

Aha

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

calcomAPP-189
4 comments

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.

Aha

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

vercelAPP-124
3 comments

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.

Aha

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

vercelAPP-087
6 comments

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.

Aha

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

gitlabAPP-095
4 comments

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.

Aha

The shift was quiet.”

flyioAPP-154
4 comments

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.

Aha

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

flyioAPP-030
4 comments

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.

Aha

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

apolloAPP-194
3 comments

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.

Aha

The shift was quiet.”

clickupAPP-013
4 comments

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.

Aha

The shift was quiet.”

riversideAPP-071
3 comments

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.

Aha

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

replitAPP-067
4 comments

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.

Aha

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

retoolAPP-069
4 comments

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.

Aha

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

craftAPP-017
3 comments

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.

Aha

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

deelAPP-180
4 comments

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.

Aha

The shift was quiet.”

squarespaceAPP-077
4 comments

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.

Aha

The shift was quiet.”

fullstoryAPP-197
3 comments

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.

Aha

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

midjourneyAPP-172
3 comments

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.

Aha

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

pitchAPP-175
3 comments

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.

Aha

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

squarespaceAPP-156
4 comments

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.

Aha

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

miroAPP-050
6 comments

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.

Aha

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

apolloAPP-003
5 comments

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.

Aha

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

posthogAPP-062
5 comments

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.

Aha

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

amplitudeAPP-002
2 comments

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.

Aha

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

mintlifyAPP-183
4 comments

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.

Aha

The company ships a new API endpoint.”

mixpanelAPP-051
6 comments

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.

Aha

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

canvaAPP-010
6 comments

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.

Aha

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

mazeAPP-182
4 comments

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.

Aha

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

resendAPP-068
5 comments

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.

Aha

The shift was quiet.”

cursorAPP-018
6 comments

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.

Aha

The shift was quiet.”

githubAPP-033
5 comments

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.

Aha

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

jiraAPP-121
4 comments

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.

Aha

The shift was quiet.”

pitchAPP-061
3 comments

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.

Aha

An investor meeting is in 48 hours.”

riveAPP-102
4 comments

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.

Aha

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

gitlabAPP-145
4 comments

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%."

Aha

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

makeAPP-169
4 comments

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.

Aha

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

mondayAPP-139
4 comments

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.

Aha

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

webflowAPP-089
3 comments

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.

Aha

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

liveblocksAPP-045
4 comments

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.

Aha

The shift was quiet.”

fullstoryAPP-108
6 comments

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.

Aha

The shift was quiet.”

sentryAPP-094
6 comments

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.

Aha

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

canvaAPP-122
4 comments

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.

Aha

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

wixAPP-174
4 comments

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.

Aha

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

perplexityAPP-058
4 comments

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.

Aha

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

roamAPP-098
2 comments

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.

Aha

They're writing an essay about institutional memory.”

clerkAPP-012
5 comments

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.

Aha

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

sentryAPP-136
4 comments

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.

Aha

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

stripeAPP-079
3 comments

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.

Aha

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

shopifyAPP-075
5 comments

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.

Aha

It's November 8th.”

beehiivAPP-007
6 comments

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.

Aha

They're in the monthly business review.”

gustoAPP-037
6 comments

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.

Aha

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

datadogAPP-019
4 comments

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.

Aha

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

deelAPP-020
5 comments

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.

Aha

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

heightAPP-111
4 comments

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.

Aha

It happened mid-workflow — sprint planning is Monday.”

storybookAPP-078
6 comments

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.

Aha

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

pagerdutyAPP-103
3 comments

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.

Aha

The shift was quiet.”

retoolAPP-133
4 comments

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.

Aha

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

pendoAPP-057
4 comments

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.

Aha

A major new feature shipped three weeks ago.”

craftAPP-185
4 comments

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.

Aha

The shift was quiet.”

splineAPP-101
3 comments

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.

Aha

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

gustoAPP-178
4 comments

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.

Aha

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

wixAPP-090
4 comments

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.

Aha

The shift was quiet.”

zapierAPP-123
4 comments

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.

Aha

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

basecampAPP-106
6 comments

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.

Aha

A client project kicks off Monday.”

gitbookAPP-104
6 comments

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.

Aha

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

cursorAPP-135
4 comments

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.

Aha

The shift was quiet.”

datadogAPP-126
3 comments

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.

Aha

The shift was quiet.”

substackAPP-149
4 comments

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.

Aha

The shift was quiet.”

framerAPP-146
4 comments

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.

Aha

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

Recognize yourself in one of these?

Every field in every persona can be confirmed, corrected, or extended by real users. Your lived experience is more accurate than any researcher's archetype.

+ Contribute to a persona