Customers

The estates that are hardest to model are the ones that need it most.

Accqrate is used by architecture teams in groups with multiple legal entities, mixed estates and a transformation programme already in flight.
Typical entity count
3 to 40 companies in one repository
Typical first catalogue
Applications, then interfaces
Typical trigger
Rationalisation, migration or carve-out
Typical first result
A populated catalogue in weeks
01Scenarios
Six situations we see repeatedly.
These are composite scenarios drawn from the kind of work Accqrate is built for, not named case studies. Named stories replace them as customers approve publication.
Manufacturing group / 14 entities
Nobody could say how many ERP instances the group ran
Each acquisition arrived with its own stack and its own spreadsheet. The application catalogue was populated entity by entity through guided import, then duplicate detection ran across the group. The rationalisation case was built on interface and contract data rather than licence counts alone.
Where it landed
A single portfolio view across all entities, and a decommissioning sequence ordered by interface dependency rather than by which system was least popular.
Financial services / regulated
The audit asked for an interface inventory nobody had
Integration documentation existed as diagrams attached to closed project records. Diagram discovery proposed interface records from those files, an architect reviewed each one, and data classification was applied to the flows that crossed borders.
Where it landed
A maintained interface catalogue with named owners and review intervals, and an evidence pack that is now produced as a report rather than a project.
Energy and utilities
Obsolescence was being discovered, not planned for
Operational technology and back-office systems shared no common record. Software was catalogued at version level with vendor support dates, and hardware was brought in with site, warranty and refresh data.
Where it landed
A rolling four-quarter obsolescence calendar, with the business processes behind each item visible next to it.
Group carve-out
A subsidiary had to be separated in nine months
The entity's estate was isolated in its own company space, shared services and cross-entity interfaces were identified explicitly, and a cloned environment held the separated target state while production stayed untouched.
Where it landed
A self-contained model handed to the buyer, and a separation plan whose dependencies had been tested before the programme committed to dates.
Public sector agency
Architecture existed, but only in one person's head
Existing registers were imported, ownership was assigned to named officers, and review workflows were configured so records are confirmed on a schedule rather than when someone remembers.
Where it landed
A model maintained by roles rather than individuals, and a data quality score that gives leadership a defensible answer about coverage.
Retail and logistics
Cloud migration waves kept slipping
The programme had an application list but no complete interface map, so each wave uncovered dependencies late. The interface catalogue was built out, then impact analysis re-sequenced the waves.
Where it landed
Waves ordered by dependency, and a target state environment the programme could plan against without editing production.
02By sector

What tends to matter most, by sector.

Manufacturing and industrialMulti-entity structures from acquisition, plant systems and operational technology alongside corporate IT, and long asset lifecycles that make the hardware layer meaningful.
Financial services and insuranceRegulatory evidence, complete interface inventories, data classification on cross-border flows and demonstrable change control.
Public sector and agenciesContinuity of knowledge across staff changes, procurement and contract transparency, and defensible reporting on coverage.
Energy and utilitiesObsolescence planning across very long-lived assets, site-level hardware records and the boundary between operational and corporate estates.
Healthcare and life sciencesValidated systems, supplier support windows, and interfaces carrying regulated data between clinical and administrative platforms.
Retail, transport and logisticsStore and site estates, seasonal capacity, high integration density and migration programmes that depend on accurate dependency sequencing.
03In their words
Placeholder quote. One specific outcome, in the customer's own words.
[Name], [Role], [Organisation]
Placeholder quote. Ideally something that names a decision the model made possible.
[Name], [Role], [Organisation]
Placeholder quote. Short is better than complete.
[Name], [Role], [Organisation]
Bring the estate that worries you most.
A working session using your own application list. If Accqrate is not the right answer for where you are, we will say so.