Case study · Corporate
Ramico
A trading and procurement house, since 1992: Damascus, Dubai, Kuala Lumpur. The site had to feel as established as the company.
The result
The problem
In procurement, trust is the product. A manufacturer deciding whether to answer an email looks at the website first, and a generic template reads as a generic company. Ramico needed weight: three decades of history, three markets, and the quiet confidence of an institution.
It also needed to be editable by the team without touching code, and to serve readers whose first language is not English.
What we built

The part the client runs
The team publishes news in five languages, manages media and reads visitor analytics from a custom control panel we wrote for them. No licence fees, no external trackers, no agency on the phone for a typo fix.
Real screens from the live control panel. Analytics run on the company's own server, IP addresses are never stored.
Hardened by default
Corporate sites carry corporate risk, so this one ships locked: a real content security policy, strict transport security, clickjacking protection and backups in three layers. None of it is marketing, all of it is verifiable from any terminal.
$ curl -I https://ramico.org strict-transport-security: max-age=31536000 content-security-policy: default-src 'self'; object-src 'none'; … x-frame-options: SAMEORIGIN x-content-type-options: nosniff ✓ live response from the production server
Why it matters
A corporate site is a handshake that happens before the meeting. This one loads fast on weak connections, answers the three questions every partner asks, who are you, what do you move, since when, and never once feels assembled from parts.