Gulf Cooperation Council markets.
Felixfusion is in an initial-contact phase across Gulf Cooperation Council markets. GCC capacity-tender design, bilateral offtake structures, and sovereign-linked procurement frames differ materially from the AU and US surfaces Folio Grid was first calibrated against. This page is the positioning view for GCC counterparties evaluating a pilot.
01. Posture
We are actively initiating conversations with GCC sovereign investors, developer consortia, and utility off-takers. No GCC pilot has closed as of this posting. The engine is designed to run the GCC ruleset; the first pilot is the commitment we are working toward rather than one we are claiming behind us.
The Felixfusion team is founder-led and Sydney-engineered. GCC engagement runs through direct introduction; there is no local office. We are prepared to mobilise onto a GCC pilot with a named senior engineer embedded for the engagement window.
02. GCC-specific surfaces
Capacity tenders. Procurement authorities in Saudi Arabia (PIF, SPPC), the UAE (EWEC, DEWA), Oman (OPWP) and peers run IPP and IWPP tenders with capacity payments as the primary revenue instrument. Folio Grid's Reservoir model supports capacity-plus-energy stacks and contract overlays that reflect the GCC contract envelope rather than a merchant-first frame.
Bilateral offtake and sovereign counterparty risk. GCC revenue stacks are more contracted than AU or ERCOT equivalents. The counterparty view in every Folio Grid IC memo carries explicit sovereign-linked risk commentary where applicable.
Heat and resource extremes. Solar irradiance, ambient temperature de-rating, and dust soiling drive the yield model differently than NEM or ERCOT. The weather histories Lattice uses are calibrated against local meteorological records for each candidate site.
Local content and in-country value (ICV). GCC procurement rules carry ICV certification requirements that a compliance-matrix engine needs to track. Folio Bid's matrix engine is the same reasoning surface and ports to ICV regimes if a GCC procurement engagement calls for it.
03. How to engage from the GCC
For sovereign investors, developer consortia, and off-takers: the /contact form is the single inbound route. Note your organisation, the asset or pursuit shape, and the jurisdiction. We route into the GCC lane on arrival.
For technical diligence counterparts: the /architecture paper covers the engine design; the /security section covers the pilot isolation posture. A 60-minute working session with the founder covers what is not in the written materials.
For partners and introducers: warm referrals are the primary path. Note the introducer's name in the message and we respond inside one business day.
Open a conversation.
We are initiating GCC engagement now. The form is the single inbound route.