01
The preview is built on your own company
Your texts, your logo, your photos - in English and in Arabic, on your own phone, three working days after you fill in the questionnaire. If you are buying speed and right-to-left Arabic, you should see speed and right-to-left Arabic before you pay for the rest of it, not read about them.
EUR 390, credited in full against the project. If you say no, you keep the written findings on your current site.
02
Live demos you can click through yourself
My own instances - no client data, nothing that needed anyone’s permission: a restaurant ordering flow with a real order cut-off and delivery-time logic, a QR table-ordering system with allergens and a multilingual menu, and a bilingual company site with real RTL. Where a payment step appears it runs in test mode with a visible notice, so you can complete a booking with a deposit yourself.
Shown live in a screen-shared call, including the admin side. Ask anything while it is open.
03
Test the enquiry path with your own email address
Send a test enquiry through this site. You get the automatic acknowledgement within seconds, and the entry is written to a log with source, page and timestamp - the same mechanism your own site would get. Thirty seconds, verifiable, no trust required in advance.
Most small company sites lose enquiries exactly here. This one does not, and you can check that yourself.
04
Check the Arabic in the page source
Switch this site to Arabic and open the source. Separate URLs per language, dir="rtl", hreflang for en, en-AE, ar, ar-AE and x-default, and separate content files for English and Arabic. That rendering layer is in production here today.
If you ever see a translation widget on a site sold to you as bilingual, walk away.
05
Every performance and security number is measured by someone else
Run them yourself on your own preview URL while we are on the call: pagespeed.web.dev, ssllabs.com/ssltest, securityheaders.com, and Search Console verification on your own domain. I do not publish self-measured scores, and I do not guarantee them forever - you upload your own images.
Measured at handover and written into the report, with the tool named.
06
A written findings report on your existing site
Not an argument - a list of checked findings with a screenshot of the browser console: a content-security policy silently blocking your tracking, a conversion event that never fires, a phone link with one digit missing, missing hreflang, mobile load time. These are the exact failure classes that show up in real systems, including in mine.
Finding them on your site proves craft without needing a single reference.
07
Production systems in Europe, described without names
No names, no links and no result figures, because I do not have written consent to publish them - and inventing them is both illegal and stupid. What runs today: a dental practice takes a card deposit at the moment of booking, with hourly automatic reconciliation between payment provider and booking database; a restaurant takes orders with a hard cut-off calculated from closing time minus preparation and driving time; two online shops process real card payments; several lead funnels record every enquiry with its source.
I describe the function. I never claim the result.
08
The operations, stated exactly
Over 100 production containers on my own server. A central gateway issuing and renewing SSL automatically for more than 80 domains. Automatic daily backups per application. A container health check every 30 seconds with automatic restart. An independent external watchdog with email alerting every 5 minutes. Once a year a backup is restored in front of you and the timestamp goes into your report.
A backup that has never been restored is a claim, not a backup.