Make the product usable by keeping every critique that shaped it
Critique, stakeholder review, dev handoff: a design is decided out loud, and the rationale rarely gets written down. 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 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. The crit you most need a record of is the one where a director tore into your flow and you stopped writing.
With Earkeep: capture is already running, so that crit is still on the timeline, and you mark the span once you can face it. How always-on works →
Stakeholder review
What has to survive it is the sign-off, or the exact objection, in the person's words. Three sprints later someone remembers it differently.
With Earkeep: connect your calendar and recurring reviews title their own spans. A verbal sign-off is a search on your own disk, 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, the half that never reaches the spec.
With Earkeep: audio is transcribed on your device and never written to disk, and 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, not where the week goes: one senior designer on Blind put meetings at 65 to 75% of the week.
| Meeting | You | What has to survive it |
|---|---|---|
| Design workshop or ideation | Co-facilitate | The agreed direction, and who committed |
| Project kickoff | Attend | Framing, constraints and success criteria |
| The desk-side "quick look at this" | Attend | The sentence that changes the design |
| Cross-functional sync | Attend | What scope is this week |
| Usability session, observed | Attend | Verbatim reactions, and where the flow broke |
| Design system review | Run or attend | Which pattern is canonical, and why |
| Team standup | Attend | Blockers and what changed |
| 1:1 with the design lead | Attend | Feedback never repeated in a group |
Every recurring row above titles its own span from your calendar, so a week of reviews ends as named transcripts.
Writing them up is a separate job, and the templates are free: the kickoff template and the sprint ceremonies.
Further reading: open-ended questions, establishing rapport and empathic listening.
See it in action
The crit is still there afterwards
The review you stopped taking notes in is still on the day timeline, to find, read and keep.
The rationale, drafted from the room
Ask your own agent what was objected to and by whom, then review a draft with the quotes attached.
Pricing: one payment, no subscription
€39
once, for one device, not a subscription.
No tiers, no per-seat billing. Try it free for 14 days, no account required. See full pricing →
FAQ for UX designers
Does Earkeep replace Figma comments or design critique tools?
No. Earkeep doesn't touch your design files; it keeps what was said in a crit or review as a transcript beside your Figma comments.
Will an AI judge my designs?
No. Earkeep transcribes what was said and generates no opinions of its own.
Can it capture an in-person design review, not just a video call?
Yes. Mic and system audio are captured the same way, so a crit around a laptop is kept like a remote one.
Does the transcript leave my device, especially critique of my own work?
No. Audio is processed only in memory, and transcripts are saved locally as plain files. No bot joins and no vendor cloud sees it.
Does Earkeep support the language my team runs reviews in?
Whisper covers 99+ languages and Parakeet-TDT v3 covers 25 European ones, including Czech. See the full list on languages and models.
Stop losing what the room said
14-day full trial, no account required.