Landscapes and systems
How many SAP landscapes are in scope, and whether each has its own release, modification history, and transport route.
Priced against your landscape, not from a list.
We do not publish plan prices, because the number that matters depends on how many landscapes are in scope, how much custom code is genuinely live, and where the analysis is allowed to run. Tell us those three things and we will give you a figure and the reasoning behind it.
Custom object volume
The size of the custom code and dictionary inventory that has to be analysed, and how much of it is still executed.
Evidence sources
Which authorized exports exist already: ATC, Readiness Check, ABAP, abapGit, DDIC, transport, interface, and migration data.
Deployment boundary
Whether analysis runs in our environment or through an operator inside your network, and what may leave that network.
Retention and audit
How long evidence must be kept, and which controls your audit and procurement teams require.
Users and workflow
How many people review findings and approve changes, and whether SSO and provisioning are required.
Controls included in any engagement.
Immutable source hashes Ingestion coverage report Interpretable risk factors Observed dependency graph Deterministic remediation rules Reviewable unified diffs Validation-state legend Impacted test selection Named coverage gaps Clean-core score Human approval history Evidence export
What happens after you contact us
We ask what you are trying to change and which evidence already exists. If the work does not fit what Adranum does, we will say so rather than scope around it. If it does, you get a bounded technical evaluation with a stated boundary before any commercial conversation.