A website is a business decision before it is a design one
Most websites that disappoint were not badly designed. They were badly decided. Nobody agreed what the site was for, who it was talking to, or what should happen after someone clicks. A designer was handed a brief that skipped all three, and the result looks fine and does nothing.
So the first part of any build here is not visual. It is deciding what this thing is supposed to change.
What I build
Corporate and business sites
For companies whose website is the first thing a serious prospect checks. Fast, credible, easy to keep current, and written so a buyer can tell within seconds whether you do what they need.
Web applications
Portals, dashboards, booking systems, internal tools — the software a business runs on rather than the brochure in front of it.
Ecommerce and enquiry flows
Where the money actually moves. Payment methods people here use, delivery expectations that match reality, and a checkout that does not lose people at the last step.
Rebuilds
The most common request. A site nobody on the team can edit any more, built by someone who has moved on, running a page builder that makes every change a negotiation.
Bilingual, with Arabic treated as a first language
Arabic is not a translation layer bolted onto an English site. It changes the layout direction, the typography, the way numbers and dates read, and the length of everything. A site built English-first and translated later shows it — broken alignment, cramped Arabic text, navigation that reads backwards. Built properly, both languages look deliberate. This is the part most UAE web work gets wrong, and it is visible to every Arabic-speaking visitor.
What I hold the build to
- Loads fast on a phone on a real connection, not on a developer’s laptop
- Passes Core Web Vitals on the pages that matter, measured on real devices
- Usable with a keyboard and a screen reader
- Editable by your team without calling anyone
- Structured so search engines and AI assistants can both read what you do
Hosting and where the data sits
For some organisations — government-adjacent work, regulated sectors, anyone handling personal data at volume — where the site and its database physically live is a requirement rather than a preference. That gets decided before the build, not after.
How a project runs
A short discovery to settle purpose, audience and the one action that matters. Then structure and content, then design, then build. Content is not a placeholder problem to solve at the end; a design drawn around real words survives contact with reality, and one drawn around dummy text never does.
Related reading
Arabic-second always shows covers what separates a bilingual site that was designed from one that was translated, and ranking and being recommended are not the same job explains what a site now has to do to be found at all.