The MEA Expansion Nobody Stress Tested

In my previous article, I argued that the market calling call centers uninvestable is not the end of BPO. It is the end of one cost curve.

The response was heavier than I expected, and it converged on one question: fine, so we move to MEA. What actually goes wrong? Across more than two decades and dozens of projects I have built, scaled or repaired in the Middle East and Africa, I have a fairly specific answer.

Here is that answer, and it will not be the one in your site selection matrix.

In 25 years of building contact center operations globally, most of them in MEA, I have never once seen an expansion fail because somebody picked the wrong city.

Regulation, cyber risk, political stability, currency exposure: these are real, and you should analyze all of them. But the expansions I have watched break did not break because someone misread the map.

They broke because nobody owned how the operation would actually live in that reality.

Six failure modes. Every one of them I have either lived through, inherited, or been called in to repair. In the few expansions that did not break under these pressures, the common pattern was simple: MEA was part of a long-term footprint and operating model before any single contract triggered the build.

Most expansion decisions I review are not decisions. They are reactions to a single client opportunity, dressed up as a growth plan.

The questions that never get answered properly: Are we entering this geography because of one contract, or because it belongs in the long-term footprint. Is the driver language capability, timezone coverage, or labour arbitrage. And critically, what is the go-to-market model. Partner and white-label, acquire, rent seats from a hosting provider, warm lease, cold lease, full greenfield build. There are a dozen viable variations. They have radically different capital requirements and radically different exit costs.

I have watched operators build for a 200-seat client, and discover twelve months later that the same client needs another 100 and a new client will require another 200 seats. Now the choice is to move everything, or run a second site with a second management team: a logistical and cost nightmare that no business case ever modelled.

In the rare cases where this did not happen, the operator had defined why MEA belonged in their global footprint, and which model they would use there, before the anchor client arrived.

Sometimes a location gets selected not because it passes the tests, but because it passes one test for one client at one moment. Every red flag gets waved through to hit a commercial window.

These projects are celebrated in year one. Then a new leadership team arrives, or the client changes their point of contact, and someone finally pulls the handbrake. The world is plastered with ex call center facilities that were once somebody's strategic masterstroke.

I was part of the leadership team that moved a global electronics brand's multilingual operation into Barcelona alongside a leading BPO. The geo study looked flawless: candidates across German, French, Dutch, Italian, Spanish, even Nordic languages. Cost per minute 30 percent below onshore. The talent was educated, multilingual, genuinely empathetic: a world away from the onshore site in a cold industrial city with strong unions and limited career paths.

Then reality arrived. Those agents were 20 to 30 years old, expats and students living in Barcelona for the life it offered. Contact center discipline, rigid schedules, high call volumes, strict adherence, was fundamentally incompatible with why they were in that city. Attrition went vertical within months. The cost advantage evaporated into a retention crisis. The operation eventually moved on.

Barcelona has hosted the European multilingual BPO industry since the early 2000s and many operators still deliver from there. But costs are now prohibitive, and a number of them survive only on the mercy of a single high-paying anchor client. The hubs that have held over time are the ones whose lifestyle, labour markets and work expectations align with the discipline the job demands.

A second one, more recent. I proposed Egypt for a 180-seat francophone requirement. The client's decision maker, of Moroccan descent, insisted on Casablanca Finance City (CFC). Selecting Morocco for French language business is somehow a reflex for many. The 50-seat trial came in 40 percent more expensive. Infrastructure costs climbed, attrition climbed, and the suppliers the client mandated were suboptimal. The project moved to Cairo after six months.

Sometimes the city was never the risk. The address was. In a BPO build-out, location is everything.

In Cape Town, Century City and Pinelands/Mutual Park are the perceived hotspots. If you need centrality and flexibility, the CBD or Foreshore work. On a tighter budget, Woodstock and Observatory are the more eclectic options. For one global US client, two large commercial floors on Long Street did the job perfectly. Or you skip Cape Town entirely, take Johannesburg, Rivonia, Sandton, Rosebank, and cut 20 to 40 percent off your cost base.

Cairo is equally layered. The hubs cluster around Sheikh Zayed, Nasr City/Abbasia, Maadi, Heliopolis, New Cairo, and Downtown. Most large BPOs default to the government facilitated technology parks, Smart Village, Maadi Technology Park, because they look like plug-and-play efficiency. They are, for about two years. Then you discover what it means to run your delivery center inside a park administered by government officials, surrounded by a dozen direct competitors who are recruiting from the same talent pool and poaching from your floor.

A concrete example. In 2020, during the COVID pandemic, we needed to move hundreds of PCs and monitors out of one of our sites so that agents could take them home and keep working. That site sat inside one of the government managed parks. Getting our own equipment out of our own building required escalation to my contacts at ministry level. That is what "administered" means in practice, and you only discover it on the day you cannot afford the delay.

One of my first decisions as CEO of a multi-thousand-seat, six-site operation in Egypt was to move delivery out of downtown Cairo and out of the government parks entirely: into a purpose-built site on the Cairo Ring Road, and a second in Alexandria. In the projects that never had to make that move, the operators had done the micro geography before signing: competition radius, transport reality, park dynamics, and the cost of control.

Perfect city, perfect address, and a central procurement team sitting eight time zones away bets on the wrong partners.

In the projects where these choices delivered instead of destroyed value, the operators did not abandon global brands. They used them where defensibility mattered, and complemented them with local partners who understood BPO economics and could be tested against a basic checklist: dual power and connectivity, competition radius, agent access, build cost per agent, and time to readiness.

Hiring the seed team is the single most consequential set of decisions in any build-out, and it is where budget pressure does the most damage.

The pattern is always the same. Overhead ratio gets locked to seat count to force a fast positive EBIT. A 50 seat ramp over six months does not "justify" an experienced Operations Manager at a 1:150 ratio, so a senior team leader or junior manager gets the role with a promise of promotion later.

This fails, predictably, for two reasons. First, that person is not just running an operation. They are firefighting the entire ramp up curve simultaneously: attrition, floor readiness, faulty equipment, transport, scheduling. Second, and more damaging, the Operations Manager is your best recruiter. The strong ones bring their previous team leaders and agents with them. And they recruit at or below their own level, so the seniority of your first ops hire sets the ceiling for your entire first cohort. Compromise there and you have compromised the operation for two years. The same dynamic applies to HR and technology leadership.

HR is the country lead's wingman, not a support function. Labour law compliance is critical across Africa, and HR sits at the intersection of legal exposure, recruitment pipeline, culture building, and attrition control alongside Ops. Get this wrong and everything else becomes harder.

And never underestimate the roles that look junior on an org chart. Drivers, security, a genuinely capable administrator. A loyal, well-connected driver in a city of 25 million people will save you time, money and credibility in ways no spreadsheet will ever capture. In most of my start-ups, when things went badly wrong, it was the strength of the seed team that determined whether we recovered.

Start-up leadership is a fundamentally different discipline from business-as-usual leadership, and BAU does not begin until year two at the earliest. I have watched large-ticket projects fail purely on leadership selection. A lion leading sheep beats an army of lions led by a sheep.

And then there is cultural fit, which is the one nobody scores properly on a hiring matrix.

I watched an operator deploy highly experienced Indian managers, genuinely good operators, deep contact center pedigree, to run teams of Saudi nationals for a leading telecom provider. None of them had worked outside India. The operational knowledge was real. The ability to lead that particular workforce, in that particular labour market, with that particular set of social expectations, was not there. It was never going to be there in the timeframe the project needed.

I watched a US player appoint an Operations Manager who had never set foot in Egypt to run a Cairo build. He struggled with the culture, the communication norms, and something as mundane and as decisive as the traffic. He was replaced within months, which was expensive, disruptive, and entirely predictable from the day he was appointed.

Neither of those failures was about ability. Both were about the assumption that a good operator is a portable asset. In this region, they are not. Someone on the leadership team has to be able to read the room, and reading the room here is a learned skill that takes years, not a briefing document.

The flipside is where the model works. In the expansions that did not fall apart, at least one senior leader came from the local market with full authority, and the seed team was budgeted as an asset, not squeezed as overhead. I call that layer Seed Team Integrity: the combination of seniority, cultural authority and trusted local network that holds a floor together when every other variable is moving.

I prefer to work with professionals I have worked with before, or who come recommended through my local leadership network. That is not preference. It is risk management.

Sometimes it is not the strategy, the location, or the team. Sometimes the world simply arrives.

In mid January 2011 I finalised the on-the-ground due diligence for a US BPO that wanted to set up in Cairo to provide English CX support for one of their largest US telecom clients. We shortlisted the right local partner, suppliers and seed team. It was a perfect setup. The week after I arrived back home, I watched the 25 January Revolution unfold on television. The project was paused by the client.

In 2016 I was leading a GCC BPO. I won a multimillion dollar Qatari airline programme delivered from Manama, Bahrain. Highly profitable, excellent client, until the Gulf diplomatic crisis of 2017. Under political pressure, the contract terminated within days. I was left with hundreds of Bahraini agents, no calls, no revenue, and a beautiful site.

In 2019, after a leading global BPO acquired a local Egyptian company with over 4,000 employees, I was brought in as first CEO. I inherited an operation built for local clients: underpriced, under-margined, in unsuitable facilities, with a leadership team not configured for global offshore delivery. The mandate was total transformation: team, business model, infrastructure, growth. I cut unprofitable accounts, restructured leadership, built an offshore delivery culture, closed the legacy sites and commissioned a purpose-built 14,000 square metre Centre of Excellence.

Then COVID arrived in the middle of it, Egypt's economy contracted sharply, and we moved thousands of employees to work from home within days.

Five of the six failure modes above share a root cause: somebody optimised the business case to get it approved, rather than building it to survive contact with reality.

Financial discipline in an expansion is not cost control. It is honesty at the modelling stage, and it starts with simple things such as attrition assumptions. When a financial model assumes 10 percent first-year attrition in this region, it is not a plan. It is a wish inside a spreadsheet. That wish is where three to five EBITDA points go to die when the operator and the buyer both choose optimism over operational reality. Model the real number, and if the real number kills the business case, you have just saved yourself two years and several million dollars.

The same applies to the ramp curve. Almost every model I review assumes a linear ramp to full productivity. Ramps are not linear. There is a plateau somewhere between month three and month five where attrition, floor readiness and supervisor bandwidth all collide, and the operators who survive it are the ones who budgeted for it rather than the ones who discovered it. Build the plateau into the model. Build the second recruitment wave into the model. Build the equipment failure rate into the model. Build buffers.

And separate your build capex from your operating P&L with real discipline. Fit-out overruns get quietly absorbed into operating costs, which contaminates your unit economics from day one and makes it impossible to know whether the operation is actually performing or merely being subsidised by a construction budget that nobody closed out properly.

Project management is the second half of this, and it is chronically underweighted. A new geography build is not a workstream that a country lead runs alongside their day job. It is a programme with hard dependencies: legal entity before banking, banking before payroll, connectivity before technology install, technology install before training, training before go live. Miss one sequencing dependency and you are paying rent on an empty building while your client's transition date sits in a contract.

I want a dedicated PMO from day one, with a single integrated plan, named owners for every dependency, and a weekly governance cadence that includes the client. Not because process is virtuous, but because the alternative is a project status that lives in six different heads and reconciles only at the point of failure.

And then KPI rigour, specifically, the right KPIs at the right stage. This is where most build-outs get measured badly. In the first six months, service level and AHT are not the numbers that tell you whether the operation will survive. Critical leading indicators are:

Those are the numbers that predict month twelve. Service level and CSAT/NPS are lagging indicators. By the time they move, the cause is three months old and the client is already having internal conversations about you.

I insist on two things here. First, one version of the truth: a single dashboard that the operator, the client and the leadership team all read, with no reconciliation layer between the floor and the board pack. Second, a named owner per metric who is accountable for the number rather than for reporting it. The gap between those two things is where most build-outs quietly lose control.

This layer is what I call the Expansion Risk Discipline: the combination of honest modelling, non linear ramp design, clean separation of capex and P&L, real PMO and leading indicators that treat risk as part of the operating model, not as an afterthought.

None of this is exotic. It is unglamorous, it is expensive to staff properly, and it is the first thing cut when someone needs the business case to clear an approval threshold.

Which brings me to the standard underneath all of it.

None of these failure modes appears in a site selection matrix. All of them appear in the P&L eventually.

Preventing them is not another consulting deliverable to be filed. It has to be a standard, and I call that standard operational integrity: a criterion that protects both the investor's P&L and the country and the talent you are entering.

Operational integrity is not a claim that we know how to operate and others do not. It is three concrete things:

Seed Team Integrity and the Expansion Risk Discipline sit inside this standard. One keeps the floor together when everything moves. The other keeps the numbers honest before anything moves.

Which is why, when an executive tells me their expansion plan is solid, my first question is never which city they chose.

I ask this:

If they cannot name the failure point, the plan has not been stress tested. And I would far rather help them find it on a whiteboard, before anyone moves bricks, seats or capital, than watch the market point it out six months later in their income statement.

If MEA is on your expansion map and you want to pressure test where yours breaks, put yourself directly on my calendar. Twenty minutes, operator to operator.