The contract was global. The execution wasn’t.

When the contract is global but delivery is local

At ACSL, the commercial model appeared relatively straightforward from the centre. Large enterprise customers such as Manpower and A.P. Moller Maersk signed global agreements with IBM, with commercial terms, standards and expectations defined centrally.

The complexity emerged when those agreements moved into execution. Each country depended on a local reseller partner to interpret the contract, configure the appropriate products, manage local requirements and coordinate delivery. The customer experienced one global agreement, but the work required to fulfil that agreement was distributed across numerous local organisations.

That created a specific form of commercial risk. The agreement itself could be perfectly clear while the customer experience still deteriorated through inconsistent interpretation, unclear ownership or weak handovers between central and local teams.

‍

Scaling the network increased the coordination challenge

What began with a limited number of countries expanded into multiple enterprise accounts across Europe, Asia, the Americas and Oceania. Each additional market introduced another set of partners, local operating realities, time zones and dependencies.

The difficulty was therefore not simply logistical. The broader challenge was making a distributed network behave like one coordinated delivery system, even though the organisations involved did not share the same management structure or local conditions.

As the scope grew, relatively small misunderstandings became more consequential. A configuration issue in one country, an unclear responsibility between partners or a delay in interpreting the global agreement could quickly become visible at account level and affect confidence in the wider relationship.

‍

Using local reseller experience to anticipate friction

My previous experience at reseller and local execution partner AXI proved particularly useful because I already understood the environment in which the local partners were operating. I knew how resellers handled IBM product codes and configurations, which information they required before they could execute and where commercial or operational processes were most likely to stall.

That perspective allowed me to look beyond the central account relationship and consider what each local partner needed in order to deliver successfully. Instead of waiting for execution problems to surface, I could anticipate many of the points where ambiguity was likely to appear.

The distinction mattered because local partners were not simply fulfilment mechanisms. They were the point at which the global agreement became real for the customer, which meant that their understanding and execution quality directly influenced the value of the central contract.

‍

Creating structure around ownership and handovers

As the network expanded, coordination needed to become more deliberate. Partners required a consistent understanding of the agreements they were executing, while responsibilities had to remain clear across regions and between central and local teams.

The work increasingly focused on standardising how agreements were interpreted, clarifying ownership and creating a more consistent follow-up rhythm across countries. The objective was not to remove every local difference, because individual markets inevitably had their own requirements, but to ensure that those differences did not undermine the central commitment.

This moved the operating model away from reactive problem solving. Instead of treating each delivery issue as an isolated exception, recurring friction could be understood as evidence that a handover, responsibility or communication process needed greater structure.

‍

Managing one account across several working days

The geographic spread introduced another dimension to the operating model. Asia required attention early in the European morning, activity continued across Europe during the day, and North American coordination extended the working cycle into the evening. Deliveries involving New Zealand could push that rhythm further still.

One rollout in New Zealand required calls around midnight while normal operations continued across Europe and the United States. The experience made the underlying issue particularly visible: execution problems were often less likely to originate inside an individual region than in the transitions between them.

That changed the emphasis from managing a collection of tasks to managing the quality of coordination between multiple actors. Time zones increased the pressure, but the underlying requirement was the same in every region: the next person in the chain needed enough clarity to continue the work without recreating the context from the beginning.

‍

Turning distributed partners into a delivery system

As the model matured, the work became more repeatable. Global agreements could be translated more consistently into local execution, accountability improved across partners and regional handovers became easier to manage.

That made it possible to scale from individual account delivery into a broader global account model spanning several continents. The same coordination principles could also support additional enterprise customers, including Microsoft, because the operating structure was no longer dependent entirely on the knowledge surrounding one account.

The value of the model therefore lay in its repeatability. A distributed partner network could support global customers effectively when ownership, interpretation and follow-up were structured strongly enough to compensate for the organisational and geographic distance between participants.

‍

Protecting the global promise through local execution

The experience reinforced an important lesson about international commercial models. Signing a global agreement creates consistency at the contractual level, but it does not automatically create consistency in the customer's experience.

That consistency has to be rebuilt at every execution point through clear ownership, reliable information and strong coordination between the people responsible for delivery. The larger the network becomes, the more important those mechanisms are because every additional handover introduces another opportunity for the original commitment to become distorted.

At ACSL, the commercial challenge was therefore not simply managing global accounts. It was creating enough structure around a distributed delivery network for customers to experience one organisation, even when the work behind that experience involved many different partners across multiple countries and time zones.