1. Agree the records
Identify the systems, record owners, access requirements and matching references. Establish what can be connected, what may need an export and what remains outside the review.
Connect → Review → Decide
2. Examine the finding
Relate the records, show the contributing evidence and flag missing or stale information. Distinguish what was observed from an interpretation, forecast or proposed priority.
3. Support the responsible team
Identify the owner and next permitted step. The team validates the finding, resolves uncertainty and decides whether to assign, escalate or use an approved workflow.
The One-Question Pilot
Start with one question that matters to your organisation. Agree the relevant systems, access requirements, success criteria and scope. Review the findings, supporting evidence and next steps before deciding whether to expand.
Duration, price, system limits, deliverables and data-handling terms are established before the engagement.
Practical questions, before you start.
Does GYR Lens replace our systems?
The approach is to connect relevant information across the ERP, service-management, identity and security tools you already use. Those systems remain responsible for their existing operational processes.
Is the analysis read-only?
The proposed starting scope is read-only analysis. Confirm the exact source permissions and any export or write-back mechanism during technical assessment. Recommendations do not authorise changes to source systems.
Where can it be hosted?
Hosting is assessed against your security and operational requirements. Self-hosting requirements, models, storage and supporting services need to be established for the selected deployment. Self-hosting alone does not establish air-gapped compatibility.
Who can access the data?
Agree the roles, source permissions, environment boundaries and administrative responsibilities before providing access. Review how those requirements will be implemented and verified in the selected scope.
What is audited?
Agree which access, analysis and workflow events require an audit record, who can review them and the required retention. Confirm the implemented coverage as part of acceptance; no universal retention period is specified here.
Which integrations are confirmed?
The named systems on this website are example sources, not a catalogue of verified connectors. Assessment covers interfaces, permissions, licensing, matching keys, refresh behaviour and any custom integration or approved export needed.
What do we need for a pilot?
Bring one priority question, a business owner, a list of relevant systems and a description of the records involved. Agree access, data-handling terms, success measures, scope, duration, price and deliverables before starting.
How would we judge success?
Possible measures to agree include evidence completeness, validated exceptions, correct ownership assignment and review time for a defined set of records. Establish a baseline and review the same scope; these are proposed measures, not achieved results.
What happens if we stop?
Agree access revocation, data return or deletion, configuration ownership and any ongoing obligations in the engagement terms. No default ownership or retention commitment is made on this website.