//
What is Earmark
Earmark turns live conversations into finished work.
Earmark is an AI meeting assistant for product and engineering teams. Your team has already talked through the problem, agreed on the tradeoffs, and decided what happens next — Earmark turns that conversation into the draft requirements, tickets, decisions, and follow-ups you’d otherwise write afterward.
Capture a meeting, choose the deliverables you need, and review them while the discussion is still fresh.
A useful meeting should produce more than a summary
A summary
Tells you what happened in the room.
A product handoff
Explains what to build, why it matters, which constraints apply, and what still needs a decision.
Earmark can produce both. Its focus is helping you move from discussion to usable work — a PRD with clear scope, tickets with acceptance criteria, a decision log with reasoning, or a brief your coding agent can use.
“Finished work” still involves human judgment. Earmark prepares the output; your team reviews and approves it before it becomes a commitment.
Built for teams whose work starts in conversation
Product managers
Turn discovery and planning into requirements, priorities, and stakeholder updates.
Engineering teams
Preserve technical decisions, constraints, dependencies, and implementation questions.
Product Operations
Establish consistent formats for recurring work and make decisions easier to find.
Cross-functional teams
Keep customer conversations and internal decisions moving into execution.
Start with the conversation. Choose what comes out.
One meeting can support several outputs — engineering gets the detail it needs, leadership gets the decisions and implications.
Conversation
Useful output
Customer discovery
Problem brief, evidence, unanswered questions
Feature planning
PRD, scope decisions, draft tickets
Technical design
Design document, alternatives, risks
Sprint planning
Work breakdown, dependencies, acceptance criteria
Stakeholder review
Decisions, changes, leadership update
Incident discussion
Timeline, follow-up actions, draft incident report
Put agents to work while the meeting is happening
Give Earmark a task such as “draft the requirements,” “track unresolved questions,” or “identify technical risks.”
Live artifacts update as the conversation develops, giving you something concrete to react to while the people with the answers are still in the room. A missing requirement becomes a question in the meeting instead of another meeting next week.
Keep using the context afterward
Saved meetings support later questions and follow-up work. Projects bring related conversations together so your team can ask about an initiative across meetings.
For local workflows, the desktop app can save transcripts as Markdown, and you can copy reviewed artifacts into documents, issue trackers, and agent prompts. The transcript preserves the discussion; the reviewed artifact tells the next person — or agent — what to do with it.
Capture without adding a meeting bot
No Earmark participant joins your call. The desktop app records audio locally and works alongside the meeting platforms you already use.
Desktop app
Captures microphone and system audio on Mac and Windows, so you get both sides of the conversation — even on headphones, with Zoom, Google Meet, or Microsoft Teams.
Web app
Captures microphone audio with different limitations. Use the desktop app for remote meetings when you need everyone’s audio.
Privacy starts with knowing where the data goes
Botless capture means no Earmark participant joins your call. It doesn’t mean all processing happens on your device.
Audio is streamed for transcription. Earmark states that it does not retain raw audio after transcription or use customer meeting content to train AI models. Saved meetings, temporary meetings, and local files have different retention behavior — review those settings before capturing sensitive discussions.
Work with the tools you already use
Prepare ticket content for Linear or Jira, copy an update into your team’s communication tool, or hand a reviewed specification to a coding agent.
The documented artifact handoff is copy-and-paste, and local Markdown is another route for tools that read files. Neither requires your team to treat Earmark as its issue tracker or code editor.
Know the boundaries
Earmark depends on the audio and context it receives. It can miss words, misinterpret a decision, or produce a plausible requirement nobody agreed to.
Before anything becomes a commitment:
Review names, ownership, dates, numbers, scope, and acceptance criteria.
Keep open questions visible.
Remember a draft ticket doesn’t become a published issue until you complete the handoff.
Try it on a meeting that normally creates more work
Choose a planning session, customer call, or technical discussion. Ask for the deliverable you usually write afterward — then judge Earmark by how much work remains.