An anonymous production deployment. The customer is real and the platform is in production; the customer is not named.
Estates acquired through corporate transactions are the hardest kind to govern. Nobody designed them. They arrived. The numbering an acquiring business inherits comes with its own carrier relationships, its own records, its own conventions, and usually no single person who can say what is in it.
This operator inherited exactly that: an international number estate that came with an acquired business, spanning multiple markets and carriers.
Deployed inside the operator's own cloud
The platform runs inside the operator's own cloud environment, not consumed as a hosted service from ours.
That is unusual, and it matters more than it first sounds. It means the governed record of the estate sits within the operator's own security and data boundary, under its own controls, while still being the authoritative record the platform governs. Governance did not require the estate, or its data, to move somewhere else.
It is also the sharper test of the operating model. A governance layer that only works when it holds everything is not really governing an estate; it is replacing one. This one had to work where the operator already was.
Delivery that reports what it finds
Work ran in defined phases against a live production platform, with transparency reporting on every phase and a standing monthly governance forum between the two companies.
That cadence is not incidental to the outcome. An inherited estate is discovered as much as it is migrated: what the records say and what the carriers hold are rarely the same thing on day one, and the gap is the work. A delivery model that reports what it finds, in a forum where both sides see the same report, is the one that survives the discovery.
What changed
The operator's own product programme is now being built to integrate with the governed record rather than around it.
That is the point at which a governance layer stops being a project and becomes part of how the business runs. The record is no longer something a team maintains alongside the systems that matter; it is the thing the next system is designed against.
Why it is anonymous
The deployment is real and in production. The customer has not been asked to be named for it, so it is not named here, and nothing in this account is intended to identify it.
If you are looking at a similar problem, seeing the whole identifier estate at once covers why consolidation projects on inherited estates so often stall, and the platform architecture sets out the model this deployment implements.