International expansion is often described through the legal milestone: incorporate the company, complete the transaction, sign the lease or acquire the property. Those milestones matter, but none of them means the new operation is ready.
I saw this very clearly while leading a cross-border acquisition and operational-establishment programme in Colombia. The programme was approximately £25m and included a 263-rack data-centre environment, property, office fit-out, legal and regulatory work, recruitment and the transition into operational ownership. The legal entity was one workstream among many.
A company can exist without being operational
The distinction sounds obvious, but programmes regularly underestimate it. A legal entity can be registered while people still cannot work effectively. A building can be acquired while power, cooling, network or security remain incomplete. Recruitment can begin before workplace, access or operating processes are ready.
Each function can be progressing legitimately while the overall capability is still not viable. That is why I treat international establishment as an integrated readiness programme rather than a set of parallel departmental projects.
The question is not simply whether every function is busy or whether each individual workstream is on schedule. It is whether the conditions required for the operation to function are converging at the same time.
The critical path crosses functions
In Colombia, the programme connected due diligence, seller negotiations, legal entities, regulatory and Free Trade Zone requirements, construction, escrow, workplace, recruitment and technology infrastructure.
The data centre itself involved power, cooling, networks, servers, monitoring, security and testing. The office had to support more than 100 employees, while the legal and operational structures had to be ready for the organisation to function independently.
The important dependencies did not respect departmental boundaries. A property or construction decision could affect infrastructure sequencing. Infrastructure readiness could affect recruitment and operational timing. Regulatory requirements could constrain what could be commissioned or transferred.
The programme view therefore had to connect those plans around common milestones rather than simply collect separate status reports.
Readiness needs evidence
One lesson from international expansion is that assumptions travel badly. What is normal in one country, supplier relationship or operating environment may not be true in another, which makes evidence particularly important.
For the Colombia programme, I strengthened acceptance controls around third-party deliverables and connected financial approvals to actual delivery progress. That became especially important after a structural issue emerged in an annex to the acquired property.
Independent review established that the annex did not meet the required seismic standard and needed to be demolished and rebuilt. The programme then had to re-sequence critical infrastructure into the compliant main building, reduce the annex scope and secure seller accountability for reconstruction.
The legal acquisition had already taken place. The operational programme still had to absorb reality.
Protect the operating outcome
International expansion creates a strong temptation to preserve the original mobilisation date because so many stakeholders are working towards it. But the real objective is not to protect a ceremonial date; it is to establish an operation that can function safely and sustainably.
That means being willing to re-baseline scope and sequencing when necessary while protecting the capabilities that determine whether the new location can actually operate. In Colombia, moving critical infrastructure away from the annex allowed the wider programme to continue while the structural problem was handled separately.
The plan changed substantially, but the operating objective remained achievable. That is a more useful measure of control than simply preserving the original baseline.
Handover is part of establishment
Another common mistake is treating go-live as the end of the programme. A new operation only becomes successful when ownership can move from the mobilisation team into stable business-as-usual structures.
That requires support models, local responsibilities, supplier arrangements, processes, access, reporting and escalation routes to be clear enough that the operation no longer depends on the people who created it. For me, transition to operational ownership is therefore part of the programme definition from the beginning, not an administrative close-out activity.
This is also where weak establishment programmes can create long tails of dependency on the central team. If ownership, support and local capability have not been built deliberately, the operation may be technically open but not truly established.
Expansion is a capability-building programme
The same principle applied when I later led establishment of a software development company in Dublin, although the scale and infrastructure requirements were different. The recurring pattern was the same: legal setup, workplace, business services, technology, recruitment and operating ownership had to converge.
That is why I think the phrase “entity setup” often understates the delivery challenge. International expansion is really about building a functioning capability in a new environment.
The entity is necessary, but the programme is everything required to make it real.