Prepare for a product demonstration

Purpose and scope

Use a short, role-specific demonstration to show the product honestly while keeping unreleased and customer-specific areas out of view.

Use this guide as orientation, then rely on the signed agreement, current policy or named support response where those sources set a more specific obligation.

Prepare the right information

• Audience roles and available time.
• The workflow that matters most.
• Questions that must be answered or parked.

Follow the controlled process

1. Frame the needState the desired outcome, affected product and accountable contact. For prepare for a product demonstration, avoid assumptions that have not been confirmed in writing.
2. Review and decideUse the current governed source, record material questions and obtain approval from the person who owns the decision.
3. Retain evidenceKeep the final reference, date, decision and any follow-up action together so a later reviewer can reconstruct what happened.

Expected record

• A focused demonstration agenda.
• A record of questions and feedback.
• Agreed next steps.

Security and disclosure boundary

• Never send passwords, authentication codes, private keys or recovery codes to Obedience staff.
• Share the minimum customer, project and commercial information needed for the stated purpose.
• Public documentation explains controls and responsibilities without publishing exploitable topology, credentials or confidential implementation detail.