A CEO or COO running a freight forwarder, a 3PL, or a 4PL does not get to control geopolitics, weather, port congestion, carrier capacity, currency moves, or labor actions. The list of variables sitting outside the operating model is long, and it keeps getting longer.

What you do control is whether your structure is built to deliver the outcomes your strategic customers asked for, consistently, while the world keeps moving. That starts with strategic clarity about which customer outcomes matter most. It ends with a function designed to hold those outcomes together no matter who, where, or how the work gets done.

The most reliable way to lose a strategic account is to leave that function undefined.

This case study is written for the VP of Strategic Accounts watching satisfaction scores slip on the customers that fund growth, for the COO who senses the contract and the daily delivery are drifting apart, and for the commercial leader fielding escalations that should never have reached their desk.

Most organizations facing a strategic-account problem invert the sequence. They start with cost. They cut, they consolidate, they relocate, and they assume the customer experience will hold. It rarely does.

The correct sequence runs in the opposite direction. Define the outcomes your strategic customers need to consider you indispensable. Reinforce or rebuild the function that owns those outcomes end to end. Decide how the work inside that function should be sorted and tiered. Then, and only then, decide where the work should live.

Define the outcomes. Reinforce the function. Sort the work. Decide the location. Each layer makes the next one possible. Reverse the order and you get cost reduction that erodes service. Keep the order and you get a function that scales with the business.

The Americas case study that follows did it in the correct order. The results, presented later, reflect that sequence directly.

A logistics organization supporting high-value strategic accounts across the Americas faced a familiar pattern. Costs were high. Volumes were large. Margins were thin. A Customer Program Management function existed, but in name more than in design. The role was stretched thin across administrative work the CPM had to handle personally, with limited technology and automation support, leaving little capacity for the strategic ownership the role was theoretically responsible for. Account coordination still defaulted to whoever was closest to the work. Escalations still followed the org chart. Customers still learned to call three people to find one answer.

The structural choice was to reposition the Customer Program Management function as a real structural role rather than a stretched title. The role itself is called Customer Program Manager, or CPM, and the same function travels under other names in other organizations. Key Account Manager. Strategic Account Manager. Account Director. The label varies. The structural responsibility does not. One named owner, accountable for the customer outcome end to end, regardless of which function inside the operation has to act.

Critically, CPM coverage was designed to flex by customer tier. Enterprise customers, where size, scope, complexity, and revenue justified the investment, received dedicated CPM coverage. Other strategic customers were grouped into manageable portfolios under a single CPM, because the design underneath made that span workable without sacrificing quality.

What made the tiered span possible was the work itself being sorted. Transactional tasks moved to lower-cost, lower-experience operators with the right enabling technology to execute them reliably. Coordination and exception management sat with an admin support layer. The CPM was freed to do the work only a CPM can do: own the customer relationship, the contractual commitments, the executive escalations, and the performance dashboards that show the customer their outcomes are being delivered.

Then, after the function and the tiering had been proven in market, the model transitioned nearshore. The sequence is the point. Strategic clarity defined the outcomes. The operating model defined the function and its tiers. The work design defined the resource profiles. The location decision came last, applied to a structure that already worked.

Once the Americas model demonstrated that the function held under load, the framework was scaled globally to support key accounts with consistent, contract-aligned service across regions.

Three numbers, presented in the order they actually justify the design.

Strategic account coverage grew by 20%. The tiered CPM model created the capacity to extend dedicated and portfolio coverage across a meaningfully larger book of strategic customers than the previous structure could support. The model scales.

Customer satisfaction rose by 15 points. Customers experienced one steady hand managing their account, one set of dashboards, one escalation path. The model delivers outcomes.

Labor savings exceeded 60%. The combination of work-tier sorting, admin support layering, enabling technology, and the nearshore location decision produced material cost reduction without compromising the function. The model is also economical.

Cost was the consequence, not the goal.

The reason this structure holds under pressure is that it isolates the customer from the variability of the network. Carriers change. Lanes shift. A port closes. A currency moves. A geopolitical event reroutes capacity overnight.

A well-designed Customer Program Management function absorbs the variability before it reaches the customer. The CPM owns the customer outcome regardless of which lever underneath has to be pulled. The customer feels continuity. The operation feels the disruption. That separation is the structural achievement.

This is what Bestshoring looks like when it is done as architecture rather than as cost reduction. The location decision is a consequence of a structural design that already works. It is not the design itself.

Before scheduling the next strategic-account review, answer these three questions honestly.

1. Have you defined, in writing, the specific outcomes your top five strategic customers need from you to consider you indispensable, or are those outcomes inferred from the contract and the latest QBR deck?
2. If your strategic accounts already have a named owner, does that owner have the support structure, technology, and freed capacity to actually own the outcome, or are they spending most of their time managing the work that should sit underneath them?
3. When something outside your control disrupts the network, does your customer feel one steady hand managing the recovery, or do they get routed through the org chart looking for it?

If any of those answers came back uncertain, the structure that holds your strategic accounts together has gaps the customer is already feeling, whether the dashboard shows it or not.

The Bestshoring Readiness & Health Check™ is a twenty-question strategic diagnostic for shared services and BPO leaders, scored across the six dimensions that determine whether an operating model is built for today’s strategy or yesterday’s design. It takes about five minutes. It produces a readiness band with thirty, sixty, and ninety day priority actions.

If the three questions above surfaced uncertainty about how your strategic accounts are held together, that is one signal. The Health Check tells you whether the same pattern shows up across the rest of your operating model: strategic clarity, model fit and value, talent and cultural readiness, governance and risk, customer impact, and digital and AI readiness. Strategic-account structure is one expression of Bestshoring readiness. The Health Check assesses the whole.

If your operating model is broadly aligned, the Health Check confirms it. If it has notable vulnerabilities or higher risk, you find out where the load-bearing walls are missing while you still have time to build them.

So the closing question is the one that matters: which of your top five strategic accounts would your largest competitor target first, and what would they find missing if they did?