Earkeep for UX researchers

Earkeep is an always-on meeting transcriber that captures every user interview, debrief, and stakeholder readout the moment it happens, entirely on your device, so turning what participants said into evidence a product team will act on takes hours instead of days.

The goal this page is built around

A UX researcher's job isn't running sessions. It's turning what users actually said into evidence a product team will act on, fast enough that the decision hasn't already been made without them. Every section below comes back to that: capture that doesn't change how participants behave, transcripts the moment a session ends, and synthesis time given back to actual analysis.

Synthesis, not sessions, is the bottleneck

Researchers can run the interviews. It's everything after that piles up: "i can run about 6 or 7 a week no problem. it's the transcribing, tagging, pulling themes, then turning all of it into something a PM will actually read instead of skim is what i'm finding difficult… once we crossed maybe 30 sessions a month the manual coding just fell apart."

That's a familiar week: three to seven interviews or usability sessions, debriefs right after each one, stakeholder kickoffs and readouts, team syncs, and for consultants, workshops and field studies on top. One researcher described wrapping 10 interviews in two days and then "manually tagging transcripts in Google Docs and it's pretty painful." A research lead put a number on what gets lost: one researcher on the team spends 6 to 8 hours a week manually tagging and coding transcripts, while feedback from Slack, internal meetings, and tickets "just doesn't get captured at all," leaving the team working from maybe 15 percent of actual customer voice.

Two more pains sit underneath the time problem.

A recorder on the table changes the room. "the room does change a bit when there's a phone or recorder sitting there. People get a little more careful. I get more aware that I'm 'recording a meeting' instead of just having a conversation." That's a hit to the very data the session exists to collect.

Transcripts alone lose signal. "A participant might say they like a feature but when you watch the recording you notice a long pause before the answer… None of that really shows up in the transcript." Researchers end up going back to the source anyway, which means what's kept has to be findable and safe to keep.

How always-on capture fixes this

Earkeep listens continuously to mic and system audio, without a start button and without a bot joining the call. There is nothing on the table to make a participant more careful, and nothing to forget to start before the session goes ahead.

  • Nothing to configure per session. The interview, the debrief you do right after it, and the hallway follow-up an hour later are all already in the day's transcript. You mark the span that was the actual research session after the fact, on a timeline.
  • Calendar auto-spans for scheduled sessions. Connect Google Calendar, Apple Calendar, Outlook, or any ICS calendar URL, and a scheduled user interview starts and ends its own span automatically.
  • Transcribed by the time the session ends. Whisper or Parakeet models run locally and transcribe as the audio comes in, so there's no transcription queue to wait on before synthesis can start.

The 6 to 8 hours a week of manual tagging becomes pointing an agent at a month of sessions and asking for themes, direct quotes, and contradictions, while staying in the loop on what it surfaces rather than trusting it blind.

Local processing answers the consent question honestly

Consent is not an abstraction for researchers. It's a real professional anxiety: "I was so sure I checked a participant's consent form prior… Well, the session went ahead," and others ask whether a verbally agreed but unsigned form compromises a study. Remote research adds protecting participant privacy across platforms and managing data security for recordings to the list of things a researcher has to answer for.

Earkeep's mechanism is specific, not a vague privacy claim: audio is transcribed only in memory and is never written to disk, never uploaded to a server, never sent to a third-party transcription API. There is no cloud copy of a participant's voice sitting on someone else's infrastructure waiting to be subpoenaed, breached, or simply mishandled. The resulting transcripts are plain text files on your disk that you control outright: you can review them, redact them, or delete a specific participant's session entirely.

That is a stronger data-handling story than any cloud research repository can offer, because there's no upload step for anything to go wrong at. It does not replace informed consent: capturing a session, local or not, still requires telling participants they're being recorded and getting their agreement, the same as with any recorder or platform transcript. Earkeep changes what happens to the recording once you have consent, not whether you need it.

Workflow: from raw session to evidence

  1. All day, in the background. Interviews, debriefs, stakeholder syncs, and readouts accumulate in one continuous, searchable transcript. Nothing to remember to start.
  2. Mark the session, or let the calendar do it. Select the span that was the actual interview, or rely on the calendar auto-span for anything scheduled in advance.
  3. Hand it to an agent, in place. Ask for themes across a month of interviews, every verbatim quote mentioning a feature, or contradictions between two participants.

Then feed your actual research stack. Transcripts are plain JSONL files, greppable and pipeable into whatever you already trust for the rigorous end of analysis: spreadsheets, R, NVivo, Atlas.ti. The built-in MCP server lets Claude Desktop, Cursor, or any MCP-capable tool read the same session history directly, and Dovetail, Condens, or whatever repository holds your coded findings keeps doing that job. Earkeep feeds it instead of trying to replace it.

Tools this role uses today

  • Capture: Otter, Rev, or the transcript built into Zoom or Meet. See Earkeep vs Otter for the capture-layer comparison: bot in the call and audio on a third-party server, versus nothing on the table and nothing that leaves your device.
  • Local, manual transcription tools like MacWhisper transcribe locally too, but start and stop per file or per session, one recording at a time. See Earkeep vs MacWhisper.
  • Repositories and manual tagging: Dovetail, Condens, EnjoyHQ, Marvin, Looppanel, and BuildBetter, with Google Docs and rainbow-sheet spreadsheets doing the tagging NVivo or Atlas.ti would do more rigorously. Earkeep isn't a repository; it's the capture and transcription layer feeding one.
  • Ad-hoc synthesis: NotebookLM, Claude, and Gemini, used daily but with real skepticism. As one researcher put it, "If I took the first pass of AI analysis as gospel, I would routinely end up working from false or distorted findings." Earkeep's in-app agents work the same way: a first pass you review, not a verdict you accept.

Pricing

€39, once, for one device. No subscription, no per-seat pricing, no tiers, and no recurring line item on a research budget.

  • 14-day free trial, full functionality, no email address and no card required to start.
  • Yours to keep, forever. Includes all updates to Earkeep 1.x. If a paid major upgrade ever ships, the version you bought keeps working.
  • 14-day money-back guarantee, no questions asked, if you buy and it doesn't fit your workflow.
  • No account, no cloud, no API keys, ever.

See full pricing details →

FAQ for UX researchers

Does Earkeep record participants without their knowledge?

No. Earkeep is always listening on your device while it runs, but it does not join calls, announce itself to other participants, or replace your obligation to obtain informed consent. Recording a research participant, local processing or not, still requires telling them and getting their agreement, exactly as it would with any other recorder or platform transcript.

Where does a participant's audio actually go?

Nowhere. Audio is processed only in memory on your device and is never written to disk, never uploaded, and never sent to a transcription API. Only the text transcript is saved locally, as a plain file you control.

Can I delete one participant's session without touching anything else?

Yes. Transcripts are plain, human-readable files on your disk, organized by day and by the spans you or your calendar mark. You can open, edit, or delete any session's data directly, the same way you'd manage any file.

Does this replace my research repository, like Dovetail or Condens?

No, and it isn't trying to. Earkeep is the capture and transcription layer: it gets a clean, complete transcript of every session without a manual tagging bottleneck. You still push synthesized findings into whatever repository your team uses.

Does Earkeep support the languages my participants speak?

Whisper covers 99+ languages; Parakeet-TDT v3 covers 25 European languages with faster, more accurate English transcription. See the full supported-language list for both models.

Will always-on capture slow down my device during back-to-back sessions?

No more than a normal transcription app. A voice-activity-detection pipeline only runs transcription when someone is actually speaking, so silence between sessions costs nothing extra.

Start turning sessions into evidence

14-day full trial, no account required.