At most SaaS companies, Product doesn’t run on documents. It runs on conversations.

Roadmap tradeoffs get decided in leadership syncs. Requirements get clarified in prod/eng meetings. Customer feedback gets interpreted in debriefs. The work is live, cross-functional, and high-context—and that’s not a flaw. That’s the job.

The problem is what happens after the conversation ends.

Someone has to translate what was said into what ships: tickets, stories, specs, updates, decisions, and rationale. That “translation tax” is rarely scheduled, rarely visible, and almost always falls on your highest-leverage people. As engineering gets faster, that translation layer becomes the bottleneck—showing up as a calendar packed with alignment, plus a second shift of follow-up work.

ServiceTitan evaluated Earmark to close that gap: reduce the time between “we talked about it” and “it’s in motion,” without adding process or degrading meeting quality. They weren’t looking for AI meeting notes. They wanted a way to turn live conversations into execution-ready work—while the meeting was still happening.

A Senior Product Manager summed up the pain—and the shift—simply:

“Most of my time… is in conversations… I don’t really get to do that ‘deep work.’ So meetings are where I lose the most energy. Earmark saves me right there, in the meeting…”
— Scott Burns, Senior Product Manager

That line—saves me right there, in the meeting—is the core of this case study. The value wasn’t a recap later. The value was removing the cognitive overhead during the conversation and producing real work before the meeting ended.

What changed when the translation tax went away

During the evaluation, Earmark repeatedly showed up as a tool doing three specific jobs. The pattern was consistent across users and use cases—not “nice summaries,” but tangible improvements in throughput and clarity.

1) Complex conversations became clean execution artifacts

Product work is messy in the middle. Technical feedback is nuanced. Decisions are partial. Context lives in spoken language—then gets reconstructed later when someone finally has time to write it up.

Earmark reduced that reconstruction step by helping PMs convert messy discussions into structured, usable artifacts: stories, tickets, and clear written outputs that matched the direction they wanted to take.

“Earmark helps me decipher conversations and then elegantly write them up with whatever direction I provide… and understand feedback on complex technical subjects to put into several tickets for development team review.”
— Christine Yang, Senior Product Manager

In practice, this meant the meeting wasn’t just alignment—it was the moment execution got shaped into something the team could act on.

2) PMs stayed present—while the work still got captured

The more important the meeting, the harder it is to both participate and document. Most PMs either half-listen while they type, or stay engaged and accept the cost of a bigger cleanup later.

Earmark changed that tradeoff. Users consistently described being more focused and retaining more, because they weren’t trying to be the scribe.

“Literally helps me focus on the meeting itself rather than trying to write down things. It truly keeps me in the present…”

This is a subtle benefit with compounding impact: better meetings, clearer decisions, and less mental fatigue—without sacrificing documentation.

3) Ideas and updates stopped slipping through the cracks

The other hidden cost of meeting-heavy work is context loss: good ticket ideas never get written down, key decisions don’t get broadcast, and stakeholders who weren’t present end up dragging the team back into recap mode.

Earmark helped teams capture and share what mattered while it was still fresh—reducing dropped details and making downstream communication easier.

“Earmark helps me capture ticket ideas so that these things don't slip through the cracks… it also saves me time generating updates for other colleagues who should be informed.”
— Amanda Taylor, Product Manager

Results: pull, time saved, and output quality

The evaluation survey wasn’t ambiguous. ServiceTitan users didn’t describe Earmark as a novelty. They described it as something they’d miss.

Retention signal (product pull):

• 67% said they’d be very disappointed if Earmark went away

• 33% said they’d be somewhat disappointed

• 0% said they wouldn’t care

Time savings (capacity returned):

• All users reported significant weekly time savings

• 67%: 5+ hours/week

• 33%: 3–5 hours/week

Output quality (minimal rework):

• Average satisfaction: ≈ 4.7 / 5

• All respondents said outputs needed only “a little” cleanup

One unexpected but important secondary effect was “polish.” When outputs look finished, teams move faster because fewer people question the artifact, and the author’s credibility increases.

“Everything Earmark produces looks so polished that my peers think I spent hours building documents out—it’s a game-changer for my credibility.”

The most telling signal: it expanded organically in 30 days

The productivity story is strong—but the adoption story is what makes this compelling for other SaaS product executives.

Earmark’s outputs—tickets, updates, docs—are naturally shareable. They flow through Slack, project trackers, and stakeholder threads. That creates “referenceability”: once people start relying on the artifacts, they want to be closer to the source, contribute, and get the same leverage. That’s how tools spread inside product orgs without being mandated.

In 30 days, usage expanded dramatically:

• Active users: 7 → 33 (4.7×)

• Meetings captured: 291 → 1,132 (3.9×)

• Tasks generated: 461 → 1,403 (3.0×)

• Total meeting hours processed: 200.48 → 797.54 (4.0×)

For a website visitor, this is the core takeaway: Earmark didn’t just help individuals. It became part of how the org operated—and pulled more people into the workflow.

What it enabled in practice

This wasn’t theoretical value. Users described concrete outcomes that map to everyday product execution:

• Turning technical discussion into delivery artifacts

• Writing stories immediately after prod/eng syncs

• Creating meeting updates for stakeholders who couldn’t attend

• Producing higher-level strategy docs and epics from live conversation

And one short external proof point captured the day-to-day experience:

“Earmark is a life saver - gives me time back and lifts the cognitive load. I stay fully locked in because it's a reliable note taker and analyzer.”

Why this matters for other SaaS product leaders

If your organization feels the modern paradox—engineering velocity accelerating while PM bandwidth stays fixed—the constraint is no longer code. It’s the translation layer between talking and shipping.

ServiceTitan’s evaluation points to a different operating model:

Meetings don’t have to create more work.
They can create finished work.

And the value is straightforward:

• More throughput without adding headcount (3–5+ hours/week back per PM)

• Faster conversion from discussion to delivery

• Higher meeting quality (presence vs. note-taking)

• Less context loss across stakeholders

• Organic expansion driven by referenceable outputs