Rotating Power Technologies.
A new gas and steam turbine engineering consultancy entering the GCC market against global incumbents on speed, independence, and multi-OEM expertise.
The problem.
An independent turbine engineering consultancy was launching in the GCC. Their positioning against global firms like DNV and Laborelec was sharp. Twenty-four hour on-site response versus a one-week mobilization from Europe. No OEM relationships and no parts to sell, so unbiased analysis. Multi-OEM experience across GE, Siemens, Mitsubishi, and Alstom. Target audience: plant managers, maintenance engineers, and insurance companies across the region.
They needed a marketing presence that communicated all of this with credibility, in both English and Arabic, with content tuned per market (GCC, Saudi Arabia, UAE). The site had to land instantly in either language, on first visit, with no friction. The founder's brief on purpose was direct.
"The main purpose is legitimacy. Communicating competence. Like a business card. They go to the website to check there's something behind it, that it's not just some guy."
Discovery.
Ninety minutes at a cafe, recorded. The founder walked through how he acquires clients, how the services are delivered, and what is actually unique about the offering. I asked him to draw it on paper: every step of the engagement process, in his own hand. The diagram became the information architecture for the site.
From the transcript, copy directions. Founder picked one. Then copy-first development: every section was written before any code went down. The visitor's journey was the spec, not a feature list.
Approach.
React islands, minimal JS
Astro renders everything to HTML at build time. Only five React components hydrate, each with the right strategy: the hero loads immediately, the value-prop cards and FAQ load when scrolled into view, modals and mobile nav load when the browser is idle. The result ships dramatically less JavaScript than a typical SPA marketing site, with no compromise on interactivity where it matters.
Bilingual EN/AR with regional variants
Two locales, three regions. Forty-two translation keys with a sparse-override pattern: SA and AE inherit from the GCC base and only override what changes. RTL is implemented as a property of the page, not a runtime mode-switch, with separate page files per locale for cleaner HTML semantics. No external i18n library, zero runtime cost.
Privacy-first geo personalization
No IP geolocation. No cookies. No tracking. Region detection happens entirely client-side via the browser's timezone. Asia/Riyadh routes to Saudi-specific content, Asia/Dubai to UAE content, otherwise the GCC default. Zero-latency, zero invasion of privacy, zero third-party dependencies.
Custom modal system with browser history
Service detail pages open as modals, but with full browser navigation. URL changes via pushState, popstate listeners for back and forward, scroll lock for iOS Safari, deep linking that opens the correct modal on shared URLs. Most SPAs break browser fundamentals when they implement modals. This one respects them.
Performance discipline
Lighthouse-optimized end to end. fetchpriority on the hero image for LCP, low-quality image placeholders, accessibility passes, hydration error fixes. The site is fast on a Saudi mobile connection, not just on a Mac on fiber.
Result.
Three days of build. Roughly five weeks from kickoff to live, with the balance going into discovery, copy iteration, and client review. Founder's reaction was a single line: "Blown away." The site has been circulated to peers and generated a referral pipeline.
The bilingual architecture is durable. Adding new market regions or new languages is a configuration exercise, not a codebase fork.
See it live.
The production site is embedded below. Open in a new tab →