Understand pricing and scoping

Purpose and scope

Treat published plan descriptions as a starting point and confirm price, capacity, services and customer-specific work in writing.

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

• Users, projects, storage and support needs.
• Integration and custom-panel scope.
• Implementation and decision timetable.

Follow the controlled process

1. Frame the needState the desired outcome, affected product and accountable contact. For understand pricing and scoping, 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 scoped commercial proposal.
• Capacity and service assumptions.
• A clear validity period and approval route.

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.