Standing up the new entity software estate.

Standing up the new entity software estate is the buyer side work of building a complete, independent and properly licensed software environment for the carved out business, so it runs entirely on its own systems and contracts once the transition services agreement ends. This is the final stage of a carve out and the one that decides whether the deal produced a clean standalone company or a fragile one that depends on the parent and carries a future audit. Standing up the new entity software estate well means building it in the right order, licensing every application in the new entity name, and putting in place the governance that stops the next audit before it starts. Done badly, the estate inherits the same latent licensing exposure the carve out was supposed to resolve.

Why standing up the new entity software estate matters

The new entity estate is what the business actually runs on after the TSA ends, so its quality is the quality of the company that emerges from the carve out. An estate stood up in a hurry, with applications still half on parent licenses and integrations copied rather than rebuilt, looks like it works on day one and then fails its first audit or its first month end. An estate built deliberately, layer by layer, with every entitlement owned in the new entity name, gives the business a clean foundation and removes the inherited exposure that standard due diligence usually misses. The difference between the two is not visible at the exit date, which is exactly why buyers underinvest in it, and exactly why it produces problems later.

Standing up the estate is also the buyer last chance to fix the licensing position before the new entity is operating alone and exposed. Anything not resolved here, a shared agreement that never split, an application running without a contract, a service account still pointing at the parent, becomes the new entity problem and the publisher opportunity. This stage is the natural endpoint of the carve out software licensing playbook and the destination of the work begun in exiting the TSA cleanly on software.

The four layers of a clean estate

A new entity software estate is built from the foundation up in four layers, and the order matters because each layer stands on the one below. Identity and infrastructure come first, because nothing runs until the new entity has its own directory, network and hosting, and every user and application depends on them. Core applications come next, the ERP, finance and HR systems, each re licensed in the new entity name rather than borrowed from the parent. Integrations and data follow, rebuilt to point at the new entity systems and reconciled so the records are complete, not just copied. Governance and software asset management sit on top, the controls that keep the estate clean and catch overuse before a publisher does. The table sets out each layer with what it establishes and why it matters.

Building in this order prevents the most common failure, which is standing up applications before the foundation is ready and then rebuilding them when identity or hosting changes. It also makes the licensing position clean by construction, because each application is licensed in the new entity name as it is stood up, rather than retrofitted onto a contract later. The governance layer is the one buyers most often skip, and it is the one that prevents the new entity from walking straight into the next audit, a point developed in negotiating software terms for the new entity.

Licensing the estate in the new entity name

The licensing principle for the new estate is simple and absolute. Every application the new entity runs must sit on a contract in the new entity own name, counted on its own metric, with its own support line. Nothing should depend on a parent agreement, and nothing should run without a contract behind it. Where an entitlement could not transfer, the application is re licensed from scratch, the cost of which should already have been priced into the deal, as set out in re licensing the carved out business from scratch. Where a shared agreement was split, the new entity portion is confirmed in its own contract. The estate is only clean when every line passes this test.

This is where inherited exposure is finally closed out. A carve out concentrates the conditions that produce publisher claims, because users, environments and agreements all move at once, and the same conditions lay behind SAP pursuing Anheuser Busch InBev for a reported 600 million dollars, as reported in trade coverage as of 2017. Standing up the estate with every application licensed in the new entity name is what removes that exposure rather than carrying it forward. This is commercial and licensing work, and the new entity own counsel should interpret any contract term that governs how an entitlement may be held or used.

Governance that stops the next audit

The last layer, governance and software asset management, is what keeps the estate clean after the carve out is over. A new entity that stands up a clean estate and then lets it drift, with no record of what is licensed, no tracking of deployment against entitlement and no owner for publisher relationships, simply recreates the exposure the carve out resolved. Putting in place a software asset management function, even a lightweight one, gives the new entity a live picture of what it owns and what it uses, so overuse is caught and trued up on the new entity terms rather than discovered in an audit on the publisher terms. This governance layer is the difference between a clean break that lasts and one that quietly degrades, and it is delivered as part of our carve out and TSA separation service and the wider carve out playbook.