Lessons

Workflows

How Progressive PMs Pair Earmark With Grok Bot

A small group of PMs is working differently from everyone else.

We've spent the past year talking with product teams about how they use AI, including a run of calls with Earmark customers this fall. Most teams still ask AI for a meeting summary. This group has moved on.

They use different agents: Claude Code, Cowork, Codex, Cursor, Grok Bot. No two setups look alike. The habits underneath are the same. Six of them keep showing up.

1. They stopped taking notes

Earmark is on for every conversation. Calls, internal meetings, and the ones that never touch Zoom.

One PM carried his laptop around a customer conference with Earmark running, to keep the hallway conversations. "I don't take any notes anymore," she told us. "I just assume I'm always going to have Earmark on."

She also narrates. Onboarding a customer in person, he says what's on the screen out loud: upper right, gear icon, preferences. A transcript can't see, so he tells it.

2. The transcript goes to their own agent

None of them treat the transcript as the end product. It's the input.

Earmark saves every conversation as a Markdown file on your machine. These PMs point an agent at that folder. Some have written their own scripts to pull from it.

What the agent does next varies:

  • One customer built a dashboard in Claude Code that takes in everything and prioritizes the tasks.

  • Another keeps a few Markdown files on people and commitments, and runs a planning skill each morning against GitHub, Linear, and Slack.

  • A third runs thirteen bots in Grok Bot under one orchestrator.

The third one called the transcripts "the hinge point that all of this rests on."

3. They ask for state, not summaries

A summary describes one meeting. These PMs want the meeting to change something that already exists.

So a customer call updates the feature request tracker, the decision log, and the tickets it touches. One customer wrote a program that updates each workstream's context after every meeting. One PM recorded a company keynote so his bots could work it into his plans.

The better setups read backward too. One PM had his bots go through months of transcripts to find the themes and customers he keeps returning to. Next he wants them to flag drift: a direction that shifted over two weeks, a point his manager keeps making.

4. The work runs on a schedule

The agent doesn't wait to be asked.

A morning brief. A scan for new transcripts every hour. An evening check on commitments. A long run overnight that refines the PRD a few times, drafts design directions in Figma, and links it all together.

One PM's routines:

It isn't flawless. The morning we talked, two of her routines had failed to run. Her orchestrator said so.

5. A person signs off

Every one of these setups stops before anything leaves.

Emails get drafted, not sent. Slack messages wait. Tickets land in Draft. One PM's standing rule for his bots: "Never send an email, never post in Slack unless I'm explicitly telling it to."

The reason is practical. Generated tickets invent requirements. Auto-extracted action items often aren't real actions, and one user still spends 10 to 15 minutes cleaning them up. If a wrong ticket gets assigned, an engineer and a designer are building from it before anyone notices.

One PM put the rule to his whole team: "If you post anything, you're responsible for it."

6. They aren't loyal to the agent

One PM moved from Claude to Grok Bot because he found it easier to follow. He'd move again. "I'm not married to GrokBot," he said.

Another account runs Claude and Codex side by side.

The agent is the part they expect to swap. The record of what customers and colleagues said is the part they keep. "Without the context, none of this other stuff really matters."

Where to start

  1. Leave Earmark on. In-person conversations too.

  2. Point one agent at your transcript folder. Use the one you already have.

  3. Pick one handoff that happens every week. Customer call to ticket draft is a good first one.

  4. Schedule it. Don't rely on remembering to ask.

  5. Keep everything in draft until you've read it.

  6. Count time to approved work. Drafts produced tells you nothing.

Why this matters to us

Building is fast now. That makes it easy to build the wrong thing fast. One PM's version: "You're moving faster in the wrong direction."

These PMs fix that by spending more time with customers and letting the agents handle the write-up.

Our job is the first half. Capture what was said, wherever it was said, and hand it to whatever agent you choose.

Mark Barbir, Earmark co-founder and CEO

Mark Barbir

Earmark Co-founder & CEO

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.