How I read a Saudi infrastructure tender like an investor

I bid on aviation infrastructure work in Saudi Arabia for a living, and I got into the habit of reading a tender pack the way I used to read a target's data room. Same questions. Does the thing I'm buying match what the paper says? What does it cost me? Who am I tied to? What breaks?

I won't name clients here. The patterns are the same across most packs, and they're what matters.

Pass one: scope

Start with what's actually being asked for, not the title. A tender called "helipad package" can mean lighting only, or civil works and lighting, or design plus supply plus installation plus testing. The bill of quantities tells the truth. The cover letter doesn't.

On one scanned Arabic tender, a single reading pass of the document agreed on only 30% of part numbers. I wrote about that in my note on running companies with agents. The investor lesson is simple: if you can't read the scope confidently, you can't price it, and pricing a misread scope is how you lose money on a contract you won.

Pass two: price

Government buyers publish the rules for guarantees, and they're worth reading as cost lines. The SAMA rulebook describes an initial guarantee of 1% to 2%, set by the tender conditions, and a final guarantee of 5% of contract value, due within 10 days of award notification. Those bonds cost money and tie up credit lines. I put them into the bid as costs before I look at margin.

Then there's local content. Saudi local content rules give national products a 10% price preference, and for some larger non-supply contracts the financial evaluation weights local content at 40% and price at 60%. I don't treat that as an obstacle. I treat it as a signal about who the buyer wants to win, and I price the local-content plan as carefully as the equipment.

Pass three: counterparties

Who sits in the chain? On many packs the buyer isn't the end owner. A contractor sub-tenders a package to a specialist, and the specialist has to deal with a designer, a quantity surveyor and an employer all at once. I map every name and every approval step. The question I ask is where payment actually comes from and how many hands it passes through.

I also read the supplier side. If a key component has one source, that's a concentration risk, and I'd flag it in an investment memo without hesitation. In bids I do the same: a single-source line gets a second quote or a contingency.

Pass four: risk

The risks I find most often are boring ones.

Time. Long lead items against a short delivery window. I back-solve the schedule from the end date before I trust any promise.

Standards. Which standard applies (international, national, or the owner's own) and whether the quote I hold meets it. A price that doesn't meet the required standard isn't a price.

Data decay. Quotes expire. In my own pricebook, 77 of 236 rows were past their validity date at last count. I flag them. Quoting stale rates as current is the cheapest mistake to avoid.

Who signs. Every price and every outbound document gets a human sign-off. I'm the human.

What I'd tell an investor

If you're looking at a company that wins infrastructure contracts in the Kingdom, ask to see how it reads a tender. The bid file tells you more than the pitch deck: whether scope is checked, whether guarantees are costed, whether the counterparty chain is mapped and whether stale prices are flagged. A team that does this well is cheap to trust. One that doesn't might still win, but you'll find out about the problems later, and that costs more.

Check any percentages above against the specific tender before relying on them. Conditions vary by pack, and the document in front of you is the one that counts.