See where the knowledge
is thin.
Most teams find out where the knowledge was thin on the day the person who held it is unavailable. Kept shows coverage per role as a simple band, so the gap is visible while there is still time to keep what fills it. Never a score of the person.
All use casesA familiar moment
“Who else
knows this?”
The setting. A finance team. The reconciliation is a monthly check that the numbers in two systems agree. Only two people know how to run it. One is on leave in March. The other has just handed in notice.
Two people can run the reconciliation. One is on leave in March. The other has just given notice. Nobody noticed, because nobody could see it.
Illustrative scenario, not a customer result.How Kept helps
See the band.
Close the gap.
- 01
See coverage by role
Owners, admins and a person's own manager see what was captured, as a red, amber or green band per person. Never a rating.
- 02
Keep what fills the gap
Where a role is thin, June interviews the people who hold it, in their own words, on their own schedule.
- 03
Watch the band move
As knowledge is kept and cited, the band moves. The gap closes before the calendar exposes it.
What Kept uncovers.
- 01
Which roles depend on one person
- 02
Which topics have no kept answer at all
- 03
Where two people hold different versions of the same process
- 04
What to keep first, and from whom
In your line of work.
Where this shows up first: the film for the operations leader who feels it, and the other lines of work where it starts.
Also in: Finance HR & People Company-wide
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
The fix for the recurring exception is known. Known by three people, none of whom are on call tonight.
Every shift change and site handoff leaks the exceptions that keep operations running, and that leak shows up as downtime.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
Tonight’s on-call hits the empty weight field and asks Kept. They get the workaround in one line, cited to the person who found it.
Exceptions stop leaking at handoffs, across shifts and sites. Kept. Keep the knowledge behind the work.
Start at zero.
Pay once when the KPIs land.
The KPIs we would propose for coverage you can see:
- 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 who are the only holder of a topic, before and after
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