Contract intelligence is useful when the right people can examine the right records. Your pilot starts with an agreed data and access scope.
Workspace boundaries
The pilot uses authenticated accounts, workspace permissions and server-side access checks. Database row-level policies help keep tenant records separated. Confirm the roles and sharing arrangements for your deployment before onboarding.
Reviewable findings
Answers link back to supporting records and the selected benchmark. Draft benchmarks produce provisional findings. Missing evidence stays visible for reviewers to resolve.
Approved AI connections
In-app AI uses configured server credentials. Connector access is authenticated and scoped to permitted records. Agree the provider, processing terms and permitted data with your organisation.
Human decisions
AI helps identify differences; your team decides whether a departure is acceptable. Agree the approval process, operational ownership and review criteria during the pilot.
Define the production boundary.
A working pilot is not a security certification. Validate deployment settings, backup and recovery, data retention, access reviews and support arrangements before a production rollout. Curtis Fitch holds ISO 27001 certification. View the certificate and its scope. The Phoenix pilot is not independently certified; agree its deployment and data arrangements before onboarding.
When evidence reaches an AI client.
Retrieved evidence is processed under the client’s applicable settings and terms. Revoking Phoenix access prevents future retrieval, but cannot retract material already returned. Model choice alone does not establish private hosting or zero retention.
This website.
The product views use synthetic examples. The pilot form stores your enquiry so the team can respond; it does not accept contract uploads or take payments.