Select a product for your outcome

Purpose and scope

Match a business outcome to Global, QuantifyQS or Cloud before starting an evaluation or support request.

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

• The commercial workflow to improve.
• The people who will use or administer it.
• Any identity, storage or integration dependency.

Follow the controlled process

1. Frame the needState the desired outcome, affected product and accountable contact. For select a product for your outcome, 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 recommended product surface.
• Known cross-product dependencies.
• Questions for discovery.

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.