Adoption
Partners who turned capture on and used Kept through the window. The minimum is a term of the pilot, so the measurement is fair to both sides.
Start at zero.
Pay when the value is proven.
A pilot with the terms written down before it starts: the KPIs, the window, and the minimum use. You pay nothing to begin. If the KPIs are met at the end of the window, a one-time payout is due and Kept continues at the recurring rate.
Kept for businessesFour steps. No surprises.
The pilot is the product in use, measured. Nothing in it is a demo.
- 01
Agree the KPIs and the window
We write down, with you, which KPIs count, how each one is measured, and the window we measure over. Nothing vague: every KPI is a number the workspace itself produces.
- 02
Start at zero
The pilot starts with nothing to pay. Your partners opt in, turn capture on themselves, and Kept starts keeping what they know.
- 03
Measure from the ledger
Through the window, the numbers come from the workspace: partners with capture on, what was kept and its coverage, questions asked, answers with a source, honest unknowns. You can export the audit ledger at any time.
- 04
Pay once when the KPIs land, then recurring
If the KPIs are met at the end of the window, a one-time payout is due and Kept continues at the recurring rate. If they are not met, the pilot ends and nothing is owed for it.
What we can measure.
Every KPI below is a number the workspace produces on its own. We pick the ones that match your use case or line of work and write them into the agreement.
Knowledge kept
What was captured per role in scope, and the coverage band per person moving from thin to covered. Never a rating of the person.
Cited answers
Questions asked of Kept, and the share answered with a source. The rest are honest unknowns, counted, not hidden.
Time to a cited answer
For a new colleague or a replacement: the days from their start to their first answer with a source, and the questions answered without interrupting a teammate.
Repeated questions
The ten most repeated questions in scope, and whether each one has a kept answer by the end of the window.
Handoffs and departures
Knowledge kept from a departing partner before their last day, by topic, and the successor's questions answered from it.
Continuity
Questions answered with a source while a manager or an expert is out, against the escalations that had to wait.
Traceability
Decisions and exceptions in scope with a kept rationale cited to the person who gave it, and the audit ledger exports produced for a review.
Systems in use
Systems and processes in scope with a kept, cited answer for how the team actually uses them.
Every use case and industry page carries the KPIs we would propose for it. Use cases · Industries
Written down
before we start.
- The KPIs, how each is measured, and the window are written down before the pilot starts.
- A minimum number of partners keep capture on and use Kept through the window; the number is set in the agreement, and the business plan starts at five seats.
- The numbers come from the workspace's own ledger and usage, exported for the review. Nothing is measured about a person that the product does not already show their workspace.
- Nothing to pay to begin. If the KPIs are met at the end of the window, a one-time payout is due and the subscription continues at the recurring rate.
- If the KPIs are not met, the pilot ends and nothing is owed for it. The knowledge kept during the pilot stays subject to the workspace's own controls, including deletion.
- No published price. Ask, and the offer with the recurring rate and the one-time payout comes by email.
What it is not.
Not a rating of people.
Kept shows a workspace what was captured and a coverage band per role. It never scores, ranks or monitors a person, and the pilot measures nothing the product does not already show.
Not capture by default.
Every partner turns capture on themselves and can stop at any time. The minimum-use term counts partners who chose to take part.
Not a demo.
The pilot runs on your workspace with your people. What is kept during it belongs to the workspace, under the same controls as any subscription, including deletion.
Questions?
Who sets the KPIs?
We propose them from the use case or line of work, you adjust them, and both sides sign the list before the pilot starts. Each KPI names how it is measured.
See the KPIs by use caseHow long is the window?
Long enough to be fair to the measurement, agreed before the start. Adoption needs a few weeks; onboarding and departure KPIs follow the people involved.
What does the pilot cost to begin?
Nothing. A one-time payout is due only if the KPIs are met at the end of the window, and Kept then continues at the recurring rate. The offer with both figures comes by email.
Ask for the offerWhat happens to the knowledge if we stop?
It stays subject to the workspace's own controls. Owners can export it or ask for deletion, and partners keep their review, hide and deletion-request rights throughout.
Read the controls