Kept for Sales.
The pipeline survives the quarter. The reasons deals close should survive the rep. Three films on keeping the selling knowledge.
All industriesFor executives
The CRM kept the fields. The rep kept the reasons.
Every departed rep takes the same thing with them: the real story of every account they ran.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Your best rep’s objection handling exists only in call recordings nobody has time to watch.
Every rep who leaves takes account context and proven answers with them, and the pipeline they built goes cold.
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 rep hits the same objection and asks Kept. They get the reframe, the math, and the discount line, cited to the rep who closed it.
Proven answers stay with the team when the rep moves on. Kept. Keep the knowledge behind the work.
Your CRM records that the deal closed. It does not record that the champion hates demos before ten, that procurement folds if legal goes first, or that the whole account almost walked over an invoice in March. That context is the difference between a handoff and a restart, and today it resigns with the rep.
Kept interviews your sellers about their accounts and their craft, and keeps it as cited memory the workspace owns. The next rep opens the territory with the story, not just the fields. Revenue stops re-learning what it already paid to learn.
For managers
Ramp from deal stories, not shadowing schedules.
Your best rep's territory knowledge is a training program nobody can attend.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Your best rep’s objection handling exists only in call recordings nobody has time to watch.
You re-explain the pricing objection on every deal review, and the rep still improvises on the call.
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 rep hits the same objection and asks Kept. They get the reframe, the math, and the discount line, cited to the rep who closed it.
Deal reviews start from what worked, not from scratch. Kept. Keep the knowledge behind the work.
New reps ramp by borrowing time from your quota carriers. Shadow calls, forwarded threads, the same three questions about the same four accounts. The knowledge transfers at the speed of favors, and the people best at selling are the ones with the least time to teach.
Kept captures how each seller actually runs their book, in conversation, and keeps it queryable for the team. Territory handoffs come with the history attached. You see what your team has captured and where the gaps are, as coverage. Kept does not rank your reps and will not start.
For partners
Get credit for the playbook in your head.
You know things about your accounts that no field in the CRM has a name for.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Your best rep’s objection handling exists only in call recordings nobody has time to watch.
The buyer pushes back on price, and the answer that worked last time isn’t yours yet.
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 rep hits the same objection and asks Kept. They get the reframe, the math, and the discount line, cited to the rep who closed it.
The answer that closed the last one is yours on the next call. Kept. Keep the knowledge behind the work.
Kept has a conversation with you about your accounts and how you sell, and keeps what you choose to share in your own words. When a teammate inherits an account you built, they read your version of the story, cited to you. Your work travels with your name on it.
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 sales.
One process, one question the team already asks.
Start at zero.
Pay once when the KPIs land.
The KPIs we would propose for a sales team:
- Time from a new colleague's first day to their first cited answer
- Questions answered by Kept in the first 30 days instead of by a teammate
- 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