Plain-English answers to the questions executives actually ask.

No. The value isn't the chat interface — it's the structured capture of experience, judgment, and unwritten knowledge that came before it. The chat is just the easiest way for a successor to retrieve answers later. Without the structured capture, a chatbot has nothing useful to draw from.

No. It supports training by preserving knowledge that would otherwise be lost or inconsistently transferred. Training teaches the official process; KeyPersonAI captures what experienced people do when the official process doesn't fit.

No. SOPs document the official process. KeyPersonAI captures the exceptions, judgment calls, relationships, and lessons that SOPs usually miss. The two complement each other — and the engagement often produces a list of specific SOP improvements as a byproduct.

Yes. Succession planning is one of the strongest use cases — particularly for retiring owners, family business transitions, and senior managers stepping back. The captured knowledge becomes part of the handoff package the successor inherits.

Yes. New employees often struggle most with the unwritten knowledge — the context, the exceptions, the relationships, the warning signs experienced people notice. A captured knowledge base gives them something to ask when there isn't a person available to interrupt.

The process is designed to feel like a conversation, not a software task. The person can answer naturally — by voice or in writing — without learning new tools. Structuring and organization happen on our side.

Start with the knowledge that would create the most disruption if the person were unavailable tomorrow. The scoping call helps identify the highest-risk areas — usually a mix of customer relationships, exceptions to standard process, and equipment or system-specific judgment.

Yes. Voice is the most common format. Text, scheduled video, and a mix of formats are also supported. The right format depends on the key person's preference and the role.

Typically two to six weeks for one role, depending on depth and availability. Roles with broad scope, regulated material, or sensitive client information take longer.

Yes. Existing SOPs, manuals, notes, checklists, and other materials are reviewed at the start of the engagement so interviews focus on what's actually missing rather than re-covering what's already documented.

The capture and structuring use AI, but knowledge-capture engagements include human guidance — particularly during planning, sensitive-topic handling, and final review. Pure automation tends to miss the judgment calls that make this kind of knowledge valuable in the first place.

Your company does. The captured knowledge belongs to you. It is not shared with anyone outside the engagement and is not used to train AI models.

No. Captured interviews, documents, and knowledge are processed under enterprise terms that prohibit using your data to train models.

Yes. Sensitive topics can be flagged in advance, restricted to specific roles, or excluded entirely. Captured material is reviewed and approved before broader access is granted.

Access is controlled by your company. The customer portal supports role-based access so the right people see the right information — and sensitive sections can be limited to specific reviewers or excluded from broader visibility.

For law firms, professional services, and other engagements with confidentiality or privilege concerns, the engagement is scoped to respect those boundaries. Sensitive material can be excluded, redacted, or held under client agreement. Formal compliance arrangements can be discussed for larger deployments.

Yes. The final knowledge base allows authorized users to ask questions in plain English and receive answers drawn from the captured interviews and documents — with citations back to the source.

Yes. PDF and Word exports are available for the playbook, successor guide, and knowledge base summaries — useful for board review, transition documents, and offline reference.

Three engagement shapes: Single Person Capture, Team Capture, and Ongoing Knowledge Continuity Programs. Pricing is consultative and tailored to scope. The pricing page describes what's included in each.

The first conversation is a no-pressure scoping call to understand the role, the timeline, and whether KeyPersonAI is a fit. If a pilot is the right fit, that's typically a Single Person Capture.

Most companies frame the value in terms of preventing one repeated mistake, shortening one painful transition, preserving one important customer or vendor relationship, or avoiding one operational disruption. The specific value depends on the role and the situation — that's part of the scoping conversation.

Yes. Most engagements begin with a single key person. Companies often see the result and then add additional captures from there.

Yes. The Ongoing Program tier is designed for organizations that want knowledge capture to be a continuous process rather than a one-time project. Formal compliance arrangements and dedicated support can be discussed.