Define the separation perimeter
Map applications, data, infrastructure, identity, security, vendors, people, and shared services to expose what must move, be recreated, or remain under transition services.
Menu
Carve-outs & TSA exits
Make Day 1 real. Make TSA exit inevitable.
A separation plan is only credible when every critical dependency has an owner, an executable path, and a decision date. We lead the technology work from perimeter definition through standalone readiness and TSA exit.
Build Day 1 and TSA control
Translate dependencies into readiness criteria, service definitions, costs, governance, escalation paths, and a practical sequence of decisions and cutovers.
Drive standalone readiness
Coordinate buyer, seller, and third-party workstreams, surface cross-tower risk early, and keep the program moving through testing, cutover, stabilization, and exit.
The objective is not a separation plan. It is a business that operates independently, on schedule, with risk under control.
Talk through the mandate