Upcoming Releases
Meeting recall you can check against the source

Post 2 of 5 — The Handoff series
If you hired a person whose only job was to remember everything - every meeting, every decision, every offhand comment about a feature, every “let’s circle back on that” - and to recall any of it instantly, on demand, you’d pay them a lot of money. Companies do.
That’s the part of Earmark we’re proudest of, and it’s the foundation everything else is built on. Before we can hand work off to your agent, before we can run loops on your behalf, before any of the flashy stuff works, one thing has to be true: the memory has to be excellent.
So let’s talk about the memory.

Meeting recall you can check against the source
Recall, not just notes
Most meeting tools give you a transcript and a summary, scoped to a single meeting. That’s a filing cabinet. Useful, but you still have to go digging.
Ask a question across saved meetings you can access, then inspect the source material behind the answer. The value is easier access to relevant context, with enough evidence to check whether it supports the conclusion.
“What meetings did I have last week?”
It starts with a fast, cheap scan of lightweight metadata - your attended meetings, titles, participants. No need to crack open a single transcript yet.
“What was discussed in the Insta meeting?”
Now it knows which meeting you mean and reads just that one.
“Give me the key quotes.”
Only now does it pull the full transcript, and only for the part you actually care about — the exact quote evidence.
This progressive approach isn’t just elegant; it’s what makes recall fast and accurate. Start broad, start cheap, go deep only when you ask for depth. The alternative - dumping every transcript into context and hoping - is slower, more expensive, and worse.
It finds what isn’t filed
Real memory handles the messy cases. The meeting that wasn’t on your calendar. The person who got mentioned but never showed up in an attendee list. The company name nobody tagged.
“What meetings did I have with ServiceTitan?” - even if “ServiceTitan” lives nowhere as a tidy field, Earmark reasons it out: it checks titles, metadata, the participant list, and even splits attendee emails to match on the domain.
“What was that meeting where Bob came up?” - Bob isn’t in any attendee list, but he was mentioned in a transcript. The ad-hoc hallway sync where you said “hey, what does Bob think?” Earmark finds it.
This is the difference between a search box and a memory. A search box matches strings. A memory understands what you’re actually asking.
Why this is genuinely hard (and why that’s the point)
Good retrieval isn’t a weekend feature you bolt on. Under the hood it’s true agentic search: full-text matching, semantic search for the fuzzy questions (“how can I get better at running my one-on-ones?”), reading artifacts and pins, and a model that knows which tool to reach for and in what order. Order matters - start at the wrong altitude and the answer falls apart.
We are investing in retrieval because useful handoffs depend on relevant evidence. Our ambition is to make meeting context easier for people and their chosen tools to use, while keeping the source and its limits visible.
Why memory is the whole game
Here’s the thing we keep coming back to from customer conversations: people are afraid of air pockets. Gaps in the record. The decision that happened in a meeting they weren’t in. The context that lives only in someone else’s head.
A useful answer should make its evidence and limits visible. Some meetings were never captured; others were kept private or temporary. That does not make the available context worthless. It means the answer should reflect the record it actually has. As people save and share relevant conversations, there can be more context to draw on—without requiring every conversation to be recorded.
This is the difference between a search box and a memory.
That’s the foundation. In the next post: what happens when that memory stops being just yours.
Want early access? waitlist@tryearmark.com.
Put your next conversation to work.
Use Earmark to prepare the spec, ticket drafts, or follow-up while the conversation is fresh. Review it, then carry it into your team's workflow.
