Keep sources close
Make the reasoning inspectable after an answer.
Them AI for Knowledge
Turn useful answers into knowledge people can check
More documents do not automatically create better shared understanding. Bring important facts, decisions, and processes into a reviewable company memory, with sources and owners that help teammates question an answer instead of merely repeating it.
Mac-only for now. Free during the beta (invite-only).
Knowledge roomShared room
You with your team
Which of these instructions should the team use?
Them AI with company contextThe reviewed process names operations as approver; the other note names the team lead. Ask the process owner to resolve that conflict before either instruction becomes the team's answer.
↗ Example process recordReview with Knowledge owner
After human approvalReviewed working process
A useful record for the next person.
Illustrative workflow. Not a live conversation.
The work gets better when the context stays.
Good judgment belongs
with the whole team.
Give knowledge ownership
Know who can review an unresolved question.
Share usable practice
Turn an approved approach into a skill.
In the day-to-day
Work your team can bring to Them AI.
Start with the question. Keep the source. Make a person responsible for what comes next.
Knowledge room Example 01
Who should check this process answer?
The process owner is responsible for the approval step. Bring them the question with the cited guidance, so they can clarify the intended rule and review the record.
↗ Example owned recordClear ownership
Start with the knowledge people rely on most. Name the responsible owner, retain the supporting source, and make the review status visible so teammates know where to take questions or corrections.
See how the workflow fits
- Bring
- Process guidance
- Review
- Named owner
- Keep
- Owned record
Knowledge room Example 02
Can we merge these instructions?
The notes disagree about who approves the request. Keep both sources attached to the review question and ask the owner to confirm the intended path before combining the guidance.
↗ Example process notesConflicting guidance
Surface disagreement between sources instead of smoothing it away. Ask what differs, keep each source available, and have the relevant owner resolve the question before treating a combined answer as guidance.
See how the workflow fits
- Bring
- Conflicting notes
- Review
- Process owner
- Keep
- Review question
Knowledge room Example 03
Why did the team choose this approach?
The decision prioritized the core requirement over optional scope. Preserve that tradeoff with the outcome, so a future teammate can check whether the original constraint still applies.
↗ Example decision rationaleDecision context
Keep the reason for a decision alongside its outcome. Review the constraints, alternatives, and supporting material, then preserve only what is appropriate for the shared workspace and useful to future teammates.
See how the workflow fits
- Bring
- Decision rationale
- Review
- Decision owner
- Keep
- Decision record
Knowledge room Example 04
What belongs in a reusable skill?
Put the review steps, decision points, and conditions for use in the skill. Keep the underlying facts in memory, where the next teammate can inspect their sources separately.
↗ Example review methodReusable practice
Separate what is true from how the team works. Keep facts in memory and a reviewed approach in a skill, giving people and MCP agents useful guidance they can retrieve again.
See how the workflow fits
- Bring
- Reviewed approach
- Review
- Practice owner
- Keep
- Reusable skill
These are example workflows to evaluate, not customer results. Connected agents use their own tools; Them AI is the shared context and review workspace.
From useful work to reusable knowledge
The conversation is
only the beginning.
Memory keeps the facts and decisions. Skills keep a way of working. People decide what deserves to become a shared reference.
Meet Rooms and the Collective- 01
Bring the context
Example process record
- 02
Make the human call
Knowledge owner reviews the sources and proposed record.
- 03
Keep the method
Knowledge review
Make it real
Choose knowledge that deserves an owner
Bring a repeated question, its best source, and someone who can review corrections.
Discuss a design partnership
Before you begin
A few things
worth knowing.
Does memory include native version history?
Not currently. Records have sources, owners, and review status. Do not treat Them AI as a document history system.
Who can read our knowledge?
Human access is organization-wide today. Client-scoped MCP feeds retrieve their own client's approved memory plus firmwide approved memory.
Where should a beta pilot begin?
Mac-only for now. Free during the beta (invite-only). Begin with approved, organization-safe knowledge and committed reviewers.
What does the current beta include?
Shared rooms, memory with sources and review status, reusable skills, and MCP access for connected agents. Mac-only for now. Free during the beta (invite-only). Human room and memory access is organization-wide. Client-scoped MCP feeds restrict agent retrieval to that client's approved records plus approved firm-wide material. Do not treat a room as a private boundary for individual members. Read the access boundaries.
Bring one real workflow
Make the next project
better informed than the last.
Start with a question your team keeps answering. Bring the sources, the people who know, and the decisions worth keeping.
Mac-only for now. Free during the beta (invite-only).