Supplier Side. Client Side. What Both Projects Taught Us About Representation.

We have managed two significant international projects in Turkey — one worth approximately €4 million, one worth approximately €6 million. On the surface, our role on both was similar: local representative, responsible for keeping things on track.

Underneath, the roles could not have been more different.

On the first project, we represented the supplier. On the second, we represent the client. The process was largely the same. The priorities, the pressures, and the daily realities were not.

This post is an honest account of both — what each role demands, where the real complexity lives, and what it means to sit on different sides of the same table.

Project One: Representing the Supplier

The first project was an automated warehouse system — specifically an AS/RS automated storage systems installation — built inside a restricted airside facility at an airport in Turkey. The system was designed to store and retrieve aircraft tyres at high speed and density, replacing a manual process that was slow, space-inefficient, and prone to human error.

The supplier was a European technology company. Our role was to be their person on the ground in Turkey: attending site meetings, coordinating with the end client, managing the Turkish supply chain, handling local procurement, and solving problems before they became delays.

On paper, the project had a clear scope. In practice, it had three layers of complexity that made it one of the most demanding engagements we have taken on.

Complexity 1: The restricted airside environment

The project site sat inside an active airport’s apron — the operational area where aircraft move, refuel, and are serviced. This is one of the most tightly controlled working environments in any industry.

Every person entering the site needed a security clearance and an active pass. Every vehicle needed a separate permit. Every piece of equipment and every material delivery required advance notification, documentation, and approval. Nothing moved without authorisation — and authorisation did not come quickly.

In a standard industrial project, a supply delay of two or three days is absorbed by adjusting the schedule. On this site, a delivery that arrived without the correct documentation simply did not get through the security gate. The material sat outside while the project waited inside. So we spent a significant amount of time managing that interface: coordinating documentation, pre-notifying security teams, and confirming every movement was cleared before the truck left the warehouse.

Complexity 2: A fragmented Turkish supply chain

The automated warehouse system required dozens of specialist components — structural steel, conveyor elements, electrical systems, control panels, sensors, cabling, and fixings — many of which had to be procured locally in Turkey to keep the project on schedule and within budget.

Turkish supply chains for industrial automation components are not always straightforward. Lead times were inconsistent. Some components were simply unavailable domestically and had to be sourced and imported, adding time and cost that the original project budget had not fully anticipated.

Furthermore, local procurement decisions had to be made quickly, with limited time for the kind of formal approval process a European headquarters typically requires. We had to balance speed — the project schedule was real and fixed — against the supplier’s internal procurement governance, which was designed for a European operating environment, not a Turkish construction site.

Supply chain management in this context was not a back-office function. It was a daily, on-site problem-solving exercise.

Complexity 3: Communication across three languages and two cultures

The supplier’s engineering and project management team was European. The end client’s facilities team was Turkish. The on-site installation workforce was a mix of both. Technical decisions needed to flow clearly between all parties — and they rarely did without active translation and mediation.

This was not primarily a language problem, though language mattered. It was a communication culture problem. The supplier’s project managers expected formal, written updates and change order documentation for every deviation from the plan. The client’s team communicated informally, made decisions verbally, and expected flexibility rather than process.

Sitting between them, our job was not just to translate words. It was to translate expectations: to frame the supplier’s concerns in a way the client would hear, and to represent the client’s priorities to a supplier whose instinct was to protect the contract rather than the relationship.

That dual translation function — technical and cultural — only works with genuine fluency on both sides.

What representing the supplier taught us. When you represent the supplier, your job is to keep the project moving without compromising the delivery. The hardest part is not the technical problems — it is managing the gap between what the contract says and what the site actually allows. Local problem-solving capability, not just project management process, is what keeps a complex industrial project on track.

Project Two: Representing the Client

The second project is ongoing — a major industrial installation in Turkey worth approximately €6 million. This time, our position at the table is reversed. We represent the client: a European company commissioning a significant piece of industrial infrastructure in Turkey.

The supplier is a well-established, technically capable company. The contract is structured along familiar international lines — the scope, variation, and claims architecture that the FIDIC contract framework made standard practice on engineering projects. The scope is defined and the timeline is agreed. Our role is to ensure that what was agreed is what actually gets delivered: on time, at the specified quality, and within budget.

This sounds straightforward. In practice, representing the client on a major project in Turkey requires a very specific set of skills — and a fundamentally different mindset from representing the supplier.

The client representative’s primary job: independent verification

A supplier’s project team is excellent at managing their own process. They know their system, their timeline, and their constraints. What they are not positioned to do is give the client an independent view of whether things are genuinely on track.

That is our job. Not to manage the supplier’s process — they do that. But to verify it: to attend design review meetings and ask the questions the client would ask if they were in the room, and to review milestone documentation not as the supplier’s ally but as the client’s eyes.

The commercial representative role, done well, is inherently independent — and that independence is only credible if it is genuine. A client representative who becomes too comfortable with the supplier, or too deferential to their explanations, stops being useful.

Managing the design and approval process

Large industrial projects go through multiple design review stages before a component is manufactured. Each stage requires client approval, and each approval decision has downstream consequences for the schedule.

On this project, our team attends design reviews on the client’s behalf, reviews technical submissions, coordinates the client’s feedback, and tracks whether supplier responses address the substance of the comments or simply close the action point. That distinction matters. A comment closed formally but not resolved genuinely is a quality risk that surfaces later — usually at installation, where it is expensive to fix.

Keeping that discipline — ensuring approvals are substantive, not just administrative — is one of the most valuable things a client representative does on a complex project.

Schedule and risk monitoring

Every project has a programme. Not every project follows it. Our role on the client side includes tracking the supplier’s production schedule against milestones, identifying risks before they become delays, and escalating proactively — giving the client time to respond rather than react.

For a European client without local presence in Turkey, this monitoring function is the difference between knowing about a problem in week three and finding out about it in week twelve. The former is manageable. The latter usually means costs, claims, and damaged relationships.

What representing the client taught us. When you represent the client, your credibility depends on your independence. The supplier has capable people who genuinely want to deliver well. Your job is not to duplicate their effort — it is to give the client a view of the project they cannot get themselves. That means being present, being specific, and being honest, even when the honest view is uncomfortable.

What Both Sides Have in Common

Despite the different roles and different pressures, both projects share the same underlying requirement: someone physically present, with the language, the relationships, and the judgment to navigate a complex industrial project in Turkey.

Remote oversight simply does not work at this level of complexity. A weekly video call and an emailed status report do not tell a client what is actually happening on a production floor or a construction site. They tell them what the supplier’s project manager has chosen to report.

The value of a local representative — whether on the supplier side or the client side — is the gap between those two things. Between what gets reported and what is actually true.

Why This Matters for Your Project

Most international projects in Turkey go wrong not because the supplier is incompetent or the client is unreasonable. They go wrong because the gap between them — in language, in culture, in expectations, and in physical presence — never gets properly bridged.

A European company commissioning a €6 million project in Turkey without local representation is managing that gap with email threads and occasional visits. A European supplier delivering a €4 million installation in Turkey without local support is managing a fragmented supply chain and a complex security environment from a Budapest or Stuttgart office.

Both situations are manageable. Neither is optimal. And the cost of the gap — in delays, in rework, in relationship damage — almost always exceeds the cost of closing it.

Our team has now sat on both sides of that table. We know what each role demands, where the real risks live, and what it takes to give either a supplier or a client genuine confidence that a complex project in Turkey is under control.

Managing a project in Turkey — on either side? MOPCONS provides on-the-ground project representation for both suppliers and clients operating in Turkey. Whether you need someone in the room on your behalf, or a local team to manage supply chain, approvals, and schedule monitoring, we have done it on both sides. Get in touch to discuss your project.

Frequently Asked Questions

What is the difference between a supplier representative and a client representative?

A supplier representative manages the delivery process on behalf of the company installing or providing a product or system. Their focus is keeping the project moving: coordinating local supply chains, managing site access, and communicating with the client. A client representative monitors the supplier’s delivery on behalf of the commissioning party — verifying quality, tracking milestones, and ensuring the client receives what was agreed. The two roles require different loyalties and different skill sets, even when managing the same project.

Why does a European company need local representation on a project in Turkey?

Complex industrial projects in Turkey involve Turkish suppliers, Turkish logistics, Turkish regulatory requirements, and Turkish business culture — all of which are best navigated by someone physically present and fluent in both languages. Remote oversight via email and video calls cannot replicate the visibility that comes from attending site meetings, reviewing production floors, and managing relationships in person. The gap between what gets reported remotely and what is actually happening on the ground is where project risk accumulates.

What does project representation cost compared to the risk of not having it?

The cost of a local project representative is a fraction of the project value — typically a small percentage of the total contract sum. The cost of a delay, a quality failure, or a relationship breakdown on a multi-million euro project is many times higher. On the projects we have managed, identifying a supply issue or a quality risk early in the programme has consistently saved more than the entire cost of the representation.

Can MOPCONS represent both sides on different projects simultaneously?

Yes, and we do. Our supplier-side and client-side engagements are managed as separate, independent mandates. Conflict of interest is taken seriously: we would not represent both the supplier and the client on the same project. But across different projects and different sectors, our team holds both types of mandate, and the experience of each informs the other.