Who Actually Buys in the Gulf: The Specification Chain and Who Holds the Budget
In the Gulf, the developer rarely holds the budget. A real buyer map from an attractions project: who specifies, who pays, who vetoes.
A few years ago I built a buyer map for a European attractions manufacturer that wanted to sell into the Gulf market: rides, water park equipment, play structures, the kind of large capital equipment that goes into a theme park or an entertainment destination. The company had a good product and no idea who they were actually selling to. They kept sending their catalogue to developers in Dubai and Abu Dhabi and wondering why nothing happened.
The developer is almost never the buyer. That single correction changed how the whole sales effort was structured.
Here is what the chain actually looks like once you follow the money and the decision rights separately, because in the Gulf they rarely sit with the same party.
Who sits where in the chain
At the top sits the landowner or master developer, the entity that controls the site, whether that is a private developer in Dubai, a government-backed authority in Abu Dhabi, or one of the giga-project vehicles in Saudi Arabia. This party sets the budget envelope for the whole destination and approves the concept, but by the time your product category is being discussed, the developer has usually already handed design authority to someone else.
That someone else is the design firm, sometimes called the master planner or the concept designer, often an international themed-entertainment architecture practice with a regional office in Dubai. This is the party that writes your product, or your competitor's, into the technical specification. If you are not in the room when the design firm is drafting that document, eighteen to twenty four months before the site opens, you have already lost the deal, because by the time it reaches tender your competitor's model number is sitting inside the spec sheet.
Below the design firm sits the operator, the company that will actually run the attraction once it opens. On newer Gulf projects the operator is increasingly a separate entity from the developer, brought in specifically because running a theme park and developing real estate are different skill sets. The operator's ride and attraction manager cares about different things than the developer: uptime, maintenance contracts, spare parts lead time, local service presence. A product that wins on the design firm's spec sheet can still lose here if the operator's technical team flags that there is no service partner within the region.
Contractors and the state's hidden veto
Then comes the main contractor, the party that actually issues your purchase order in most cases. The main contractor does not care about your brand story. They care about delivery schedule, payment terms, and whether your equipment fits into a construction sequence that has penalty clauses attached to every late milestone. Below the main contractor sit the specialist subcontractors and fit-out companies, and for some product categories this is the level your company actually transacts with, several tiers removed from the developer whose name is on the press release.
For state-led projects, there is a sixth party worth naming separately: a government tourism or investment authority's project office, which shows up on giga-projects and legacy developments where a public entity retains approval rights even after a private operator and contractor are appointed. I saw this directly on a Gulf attractions buyer-mapping project where the actual sign-off for one product category sat with a project office inside a government authority, not with the private developer whose branding was on every rendering.
Three parties, three different conversations
Who holds the budget, in practice, is usually the operator or the developer's asset management arm, because they own the asset's performance after opening. Who releases the payment is the main contractor or the tier below it. Who decides which product gets specified is the design firm, working from what the operator has told them they need and what the developer has told them they can afford. Three different parties, three different conversations, and a foreign company selling into the region needs a different message and a different point of contact for each one.
The practical consequence is about timing more than anything else. Companies that arrive with a finished catalogue when the tender is published are competing on price against a spec that was already written around someone else's equipment. Companies that get into the design firm's office while the concept is still being drawn, often through the design firm's Dubai studio rather than its headquarters elsewhere, have a real chance of shaping the specification itself.
Where the regional trade shows fit in
This is also where regional trade events matter, and it is worth being specific rather than vague about which ones. DEAL, the Dubai Entertainment, Amusement and Leisure show, held at the Dubai World Trade Centre, is where the region's developers, design firms and operators for this sector actually walk the floor together in one place. WETEX, on the water and energy technology side, plays a similar role for a different set of buyers. Showing up at the right one, with the right person from the right tier of the chain already expecting you, is worth more than a stand at a general trade fair with no prior contact.
None of this is unique to attractions equipment. The same layered structure, developer, design authority, operator, contractor, and in state-led projects a government project office, shows up across construction-adjacent sectors in the Gulf: hospitality fit-out, banking technology procurement through a systems integrator, retail fit-out through a main contractor. The names of the parties change by sector. The shape of the chain does not. Anyone selling capital equipment or specialist services into this region should build this map before the first sales call, not after the third one goes nowhere.
Updated: September 2026
Working on the same problem? Always happy to compare notes.
Let's explore synergies