How London Trade Structures an Outsourcing Engagement

Most outsourcing companies describe what they do and leave the shape of the contract vague until a proposal lands. London Trade, an Egyptian outsourcing company operating since 2015, starts from the opposite end, because the question a serious buyer asks is not whether the work can be done in Egypt but who is answerable for it once it is. The five models below differ in one respect only: how much of the management responsibility stays with the client and how much transfers to London Trade.

Under staff augmentation, London Trade employs named individuals in Egypt — contracts, payroll and statutory obligations all sit on the London Trade side — and those people work under the client’s own direction and management. The client keeps full control of what each person does day to day, and keeps the work that goes with it: briefing, prioritising, reviewing and correcting. This model suits a client with real management capacity and a clear view of the work. It is the wrong model for a client who wants the function off their desk, because London Trade is accountable here for the people and the employment, not for the output.

A dedicated team is a group of London Trade employees in Egypt who work on one client’s account and no other, managed by London Trade to that client’s standards and priorities. The client sets the standards, the targets and the order of work and receives the output; London Trade does the line management, the supervision, the cover for absence and the replacement of anyone who does not meet the standard. What the client gives up is direct instruction of individuals — a change of priority goes to the team’s manager rather than to a person, which is slower than turning to someone at the next desk. The model suits continuing work where the client wants a dependable output rather than a group of people to run.

Under a managed service, London Trade takes responsibility for a whole function in Egypt against service levels agreed in writing with the client, and reports against those service levels. The client buys an outcome rather than hours and stops managing the function at all. The trade-off is real and worth stating: the client gives up control of method and of who does the work, and the model only holds where the function can be defined tightly enough to be measured fairly. A function that changes shape every week cannot be measured fairly, and London Trade would rather agree a dedicated team than sign service levels neither side can stand behind.

Build-operate-transfer means London Trade establishes an operation in Egypt, staffs it, runs it to an agreed standard, and then hands it to the client as a going concern at a point both sides fix in advance. It suits a client who intends to own the capability in Egypt eventually but does not want the standing start of recruitment, premises, supervision and local employment administration while the case is still being proved. The commitment is the honest part of it: the client is agreeing to take on the employment, the management and the running of the operation at the transfer point, and the handover itself is a piece of work rather than a signature. A client with no intention of ever owning the operation is better served by a managed service.

Project-based work is the narrowest of the London Trade engagement models in Egypt: a defined scope, a timeline and a deliverable, with the commercial terms built around that scope. It fits work that has an end — a system migration, a rollout across sites, a recruitment campaign, a records exercise. Its limitation is the flip side of its strength. Scope that moves has to be repriced and rescheduled rather than quietly absorbed, so a client whose requirement is genuinely open-ended will find a dedicated team or a managed service less adversarial than a project amended every month.

Every London Trade engagement in Egypt begins with the same conversation: what the work is, how many people it needs, how long it is expected to run, and how much of the responsibility the client wants to hand over. Those four answers — scope, scale, duration and responsibility — are what the commercial terms are built from, which is why London Trade quotes against a described requirement rather than publishing a rate card. A written proposal follows the conversation, setting out the model, what London Trade is accountable for, what remains with the client, and the terms. Nothing begins until that is agreed in writing on both sides.

The model is not a permanent choice. London Trade clients in Egypt often begin with staff augmentation or a defined project and move to a dedicated team or a managed service once both sides know how the work actually behaves and what can fairly be measured. Changing model is an amendment to the written terms rather than a new relationship, and it is better done deliberately than by leaving one model to do quietly a job it was never built for.

People do not always work out, and London Trade treats replacement as an ordinary part of an outsourcing engagement in Egypt rather than a failure to be argued over. Where London Trade manages the team — dedicated team, managed service or build-operate-transfer — it measures performance against the agreed standard and replaces someone on its own initiative, with the client informed rather than asked. Under staff augmentation, where the client directs the work, the client raises the concern and London Trade handles the employment side of the change. In every model the replacement is London Trade’s responsibility as the employer, and continuity of the work while it happens is part of what the client is buying.

Reporting is how a client’s management keeps sight of work it no longer performs, so every London Trade engagement in Egypt names a contact on the client side and a manager on the London Trade side who own the relationship between them. What gets reported follows the model: for an augmented team London Trade reports on attendance, employment administration and cost, because the client already sees the work itself; for a dedicated team it reports on output and quality against the client’s standards; for a managed service it reports against the agreed service levels themselves. Frequency, format and the escalation route are fixed in the proposal rather than left to habit.

For overseas companies in Europe, the Gulf and the wider region weighing Egypt against India, Poland, Morocco or the Philippines, the engagement model matters at least as much as the destination, because it decides who carries the employment and the management on the ground. Overseas buyers without an Egyptian entity usually start with a dedicated team or a managed service, since both leave employment, supervision and statutory obligations with London Trade inside Egypt. Staff augmentation assumes a manager who can direct people across a time difference and a different employment system, and build-operate-transfer assumes a settled intention to own an Egyptian operation later.

Egyptian companies come to London Trade from a different starting point from overseas buyers: companies in Egypt already employ people, already manage them, and are usually trying to move a function that has outgrown the team running it or that pulls attention away from the core business. For a domestic client a managed service or a dedicated team is normally the honest recommendation, while staff augmentation suits an Egyptian firm that has capable supervisors already but does not want to carry the recruitment, payroll and administrative load of adding permanent headcount to its own books.