Web Design Projects in QatarWeb Design Projects in Qatar✨ Case Study: Giving a Local Spa a Digital Glow-Up
Most local spas still run on phone calls and DMs. So I rebuilt one — end to end.
Meet Séraya Spa → 🔗 https://seraya-spa-retreat.base44.app/
Built with @Base44 for the #GiveItAGlowchallenge. No code. Fully live.
Before: No website, no online booking — everything handled manually by phone.
After:
🌿 Luxury design — light + dark themes, cinematic scroll animations, mobile-first
📅 Real-time booking with live price configurator
🤖 AI Concierge — answers FAQs, recommends treatments, books them 24/7
📧 Automated confirmations, reminders & rebooking nudges
💬 One-tap WhatsApp flows
🗂️ Owner dashboard — every booking, lead & message lands in one place, ready to manage
Every automation replaces something the owner did manually.
🎥 Full walkthrough below (6 min) — the complete guest journey, how bookings flow into the dashboard in real time, the automations firing, and the full experience on tablet & mobile. Worth watching to the end.
Small businesses don't need bigger budgets — they need the systems big brands take for granted.
Run a spa, salon, or studio that deserves better? DMs open. ✨
#GiveItAGlow @Base44 #webdesign #freelance @Contra HQ @Contra Title:
SEOForge — Multi-Tenant SEO SaaS Platform
Short description:
Built a scalable SaaS platform for agencies and businesses to centralize SEO auditing, keyword tracking, backlink and competitor analysis, Search Console data, reporting, and multi-project management.
Our contribution:
SaaS architecture, React/TypeScript frontend, Node.js backend, PostgreSQL data layer, third-party SEO/API integrations, authentication and roles, Redis caching, Docker/cloud deployment, and CI/CD.
Services/tags:
SaaS Development · Web Development · React · TypeScript · Node.js · PostgreSQL · AWS
This should probably become your flagship SaaS case study.
One caution: your graphic contains specific impact claims such as +200% user growth, +35% client traffic, -60% reporting time, 150 agencies and 4.8/5. Only publish those as factual outcomes if you can substantiate them. Otherwise I'd remove/replace those claims before treating the graphic as a formal case study. 
