Every document you write about work - the status update, the CRM entry, the project recap - is stale the moment you hit save. You know this. You've felt it. You spend Friday afternoon assembling a summary of the week, and by Monday's standup half of it is wrong. So you update it. And then you update it again. Somewhere along the way, maintaining the record of the work became a second job on top of the work itself.

We think that second job is about to disappear.

Work about work

Most of the tools we use every day - CRMs, project trackers, status docs, weekly ceremonies — exist for one reason: coordination. How do we divide and conquer? How do we avoid colliding with each other? How does everyone stay accountable? Those are real problems, and for decades the answer was the same: make people write things down, then make other people read them.

But notice what all of those artifacts have in common. They're snapshots. A CRM is obsessed with the outcome of activity - the deal stage, the pipeline number - while the actual machinery of the work lives somewhere else entirely: in the conversations. The meeting where the customer told you what they actually needed. The call where the blocker surfaced. The hallway conversation that changed the plan.

The snapshot was never the source of truth. The conversations were. We just didn't have a way to ask them anything.

Ask, don't maintain

Now we do. When every conversation your team has is captured and instantly retrievable, the whole equation flips. You don't prepare a status update - you ask, "where are we with this customer?" and get a just-in-time answer built from everything that's actually been said. You don't maintain a document - you retrieve. A flat system with instant, intelligent recall beats any folder hierarchy you could ever hope to build.

This is the same reason we've stopped asking whether we even need a CRM internally. Not because tracking deals doesn't matter, but because the answer to "remind me where we left off" shouldn't live in a form somebody filled out from memory three weeks ago. It should come from the conversation itself.

The new primitive: live views, not documents

Here's where it gets interesting. If retrieval replaces the document, what replaces the shared document - the thing a team looks at together?

Our answer: you don't pin documents anymore. You pin questions.

Imagine a project view where the things you care about - latest blockers, open risks, where a decision landed - aren't paragraphs someone wrote, but standing prompts that recompute every time a new meeting flows in. Nobody edits them. Nobody updates them. If the output isn't what you need, you change the question, not the answer. It's always live, it's shared by default with everyone in the project, and if you want more depth you just ask a follow-up.

Don't subscribe to summaries. Subscribe to answers.

The super-empowered individual

Zoom out and this is a bigger shift than a feature. The working model that's emerging isn't a bigger team with more ceremonies - it's a single person with layers of automation underneath them and full context on demand. Status is ambient. Roll-ups are a prompt. The calibration moments that used to require a meeting now require a question.

Tools like Gong figured this out for one role: hop on a sales call and the system preps you - where you left off, the risks, the action items. We think that's too narrow. Every role has conversations. Every role deserves that leverage. Why should sales be the only function that gets to show up to every interaction already knowing everything?

The people we talk to feel this pressure acutely. Everyone's being asked to move faster with smaller teams. Everyone's spinning up new workflows and quietly worrying whether the quality holds. The winners won't be the ones who write better status updates. They'll be the ones who stopped writing them.

Meeting you where you are

One honest caveat: not every organization is ready to burn the artifacts. That's fine. This isn't all-or-nothing. If your org runs on documents, generate them - from the real source of truth, in seconds instead of an afternoon - and ship them into whatever tools your team already uses. The foundation is the same either way: every conversation, captured and retrievable. How far you take it is up to you.

What's coming in Earmark

This is the direction we're building. Full-history retrieval - ask anything across every meeting you've ever had, not just the recent ones - is in internal testing now. Live project views built on pinned prompts are right behind it, along with deeper ways to pipe Earmark's context into the rest of your workflow through MCP. Recording the meeting was where we started. It's quickly becoming the least interesting thing we do.

The future of work isn't a better document. It's never having to ask someone "what's the latest?" - because the answer is already there, already current, already yours.

Stay tuned.