Kept for Company-wide.
Not one department. The whole company's memory, kept. Three films on continuity as an operating principle.
All industriesFor executives
When someone leaves, the work stays.
Payroll counts the people. Nothing on the balance sheet counts what they know.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Every company runs on things nobody wrote down. Who decided, why, and how it gets done.
When those people move on, the reasoning goes with them, and the company pays to learn it twice.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
Six months later a new lead asks why planning is quarterly. Kept answers in one line and shows the words you said on the call.
The reasoning stays with the company, not just the people who happened to be there. Kept. Keep the knowledge behind the work.
Every function runs on knowledge that resigns: the engineer with the architecture, the rep with the relationship, the controller with the close, the buyer with the leverage. Companies pay to learn things once, then pay again every time the person who learned them walks.
Kept interviews your people about the work they actually do and turns it into knowledge that authorized people can retrieve with available sources. Kept is designed to make missing evidence clear. AI can still make mistakes. The workspace owns its work product. The people keep their dignity. Both are enforced.
For managers
Your team knows more than any of its members.
The knowledge is all there. It is just allocated one head at a time.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Every company runs on things nobody wrote down. Who decided, why, and how it gets done.
Your team rebuilds that context every quarter, one meeting and one hallway question at a time.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
Six months later a new lead asks why planning is quarterly. Kept answers in one line and shows the words you said on the call.
Your team gets the why without booking a meeting with you. Kept. Keep the knowledge behind the work.
Managing is watching knowledge move at the speed of interruptions: the new hire waiting on the veteran, the handoff that lost its context, the question that dies when its answerer is on leave. Every quarter the team re-buys knowledge it already owned.
Kept captures what each person knows through real conversation and keeps it cited for the team. You see coverage: what is kept, where it is thin, as a simple band per person for how much, never a score of anyone. Onboarding halves. The favors become lookups.
For partners
It is your knowledge. Kept just makes sure it counts.
You answer the same questions, train every new teammate, and none of it shows up anywhere with your name on it.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Every company runs on things nobody wrote down. Who decided, why, and how it gets done.
You end up chasing three people for one answer, and the third one isn’t sure either.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
Six months later a new lead asks why planning is quarterly. Kept answers in one line and shows the words you said on the call.
Ask once, get the answer and where it came from. Kept. Keep the knowledge behind the work.
Kept has real conversations with you about your work and keeps what you share in your own words. Teammates get your answers, cited to you, without taking your time. What you know becomes visible as your contribution, not absorbed anonymously into the org.
Capture starts with each partner's consent. They can skip a question, stop a session and review their captured knowledge. A business workspace's access rules determine who else can use it.
Knowledge captured for a business workspace belongs to that workspace. Partners retain visibility, removal from view and in-session retraction controls. Permanent deletion follows the workspace request process, unless a provisioned legal erasure window applies.
Kept's internal partner model is not employer-facing. A business workspace can see a red, amber or green capture band, based on contributed knowledge, alongside the access and audit records described in the Privacy Notice. It is not a score of a person's work or judgment.
Where it starts in company-wide.
One process, one question the team already asks.
Start at zero.
Pay once when the KPIs land.
The KPIs we would propose for a company-wide team:
- Roles in scope moving from a thin band to a covered band over the window
- Topics with a kept, cited answer, against topics with none
- Partners with capture on, and using Kept, through the whole window
- Knowledge kept per role in scope, and its coverage band moving from thin to covered
Agreed before the pilot starts and measured from the workspace's own ledger over a window we set together, with a minimum number of partners using Kept through it. Nothing to pay to begin. A one-time payout when the KPIs are met, then the recurring rate.
How the proof of value worksUseful knowledge.
Visible limits.
Kept supports the work. It does not assess competence, monitor people or replace training, supervision or required qualifications. Business knowledge follows workspace access and ownership rules.
Kept is designed to ground answers about your work in available sources and say when it does not know. AI can still make mistakes. Inspect the sources and review important answers before relying on them.
Security and compliance