Current client · Healthcare, Riyadh
Working together now
Avant Clinics: one platform from first visit to CEO decisions
Avant Clinics is a dermatology, aesthetics and laser clinic in Ar Rabi, Riyadh. I rebuilt its digital operation end to end and I run it with the team: a bilingual website hosted in Saudi Arabia, online payments, three ways to book including instant booking into the clinic system, operations tools for the front desk, and an executive cockpit for the CEO.
- Dammam region
- Website, CMS, database and workers configured in Google Cloud Dammam
- Online payments
- Real payments documented since 29 August 2026 through Moyasar
- 3 booking paths
- Instant booking, a request form and AI chat, with reception follow-up
- 9 data sources
- Cockpit integration scope, with dated readings and unavailable states
- 201 pages
- URLs in the bilingual delivery sitemap, including doctors and services
These are documented delivery milestones and scope counts. Source dates belong to each reading in the cockpit; this inventory does not measure conversion, revenue or time saved.
What we built
Six parts that work as one system
01
Website and SEO migration
A ground-up bilingual rebuild that replaced WordPress with a documented URL and SEO migration.
- Arabic first (RTL) with English as a full second language
- 10 doctor profiles, 9 devices, 31 service pages and campaign landing pages
- Old URLs mapped with 301 redirects, Arabic-slug redirects and a 410 list for dead pages
- Structured data without invented ratings, and a clean 201-URL sitemap
Next.js 15React 19Directus CMS
02
Hosting and architecture in Saudi Arabia
The website, APIs, CMS, database and workers are configured in Google Cloud Dammam. Connected providers have their own processing boundaries.
- Separate services for the website, the CMS and a background worker for notifications
- PostgreSQL 16 with typed data access and validation at every boundary
- Media on a CDN, private invoice files kept in a separate private bucket
- Automated tests and review gates on every change before it reaches production
Google Cloud RunCloud SQLme-central2
03
Payments and gift vouchers
Package purchases have their own payment flow. An order is confirmed only after a verified provider webhook.
- Mada and Apple Pay through Moyasar, live on real money since August 2026
- Webhook verification, event deduplication, and amount and currency checks guard order confirmation
- Each paid order issues a voucher; gifts send a claim link the receiver binds to their own name
- Reception finds and reissues vouchers; an invoice request goes to a person in the finance team
MoyasarMadaApple Pay
04
Booking and instant booking
Three ways to book, one queue for reception. Instant booking writes the appointment straight into the clinic’s own system.
- Instant booking on doctor pages: live slots for the next 14 days, Riyadh time
- The slot is re-checked at the moment of booking, the patient is matched or registered, and one appointment is created in Nixpend
- A booking form and an AI chat assistant capture requests with explicit consent
- If the clinic system is slow, the visitor gets a clear “we will call you” instead of a double booking
NixpendChatbaseDirectus
05
Operations tools for the team
The front desk works from tools built around its day, not around a spreadsheet.
- A coordinator console for WhatsApp follow-ups with ready templates per doctor, behind Google sign-in
- Every coordinator action is logged, with a guide for managers to review it
- A reception board for every booking request, with access limited by role
- Staff pages for vouchers and invoices, and alerts when a paid order gets stuck
WhatsApp Cloud APIFirebaseCloud Logging
06
The CEO cockpit
One private, Arabic-first cockpit that answers the CEO’s questions about traffic, bookings, sales and ad spend in one place.
- Traffic, bookings, capacity, sales, collections and ad spend, with a date and availability state for each source
- Ready-made CEO reports, a booking funnel, and tasks, targets and decisions with full history
- A source-health panel that shows how fresh each number is instead of faking zeros
- Read-only by design: it can never launch a campaign, take a payment or message a patient
BigQueryGA4Google AdsMeta Ads
The workflow, step by step
From the visitor to the CEO
Follow a request from the visitor to the clinic system and staff, then to the evidence leadership reviews.
01
Find a service or doctor
The visitor starts on the Arabic or English website and explores doctor, device and service pages.
Next: choose the appropriate booking route.
See the public homepage capture02
Choose a booking path
A public form or chat captures a request with consent. On a doctor page, instant booking offers available slots.
Next: a saved request for staff, or a slot to verify.
See the empty public booking form03
Confirm the appointment correctly
Instant booking rechecks the slot, matches or registers the patient and creates the appointment in Nixpend. An uncertain response stays a follow-up request.
Next: a confirmed appointment or a clear request for reception.
Read the booking safeguards04
Hand over to reception
The reception board and coordinator tools let staff review requests and follow up with the appropriate template. Access is limited by role and actions are logged.
Next: staff follow-up and an operational record.
Read how the private staff tools work05
Review dated operating evidence
The private CEO cockpit brings source readings into one summary. Each source has a timestamp and health state; unavailable data stays unavailable, rather than becoming a zero or a live claim.
Next: review the evidence and record a human decision.
Read the cockpit and freshness controls
A separate path for package purchases
Package checkout leads to a verified Moyasar webhook, then a voucher and an invoice request. A person in finance issues the invoice and closes the request. This purchase flow is separate from appointment booking.
Read the payment safeguardsPrivate interface captures show the working layout with record values, operational metrics and totals masked before capture. The images contain no readable patient or customer records.
From the public website
Public pages, historical captures
Working product screens
Inside the operations tools
The CEO cockpit brings operational signals together, while the team manages orders and booking requests in the CMS. Private values are masked before capture. Open any image for a closer look.
Trust and compliance
Publishing controls and the hosting boundary
The delivery includes database and code gates for ad approvals, device clearance and licensed doctor titles. Application hosting in Dammam is one documented boundary; connected providers and their data journeys need their own review.
- Service pages need a Ministry of Health ad approval before they can go live
- Devices are gated on their SFDA clearance
- Doctor titles come from a closed list that matches their licence, in correct Arabic grammar
- Booking forms request explicit consent, and analytics events exclude personal data
For your clinic or company
Tell me what slows you down, and I will tell you what to build first.
The same approach: start with what costs you most, build it, run it, then move to the next part.