The Pipeline Is Always Big

The Number Is Not the Information

A pipeline on a Gulf review slide is rarely small. The projects here are substantial, the quoted values pile up quickly, and the sum at the bottom of the page runs into the millions without anybody having exaggerated anything.

That figure is the least useful thing on the slide.

It is not that the entries are invented. Each one is a real conversation with a real party about a real requirement somebody described. The problem is that the qualification and the timelines behind each line vary so enormously that adding them together produces a number with no meaning attached. A project that is specified, funded and out to tender sits on the same row as one where a consultant mentioned a requirement and asked what it might cost.

Western management reads the total and reasonably concludes the region is performing. The regional team reads the same total and knows the difference between the rows. What separates them is not optimism. It is qualification.

The Questions That Qualify

There is a short list that sorts the rows, and it does not require anybody's cooperation to run.

Who are you quoting to — an integrator or the end user? Is this new, or is it a replacement of something already installed? If it is new, is the building even ready? If the request came through an integrator, how many other integrators have approached you about the same requirement — because several of them chasing the same project means it is genuinely out for bid, and a single one means you may be looking at that integrator's speculation rather than at a project. Is there an official request for proposal issued, and are you bidding against it? And are you the vendor the requirement was written around, or are you being invited as an equivalent to somebody else who is — because the specification is written long before the tender opens, and being invited to match one is a materially weaker position than having shaped it.

Each of those is answerable, and each of them moves an entry up or down the page rather than leaving it in the undifferentiated middle.

Then the one that matters most, and the one almost nobody runs.

Have other items been quoted on this project, apart from yours?

A real project needs more than your product. It needs infrastructure, cabling, switching, integration, whatever the category demands around it. If nobody else has been asked to quote anything, there is no project — there is somebody assembling a budget estimate, or testing the market, or doing something else entirely. And a frank conversation with the other vendors who would be on the same bill of materials qualifies a project faster than any amount of contact with the buyer.

Triangulation Is the Whole Method

That cross-check is not a trick for one situation. It is the general method, and it applies again in a different form when a partner is being difficult.

The signals read much the same in the Emirates and in Saudi Arabia. The real difference is not the country — it is whether the partner in front of you knows you. A partner with a history with you will be direct. A partner who does not know you will frequently make you work for information that costs them nothing to give, and you can spend a quarter going in circles establishing facts that were never in doubt.

The way out is to stop asking them and look at the opportunity from above.

What else must this client be buying? A project of this kind needs particular infrastructure, particular systems, particular categories of supplier — and those vendors are further along than you are. Who among the bidders already holds a major service contract with this client, or has a relationship that predates the project? Those parties usually know who the players in the final round are going to be, and in my experience they are considerably more willing to tell you than the party who is managing you.

None of this is about going around anybody. It is about recognising that in a market where a single source will tell you only what suits them, the requirement is a second source.

The Demo Is the Qualification

Everything above narrows the field. One thing settles it.

A project is real when a demonstration has happened and you have met the end user. Not the integrator, not the consultant — the organisation that will own the thing and pay for it.

That single event answers four questions at once, and it answers them first-hand rather than through a chain of people with their own reasons for shaping the story. It tells you whether a budget exists. It tells you what the timeline actually is. It tells you whether the need is genuine or aspirational. And it tells you who has to approve it, which is usually different from who you have been talking to.

Second-hand is acceptable when it comes from the right source. A key integrator or consultant who has been in the room can carry those answers credibly. What is not acceptable is a chain of assurances where nobody in it has met the buyer.

This is also why a demonstration capability in the region is not a marketing expense. It is the instrument that converts a conversation into a qualified opportunity, and a vendor without one is dependent on other people's accounts of whether their own deals are real. It is among the first things worth building in a new market, and the reason is this rather than anything to do with presenting the product well.

What a Partner Is Telling You

Choosing a distributor is a separate problem and covered elsewhere in this series. This is about reading the one you already have, or a system integrator carrying an opportunity.

A partner doing real work is recognisable within one meeting. They ask good questions. They have read the specification and can discuss it. They know the technical ground well enough to disagree with you about it, which is a better sign than agreement.

But the decisive test is simpler than any of that.

Does the partner take you to the client?

Most will not. The instinct across this region is to keep the vendor away from the end user, because the relationship is the partner's asset and every introduction dilutes it. That instinct is understandable and it is also, from your side, the single most informative behaviour available to you. A partner who brings you into the room with the consultant or the customer has decided that winning this project matters more to them than protecting the account from you. A partner who will not is either not serious about the opportunity or not serious about you, and it is worth finding out which before you build a quarter around them.

The corollary is worth stating because it cuts the other way. A partner who has delivered with you once will usually deliver again. The first successful project is expensive to obtain and it changes the relationship permanently, which is a reason to overinvest in the first one rather than spreading the same effort across three.

What Time Actually Means Here

There is no correct answer to how long any of this should take, and anyone offering you one is describing their own market rather than this one. The honest version is that duration depends on the speed of execution that is needed and, more to the point, possible.

Which produces a test that is more reliable than anything a buyer will tell you.

If somebody says the requirement is needed next quarter, and the building it goes into is not complete, that is a bluff. Not necessarily a dishonest one — urgency is often genuinely felt at the level of the person expressing it — but the physical facts of the site outrank the stated timeline every time. Construction reality is checkable and it does not negotiate.

Delays, meanwhile, are not rejections. This is where vendors most often misread the market in the pessimistic direction, having spent the previous two quarters misreading it in the optimistic one. A project going quiet in this region is unremarkable and frequently means nothing at all. Budgets get cut back. Construction slips. Sponsors move. None of that is a decision about you.

And a real no usually arrives as a no. A partner will generally tell you when you have not made the cut, which is more courtesy than the reputation of this region suggests. The discipline is to hear it, and to move your effort somewhere else quickly rather than spending another cycle on an account that has already resolved.

What this means for reporting is specific. Where an official procurement process has been issued, the project will come eventually. It should come out of the forecast, because it is not going to close in any period you can name — but it should not be discarded. It stays on the horizon and gets checked each quarter.

I had one return after three years. By the time it came back, the product was approaching end of life and I could no longer supply it for a project I had helped shape.

What I Got Wrong

The mistake I made was not mistaking activity for progress. It was in how I reported the largest opportunities upward, and it took me years to find a defensible position.

Major projects in this region slip on execution, routinely and by margins that are not reasonable by any standard a head office recognises. And the very largest ones cannot be replaced. If a mega-project moves a year to the right, nothing else in the territory is going to fill that hole in the year it was supposed to land.

Which puts a regional manager in a genuine bind rather than a moral one. Declare the project and you receive the support it needs — the engineering attention, the executive visits, the pricing latitude — and you also receive the question at every subsequent review, for as long as it takes. Do not declare it and you keep the reviews clean, and you go into the largest opportunity in your territory without the resources to win it.

For a long time I handled that badly in both directions. What I eventually arrived at was neither concealment nor optimism: understand the timeline properly, set the closure date as far out as the evidence honestly supports rather than where it would be convenient, and be explicit with head office that this is how the region operates. Large orders are always welcome. Large orders that arrive two years after they were forecast cost you the credibility to be believed about the next one.

That is not a technique. It is expectation management, and it is a substantial part of the job nobody writes into the offer letter — managing upward through a reporting cycle designed for a market that behaves differently from this one.

Connektions MEA sits alongside vendors already operating here, applying this judgement to a live pipeline month by month rather than once. That work is described under Execution Oversight.