Procurement Is Not Where the Decision Is Made

The Tender Was Not the Decision

Procurement, in almost every Gulf project I have worked on, goes back to the end user.

Not once, as a formality. Continuously. A submission arrives, something in it is unclear, and the buyer asks the person who wrote the requirement what they meant and whether this answers it. That is not a loophole. It is how a process staffed by generalists evaluates technical proposals it is not equipped to judge on its own.

Western vendors arrive with a model in which that would be unusual. Procurement is a function. It executes a decision taken elsewhere. It negotiates the price, checks the paper, issues the order. Win the commercial argument and procurement is administration.

Here it runs the other way, and it produces a specific failure — not the one people expect. The failure is not that procurement blocks you. It is that you arrive at procurement as a stranger, with nobody inside who can answer for the requirement when the question comes back.

We always worked the end user first, before going anywhere near procurement. Once somebody on the inside was batting for the requirement — not for us, for the requirement we had helped shape — the process smoothed out. Not because anything improper happened, but because every clarification round came back to a person who already understood what the specification was for and why it read the way it did.

A vendor with a perfect submission and nobody inside is at the mercy of every ambiguity in their own paperwork. A vendor with a specification they helped write survives ambiguity, because the ambiguity gets resolved by someone who knows the answer.

What Procurement Is Actually Buying

The question in the room is not whether yours is the best product. It is whether this is a safe thing to approve.

Those sound similar and they are not. Best is a claim about the product. Safe is a claim about everything around it — whether somebody in the country answers the phone, whether the documentation is complete and current, whether the counterparty is already on the system, whether anyone in the building has bought this before and can be asked how it went.

This is where a genuinely strong Western company misreads its own position most badly. You arrive with the logos: the Fortune 100 references, the market share, the analyst placement. All of it is real and almost none of it transfers. A reference the buyer cannot telephone is not a reference. An installation they cannot visit is a claim.

Prequalification Happens During Specification, Not After

Most vendors treat prequalification as a later gate — something that happens once a tender is announced. It is usually running much earlier than that, inside the specification process itself.

What gets asked for is consistent. Local references, with contact names, email addresses and telephone numbers, because the buyer intends to ring them. And a standard company questionnaire covering the global entity: financials, structure, track record, insurance, the usual.

The global questionnaire you can answer in an afternoon. The local references you cannot, and that is the whole point. A vendor with no installed base in the country cannot produce a contactable local reference, and no amount of head-office material substitutes for one.

This is the mechanism behind the impasse described in the first article in this series: you cannot get the first reference without the first project, and the first project asks for references. It is also why the sequencing question is not academic. Prequalification asks for something that takes a year to acquire, at a moment when you have weeks.

The Documents, and What Each One Unlocks

The document set depends heavily on whether you are selling directly or through a partner, and most vendors assume the direct-sale list applies to them when it does not.

Selling through a partner, the documents the buyer wants are largely about the relationship between you and that partner. A manufacturer authorisation letter, typically in a format the buyer prescribes rather than one of your own. Warranty documentation covering what is guaranteed, by whom, and for how long. And in some cases the partnership agreement itself, in copy.

The prescribed format sounds like a recurring obstacle and is not. Once you have built a template that satisfies it, the same letter serves across projects and across partners with the names changed. It is a one-time piece of work that vendors routinely treat as a per-tender scramble, which is the wrong way round: draft it properly once, before you need it, and it stops being a variable.

Compliance certificates are the item most often over-engineered. In most categories these are issued by your own quality function at the factory. They are a statement you make about your own product, not something a third party grants you, and treating them as a procurement obstacle wastes attention that belongs downstream.

Where It Actually Blocks You Is Import, Not Award

This is the part that costs projects, and it is almost never explained.

Certification requirements are category-dependent and are set out in the tender. For most categories, existing United States and European compliance is sufficient to satisfy the compliance check at bid stage. A vendor reads that, concludes certification is handled, and moves on.

The problem arrives at delivery.

Where the product contains anything that transmits — a radio, a wireless module, a communications device — the region requires its own type approval, and existing US or EU certification does not substitute. In the United Arab Emirates that is the Telecommunications and Digital Government Regulatory Authority, TDRA, which took over from the former TRA when it merged with the Digital Dubai Authority in 2021. In Saudi Arabia it is the Communications, Space and Technology Commission, CST, which was the Communications and Information Technology Commission until December 2022. CST approval is granted on the basis of testing to the European Radio Equipment Directive, so the tests need not be run in local laboratories, and the approval runs two years.

If your category requires testing, that takes time. And the consequence of not having it is not that you lose the bid. You win the bid, and then you cannot bring the goods into the country.

Saudi Arabia Is Not the Same Market

Three differences matter enough to change a plan, and all three run the same direction.

Importing into the United Arab Emirates is the simplest route in the region. Importing into Saudi Arabia is the most demanding, and the mechanism is SABER. Every product model must be registered on the SABER platform and hold a Product Certificate of Conformity, valid for a year and requiring test reports. Then every individual shipment requires its own Shipment Certificate of Conformity, issued against that registration, presented at customs before the goods clear. There is a cost attached to each line of your shipping document, not to the shipment as a whole — which means a consignment with forty line items carries forty of them.

For a vendor shipping a single configured system that is an administrative cost. For a vendor shipping a bill of materials with many components, it is a commercial one that belongs in the price before you quote it, not after.

Second, local presence. Procurement will ask for your local office details as a matter of routine. On some Saudi projects it goes further and requires an in-country office and a trade licence — not a distributor's, yours. That is a different order of commitment from appointing a partner, and discovering it after you have been specified is the wrong sequence.

Third, and least visible until the invoice: withholding tax. Saudi Arabia applies withholding tax on payments to non-residents, and the rate turns on classification. Payments for the use of software or intellectual property are treated as royalties and carry fifteen per cent. Technical and consulting services carry five. The classification follows the economic substance of what is being paid for, not the description on the invoice, so calling a licence a service does not make it one. The United Arab Emirates, by contrast, currently applies a zero per cent rate under the corporate tax law, with no withholding on royalties, interest, dividends or service fees.

Fifteen per cent off the top of a software line is not a tax detail. It is a margin decision, and it belongs in the model before you price the deal.

The Cycle Is Not One Length

The planning assumption most boards carry is a single procurement timeline, and there is no such thing.

Greenfield mega-projects run three to four years from specification to tender, sometimes longer. The specification drives the budget, the budget drives the approval cycle, and none of that is compressible from outside.

Refurbishment and replacement projects — which is most projects — run six to twelve months on the same path. That is a materially different business to plan around, and it is the bulk of the addressable work in any established market.

And in genuinely urgent cases everything is fast-tracked. The same institution that took a year on a planned project can move in weeks when it has to.

The practical consequence is that "Gulf procurement is slow" is not a useful planning input. What is useful is knowing which of the three you are in, which you find out by asking the end user what is driving the timing — another question you cannot ask if you have no one inside.

What I Got Wrong

Being specified is not the end of the problem. It creates a different one, and it took me a while to understand that it was mine to solve.

In our category, once we were written into a specification we effectively had a lock. That sounds like a good position, and commercially it was. But a public buyer cannot award against a single compliant bid. The process requires a competition, and a sole-source position produces the opposite of one.

So the work became orchestration. We had to make sure every qualified bidding party actually received a bid from us, and that the numbers came back inside a sensible band — close enough to constitute a genuine field, far enough apart to be credible as independent submissions. That is a tightrope, and it is not a comfortable one to walk.

The clearest case was a large service contract where the requirement rested on certification held against an earlier generation of the product. Only one bidder held that certification, and nobody else could easily acquire it. On paper that is the strongest possible position: no qualified competitor exists.

In practice it meant we spent our effort not on winning the bid but on obtaining permission for there to be only one. Getting a very large order approved as a single source is precisely the circumstance in which a buyer is least willing to do it — the value is exactly what makes the justification hard. What should have been a formality became the hardest part of the deal.

The other failure was blunter. On a different tender we did not have three proper bids in place when it closed. Not three credible ones, not three that stood up. The process could not complete as run and the whole thing went to re-tender. Everybody lost months — the end user who wanted the system, the bidders who had done real work, and us, holding a specification now sitting inside a re-tender we had caused by not managing the field we had created.

One of those two problems is also on the record elsewhere in this series, where a bidder undercut the field by a wide margin assuming the vendor could be squeezed afterwards to make the economics work.

The lesson I would give anyone approaching a sole-source position: the moment you win the specification, you have inherited responsibility for the competition around it. Being the only party who can comply is not a finish line. It is a procurement problem with your name on it, and if you do not staff that work the process will fail around you.

This is commercial guidance and not legal or tax advice, current as at September 2026. Certification regimes, tax treatment and local-content rules in this region change, and they change without much notice — verify anything here against your own category and your own advisers before you commit to a plan.

The pattern underneath all of it is the same. Everything that decides a Gulf project happens before the tender opens, and almost everything that stops a Gulf project happens after the award. The tender itself, which is where most vendors put their effort, is the part where the least is actually decided.

Connektions MEA builds the entry plan that sequences this work — the references, the approvals, the entity and the partner — in the order the region actually requires. That work is described under Entry Blueprint.