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

The Riverside Remote Podcast Host

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

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

The Hotjar UX Researcher

A UX researcher, product designer, or growth PM who uses Hotjar as their window into real user behavior. They watch session recordings to understand confusion, analyze heatmaps to validate layout decisions, and run micro-surveys to capture user sentiment in context. They are the person on the team who says "let me check what users are actually doing" before anyone makes a design decision based on assumptions. They think in user journeys, not funnels.

“The shift was quiet.”

The 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 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 Jira Engineering Manager

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

“The shift was quiet.”

The Descript Podcast Producer

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

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

The Loom Async Communicator

A product manager, engineering lead, or designer working on a remote or distributed team who realized that most meetings could be a Loom. They record 5–15 looms per week — product updates, code walkthroughs, design feedback, project kickoffs. They've developed a recording style: concise, screen-shared, with their face in the corner. They are an async communication evangelist who believes the 30-minute meeting is a relic of co-located work.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about video organization becomes a mess — finding a specific loom from three months ago requires remembering the exact title in two weeks.”

The Dovetail UX Researcher

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

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about research that gets done, presented, and forgotten — the insight graveyard problem in two weeks.”

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

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

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