GULF MEP

Overview

• What: a production B2B procurement platform for a GCC-based client, bilingual with Arabic first.
• Hardest problem: replacing public checkout and pricing with an RFQ-based inquiry workflow across a 1,000+ product catalogue.
• How it is validated: delivered and deployed for a real client; the site is live at gulfmep.com.

This was freelance work from June to August 2026. The catalogue spans multiple categories, subcategories and brands, with site search, a blog and an SEO-oriented page structure. Staff manage products, content and RFQs through an admin dashboard built with Laravel and Filament.

Architecture

 visitor (Arabic / English) --> catalogue, search, blog
          |
          v
   RFQ inquiry (no public checkout or pricing)
          |
          v
 Laravel + Filament admin --> products / content / RFQs  --> MySQL
 validation, rate limiting, upload protection, authorization checks, audit logging
 hosted on Hostinger

Highlights

• Built a B2B MEP procurement and RFQ platform for a GCC-based client, bilingual (Arabic-first and English), covering 1,000+ products across multiple categories, subcategories and brands.
• Implemented an RFQ-based inquiry workflow in place of public checkout and pricing, along with site search, a blog and an SEO-oriented page structure.
• Designed and built an admin dashboard for product, content and RFQ management using Laravel and Filament.
• Implemented input validation, rate limiting, upload protection, authorization checks and audit logging.
• Deployed the platform on Hostinger.

What I learned

An RFQ workflow changes what the product is: there is no cart to lean on, so the catalogue, search and inquiry flow have to carry the whole buyer journey. On a public site for a client, security work such as validation, rate limiting, upload protection and audit logging belongs in the first build, not a later pass.