The manager is out sick.
The questions are not.
A team's questions do not wait for a manager's return. Kept answers from what the manager and the team have already kept, and every answer shows the conversation it came from, so the person asking can check it and act.
All use casesA familiar moment
“Can this ship
without sign-off?”
The setting. An engineering team that ships software every week. The release manager decides what can go out and when. She is away for a week. An engineer has a hotfix ready and does not know whether it needs a second approval.
The release manager is off for a week. The engineer needs to know whether the hotfix needs a second approver. The rule exists. It was explained once, in a meeting, by the person who is out.
Illustrative scenario, not a customer result.How Kept helps
Ask first.
Read the source.
- 01
Ask Kept first
The team asks the question they would have asked the manager. Kept answers from the kept record, or says it does not know.
- 02
Read the source
The answer cites the conversation it came from. Open it, read the manager's own words, decide.
- 03
Keep moving
Decisions that can be made are made. Decisions that need the manager are marked as unknown, not guessed.
What Kept uncovers.
- 01
The rules a manager applies from memory, and the reasons behind them
- 02
Which decisions the team can take alone, and which need a sign-off
- 03
The questions that only ever reach one person
- 04
Where the team is dependent on one calendar
In your line of work.
Where this shows up first: the film for the engineering leader who feels it, and the other lines of work where it starts.
Also in: Operations Customer support IT & Security
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
The reason the retry limit is three isn’t in the code. It left with someone in March.
Architecture decisions and incident lessons fragment across repos and people, and the next outage repeats the last one.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
A new engineer opens the config and asks why it’s three. Kept answers from the March backfill and shows the exact words from the call.
Incident lessons and design reasoning stay with the system, not the person. Kept. Keep the knowledge behind the work.
Start at zero.
Pay once when the KPIs land.
The KPIs we would propose for when the manager is out:
- Questions answered with a source during a manager's absence, against escalations
- Manager-held rules and sign-off boundaries with a kept, cited answer
- Honest unknowns raised during the window, and how many became kept answers after it
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