Skip to content

Portfolio · Pilgrimage operators · Web

A pilgrimage in four steps,run from one console.

This is a Hajj and Umrah operator’s public site and the console behind it. A pilgrim moves along one continuous path — the journey explained in four steps, then a departure month in the Islamic calendar, then a batch inside it, then a package tier — and arrives at an enquiry rather than a checkout. Everything on that path is published from a single administrative surface: the packages, the gallery, and the taxonomy that orders them.

A pilgrimage operator’s home page opening over a night-time photograph of the Haram, with Explore packages and Contact us offered as two buttons.
The site opens on the journey itself, and offers two ways in — read the packages, or talk to somebody.
01Sector
Pilgrimage operators — Hajj, Umrah and Ramazan
02Surfaces
Public site and operator console
03Console
Eight modules, dashboard to access
04Path
Four steps, ending at an enquiry
Act 01/ 031 capture

The pilgrim’s path

The journey, before the price.

The site answers how this actually works before it asks for anything. Four steps run down one column, a sentence each: an enquiry by call, WhatsApp or the office; a package chosen against the pilgrim’s own dates and budget; a booking confirmed on minimal documentation, with the pricing shown before the commitment rather than after it; then travel, with a guide on the ground and support for the length of the journey. The first step is deliberately not digital — a pilgrim who would rather walk into an office is still on the path.

A four-step process section headed Your Journey to Holiness, listing enquiry, package selection, booking, and travel and guidance down a vertical timeline.
Four steps, one sentence each, in the order they actually happen.
  1. 01.01

    Enquiry is not digital-only

    Call, WhatsApp and the physical office are all named as ways in, on the first step.

  2. 01.02

    Priced before the commitment

    The booking step states that pricing is shown first and the documentation kept minimal.

  3. 01.03

    The journey does not end at departure

    Guides on the ground and support for the duration are the fourth step, not an add-on.

Act 02/ 032 captures

Departures and tiers

The calendar the decision is made in.

A pilgrim picks the month first — Rabi-ul-Awwal, Rajab or Shaban — then one of three batches inside it, each running the same fourteen days, so the choice is about timing rather than duration. The selection resolves into one confirmation line carrying the departure date, the estimated return and the length. Only then do the tiers appear, and they lead with the two facts a pilgrim actually feels: how far the hotel is from the Haram, and how many share a room.

A departure selector offering Rabi-ul-Awwal, Rajab and Shaban as three month buttons, three dated batches beneath them, and a summary line resolving departure, return and duration.
The month first, then a batch inside it — and the choice resolves into one line.
Three package cards — Standard, Deluxe and Super Deluxe — each leading with distance from Makkah and Madinah and its room occupancy, above a struck-through price and the saving.
Metres from the Haram and how many share a room, read before the figure.
  1. 02.01

    Three months, three batches each

    Rabi-ul-Awwal, Rajab and Shaban, each holding three dated departure windows.

  2. 02.02

    Fourteen days, every batch

    The length is fixed, so the decision is about when to go rather than how long to stay.

  3. 02.03

    Distance leads the card

    Metres from both Harams and the room occupancy sit above the price, which carries its own strike-through and saving.

Act 03/ 033 captures

The operator console

Everything the site shows is published from here.

The console opens on volume rather than on a menu: packages and active services counted live, beside the asset library and the taxonomy filters that sort it, with revenue and booking volume plotted together on a weekly or monthly axis. Eight modules sit behind that — dashboard, analytics, taxonomy, packages, media, inquiries, users and access. The gallery and the categories that order it are their own modules rather than page content, so a moment can be retitled, recategorised, relaid or switched off without anybody touching a page.

An operator dashboard counting total packages, active services, asset library and taxonomy filters across the top, with a financial trajectory chart and a workflow terminal beneath.
Four counts, a revenue and booking curve, and the four places staff go next.
An analytics screen with a category portfolio donut broken down by Hajj, Rabi-ul-Awwal, Rajab, Ramadan, Shaban and Ziyarath, beside a bar chart of top performing locations.
The catalogue read as a distribution: which journeys, and where they go.
A media library table listing gallery moments, each row carrying a preview, a location and date, a category and grid layout, and a visibility toggle.
Each gallery moment carries its own category, layout and visibility switch.
  1. 03.01

    Counted live, not entered

    Packages, active services, assets and taxonomy filters are read off the catalogue itself.

  2. 03.02

    Revenue against volume

    Both are plotted on one axis, switchable between a weekly and a monthly view.

  3. 03.03

    The gallery is a module

    Moments carry a category, a grid layout and a visibility toggle, rather than living inside a page.

The last word

This shows how Famysys builds for an operator whose season is sold in batches: a public path that explains the journey before it prices it, departures chosen in the calendar the decision is actually made in, and a console where the packages, the gallery and the filters that order them are published from one place. If your customers take a journey, we start from the path they take it on rather than from a template.

Built in

  • Public booking path
  • Departure batches
  • Package tiers
  • Operator console
  • Media & taxonomy

All projects

Let's build what's next

Technology alone doesn't transform businesses.The right partnership does.

Modernizing systems, building a new product, or exploring AI-driven transformation — Famysys helps you move forward with confidence.

Schedule Executive SessionEmail Us Directly
  • SOC2 Type II Compliant
  • Strict Commercial NDA
  • Zero Lock-In Guarantee

Famysys

We Engineer Clarity

Scan to Connect

Instant digital business card & WhatsApp link