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

The Asana Agency Project Manager

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

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

The Basecamp Small Agency Owner

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

“A client project kicks off Monday.”

The Height Engineering Team Lead

An engineering team lead or technical PM at a company of 20–150 people who evaluated Linear and wanted more — more project hierarchy, more cross-functional visibility, more flexibility for non-engineering teams to work alongside engineering in the same tool. They chose Height. They're building their system in it. They like that it feels like a tool built by people who understand engineering workflows, not a project management tool that engineering is expected to tolerate. They're still learning the edges of it.

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

The 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 Height Autonomous Project Tracker

A product team lead or engineering manager at a startup who chose Height because it promised what every PM secretly wants: a project tracker that maintains itself. They use Height's AI features to auto-triage bug reports, suggest task labels, and identify duplicate issues. They still do the strategic work — prioritization, sprint planning, roadmap decisions — but the administrative overhead of keeping the tracker clean is lower than with Jira or Linear. They are cautiously optimistic about AI in project management — it works 75% of the time, and the 25% it doesn't requires less effort to fix than doing it all manually.

“A teammate asked how they managed reduce the time spent on task triage, labeling, and organization by 50% with AI assistance.”

The Asana Project Coordinator

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

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

The ClickUp Everything-App Operator

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

“The shift was quiet.”

The Jira-Burdened PM

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

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

The Monday.com Team Lead

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

“Their team has just absorbed a new function.”

The Ramp Finance Controller

A finance controller, VP of Finance, or head of accounting at a 50–500 person company who chose Ramp because they were tired of chasing receipts, manually categorizing expenses, and closing the books a week after month-end. They manage corporate cards, set spend policies, and review transactions. They appreciate Ramp's automation but know that "automated" still means they're the one who catches the exceptions. They are the financial guardrail of the company.

“It happened mid-workflow — month-end arrives.”

The 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 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 Contentful Headless CMS Developer

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

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

The 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 Ramp Finance Manager

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

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

The Vercel Agency Deployer

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

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

The Dropbox Cross-Functional File Sharer

A project manager, creative director, or department lead at a company that produces large files — design assets, video, documents, presentations — that need to move between internal teams and external partners. They use Dropbox because it works for people who aren't on their company's Google or Microsoft stack. It's the lowest-friction way to get a 2GB folder to a client or vendor who uses a PC, a Mac, or a Linux box, and doesn't have access to their internal SharePoint.

“A client has requested all source files from a project completed eight months ago.”

The Todoist GTD Practitioner

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

“It's Sunday evening.”

The Liveblocks Real-Time Developer

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

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