When someone leaves,
the work stays.
A resignation used to mean two weeks of frantic documentation and a successor who spends months rediscovering what the last person knew. With Kept, the knowledge is already there, in the person's own words, before the notice is handed in.
All use casesA familiar moment
“She left last month.
Who knows how this works?”
The setting. A finance team at a mid-sized company. The controller is the person who closes the books every month. She left last month after six years. Her replacement has started, and the next month-end is two weeks away.
The controller who ran the close for six years has gone. The checklist survived. The reasons behind step four, the vendor to call first and the exception for the quarter-end did not.
Illustrative scenario, not a customer result.How Kept helps
Keep it while they are here.
Onboard from it.
- 01
Keep it while they are here
Capture is opt-in and ongoing, so the knowledge is kept over months of ordinary work, not in a rushed exit interview.
- 02
Hand the record to the workspace
Work captured for a business workspace belongs to the workspace. When someone leaves, it stays, with its sources.
- 03
Onboard the replacement from it
The successor asks Kept how the work was done and why. Every answer cites the person who gave it, on the day they said it.
What Kept uncovers.
- 01
The exceptions and judgment calls that never made the checklist
- 02
Who to call first, and when to involve them
- 03
The reasoning behind decisions the successor would otherwise reverse
- 04
What the departing person knew that nobody else did, so the gap is visible before it hurts
In your line of work.
Where this shows up first: the film for the finance leader who feels it, and the other lines of work where it starts.
Also in: Engineering HR & People Legal & Compliance
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Month-end close depends on steps that live in one controller’s head. Nobody else can run it.
If that controller leaves in March, the close slips, and the reasoning behind every accrual goes with them.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
At the next close, a new analyst asks why the rebate sits in the prior period. Kept answers and cites the words from your call.
The close survives a resignation, and the reasoning behind it is on record. Kept. Keep the knowledge behind the work.
Start at zero.
Pay once when the KPIs land.
The KPIs we would propose for when someone leaves:
- Knowledge kept per departing partner before their last day, by topic
- Questions the replacement asks in their first 60 days that are answered with a source
- Days from the replacement's start to their first cited answer
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