Field notes
knowledge capture

How to Capture Your Firm's Knowledge Without Adding Another Tool

The knowledge that matters is already being written in Slack and email. The problem is not that you need another place to put it. It is that none of your tools talk to each other, and the context decays before anyone can use it.

TJ
Tommy Jamet · 18 March 2026 · 6 min read

The knowledge that runs your firm is already being written down. It is in the Slack thread where a position got agreed, the email where a client confirmed a deadline, the meeting summary nobody will open again. The problem was never that you lacked a place to put it. It is that the places do not talk to each other, and the context evaporates before anyone can use it.

So the instinct to "get a tool for this" is usually wrong. Another system is another silo. What you need is a way to capture what already exists, selectively and with consent, and resolve it into something your firm can ask.

Key Takeaways

  • Knowledge decays fast: retention drops to about 25% after a week without reinforcement (PLOS ONE, 2015).
  • More software makes it worse, not better. The average enterprise runs 291 SaaS applications, with at least 30% of licenses unused (Zylo, 2026).
  • Switching between those tools is expensive: it takes about 23 minutes to fully refocus after an interruption (Gloria Mark, UC Irvine, via Asana).
  • The fix is selective, consent-gated capture from where work already happens, resolved into grounded, cited knowledge, not a new place to file things.

Why the knowledge disappears

Two forces work against you. The first is human. Hermann Ebbinghaus measured the forgetting curve in 1885, and replications since confirm it: without reinforcement, people retain only about a quarter of new detail after a week (PLOS ONE, 2015). The reasoning behind a decision is gone long before the engagement closes.

The second is structural. The knowledge lives in different places, owned by different people, in different formats. What a client asked sits in a call note. The concern that reframed it is in a Slack thread. The confirmation is in email. Individually, each is a fragment. Connected, they are the firm's actual position. But nothing connects them, so they decay in parallel and never intersect.

The tool-sprawl tax

The reflex is to add a system to hold the knowledge. This makes it worse, because every new tool is a new silo.

The average enterprise runs 291 SaaS applications in 2026, up from 110 in 2020, and at least 30% of those licenses go unused (Zylo, 2026). Each one knows about its own slice and nothing else. And every time someone jumps between them they pay a real tax: research from Gloria Mark at UC Irvine found it takes about 23 minutes to fully regain focus after an interruption.

More tools, more silos: SaaS apps per enterprise20201102026291At least 30% of licenses go unused. Source: Zylo SaaS Management Index, 2026.

So before adding anything, ask the only question that matters: will this connect the knowledge that already exists across the tools we have, or will it just create one more place for context to die?

Capture where the work already happens

The better model does not ask anyone to file things into a new system. It captures from where the knowledge is already being written, and it does so on three principles that matter for a firm handling confidential, regulated work.

Selective, not a firehose. You choose the channels and inboxes that hold real engagement knowledge. The watercooler channel and the receipts stay out. Capturing everything is how you end up oversharing and oversurfacing, and for a confidentiality-bound firm it is also a liability.

Consent-gated and confirmed. Nothing is vacuumed up silently. A relevant message or email is lifted, resolved into a piece of knowledge, and you confirm it. For firms whose data is governed by external rules, capture is a deliberate, recorded act, not a background process.

Resolved, not just stored. A captured artifact does not become another note in another folder. It becomes a piece of grounded knowledge that carries its source and date, so the answer it later supports can be traced back to the exact words it came from.

From capture to an answer you can trust

Capturing is only half of it. The point is to ask your firm a question later and get an answer you can stand behind. That requires two things the capture step sets up.

First, every piece of knowledge keeps its evidence: the artifact it came from and when. Second, when you ask and the evidence is not there, the honest response is that there is nothing, rather than a confident guess. A system that fills the gap with an invention is worse than no system, because someone acts on it. One that retrieves what is real, cites it, and abstains otherwise is what a careful firm can actually use. This is the discipline behind a real company brain, and the architecture that makes it work.

You do not need another tool. You need the knowledge you already produce to stop decaying, captured where it lives and resolved into something you can ask, under your own control and key.

Frequently Asked Questions

What does it mean to capture knowledge selectively?

Selective capture means you choose which sources (specific Slack channels, specific inboxes) hold genuine engagement knowledge, and only those are captured. It is the opposite of the "ingest everything and filter later" model, which degrades answer quality and, for a confidentiality-bound firm, creates real exposure.

Why not just add a dedicated knowledge tool?

Because each new tool is another silo that does not talk to the others. The average enterprise already runs 291 SaaS applications (Zylo, 2026), most under-used. The gain comes from connecting the knowledge already being written in the tools you have, not adding a place to re-enter it.

How fast does this knowledge actually decay?

Fast. Replications of the Ebbinghaus forgetting curve put retention at roughly 25% after a week without reinforcement (PLOS ONE, 2015). The reasoning behind a decision is usually gone before the engagement even closes.

Is capturing confidential client data into an AI system safe?

Only if it is built for it. Gravii captures selectively and with consent, isolates each firm's data, and encrypts it with the firm's own revocable key. See how your data is protected for the precise claims and the honest caveats.

TJ
Tommy Jamet

Seasoned Head of Product, Founder of Gravii. He writes about grounded knowledge, honest abstention, and data sovereignty for teams that hold confidential, regulated data.

Request a pilot