Anchored in Saudi context — Vision 2030 and healthcare innovation in focus.

Pharma cycle meetings, banking national sales conferences, automotive dealer summits — programmes that recur quarterly or twice yearly and require a different register from a one-off gala. The audience is internal, the stakes are learning and alignment, and the budget sits inside an operating line, not a marketing campaign.

We programme the full arc: plenaries, breakout clinics, roundtable formats, evening hospitality. The BoQ reflects that repeatability — reusable staging, branded kit that survives three cycles, vendor relationships the client keeps between engagements.

LEAP, GITEX Global, FII, Biban — each calls for a different stand register. LEAP rewards experiential spectacle; FII rewards institutional weight; GITEX rewards product demos with throughput; Biban rewards accessibility to an SME audience. The concept has to read correctly for the show, not just for the client.

We open every booth engagement with live show research — attendance, audience profile, typical stand sizes, adjacent exhibitors — so the concept is designed against the real room, not a generic summit.

Most events in the Kingdom require some combination of GEA entertainment licensing, SCEGA approval for conventions, municipality permissions, venue permissions, and civil defence sign-off above certain capacities. We carry the checklist for every project and track who is responsible for each item.

Clients are kept in the loop on any item that requires their signature or their corporate documents — we do not silently handle permissions that legally need the client's name on the application.

Hijri calendar considerations are read into the planning stage, not bolted on at the end. Ramadan reshapes programming hours; Eid al-Fitr and Eid al-Adha close certain vendor chains for a week at a time; Hajj adds load to logistics routes out of Jeddah; National Day and Founding Day drag every good venue into the same week.

We flag blackout days automatically on the project timeline and write the policy per project: some clients are fine with late-Ramadan programming, some are not. The schedule follows the client's policy, not a default.