Company memory

Keep the answer. Keep why it was right.

Why did we choose this approach? Which policy applies? Keep the answer with its source, the reason behind it, and the person responsible for keeping it current.

Join the waitlistSee it in practice

Mac-only for now. Free during the beta (invite-only).

Keep the useful part

Turn source material into knowledge your team can check.

Keep the policy that settled the question, the reason behind a technical choice, or a method worth using again. Add its source and owner, then review it for reuse.

Native source imports

Two guides disagree. Give the answer an owner.

  1. Two source pages

    Bring the onboarding guide and the current access-request procedure into the relevant knowledge room.

  2. A record to review

    Review the proposed guidance, resolve conflicting steps with the policy owner, and approve the corrected record.

  3. A shared answer

    Your AI teammate can use the approved guidance with its source reference when the same onboarding question returns.

Explore company knowledge
NotionConfluence
Them AI Prepared for review
Proposed record

New software access goes through the service desk. The service owner confirms the required approval.

Your team decides the next step

Notion and Confluence import readable page content as draft memory. Review it before your AI team uses it as approved guidance.

Native source imports

Keep why a change was made after the issue is closed.

  1. The recorded rationale

    Import the architecture decision and completed issue description that explain why a recovery method changed.

  2. A decision with a source

    An engineer checks the proposed decision record and approves the explanation the next teammate should rely on.

  3. Context for the next question

    The next engineer can find the decision and its source when preparing a recovery brief, then check whether the earlier reasoning still applies.

Explore engineering knowledge
GitHubLinear
Them AI Prepared for review
Decision draft

Retries must preserve the original request identity to avoid creating duplicate work.

Your team decides the next step

GitHub reads selected README and ADR files and merged PR bodies. Linear reads completed issue descriptions and documents, not every discussion.

Source imports where configured

Keep the method without carrying every client detail forward.

  1. Cleared source material

    Bring a sanitized scoping document and an approved delivery-method excerpt, excluding confidential client details.

  2. A reusable principle

    The reviewer separates the general method from engagement-specific assumptions before approving the knowledge record.

  3. A better starting point

    The approved method helps prepare the next scope review while the engagement lead checks whether it applies.

Explore consulting knowledge
Google DriveSharePoint
Them AI Prepared for review
Method draft

Confirm the customer’s data owner and input format before agreeing a delivery milestone.

Your team decides the next step

Google Drive and SharePoint source imports require workspace setup. Use Google Docs or supported SharePoint files, with sensitive client details removed.

Inside Company memory

Knowledge your team can come back to.

Keep the source

An answer is more useful when you can check it.

Keep the policy, customer context, decision or process with its supporting source and owner. The next person can follow the reasoning, not just repeat the answer.

Source-linked company knowledge with owners and review details

Company knowledge with its source and owner.01 / 03

Review what stays

Make approval part of the record.

Contributions start as drafts. People with review permission approve what stays and check whether existing knowledge is still current.

A draft company memory’s status, room and owner

The review status and the person responsible.02 / 03

Use it in the work

Bring yesterday’s reasoning into today’s question.

Find relevant approved knowledge with your teammate. Follow its sources and check whether the earlier answer fits the question in front of you.

Relevant approved records and their owners beside a customer question

Relevant records, with sources you can check.03 / 03

Explore the full task

Knowledge

Repair an onboarding answer

Sources, review and next steps Consulting

Workshop to design brief

Sources, review and next steps Customer success

Customer handoff

Sources, review and next steps

A few things worth knowing.

What belongs in company memory?
Facts, records about customers or other entities, decisions and processes. Keep the useful knowledge with an owner and supporting sources, rather than saving an entire conversation as guidance.
Who can read the records?
Human access is organization-wide in the current beta. Rooms organize context, not private spaces between members. Configure external-agent retrieval scopes separately.
Is memory shared with AI teammates by default?
Approved shared company memory is available by default alongside a teammate’s assigned room. You can turn shared memory off for a teammate and grant additional room access explicitly.

Bring one real workflow

Try it on work your team already does.

Choose one recurring question, bring the source material, and name the person who will review the answer. Start there, then decide what is worth repeating.

Mac-only for now. Free during the beta (invite-only). Have a workflow in mind? Plan a pilot with us.