Skip to content

Custom software development · Medina

Hospitality Software for Medina Operators

We build hospitality software for businesses operating in and around Medina: reservation and booking platforms, fleet and transport systems, occupancy dashboards and permit records, alongside backend systems for its date-processing and manufacturing trade. We work remotely from Ahmedabad, India, on Saudi hours. There is no QalbIT office in Medina, and no QalbIT entity anywhere in the Kingdom.

The obvious story about Medina is the size of the crowd passing through it every year. The software story is narrower and more useful: the booking, transport, occupancy and permit systems behind the businesses that serve that flow, and the two legal questions any vendor outside the Kingdom has to answer before you hire one.

  • 2018

    Building software since

  • 5.0

    Clutch rating

  • 50+

    Clients served

  • 4.9

    Google rating, 18 reviews

Get your free estimate

Three quick questions: scope, approach and a price range back within 48 hours. No sales call required first.

What do you need built?
When do you want to start?
Where should we send the estimate?

Answer all three questions above, then send.

NDA-friendly · IP yours from day one

Definition


What a remote software partner actually does for a Medina company

QalbIT builds operational software, booking and reservation platforms, fleet and occupancy systems, CRM and backends, for businesses operating around Medina, as a remote engineering partner rather than a Kingdom-based firm. We build the systems that move people, vehicles and paperwork; we do not build or advise on religious content, ritual guidance or anything doctrinal, and that boundary does not move. Two national rules shape every build here, as they do anywhere in the Kingdom: ZATCA Phase 2 e-invoicing, which Wave 25 extends to almost every VAT-registered business by 1 February 2027, and PDPL Article 29 on personal data sent outside Saudi Arabia. Our team works from Ahmedabad, India, on Medina working hours.

Medina’s economy looks unusual on paper: a resident population running ordinary businesses, and a visitor population that can multiply the working city several times over for a matter of weeks, then recede almost as fast. Software sized for one crowd breaks under the other.

The shape of that swing is Medina’s own. Mecca’s busiest days are fixed by the Hajj itself; Medina sees waves instead. Hajj flights start landing at Prince Mohammad bin Abdulaziz International Airport weeks before the Hajj, groups come back through the city after it, and Ramadan brings a wave of its own. The Haramain High Speed Railway carries part of that flow to and from Mecca and Jeddah, so a transfer roster has to cover the airport, the rail station and the hotels in one schedule.

A firm registered inside the Kingdom can staff a reception desk, walk a hotel floor before a peak, or sit in the transport office when a roster needs revising at short notice. We cannot do any of that. What we can do is build the reservation, occupancy, fleet and permit systems that stand behind that desk, that floor and that roster, and say plainly where a remote build stops being the right tool.

None of that touches what a visit to Medina means to the person making it. That is not a subject we build products around and not one we offer an opinion on: our systems track a booking reference, a vehicle, a room and a permit number, never a rite.

We are that second kind of vendor, and we would rather you read it here than discover it in month two.

At a glance

  • Core focus

    Booking, fleet, occupancy and permit systems, CRM and APIs

  • Engagements

    First builds · legacy rebuilds · integrations · seasonal-scale systems

  • Delivery

    Remote from India on Medina hours, Sunday–Thursday overlap

  • Saudi position

    No local entity. Processor outside the Kingdom under PDPL

Definition


Local Medina operator vs global consultancy vs remote engineering partner

The same three options any Saudi buyer weighs, priced and staffed differently around a season rather than a steady month.

  • Local Medina operator or systems house

    Registered in the Kingdom, close to the booking desk, the transport yard or the packing shed, Arabic-first. Best when the work touches a floor team daily, especially through a peak week.

  • Global consultancy

    A large firm with staff in the Kingdom, usually hired for a hotel group’s shared platform or a multi-company transformation that a board has sponsored.

  • Remote engineering partner

    A small senior team in Ahmedabad building one defined system on Medina hours. It has no entity in the Kingdom, so moving personal data to it needs a contract. It suits a buyer who can already describe the system.

We are the third. Where a Medina operator is genuinely the better fit, for example staffing a reception desk through a peak week, we will say so before you sign anything with us.

Fit


When a remote partner is the right call for a Medina business

A vendor selling into a seasonal city usually argues only the side that gets the contract signed. This page gives you both.

  • Hire a remote partner when

    • You can describe the system: a reservation platform, a fleet and dispatch tool, an occupancy dashboard, a permit register.
    • Your managers make the daily calls themselves, so the two-and-a-half hour gap to India rarely matters.
    • The job is one system or one rebuild, a booking engine or a harvest ledger, not a programme with no end date.
    • You want to own the code and decide the roadmap yourself after launch.
    • Guest, passenger and driver data can travel under PDPL’s standard transfer safeguards.
  • Hire locally instead when

    • The system would hold data PDPL treats as sensitive, such as health, biometric or genetic data or criminal records. That belongs with a provider inside the Kingdom.
    • The buyer is a government body, municipality or endowment tendering on Etimad, with in-Kingdom delivery as a condition.
    • Your front-desk and dispatch staff need the whole project run in Arabic, not only the screens.
    • You need people physically present on a hotel floor or in a transport yard during a seasonal cutover.
    • Your own procurement rules ask for a contractor with a Saudi commercial registration.

Projects on the second list get a no from us. A remote build where a Medina-based operator is the honest answer wastes a season, and with sensitive data it creates a legal problem for both sides.

Next step


Not sure whether to hire locally?

Tell us what the system needs to do and what data it will hold, guest records included. We will say plainly which side of that line you are on, including when the honest answer is an operator based in Medina.

Comparison


Remote partner vs local operator vs global consultancy

There are no rates in this table. Each row is a real difference between the three options, including the rows where we come off worse. Send us your scope and the data the system will hold, and we will fill this in for your case.

Remote engineering partner compared with a local Medina operator and a global consultancy, row by row
Local Medina operatorGlobal consultancyQalbIT (remote partner)
Physical Medina officeYesUsuallyNo
Arabic-first deliveryYesVariesNo · English delivery, Arabic in the product
PDPL roleController or processor, in-KingdomProcessor, usually in-KingdomProcessor outside the Kingdom · safeguards required
Data residencyIn-Kingdom by defaultIn-Kingdom availableIn-Kingdom hosting, remote engineering
ZATCA Fatoora integrationCommonCommonYes
Working-week overlapFullFullSunday–Thursday, 2.5-hour offset from India
Peak-week floor presenceAvailableSometimesNot available · architecture is built peak-ready in advance instead
Source code ownershipVariesVariesYours, full repository
Team size on your accountVariesLarge, layeredSmall and senior, founder-accessible
  • 01

    The rows we lose are still on the table.

    At least two of those rows argue for hiring someone else. We would rather a Medina buyer read that here than discover it a month before a peak week.

  • 02

    A seasonal spike is a specification question, not a location question.

    Whether we have built for your exact peak before matters less than whether the peak is quantified. We ask for last year’s numbers at the scoping call.

  • 03

    The time offset is smaller than it looks.

    Medina is on UTC+3 and Ahmedabad on UTC+5:30, so a Medina morning falls in our afternoon, and four of the five Sunday–Thursday days overlap live.

  • 04

    Etimad and endowment eligibility is binary.

    When the buyer is a government body, a municipality or an endowment buying through Etimad, and the tender asks for an in-Kingdom registration, the vendor is chosen before quality is weighed. Ask us at the start.

What we build


Custom software we build for Medina companies

Systems that talk to each other, so a reservation, a vehicle and an invoice do not have to be re-entered three times by three different people.

  • Booking

    Reservation and booking platforms

    Seat, room and slot allocation, group bookings and cancellation rules for licensed tour, transport and accommodation operators, replacing a phone-and-spreadsheet booking desk.

  • Fleet

    Transport and fleet management systems

    Vehicle rosters, driver assignment, trip logging and permit status for operators moving visitors between sites, built to hold up when the schedule changes an hour before departure.

  • Occupancy

    Hotel and accommodation occupancy systems

    Room inventory, rate and channel management and occupancy forecasting for properties that run near empty for months and near capacity for weeks. Group allotments held for agents carry release dates, so unsold rooms go back on sale in time.

  • Permits

    Vendor and permit management

    Ministry of Tourism licence records for hotels and serviced apartments, vehicle and driver permits for transport operators, and renewal reminders that fire before a licence lapses in the middle of a season.

  • Trade

    Date and agriculture trade platforms

    Harvest intake by farm and variety, Ajwa, Safawi and Anbara among them, grading by size and quality, batch tracking from field crate to packed carton, and the export paperwork a buyer abroad asks for, replacing a paper ledger only one person can read.

  • Backend

    Custom backends and APIs

    Laravel, Node.js and NestJS services that join the booking desk, the transport roster and the packing shed to one set of records, with queues and scheduled jobs for the nightly syncs.

Cost


How much does custom software development cost in Medina?

Custom software development cost in Medina is driven by scope, integration count, seasonal-scaling requirements and compliance depth rather than by headcount or an hourly rate. A ZATCA-integrated booking or invoicing layer, a fleet or property-management integration, and a peak-ready architecture are each a separate cost driver. We scope first, then give a fixed estimate for phase one.

We publish no price range for Medina work, and a firm that does deserves a careful second look.

A single-property booking system and a multi-site occupancy platform with a fleet module and Fatoora clearance are not remotely the same project, so a range wide enough for both is no help to you.

Instead you get a scoping call, a map of how bookings, vehicles or harvest batches move today, and a fixed estimate for phase one before you commit past discovery. The drivers below are what move that figure; use them to test any quote, ours included.

Try the software development cost calculator

What moves the number

  • Scope of phase one

    The biggest factor. A first phase usually joins two modules that already share data, booking with fleet or harvest intake with grading, rather than spreading thinly across five.

  • Integration count and quality

    A current REST API with OAuth is a small job. An older property-management system or a channel manager that cannot push events needs a middleware and reconciliation layer between it and your records.

  • ZATCA integration depth

    Reporting a guest’s simplified invoice is a lighter job than clearing a wholesaler’s standard invoice, which needs CSID onboarding, XAdES signing, hash chaining and a path for rejected invoices.

  • Seasonal load and scaling design

    A system that only has to hold steady traffic is a different build from one that has to absorb a demand spike several times its normal size and then scale back down without breaking.

  • Data protection architecture

    Where guest, passenger and driver records are stored, which of them cross the border, and what is tokenised before they do. Cheap to decide at the start and costly to change later.

  • Arabic in the product

    Bilingual interface, right-to-left layout, Arabic-correct booking confirmations and invoice output. Real engineering, frequently underestimated.

How we work with Medina teams


A delivery process built around a 2.5-hour offset

The offset is small. What is not small is the gap between a quiet month and a peak week, and we plan the whole schedule around that gap rather than around the clock difference alone.

  1. Discovery and process mapping

    Walk through how a booking, a vehicle assignment, a room block or a harvest delivery moves through your business today, who touches it, and where it breaks under load. Pick the system that hurts most for phase one, and set out the data-protection profile for guest, passenger and driver records.

    Your process on one page, the systems in priority order, a phase-one estimate and a written data-transfer position.

    1–2 weeks

  2. Architecture and data design

    Design the data model, screens and integration contracts, including any property-management, fleet or payment interfaces. Decide what is hosted in-Kingdom and what never leaves, and size the architecture for peak load rather than an average day.

    A signed-off data model and screens, the integration plan, and where each record will be hosted.

    2–3 weeks

  3. Build phase one

    Weekly increments, each demoed on your own bookings, vehicles, rooms or harvest batches rather than sample data, inside your Sunday–Thursday week.

    Modules tested against real days at the front desk, the transport yard and the packing shed.

    6–14 weeks, scope-dependent

  4. Migration, training and parallel run

    Migrate masters and open bookings, train front-desk and dispatch staff, and run the new system alongside the old one until the numbers reconcile, timed to land before the next peak window rather than during it.

    Confident go-live with reconciled data and trained users, ahead of the season that would have made it risky.

    2–4 weeks

  5. Stabilise, extend, roll out next

    Tune for the next arrival wave, add the reports and automations people ask for, and start the next system on the roadmap once the first has settled.

    Software that keeps pace with the business instead of a single hand-over.

    Ongoing, month-to-month

Medina works Sunday to Thursday on UTC+3, and our team in Ahmedabad is on UTC+5:30: two and a half hours apart, with four of the five working days overlapping live. Thursday afternoon and the weekend run on written updates, and go-live dates are set around the arrival waves and the harvest, not a standard release calendar.

Book a scoping call

Where we fit best


Medina projects we take on

Four Medina engagements that a remote team delivers well, from the booking desk to the packing shed. The ones we decline are in the fit section above.

  • First build

    Replacing a phone-and-spreadsheet booking desk

    Transport, accommodation and tour operators running reservations, vehicle rosters or room blocks on spreadsheets and phone calls who need a real system built properly the first time. For transport, accommodation and visitor-services operators.

  • Modernisation

    Rebuilding software you have outgrown

    An old desktop hotel system, or a packing shed’s spreadsheet-and-paper ledger, rebuilt as a modern web application without losing years of booking, guest or harvest history, and without retraining everyone overnight. For hotels and date packers on unsupported systems.

  • Compliance

    ZATCA and PDPL retrofit

    Bringing a hotel’s booking engine or a packer’s wholesale invoicing to Fatoora clearance, and moving guest, passenger and driver data to where it belongs. A Wave 25 notification usually starts the conversation. For Medina businesses with a Wave 25 notification.

  • Seasonal scale

    Systems built to peak hard and stand down after

    Reservation, occupancy and fleet platforms engineered for a handful of high-volume weeks each year, sized to absorb the spike without a rebuild every cycle. For hotels and transport operators riding the arrival waves.

Industries


Sectors we build for in Medina

Medina runs on two calendars at once, the visitor flow and the palm harvest, and these four sectors sit across them.

  • Visitor transport and logistics

    Vehicle rosters, driver assignment, permit compliance and trip records across a demand curve that can multiply several times over in a matter of weeks.

  • Hospitality and accommodation

    Occupancy, rate and channel management for properties running from a quiet month to a fully booked one without warning, and back again.

  • Date and agriculture processing

    Harvest intake, batch grading, packing and export documentation for a farming and processing trade that predates the visitor economy. The harvest follows the solar year while Ramadan and Hajj follow the lunar one, so the two busy seasons drift against each other year by year.

  • Retail and small manufacturing

    Multi-branch operations, simplified-invoice reporting to ZATCA, and production tracking for the workshops and small manufacturers supplying the wider region.

Next step


Your process is the reason the off-the-shelf tool doesn’t fit.

That is usually the actual case for a custom build. Describe the process, whether it runs through a booking desk, a transport yard or a packing line, and we will tell you honestly whether it justifies the project.

Saudi compliance


Building software for Medina: ZATCA, PDPL and data residency

ZATCA and PDPL apply in Medina as they do anywhere in the Kingdom. What differs is which system raises them first: a reservation platform holding guests’ names and passport numbers, a fleet system carrying driver records, or a date packer invoicing wholesalers.

  1. ZATCA e-invoicing (Fatoora)

    Phase 2 means connecting directly to ZATCA’s Fatoora platform. An invoice to a business or government buyer, a wholesaler taking a pallet of dates for instance, is cleared before it is sent; a simplified invoice to a hotel guest is reported to ZATCA after it is issued. The invoice itself is UBL 2.1 XML with a UUID, a cryptographic stamp and a QR code. Wave 25, which ZATCA announced on 24 July 2026, brings in every taxpayer whose VAT-subject revenue went above SAR 187,500 in any year from 2022 to 2025, and sets 1 February 2027 as the integration date. That is half of Wave 24’s SAR 375,000 threshold, low enough that a small guesthouse or a family-run packing business is likely inside it. For an operator in Medina this usually pulls in both the invoicing system and any booking or reservation platform that issues a tax invoice on confirmation, not just one of them. Integrations tend to break in three places: CSID onboarding, XAdES signature validity, and the previous-invoice-hash chain, which one rejected clearance can break for every invoice after it. A booking engine that invoices in bursts on a busy arrival day meets that last one first. Sources: ZATCA Wave 25 e-invoicing announcement, zatca.gov.sa · Zakat, Tax and Customs Authority.

    Phase 2 · Wave 25

  2. PDPL and cross-border data

    Saudi Arabia’s Personal Data Protection Law, Royal Decree M/19 as amended by M/148, has applied in full since 14 September 2024. Its reach is extraterritorial, so our team in Ahmedabad is in scope the moment it handles personal data about people in the Kingdom. For a Medina operator this most often means guest, passenger and driver records held inside a booking, fleet or property-management system. Article 29 lets that data leave the Kingdom only under SDAIA’s approved safeguards, Saudi Standard Contractual Clauses among them, plus a risk assessment where those apply. A group booking that stores passport scans is usually the first record worth designing around. You stay the controller and we act as processor, so the transfer needs a written basis and a contract before the first guest record moves. Sources: Regulation on Personal Data Transfer Outside the Kingdom, v2.0, August 2024, dgp.sdaia.gov.sa · Saudi Data & AI Authority.

    Royal Decree M/19

  3. Vision 2030 context

    By 2024 the Kingdom’s ICT market had passed SAR 180 billion, inside a digital economy of roughly SAR 495 billion, around 15% of GDP. In the ITU’s 2025 ICT Development Index, Saudi Arabia ranked first in the world. Sources: Ministry of Communications and Information Technology · Communications, Space and Technology Commission.

Compliant invoices and data handling are designed into the system from the first sprint, not added as a module later. If a Wave 25 notification set your deadline, the plan runs backwards from 1 February 2027.

Working with us


Hiring a vendor outside the Kingdom: the honest version

Four things change when the vendor sits outside the Kingdom. A Medina hotel or transport operator should hear them before the estimate, not after.

  • Data transfer

    You remain the controller. Before any guest, passenger or driver record reaches us, Article 29 needs a lawful basis and documented safeguards, written into the contract once, ahead of the build.

  • Sensitive data

    Tighter rules cover health, biometric, genetic and criminal-record data. If a booking or medical-transport system you run touches any of it, plan for in-Kingdom processing regardless of who writes the code.

  • Government and endowment procurement

    An Etimad tender, a municipal contract or an endowment’s procurement may require the contracting party to hold a Saudi commercial registration. QalbIT holds none.

  • Physical presence

    Nobody from our team will be on a hotel floor, in a transport yard or at a permit counter during a peak week. Rollouts and floor training around a seasonal cutover need local hands, and we say so before you sign.

  • Everything else

    Payment gateways, e-invoicing service providers, hotel and property-management systems, channel managers, fleet and dispatch platforms, banking APIs, BI tools.

    Integrations

None of this rules out a remote partner. It means the contract gets settled in a quiet month, not in the week the arrival flights start.

Tech stack


Technology we use for Medina builds

Booking, fleet and occupancy systems have to survive a demand spike measured in multiples, not percentages. We choose proven technology that holds under that load and that your future team, internal or external, can still maintain afterwards.

  • Backend and business logic

    • Laravel (PHP 8.x) for booking, licence and harvest records that need a clean audit trail.
    • NestJS (TypeScript) for booking, fleet and dispatch flows with heavy real-time updates.
    • Queues and schedulers for licence-renewal reminders, allotment release dates and nightly occupancy reports.
  • Frontend and usability

    • Next.js and React for fast, keyboard-first data entry at a booking or front desk.
    • Arabic and English screens with proper right-to-left layout, from the front desk to the packing-shed tablet.
    • Role-based dashboards for owners, dispatchers and front-desk teams.
  • Data and integrations

    • PostgreSQL and MySQL with constraints that stop a room or a seat being sold twice.
    • ZATCA Fatoora clearance for wholesale invoices and reporting for guest invoices.
    • Integrations with property-management systems, channel managers, fleet platforms and payment gateways.
  • Security and residency

    • Access scoped to each property, depot and packing site, with a full audit log.
    • Hosting inside the Kingdom for guest and passport records where residency is needed.
    • Automated backups, staged releases, and monitoring with alerts tuned for an arrival-wave load.

Already running a property-management system, a fleet spreadsheet or a paper permit register? We extend and integrate before we replace, and the migration route is planned from the first week.

Outcomes


What the project should actually change

These are not forecasts. Each row is a change the build should cause at a front desk, a transport yard or a packing shed, with the way you would check it.

What the project should actually change: what changes and how you would measure it
What changesHow you’d measure it
One booking and occupancy record across every channelRooms sold against rooms actually free, checked at night audit
VAT and invoice records come straight out of the booking and sales systemsStaff hours spent assembling each VAT return
Wholesale invoices clear ZATCA on the first attemptClearance rejections and hash-chain breaks per month
Vehicle and permit records stay current through a peakShare of trips and permits with a complete audit trail
Every packed carton traces back to its farm intake and gradeTime to answer a buyer’s question about one batch
Arabic confirmations and invoices go out without hand-correctionDocuments fixed by hand before sending
Owners see tonight’s occupancy and this week’s packed stock without phoning anyoneMinutes from a question to a reliable answer
  • A note on sourcing

    A note on sourcing

    You will not find a software failure rate quoted here. The often-repeated 55–75% attributed to Gartner cannot be traced to a primary source, and repeating it would make a point without proving one. Numbers on this page carry their source and date.

Why QalbIT


Why work with us

  1. Eight years building operational software

    120+ engagements delivered across web, mobile and platform work, with 50+ clients. Clutch 5.0, Google 4.9, Upwork Top Rated. Today we deliver into the GCC white-label, for a regional agency. A Medina operator hiring us directly gets that same engineering practice with our name on the contract.

  2. We say what we are

    No Medina office, no local entity, no implied presence. The compliance section above is there because losing a deal at the scoping call is better than losing it at the audit.

  3. You own the code

    The source code is documented and lives in your repository. There is no licence fee, no per-seat charge, and nothing stopping you from moving to another team later.

  4. Senior team, founder-led

    You deal directly with the senior engineers building the system, not with an account manager passing messages to people you never meet.

  5. We’ll tell you to hire locally

    If a Medina operator or systems house would serve you better, you hear it on the first call. That loses us the work and spares you a wasted peak.

The biggest difference has been their flexibility and solution-oriented approach. Rather than pointing out problems, they focus on solving them. I genuinely cannot recall hearing them say, ‘This cannot be done.’ No matter how many changes or updates we send their way, even after long working days, they consistently respond positively and find a way forward. What stands out most is that our relationship has evolved beyond a traditional client-supplier setup and feels more like a partnership. QalbIT takes genuine responsibility for the platform’s functionality, and when bugs are identified, they are addressed without hesitation.
Gabriell Summerland, CEO, Bluecircle

FAQs · Custom software development in Medina


Frequently asked questions from Medina teams

The questions hotel managers, transport operators and date-trade owners ask when they weigh a remote partner against a Medina operator.

Talk to the team
No. QalbIT has no office or legal entity anywhere in Saudi Arabia. Delivery runs remotely from Ahmedabad, India, on Medina working hours. We say this plainly because implying a local presence creates a problem for both of us the first time it is checked.
Yes, with the data-protection position handled properly. Under PDPL you are the controller and we are the processor. Transferring personal data outside the Kingdom is permitted under Article 29 with approved safeguards, including Saudi Standard Contractual Clauses. That is contract work done once, before the build starts.
Yes. Phase 2 requires direct integration with the Fatoora platform: UBL 2.1 XML, UUID, cryptographic stamp and QR code, with standard invoices cleared before sending and simplified invoices reported afterwards.
Wave 25 covers VAT-subject revenue above SAR 187,500 in any of 2022 to 2025, with integration required by 1 February 2027. Treat the notification you received from ZATCA as authoritative for your own date, and confirm your status directly rather than relying on any article, this one included.
Medina is UTC+3 and we are UTC+5:30: a two and a half hour offset. Your Sunday to Thursday week overlaps ours on four days out of five. Demos and decision calls are scheduled in your hours; Thursday afternoon through Saturday runs on written updates.
Your organisation, in full, in your own repository, once project payments are complete. No licence, no per-seat fee, no restriction on hiring another team afterwards.
Booking and reservation platforms, fleet and dispatch tools, occupancy tracking and permit systems: the operational software behind a visitor-services or transport business. Group bookings, cancellation rules and driver assignment are the kind of detail we design around, not an afterthought. We do not build or advise on religious content or ritual guidance, and we say so plainly if asked.
Three kinds: systems houses registered in the Kingdom, global consultancies with Saudi staff, and remote engineering partners such as QalbIT. We build reservation and booking systems for Medina hotels and serviced apartments from Ahmedabad, on Saudi hours, with no office in the city. Which kind suits you depends on how much of the work needs people on the hotel floor. Whoever you shortlist, ask to see the room-inventory rule that stops one room being sold twice when the booking desk and an online channel confirm it in the same minute.
Vehicle count matters less than four other things: how seats and trips are allocated, whether the system issues ZATCA invoices, which payment gateway and fleet tools it joins, and how hard it has to peak. We put no public price on it. You get a scope and a phase-one estimate within 24–48 hours of a scoping call. A seat-booking screen over one roster is a far smaller job than agent allocations, Fatoora clearance and a driver app together, and the cost section above lists each driver so you can test any quote, ours included.
We do, as a remote partner rather than a Madinah firm. The forecast starts from your own records: past occupancy by date, the group allotments still held and their release dates, and the arrival waves around Hajj and Ramadan. It shows the front office which nights are filling early and which allotments to hand back before they lapse. Because Hajj and Ramadan follow the lunar calendar, the model reads Hijri dates as well as Gregorian ones. It is a planning tool, and we quote no accuracy figure before we have seen your data.
Yes, for the software: vehicle and driver rosters, trip assignment, permit expiry dates and a dispatch board that follows each group from arrival to departure. A remote team cannot stand in your yard during the cutover or train drivers face to face, so that part needs your own supervisors or a local partner, and we plan it with them. When a flight lands late or a train is delayed, the board moves the pickup and the driver sees the change on their phone, instead of the dispatcher ringing round.
Yes. We build CRM for Madinah hotels, serviced apartments and transport operators around the people who actually send you business: travel agents and group organisers, their contracts and allotments, repeat guests, and the follow-up after each season. It runs on the same records as the booking system, so one group’s history sits in one place. Guest and agent contacts are personal data under PDPL, so where the CRM is hosted and what reaches our team is settled in the contract before the build starts.
That is the case we design for, not the exception. Vehicle rosters, driver assignment and trip logging are built to absorb a late change without the whole day’s schedule breaking, because in transport and visitor-services operations that call comes in more often than a calm rollout plan assumes.
Yes. Medina’s economy is not only visitor-services and transport: we also build backend systems, workflow tools and CRM for its date-trade and manufacturing businesses. The starting questions are the same either way: what spreadsheet or phone call is the system replacing, and what does the first release need to do on day one.
We size the architecture for your highest week, not your average one. A booking or occupancy system that is over-built for its quiet months costs more to run and maintain all year for capacity you use a handful of times, so the peak numbers get established at the discovery stage, before anything is estimated.
Yes. Booking confirmations, permit documents and reporting can be fully bilingual with correct right-to-left layout and Arabic sorting. Project delivery itself, calls, documentation, written updates, runs in English. If your stakeholder group needs Arabic-language delivery throughout, a local systems house is the better fit and we will say so.
Our current GCC delivery is a white-label engagement, so we cannot name the end client in that sector. We can share detailed case studies from comparable booking and scheduling builds in Europe and India, and we would rather tell you that than manufacture a Medina reference.

Next step


Let’s scope the first system.

Tell us how a booking, a vehicle or a shipment of dates moves through your business today. We will map the process, name the system that earns its place first, and give you an honest, phased estimate. If a Medina operator is the better answer, we will say that instead. Typically a reply within 24–48 hours, with questions rather than a brochure.