Product
One evidence set, carried from first discovery to post-close operations.
Most integration programmes fail at the seam between the diligence pack and the delivery plan. Two teams, two spreadsheets, two versions of the estate. ACQI removes the seam by keeping one record from the first collector run to the last hypercare ticket.
Architecture
The product has three parts. A desktop application that operators work in. A service tier that schedules and executes collector runs. A database and evidence store that hold what was found, when it was found, and which credential read it.
All three sit inside your environment. There is no control plane of ours in the request path, and no analytics endpoint that sees your estate.
Every collected fact keeps its provenance. If two sources disagree about how many mailboxes a department owns, the product shows both readings, the timestamp of each, and the collector that produced them. It does not average them.
Inside the customer boundary
- Operator workstation: signed desktop application
- Service host: run scheduling, credential brokering, execution
- Database: estate record, conflicts, decisions
- Evidence store: raw collector output, immutable per run
- Log stream: local, exportable to your SIEM
Outside the boundary: nothing but the licence check and, if you enable it, the error-signature feed.
The five stages
Discover
Collectors cover Microsoft 365, Entra ID, Azure, Active Directory, AWS, Google Cloud, and on-premises hypervisor, network and endpoint inventories. Each run is scoped to an explicit set of endpoints and a named credential, and each run produces an evidence file. Read-only permissions are the default and the product will refuse a credential that carries write scope in a discovery-only run.
Consolidate
Entities are matched across sources into canonical records: person, application, workspace, site, device, licence, information system. Matching is rule-driven and inspectable, and every merge can be reversed. Where the rules cannot decide, the record is flagged for a human rather than guessed at.
Assess
The consolidated estate feeds security, compliance, organisational and commercial analysis. Because the analysis reads the same record as the migration plan, a finding raised in diligence is still visible when the wave that remediates it is scheduled.
Plan and migrate
Waves group workloads by dependency, not by convenience. Mappings translate identities, domains, sites and permissions from source to target. A rehearsal runs the plan against recorded state and reports what would have broken. Cut-over executes only what an operator has approved, and every action is logged against the person who approved it.
Operate and close
Day-one command shows service health, ticket volume and outstanding exceptions. Hypercare holds the queue until the estate is stable. Synergy tracking compares the modelled saving with the observed one and records the difference, including when the difference is bad news.
The surfaces an operator works in
Names as they appear in the product
| Surface | What it holds |
|---|---|
| Overview | Deal state, open work, exceptions that need a named owner. |
| Deal | Target record, deal team, stage gates, diligence requests. |
| Discovery Hub | Connector catalogue, run orchestration, topology and collector health. |
| Discovered Hub | Results browser for every discovered entity type. |
| Consolidated Enterprise Views | People, applications, workspaces, sites, licensing and information systems in one shape. |
| Organisation Map | Reporting lines, spans, duplication between the two organisations. |
| M&A Governance | Workstreams, decisions, risk register and the issue log. |
| Analytics | Estate measures with the query behind each figure. |
| Security | Identity posture, exposure findings, control gaps worth pricing. |
| Compliance | Obligations mapped to the estate, evidence attached. |
| Migration | Waves, mappings, rehearsal, cut-over and go/no-go. |
| Cloud Fit | Workload placement and landing zone readiness. |
| Licensing Hub | Entitlement against consumption, renewal exposure, duplication. |
| Operations | Day-one command, hypercare and run state after close. |
| Reports | Board pack, diligence appendix and the export set. |
| Aria Assist | In-product assistant over your own estate record. Scoped, audited, no external model call by default. |
| Setup, Administration, Settings | Environment connection, roles and policy. |
A sell-side perspective replaces the buyer tree with exit readiness, remediation, fact book, data room and buyer Q&A surfaces. A deal-side perspective keeps the view to the deal record, settings and the assistant.
What a deployment needs
- Operating system
- Windows 11 or Windows Server 2022 for the operator workstation and service host.
- Runtime
- Bundled. No separate .NET or PowerShell installation is required on the operator workstation.
- Database
- Microsoft SQL Server 2019 or later, in your tenancy. Azure SQL is supported.
- Directory
- Microsoft Entra ID, or Active Directory with Entra Connect.
- Network
- Outbound HTTPS to the target tenant endpoints you approve. No inbound path to the internet is required.
- Air gap
- Supported. Connector payloads can be carried across the boundary as signed archives.
- Footprint
- Service host 4 vCPU, 8 GB memory, 200 GB storage for a mid-size estate. Sizing is confirmed at scoping.
A deployment is a project, not a download. A first install typically takes two to four weeks of elapsed time: environment review, credential design, a pilot collector run against a non-production slice, then the production scope. We run it with your team rather than shipping a link.
If your environment cannot meet these requirements, say so at scoping. There are estates we cannot serve today, and finding that out on day one is cheaper than finding it out in week six.
Current state
The product is in active development with design partners. Some collectors and some migration workloads are complete; others are scoped but not built. The status page lists what exists and what does not, and it does not show a green light for anything we do not measure.
We would rather lose a deal to an honest gap list than win one on a promise we cannot keep in the customer's environment.
Not yet available
- Hosted or managed instance. There is no cloud offering.
- Self-serve trial. Evaluation is a scoped pilot with our engineers.
- Third-party marketplace billing.
- ISO 27001 or SOC 2 attestation. Both are planned.
Evaluate
See the shell before you see the price.
The preview is the real navigation and the real interaction model with a fictional deal loaded. It is gated because we do not publish unreleased screens.
Access is issued through the fund's application channel, or on request from a named contact at a prospective customer. The password is not published here.