Kept for RevOps.
The revenue engine runs on definitions someone chose for a reason. Three films on keeping the logic behind the funnel.
All industriesFor executives
The dashboard is confident. Is anyone sure why?
Every revenue number rests on definitions somebody chose, for reasons somebody knew, who may no longer work here.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Three teams use the word qualified and mean three different things. The routing rules assume a fourth.
Definitions and routing logic drift between teams, and the pipeline numbers you’re steering by drift 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.
A new ops hire asks why rule 17 exists before changing it. Kept answers with the capacity reason and cites your call.
Shared definitions hold, so the numbers you steer by hold too. Kept. Keep the knowledge behind the work.
Stage definitions, attribution rules, the exception logic in the commission calc: revenue truth is a stack of decisions, and the stack's documentation is usually a person. When that person leaves, the numbers keep printing, and the ability to defend them quietly does not.
Kept captures the reasoning from the people who built the engine and keeps it cited: why the stage gate sits there, what that field actually means, which report is trusted and which is decoration. When the board asks why, the answer has a name and a date on it.
For managers
Nobody inherits a CRM. They excavate one.
Every workflow rule was somebody's fix for something. Change one without the story and find out which.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Three teams use the word qualified and mean three different things. The routing rules assume a fourth.
You spend the pipeline meeting reconciling definitions instead of running the pipeline.
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 ops hire asks why rule 17 exists before changing it. Kept answers with the capacity reason and cites your call.
The pipeline meeting runs the pipeline. Kept. Keep the knowledge behind the work.
The instance is an archaeological site: validation rules from a 2023 crisis, a routing flow tuned to a rep who left, fields three teams read differently. Every admin transition triggers weeks of careful digging, and every confident cleanup breaks something sales was quietly depending on.
Kept interviews the people who shaped the system and keeps the why in their words, cited and current. Changes start from reasons. New admins ramp from answers. You see what is covered across the team, and nobody gets graded on any of it.
For partners
You are the documentation layer of the revenue stack.
Every week someone asks why the field behaves that way. Every week the answer is a meeting instead of a lookup.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Three teams use the word qualified and mean three different things. The routing rules assume a fourth.
You fix a routing rule without knowing who set it, and a week later a lead lands in the wrong queue.
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 ops hire asks why rule 17 exists before changing it. Kept answers with the capacity reason and cites your call.
You change a rule knowing who set it and why. Kept. Keep the knowledge behind the work.
Kept talks with you about the system you actually built: the rules, the exceptions, the reason that automation exists. It keeps your answers in your words, and the next question finds your explanation, cited to you, instead of finding your calendar.
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 revops.
One process, one question the team already asks.
Start at zero.
Pay once when the KPIs land.
The KPIs we would propose for a revops team:
- Systems and processes with a kept, cited answer for “how do we use this here”
- Partners with capture on who use the systems in scope, through the whole window
- 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