Make the product usable by keeping every critique that shaped it

Critique, stakeholder review, dev handoff: a design is decided out loud by people describing what is wrong with it, then delivered as a revision, a spec and a rationale nobody has time to write. Earkeep is an always-on transcriber that keeps every one of those rooms on your own device, with no bot present, so v3 never re-litigates what v1 already settled.

No bot · No cloud · No record button

14-day full trial, no account required.

The rooms that decide it

Design critique

What has to survive it is the specific feedback per screen and who gave it, because a crit whose input disappears is one people stop contributing to. NN/g names the failure exactly. The session ends and the feedback gets filed somewhere nobody opens again. The crit you most need a record of is the one where a director tore into your flow and you stopped writing anything down.

With Earkeep: capture is already running, so the crit you froze in is still on the timeline afterwards, and you mark the span once you can face it. The desk-side "quick look at this" that changed the design in one sentence is on that same timeline, with nothing to invite and no button to hit. How always-on works →

Stakeholder review

What has to survive it is the sign-off, or the exact objection blocking ship, in the words the person used. Three sprints later the same decision gets reopened by someone who was in the room and remembers it differently.

With Earkeep: connect Google Calendar, Apple Calendar, Outlook or any ICS URL and the recurring reviews start, end and title their own spans. Transcripts are plain dated files on your own disk, so the exact wording of a verbal sign-off is a search, not a memory. From what was said to what you know →

Dev handoff

What has to survive it is the verbal decision on states and edge cases, which is the half of the handoff that never reaches the spec. Everything agreed out loud gets asked again in three weeks, one Slack message at a time.

With Earkeep: audio is transcribed on your device and never written to disk, so a handoff over a laptop is captured with no vendor in the room and nothing uploaded anywhere. The edge cases you covered aloud are in the transcript the spec gets written from. See agents and MCP →

The rest of the week

Those three are where the design is decided. They are not where the week goes: one senior designer on Blind put it at 65 to 75% of the week in meetings, leaving "3/8 hours to design". Figma's own research found 92% of designers and 91% of developers believing handoff could be improved, with 84% of designers collaborating with developers at least weekly.

MeetingYouWhat has to survive it
Design workshop or ideationCo-facilitateWhich direction was agreed, and who committed to it
Project kickoffAttendThe problem framing, the constraints and the success criteria
The desk-side "quick look at this"AttendThe one sentence of feedback that changes the design
Cross-functional syncAttendWhat scope actually is this week, and what moved
Usability session, observedAttendVerbatim participant reactions, and the moment the flow broke
Design system reviewRun or attendWhich pattern is now canonical, and the reasoning for it
Team standupAttendBlockers, and what changed under the work since yesterday
1:1 with the design leadAttendFeedback on the work that never gets repeated in a group

Earkeep does not ask you to choose between them. Every recurring row above starts, ends and titles its own span from your calendar, so a week of reviews ends as named transcripts with nothing left to file.

Writing them up is a separate job from keeping them, and the templates are free: the kickoff template, where the problem framing and the constraints get recorded in the sponsor's own words, and templates for the sprint ceremonies you sit in.

Two of the conversations above are interviews whether or not they are called that. The craft is in open-ended questions, establishing rapport and empathic listening, three pages written to be read together, and the last is the one that matters most in a critique.

Pricing: one payment, no subscription

€39

once, for one device, not a subscription.

No tiers, no per-seat billing, no recurring bill. Try it free for 14 days with full functionality, no email and no account required. See full pricing and policy details →

FAQ for UX designers

Does Earkeep replace Figma comments or design critique tools?

No. Earkeep doesn't touch your design files or annotate your work; it captures the spoken meetings around the work, mic and system audio, so what was said in a crit or review exists as a transcript alongside whatever lives in Figma comments.

Will an AI judge my designs?

No. Earkeep transcribes what was said; it doesn't generate opinions about your work. Designers report being wary of AI tools that critique their designs on a PM's behalf. Earkeep isn't that: it's a record of the human conversation, that you point your own agent at, on your own terms.

Can it capture an in-person design review, not just a video call?

Yes. Earkeep captures mic and system audio the same way whether the meeting is a video call or people gathered around a laptop, so a whiteboard-adjacent, in-person crit is captured exactly like a remote one.

Does the transcript leave my device, especially critique of my own work?

No. Audio is processed only in memory and never written to disk, and transcripts are saved locally as plain files. No bot joins the call, and no vendor cloud sees a director's offhand comment about your flow. It's your record, on your own device.

Does Earkeep support the language my team runs reviews in?

Earkeep transcribes with Whisper (99+ languages) or Parakeet-TDT v3 (25 European languages, including Czech, with faster and more accurate English transcription). See the full supported-language list on languages and models.

Stop losing what the room said

14-day full trial, no account required.